From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22812 invoked by alias); 20 May 2009 21:22:47 -0000 Received: (qmail 22803 invoked by uid 22791); 20 May 2009 21:22:46 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from alicia.2020media.com (HELO alicia.2020mail.com) (212.124.192.215) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 20 May 2009 21:22:41 +0000 Received: from [212.124.199.38] (helo=[192.168.0.2]) by alicia.2020mail.com with esmtp (Exim 4.30; FreeBSD) id 1M6tF7-000Ot1-GY; Wed, 20 May 2009 22:22:29 +0100 Message-ID: <4A14749E.4040602@zynaptic.com> Date: Wed, 20 May 2009 21:22: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> In-Reply-To: <4A12B508.2050908@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/msg00066.txt.bz2 Hi John, Sorry about the delay in getting back - I got distracted by the other thread of this discussion... John Dallaway wrote: > Hi Chris > > Great to see more USB support for eCos. > > Chris Holgate wrote: > >> OK - I've now done a bit of tidying up which I hope won't have broken >> it! The latest version of the package is here: >> >> http://www.zynaptic.com/ecos/packages/stm32-usb-20090519.epk > > 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. 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. 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? Chris.