From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8017 invoked by alias); 8 Nov 2008 21:40:26 -0000 Received: (qmail 7915 invoked by uid 22791); 8 Nov 2008 21:40:25 -0000 X-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from fg-out-1718.google.com (HELO fg-out-1718.google.com) (72.14.220.157) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 08 Nov 2008 21:39:48 +0000 Received: by fg-out-1718.google.com with SMTP id 16so1722286fgg.44 for ; Sat, 08 Nov 2008 13:39:45 -0800 (PST) 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= Received: by 10.86.50.6 with SMTP id x6mr5498454fgx.31.1226180384993; Sat, 08 Nov 2008 13:39:44 -0800 (PST) Received: by 10.86.36.7 with HTTP; Sat, 8 Nov 2008 13:39:44 -0800 (PST) Message-ID: <30c102240811081339l17a02418w19863a27256eadc9@mail.gmail.com> Date: Sat, 08 Nov 2008 21:40:00 -0000 From: "=?ISO-8859-1?Q?G=E1bor_T=F6r=F6k?=" To: munz@speag.ch, ecos-devel@ecos.sourceware.org Subject: Re: What is the reason to... In-Reply-To: <49148705.3090007@speag.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4910602A.3090408@speag.ch> <49148705.3090007@speag.ch> X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2008-11/txt/msg00009.txt.bz2 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 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 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 >> >>