From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5972 invoked by alias); 12 Aug 2004 12:08:09 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 5929 invoked from network); 12 Aug 2004 12:08:06 -0000 Received: from unknown (HELO smtp.ecoscentric.com) (194.153.168.165) by sourceware.org with SMTP; 12 Aug 2004 12:08:06 -0000 Received: by smtp.ecoscentric.com (Postfix, from userid 99) id 049AF65C168; Thu, 12 Aug 2004 13:08:03 +0100 (BST) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by smtp.ecoscentric.com (Postfix) with ESMTP id 4446F65C123 for ; Thu, 12 Aug 2004 13:08:02 +0100 (BST) Message-ID: <411B5D9B.1030208@ecoscentric.com> Date: Thu, 12 Aug 2004 12:08:00 -0000 From: John Dallaway Organization: eCosCentric Limited User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 MIME-Version: 1.0 To: ecos-discuss@ecos.sourceware.org References: <20040811150749.462c9146.jani@iv.ro> <411A8045.3060409@ecoscentric.com> <20040812073701.GO27052@lunn.ch> <411B270D.2020408@ecoscentric.com> <20040812082956.GS27052@lunn.ch> <411B2F0C.6080304@ecoscentric.com> <1092308646.25147.1849.camel@hermes> In-Reply-To: X-Enigmail-Version: 0.84.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on norbert.ecoscentric.com X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.63 Subject: [ECOS] Re: PC targets and ethernet X-SW-Source: 2004-08/txt/msg00204.txt.bz2 Nick Garnett wrote: >>Perhaps devices like this (which may or not be present) should just not >>be marked as "hardware" in the database. Would that not work? > > While that might solve the problem for PCs, it would then make these > packages optional for all other targets that use them. Which we don't > want to do. > > The base problem is that the PC is an unusual target as far as eCos is > concerned. Most boards that have ethernet have the MAC in the > microcontroller or soldered quite firmly to the board. So there is no > question of it being changeable. The PC is different in that any PCI > card can be plugged in. So far we have coped with this quite > successfully by defining different targets for each supported ethernet > card. This is not particularly hard to do -- the ecos.db changes are > trivial compared with creating the target specific package and maybe > modifying the driver to work. > > I'm not sure I really like the idea of compromising the functionality > of eCos simply to make a specific, unusual, target slightly more > convenient to use. I agree with Nick. Adding a new target record in ecos.db is a simple solution to this board-specific problem. It is also more convenient than repeatedly adding/removing packages each time a new configuration is created. John Dallaway eCosCentric Limited -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss