From: Brian Waite <waite@skycomputers.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Configuration System
Date: Mon, 3 May 2004 07:05:57 -0400 [thread overview]
Message-ID: <200405030705.57724.waite@skycomputers.com> (raw)
In-Reply-To: <20040430231932.204D4C109F@atlas.denx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 30 April 2004 07:19 pm, Wolfgang Denk wrote:
> > > I definitely don't want to have to add 25 new files with meta- or
> > > config data just to get my job done.
> >
> > I don't think it will take that at all. Maybe a couple 2 or 3?
>
> Ummm... is you add only 3 files, you will have at least one monster
> of a config file which nobody will be able to understand nor
> maintain.
>
First, let me say I don't find the configurator that we are talking about all
the helpful to my work, but I think I might have a solution that will reduce
the maintainability. So what I was thinking about was using the maintainers
file along with a configurator script in the tools directory. The
configurator would be all the smarts. It would read the MAINTAINERS file,
which has the bits in a well-defined structure, and generate the views with
some type of filtering. So you could say "Show me all boards supporting CPU
xyz" or "Show me all boards supported by CPU xyz". The obvioous final step of
the configurator is "make <configuration>"
Here are the pros and cons I see to this:
PROS:
* The only new files are specificaly for the configurator and only need be
modified to fix the configurator.
* Only the people interested in the system need to know about it.
* Automatically updated with each supported board.
* Minimal added work for Wolfgang.
* It can be extracted from the tree and maintained on the side until Wolfgang
has the time to review and appove it.
* No one other then the interested parties has to do anything other than add
their board to the MAINTAINERS list to work in u-boot.
* It does not preclude the make <configuration> well known system.
* Many others I am sure :)
CONS:
* More files in the u-boot tree.
* The configurator itself becomes somewhat complex.
* Many others I am sure :)
Jon, Wolfgang what are your thoughts on a system like this?
Thanks
Brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQFAlieVmxLCz0u+Ko8RAtc2AJ9kwRymVMYLSTs09ENX7OZBBQOGuACfeRM9
IEsWwBilha9w46iUmnqrURw=
=7yQG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-05-03 11:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 21:17 [U-Boot-Users] Configuration System Jon Loeliger
2004-04-29 22:14 ` Wolfgang Denk
2004-04-30 5:31 ` Robert Schwebel
2004-04-30 15:07 ` Sam Ravnborg
2004-04-30 15:39 ` Wolfgang Denk
2004-04-30 16:00 ` Sam Ravnborg
2004-04-30 16:18 ` Wolfgang Denk
2004-04-30 16:05 ` Jon Loeliger
2004-04-30 16:31 ` Wolfgang Denk
2004-04-30 22:24 ` Jon Loeliger
2004-04-30 23:19 ` Wolfgang Denk
2004-05-03 11:05 ` Brian Waite [this message]
2004-05-03 20:12 ` Wolfgang Denk
2004-04-30 21:46 ` Sam Ravnborg
2004-05-03 11:18 ` [U-Boot-Users] [Newbie help] Motorola Board with GT64260 Oliver Korpilla
2004-05-02 10:45 ` Wolfgang Denk
2004-05-03 1:46 ` Mike McCullough
2004-05-03 9:46 ` Oliver Korpilla
2004-05-03 10:23 ` Wolfgang Denk
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=200405030705.57724.waite@skycomputers.com \
--to=waite@skycomputers.com \
--cc=u-boot@lists.denx.de \
/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