This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Re: PC targets and ethernet
- From: Andrew Lunn <andrew at lunn dot ch>
- To: John Dallaway <jld at ecoscentric dot com>
- Cc: Jani Monoses <jani at iv dot ro>, ecos-discuss at ecos dot sourceware dot org
- Date: Thu, 12 Aug 2004 09:37:01 +0200
- Subject: Re: [ECOS] Re: PC targets and ethernet
- References: <20040811150749.462c9146.jani@iv.ro> <411A8045.3060409@ecoscentric.com>
On Wed, Aug 11, 2004 at 09:23:33PM +0100, John Dallaway wrote:
> Hi Jani
>
> Jani Monoses wrote:
>
> >there are 3 pc targets in ecos.db which only differ in the ETH drivers they
> >use.I made a new one for use in the qemu simulator and had to use yet
> >another
> >eth driver (amd pcnet)
> >I propose adding a target (it used to be one called pc) which has no
> >ethernet
> >so that one can chose what eth driver to add without modifying ecos.db
> >From what I saw once you go with a target you cannot remove packages.
>
> The scheme you propose will not work with the eCos Configuration Tool
> which prevents users from adding/removing _hardware_ packages from their
> configuration.
lunn@londo:~/eCos$ ecosconfig new csb281
lunn@londo:~/eCos/tmp$ ecosconfig remove CYGPKG_DEVS_ETH_INTEL_I82559
lunn@londo:~/eCos/tmp$
package CYGPKG_DEVS_ETH_INTEL_I82559 {
alias { "Intel 82559 ethernet driver"
devs_eth_intel_i82559 i82559_eth_driver }
hardware
directory devs/eth/intel/i82559
script intel_i82559_eth_drivers.cdl
description "Ethernet driver for Intel 82559 NIC."
}
So I presume you mean the GUI tool has this limitation. It seems the
CLI tool has no problems with this.
Question: Why should hardware packages not be removable?
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss