This is the mail archive of the
ecos-devel@sourceware.org
mailing list for the eCos project.
Re: What is the reason to...
- From: "Gábor Török" <tgabor84 at gmail dot com>
- To: munz at speag dot ch, ecos-devel at ecos dot sourceware dot org
- Date: Sat, 8 Nov 2008 22:39:44 +0100
- Subject: Re: What is the reason to...
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=m5qQFNooB5gg4gaRSjHLvRRtB58I4HKhhkcRos5PXb4=; b=KG2Sp+Kbt/MYhUrwscAjfc/iVFiN13SmWILGE9I+BsWiw1zFka9W1tpln+1J0iykZh xt7b/zpaF87bajZPC+oov2jz3gpQfw0YTo1uPWIiG9Ge0XBCEJa0Utg27nEX7MVJY8nS OyFIVjmpbhVwZ01/aWwHOrCBP842v1hTTLzDg=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=RYO12JwdnRynVujqos4DmR04F3Ge3ctjEM5ZVf5qPfzOGF8qK4162xNqZjsQf/wP20 MSxwvtLGH886Xm/63zxkD+eHpdRSRfZmeq8KmWWGUHnEio7tq6dXPDWW271f9Jtf9Dih 6WXqghu+gIYEb+ZeBrBaoFkVJUlyvaVF/2Q6A=
- References: <4910602A.3090408@speag.ch> <pnr65rjp66.fsf@delenn.bartv.net> <49148705.3090007@speag.ch>
I think it is the same issue CYGPKG_IO_USB and CYGPKG_IO_USB_SLAVE,
which are also marked as hadware packages and not included in the
templates.
On Fri, Nov 7, 2008 at 7:20 PM, oliver munz @ s p e a g <munz@speag.ch> wrote:
> In this case templates like:
>
> target at91sam7sek {
> alias { "Atmel AT91SAM7SEK evaluation board" at91_at91sam7sek }
> packages { CYGPKG_HAL_ARM
> CYGPKG_HAL_ARM_AT91
> CYGPKG_HAL_ARM_AT91SAM7
> CYGPKG_HAL_ARM_AT91SAM7SEK
> CYGPKG_IO_SERIAL_ARM_AT91
> CYGPKG_DEVS_FLASH_AT91
> CYGPKG_DEVS_SPI_ARM_AT91
> CYGPKG_DEVICES_WATCHDOG_ARM_AT91WDTC
> CYGPKG_DEVS_USB_AT91
> }
> description "
> The at91sam7sek target provides the packages needed to run eCos on an
> Atmel AT91SAM7S-EK evaluation board."
> }
>
> should be changed?
>
> They are missing the CYGPKG_IO_SPI and so on...
>
> Thanks Oliver
>
> Bart Veer schrieb:
>>>>>>>
>>>>>>> "Oliver" == oliver munz @ s p e a g <munz@speag.ch> writes:
>>>>>>>
>>
>> Oliver> mark CYGPKG_IO_SPI as HARDWARE?
>> Oliver> I think Generic SPI or I2C and so one should be loadable
>> Oliver> whitout an template. Can we change this?
>>
>> The problem here is that other drivers such as the wallclock or
>> dataflash are likely to depend on the SPI/I2C bus being available. On
>> some platforms there may even be platform HAL dependencies on the bus.
>> Now, by convention you can enable flash support on a given platform
>> simply by e.g. "ecosconfig add flash" and everything sorts itself out.
>> If the SPI or I2C bus driver was not automatically part of the
>> configuration then that would stop working.
>>
>> If you want the SPI or I2C support to be automatically available when
>> needed, working within the limitations of current CDL, then the
>> generic SPI or I2C packages have to be part of the target definition
>> in ecos.db. That means they have to be hardware packages.
>>
>> Also, in most cases the expectation is that the generic SPI and I2C
>> packages will only be usable if the target definition also specifies a
>> device driver appropriate for the hardware. So if you are adding SPI
>> or I2C support to a target then you have to edit the ecos.db target
>> entry anyway, and adding two packages instead of one is no big deal.
>>
>> Now, both the generic SPI and I2C packages have been carefully
>> designed to ensure that they add zero overhead to the application if
>> nothing actually uses the SPI or I2C bus. Any unused functionality
>> gets eliminated at link-time by linker garbage collection. Hence the
>> only real overhead is at build-time: ecosconfig or the configtool may
>> take a little longer to run, and a couple more files get compiled.
>> Neither is likely to be noticed by users unless they sit down with a
>> stopwatch.
>>
>> Bart
>>
>>