This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Custom Device Driver
- To: "eCos discussion" <ecos-discuss at sources dot redhat dot com>
- Subject: [ECOS] Custom Device Driver
- From: "Andy Simpkins" <Andy dot Simpkins at TardisMobile dot com>
- Date: Tue, 27 Mar 2001 16:16:51 +0100
- Reply-To: Andy dot Simpkins at TardisMobile dot com
I am integrating a GPS receiver into eCos, the problem is that the IP for
this is in the form of an ARM ADS library. To overcome this problem I
simply call the appropriate routine in memory when one of the relevant
interrupts are received. The calling function takes the form of an eCos
device driver. Great everything works, eCos and the GPS engine.
The GPS engine currently flashes LEDs when a GPS event occurs. What I am
now trying to do is get events generated by the GPS engine to be recognised
by eCos. These events happen for example when there is position information
available.
1. How would one go about incorporating this into a device driver?
2. How should I then pass this information out to interested threads?
3. I am guessing that the thread would treat this in much the same way as a
serial device but the data will be a single event code (probably one byte)?
Any ideas of how to approach this would be most helpful.
Andy