This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: SPI/SSI driver for EDB7XXX
- To: "Trenton D. Adams" <tadams at theone dot dnsalias dot com>
- Subject: Re: [ECOS] SPI/SSI driver for EDB7XXX
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Wed, 12 Sep 2001 21:55:34 +0100
- Cc: eCos Discussion <ecos-discuss at sourceware dot cygnus dot com>
- Organization: Red Hat UK Ltd.
- References: <000a01c13bbb$2c8b14c0$090110ac@TRENT>
"Trenton D. Adams" wrote:
>
> I'm going to be writing a driver for the SSI2 interface on my EDB7111-2
> board. Would it be safe to assume that the layout for the RS232 serial
> driver would be a good start? If so, does anyone know off hand if all
> the EBD7XXX boards have the same SSI2 interface? I think most of those
> boards have the same CPUs right - EP7211?
Or EP7212, EP7209 and hopefully EP7312 if anyone ever manages to contribute
it!
> If so, then they must all
> have the same SSI interface because I think it's internal to the CPU.
Probably the same on all the CPUs. Probably :).
> I would also like to know where I should put this driver!
> devs\serial\arm\edb7xxx\ already has a current directory. Is it ok to
> put another directory called "ssi2" under there? If so, maybe current
> should be put into a directory called rs232 or serial or something?
You could change the structure to be:
devs/serial/arm/edb7xxx/async/current
devs/serial/arm/edb7xxx/ssi2/current
and adjust the entry in ecos.db appropriately.
Or you could actually just do both of them within
devs/serial/arm/edb7xxx/current, and just separate all the async serial
stuff into it's own cdl_package under the top CYGPKG_IO_SERIAL_ARM_EDB7XXX
cdl_package. They would both have CYGPKG_IO_SERIAL_DEVICES as a parent etc.
presumably. I think this is probably preferable really.
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