From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3665 invoked by alias); 21 May 2009 07:27:21 -0000 Received: (qmail 3653 invoked by uid 22791); 21 May 2009 07:27:17 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_93 X-Spam-Check-By: sourceware.org Received: from mtaout02-winn.ispmail.ntl.com (HELO mtaout02-winn.ispmail.ntl.com) (81.103.221.48) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 21 May 2009 07:27:11 +0000 Received: from aamtaout01-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout02-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20090521072704.QMXZ29481.mtaout02-winn.ispmail.ntl.com@aamtaout01-winn.ispmail.ntl.com>; Thu, 21 May 2009 08:27:04 +0100 Received: from cog.dallaway.org.uk ([86.9.207.237]) by aamtaout01-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20090521072703.GXRX13254.aamtaout01-winn.ispmail.ntl.com@cog.dallaway.org.uk>; Thu, 21 May 2009 08:27:03 +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 n4L7R10l009359; Thu, 21 May 2009 08:27:01 +0100 Message-ID: <4A150245.3020105@dallaway.org.uk> Date: Thu, 21 May 2009 07:27:00 -0000 From: John Dallaway User-Agent: Thunderbird 2.0.0.19 (X11/20090107) MIME-Version: 1.0 To: Chris Holgate CC: ecos-devel@sourceware.org Subject: Re: STM32 USB support References: <4A11CAAA.8040900@intefo.ch> <4A11D861.8090206@zynaptic.com> <4A11E5DF.2000403@intefo.ch> <4A129C34.9090606@zynaptic.com> <4A12B508.2050908@dallaway.org.uk> <4A14749E.4040602@zynaptic.com> In-Reply-To: <4A14749E.4040602@zynaptic.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 2009-05/txt/msg00068.txt.bz2 Hi Chris Chris Holgate wrote: > John Dallaway wrote: >> >> I note that you've defined a new eCos target for "STM3210E-EVAL with >> USB". This should not be necessary. > > That's there because I want the new package to be loadable against the > 3.0 release using the package manager and I couldn't see a way of adding > in new hardware packages to a platform without creating a new target. If you provide a new target record in pkgadd.db which matches the name of an existing target record in ecos.db, the packages listed in the new target record will be appended to the existing target record by ecosadmin.tcl. So you could do something like this in your pkgadd.db: target stm3210e_eval { packages { CYGPKG_IO_USB CYGPKG_IO_USB_SLAVE CYGPKG_DEVS_USB_CORTEXM_STM32 } } > When we're all happy that the driver is up to scratch for a CVS commit > I'll modify the existing target as you suggested. OK, but you _will_ need to provide a mechanism for disabling the compilation of the driver source code as I outlined in my previous e-mail. > However, this raises another question for the maintainers. I'm now > developing against 3.0 for production purposes and would rather add in > things like this USB driver as stable 3.0 packages rather than pulling a > potentially unstable CVS tree. Is there an 'official' place where all > such additional 3.0 packages could be located? We have tended to avoid doing this in the past. If we did this for all new packages we would end up with quite a number of .epk files over the lifetime of an eCos release. These files might also require updating if bugs are found and fixed. The maintainers focus their efforts on the CVS repository between releases. If developers want the very latest packages we advise them to use CVS. John Dallaway