From: Andrew Lunn <andrew@lunn.ch>
To: John Dallaway <jld@ecoscentric.com>
Cc: Andrew Lunn <andrew@lunn.ch>, ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: PC targets and ethernet
Date: Thu, 12 Aug 2004 08:29:00 -0000 [thread overview]
Message-ID: <20040812082956.GS27052@lunn.ch> (raw)
In-Reply-To: <411B270D.2020408@ecoscentric.com>
On Thu, Aug 12, 2004 at 09:15:09AM +0100, John Dallaway wrote:
> Hi Andrew
>
> Andrew Lunn wrote:
>
> >>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.
>
> Correct. Hence my reference to "eCos Configuration Tool" rather than
> "ecosconfig" above.
Thats what i thought you meant, but to me, ecosconfig is also an eCos
Configuration Tool.
> >Question: Why should hardware packages not be removable?
>
> This was a design decision intended to prevent users from modifying
> their configuration to such an extent that it was effectively targetting
> a different board. The eCos Configuration Tool uses the selected
> "Hardware Template" (target) for more than just package selection. For
> example, the "Run Tests" feature requires knowledge of the selected board.
OK.
This leads to the counter question. Is ecosconfig broken? Should it
also not allow hardware targets to be removed?
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
next prev parent reply other threads:[~2004-08-12 8:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 12:07 [ECOS] " Jani Monoses
2004-08-11 12:16 ` Andrew Lunn
2004-08-11 20:23 ` [ECOS] " John Dallaway
2004-08-12 7:40 ` Andrew Lunn
2004-08-12 8:15 ` John Dallaway
2004-08-12 8:29 ` Andrew Lunn [this message]
2004-08-12 8:49 ` John Dallaway
2004-08-12 11:04 ` Gary Thomas
2004-08-12 11:46 ` Nick Garnett
2004-08-12 12:08 ` John Dallaway
2004-08-12 12:17 ` Jani Monoses
2004-08-13 7:18 ` Andrew Lunn
2004-08-12 10:39 ` andy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040812082956.GS27052@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=jld@ecoscentric.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).