From: "Mike Sweeney" <msweeney77@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Device driver implementation questions
Date: Fri, 15 Jun 2007 01:21:00 -0000 [thread overview]
Message-ID: <70d4f620706141241x6eefc498w18d9590e5dc2ef93@mail.gmail.com> (raw)
I am finding the way device drivers are implemented in eCos to be
slightly confusing so was looking for some help. The main source of my
confusion is the need for some sort of interface under the io package
and then another part of the driver in the devs package. I have looked
at examples like the serial driver and understand how it works in that
context, but am having trouble seeing the bigger picture. Should
drivers for all types of devices follow this split implementation
design? Furthermore, can someone provide me an analogy between the
eCos driver model and Linux, for example? I don't see this two layer
method in Linux so am hoping someone can clarify this.
Thanks.
--
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:[~2007-06-14 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 1:21 Mike Sweeney [this message]
2007-06-15 8:43 ` [ECOS] " Grant Edwards
2007-06-15 9:43 ` Mike Sweeney
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=70d4f620706141241x6eefc498w18d9590e5dc2ef93@mail.gmail.com \
--to=msweeney77@gmail.com \
--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).