This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Custom Device Driver
- To: Andy dot Simpkins at TardisMobile dot com
- Subject: Re: [ECOS] Custom Device Driver
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Tue, 27 Mar 2001 16:44:10 +0100
- Cc: eCos discussion <ecos-discuss at sources dot redhat dot com>
- Organization: Red Hat UK Ltd.
- References: <NEBBKCPHAKKLBOKILBONMEHMCBAA.Andy.Simpkins@TardisMobile.com>
Andy Simpkins wrote:
>
> 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?
Assuming it can deliver interrupts, write an ISR that acks the interrupt,
and returns a code instructing eCos to call a DSR.
> 2. How should I then pass this information out to interested threads?
Create a message box, and in the DSR, put the information in that. The
threads can then read out of it.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine