From: Sam Ravnborg <sam@ravnborg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Configuration System
Date: Fri, 30 Apr 2004 23:46:39 +0200 [thread overview]
Message-ID: <20040430214639.GA2233@mars.ravnborg.org> (raw)
In-Reply-To: <1083341111.5420.15.camel@gleep.sps.mot.com>
On Fri, Apr 30, 2004 at 11:05:11AM -0500, Jon Loeliger wrote:
> On Fri, 2004-04-30 at 10:39, Wolfgang Denk wrote:
> > > With respect to selecting architecture it must be pretty genial,
> > > otherwise the current scheme is preferable.
>
> I confess, I am not sure what constitutes "genial" here.
> >From the high-level perspective, my current notion is to
> roughly ask three basic questions at the onset:
>
> - What CPU Architecture is being targeted?
> (ARM, MIPS, PPC, Xscale, etc)
>
> - Given the CPU Architecture is now known, which processor
> is being selected? This might involve an intermediate step
> in which a "family" of processors might be selected to help
> narrow the selection. For example, maybe it is OK to just
> offer the 7 XSCALE processors directly (ixdp425, xm250, etc),
> while the prolific PPC might do a PPC4xx, 82xx, 85xx, etc
> selection for family in order to get to a specific cpu
> such as the mpc8540.
>
> - What board is being targeted?
> (ADS, CDS, IceCube, etc)
> Basically anything in u-boot/boards that is appropriate
> for the given target CPU Arch or specific CPU.
It is better not asking less obvious questions.
So when I know I have board XXX why should I then select CPU and
CPU family.
On the other hand knowing that I want an ARM, then I expect to see a
list of available boards. Did I only select ARM9, again a even
smaller set of boards.
Maybe this was what you had in mind already - my point is that it
should be intuitive and simple. Simple from both a usage and
implementation point of view.
But I see all this as something that can come later, the better
approach is to start out small and incremental add more.
Sam
next prev parent reply other threads:[~2004-04-30 21:46 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
2004-05-03 20:12 ` Wolfgang Denk
2004-04-30 21:46 ` Sam Ravnborg [this message]
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=20040430214639.GA2233@mars.ravnborg.org \
--to=sam@ravnborg.org \
--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