From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23268 invoked by alias); 9 Nov 2008 15:34:44 -0000 Received: (qmail 23223 invoked by uid 22791); 9 Nov 2008 15:34:43 -0000 X-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Received: from elasmtp-mealy.atl.sa.earthlink.net (HELO elasmtp-mealy.atl.sa.earthlink.net) (209.86.89.69) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 09 Nov 2008 15:34:02 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=Y43CjV7KlMBlBunscuokwVPYB3+kwxtFW6uekCJrjM96ot8+Rho4aFkwBpM9qKYN; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [75.194.175.237] by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1KzCIW-0006kO-Cs; Sun, 09 Nov 2008 10:33:56 -0500 Message-ID: <491702E0.9070202@mindspring.com> Date: Sun, 09 Nov 2008 15:34:00 -0000 From: Frank Pagliughi User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: Bart Veer CC: =?ISO-8859-1?Q?G=E1bor_T=F6r=F6k?= , munz@speag.ch, ecos-devel@ecos.sourceware.org Subject: Re: What is the reason to... References: <4910602A.3090408@speag.ch> <49148705.3090007@speag.ch> <30c102240811081339l17a02418w19863a27256eadc9@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 4d82f965df0f6dd9e3f977c6d1ea408f0a9da525759e26541ac772956d476211dd62eda3a17cf4acdaeb3e8d137e934c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 75.194.175.237 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/msg00015.txt.bz2 I also think that our views on the issue are affected by which configuration editor we use. If I'm not mistaken, when using the command-line editor you can just "add" the drivers into your configuration, but if you use the GUI configtool, you can't add the packages and must edit "ecos.db" to get these drivers. And then you must manage a non-standard database file when upgrading from CVS. So people, like me, who tend to use the GUI configtool would have more of a reason to want to see theese drivers included in the target definition. - Frank Pagliughi Bart Veer wrote: >>>>>> tgabor84> I think it is the same issue CYGPKG_IO_USB and >>>>>> tgabor84> CYGPKG_IO_USB_SLAVE, which are also marked as hadware >>>>>> tgabor84> packages and not included in the templates. >>>>>> >>>>>> CYGPKG_IO_USB and CYGPKG_IO_USB_SLAVE are included in the target >>>>>> definitions for some targets, e.g. assabet, corresponding to the >>>>>> boards for which slave-side USB first became available. The reasoning >>>>>> is the same as for SPI and I2C: if the application does not use the >>>>>> functionality then it gets eliminated at link-time. Again I do not >>>>>> know if this works properly with more recent drivers. Also, USB is >>>>>> somewhat more complicated than SPI. >>>>>> >>>>>> Side issue: please be careful with terminology. A template is a >>>>>> hardware-independent description of functionality, e.g. "default", >>>>>> "redboot", or "net". Templates live in separate files below the >>>>>> templates/ subdirectory of the eCos repository. A target definition >>>>>> describes a hardware target, i.e. a specific board. Target definitions >>>>>> live in the ecos.db file. The combination of a target definition and a >>>>>> template gives an initial configuration. >>>>>> >>>>>> Bart >>>>>> >>>>>>