From: Oleg Uzenkov <o.uzenkov@unicore.co.ua>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] STM32 Standard Peripheral Library in eCos
Date: Wed, 18 Jun 2014 08:18:00 -0000 [thread overview]
Message-ID: <53A14B41.3080106@unicore.co.ua> (raw)
Dear All,
I have a question regarding STM32 Standard Peripheral Library and using
this library with eCos.
Is there any way (a HAL wrapper or something) to interface drivers from
this library in application with eCos?
Do you reckon it is feasible to make an eCos port for a driver from this
library? I started doing so for SDIO but got overwhelmed with how much
staff needs rewriting in the eCos way.
There are some drivers like SDIO to interface SD card that are not
implemented in eCos yet, and it would great to have such support.
I would be grateful for any information on this.
Oleg
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2014-06-18 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 8:18 Oleg Uzenkov [this message]
2014-06-18 9:16 ` Jerzy Dyrda
2014-06-18 9:39 ` Oleg Uzenkov
2014-06-18 10:08 ` Jerzy Dyrda
2014-06-18 12:40 ` Oleg Uzenkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53A14B41.3080106@unicore.co.ua \
--to=o.uzenkov@unicore.co.ua \
--cc=ecos-discuss@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).