This is the mail archive of the
ecos-devel@sourceware.org
mailing list for the eCos project.
Re: What is the reason to...
>>>>> "Oliver" == oliver munz @ s p e a g <munz@speag.ch> writes:
Oliver> In this case templates like:
Oliver> target at91sam7sek {
Oliver> alias { "Atmel AT91SAM7SEK evaluation board" at91_at91sam7sek }
Oliver> packages { CYGPKG_HAL_ARM
Oliver> CYGPKG_HAL_ARM_AT91
Oliver> CYGPKG_HAL_ARM_AT91SAM7
Oliver> CYGPKG_HAL_ARM_AT91SAM7SEK
Oliver> CYGPKG_IO_SERIAL_ARM_AT91
Oliver> CYGPKG_DEVS_FLASH_AT91
Oliver> CYGPKG_DEVS_SPI_ARM_AT91
Oliver> CYGPKG_DEVICES_WATCHDOG_ARM_AT91WDTC
Oliver> CYGPKG_DEVS_USB_AT91
Oliver> }
Oliver> description "
Oliver> The at91sam7sek target provides the packages needed to run eCos
Oliver> on an
Oliver> Atmel AT91SAM7S-EK evaluation board."
Oliver> }
Oliver> should be changed?
Oliver> They are missing the CYGPKG_IO_SPI and so on...
I believe they should be changed. From
http://ecos.sourceware.org/docs-latest/ref/spi-porting.html:
"If there is already an SPI bus driver for the target hardware then
both that driver and this generic SPI package CYGPKG_IO_SPI should
be included in the ecos.db target entry."
I do not know all the inner details of the AT91 SPI driver so there
may be unexpected side effects.
Bart
--
Bart Veer eCos Configuration Architect
eCosCentric Limited The eCos experts http://www.ecoscentric.com/
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.