From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2078 invoked by alias); 31 May 2009 15:01:51 -0000 Received: (qmail 1723 invoked by uid 22791); 31 May 2009 15:01:47 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_93,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from vicky.2020media.com (HELO smtp.2020smtp.net) (212.124.192.213) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 31 May 2009 15:01:37 +0000 Received: from [212.124.199.38] (helo=[192.168.0.2]) by smtp.2020smtp.net with esmtp (Exim 4.63) (envelope-from ) id 1MAmXT-00007W-0c; Sun, 31 May 2009 16:01:31 +0100 Message-ID: <4A229BCA.3020906@zynaptic.com> Date: Sun, 31 May 2009 15:01:00 -0000 From: Chris Holgate User-Agent: Thunderbird 2.0.0.19 (X11/20081227) MIME-Version: 1.0 To: John Dallaway 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> <4A150245.3020105@dallaway.org.uk> In-Reply-To: <4A150245.3020105@dallaway.org.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 2009-05/txt/msg00078.txt.bz2 Hi John, John Dallaway wrote: > 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 > } > } I tried this and while it works for adding in a new package, I found that it has the unfortunate side effect of causing the entire STM3210E target to be removed when removing the USB package. Subsequently re-adding the USB package then just adds in this truncated target definition which results in ecos.db becoming unloadable. On balance, I think I'll probably stick with adding in a completely new target for the time being since this seems to be more robust. The other changes you suggested have now gone in and should allow the USB driver to be added to the standard target in CVS. Chris.