This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
device driver interface
- From: "Koeller, T." <Thomas dot Koeller at baslerweb dot com>
- To: "ecos-discuss (E-Mail)" <ecos-discuss at sources dot redhat dot com>
- Date: Fri, 12 Apr 2002 11:35:36 +0200
- Subject: [ECOS] device driver interface
Hi all,
what would be the recommended way of coding a device driver that does
not fit the rather rudimentary and rigid read/write/set_config/get_config
model
as described by the documentation? If, for example, I wanted asynchronous
notifications upon certain driver-detected events, such as data arriving, is
there a standard way of coding this, or do I have to use sychronization
primitives directly, extending the I/O API in a nonstandard way? Is there
something similar to an ioctl API, allowing for more generalized I/O
operations
that require additional parameters beyond just a buffer and a byte count?
Can I attach context information to I/O requests that can be retrieved
after the operation is finished?
Any advice greatly appreciated!
Thomas
-----------------------------------------------
Thomas Koeller, Software Development
Basler Vision Technologies
An der Strusbek 60-62
22926 Ahrensburg
Germany
Tel +49 (4102) 463-390
Fax +49 (4102) 463-46390
mailto:Thomas.Koeller@baslerweb.com
http://www.baslerweb.com
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss