This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Driver Development approach
- To: "Trenton D. Adams" <tadams at extremeeng dot com>
- Subject: Re: [ECOS] Driver Development approach
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Tue, 12 Jun 2001 19:08:50 +0100
- Cc: 'eCos Discussion' <ecos-discuss at sourceware dot cygnus dot com>
- Organization: Red Hat UK Ltd.
- References: <000e01c0f2c2$77c59ab0$090110ac@BURN>
"Trenton D. Adams" wrote:
>
> I've been reading up on driver development. I want some advice on my
> approach.
>
> I was thinking that I could make a driver that simply prints to stdout
> when cyg_io_write() or cyg_io_read() are called on it. I could make a
> test harness program, and run it through GDB. Then when connecting
> through GDB, I would know that it's working because the messages would
> be output to me.
>
> Will this even work? If so, is this a good approach to learn how the
> drivers interact with the system?
I think it could work, while the cyg_io stuff isn't particularly intended
to be re-entrant, I think it is anyway.
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
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/