From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20087 invoked by alias); 27 May 2009 07:40:49 -0000 Received: (qmail 20073 invoked by uid 22791); 27 May 2009 07:40:47 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mtaout01-winn.ispmail.ntl.com (HELO mtaout01-winn.ispmail.ntl.com) (81.103.221.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 27 May 2009 07:40:38 +0000 Received: from aamtaout03-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout01-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20090527074031.YLQR6742.mtaout01-winn.ispmail.ntl.com@aamtaout03-winn.ispmail.ntl.com>; Wed, 27 May 2009 08:40:31 +0100 Received: from cog.dallaway.org.uk ([86.9.207.237]) by aamtaout03-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20090527074031.LWAM2093.aamtaout03-winn.ispmail.ntl.com@cog.dallaway.org.uk>; Wed, 27 May 2009 08:40:31 +0100 Received: from cog.dallaway.org.uk (cog.dallaway.org.uk [127.0.0.1]) by cog.dallaway.org.uk (8.13.8/8.13.8) with ESMTP id n4R7eS0E032563; Wed, 27 May 2009 08:40:29 +0100 Message-ID: <4A1CEE6C.6000403@dallaway.org.uk> Date: Wed, 27 May 2009 07:40:00 -0000 From: John Dallaway User-Agent: Thunderbird 2.0.0.19 (X11/20090107) MIME-Version: 1.0 To: Peter Niebert CC: ecos-discuss@sourceware.org References: <04F44069-1B94-4563-8261-311AD85ED3CE@niebert.com> In-Reply-To: <04F44069-1B94-4563-8261-311AD85ED3CE@niebert.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Re: CYGPKG_DEVS_DISK_MMC "hardware"? X-SW-Source: 2009-05/txt/msg00113.txt.bz2 Hi Peter Peter Niebert wrote: > The package CYGPKG_DEVS_DISK_MMC which implements a disk driver for MMC > cards via SPI has a "hardware" attribute in the ecos.db > In order to make it run, a corresponding SPI device must be declared > with a low level SPI driver (in my case AT91). > > As a consequence of the "hardware" attribute, ecosconfig refuses to add > this package. My feeling is, it should not be there and the "interface" > declaration in the > cdl script of the driver should be sufficient for requirements? The documentation for this package indicates that the presence of the hardware attribute is deliberate, but it's not clear why this should be necessary. I expect Bart Veer can explain. Bart? John Dallaway -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss