From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Kconfig menu layout
Date: Tue, 21 Apr 2009 07:59:56 -0400 [thread overview]
Message-ID: <49EDB53C.2050306@ge.com> (raw)
In-Reply-To: <9e4733910904201712x68658ddfk3c18298deb82bd9f@mail.gmail.com>
Jon Smirl wrote:
> On Mon, Apr 20, 2009 at 8:06 PM, Jon Smirl <jonsmirl@gmail.com> wrote:
>> On Mon, Apr 20, 2009 at 7:57 PM, Kumar Gala <galak@kernel.crashing.org> wrote:
>>> On Apr 20, 2009, at 5:01 PM, Jon Smirl wrote:
>>>
>>>> On Mon, Apr 20, 2009 at 5:11 PM, Kumar Gala <galak@kernel.crashing.org>
>>>> wrote:
>>>>> In chatting w/Wolfgang on IRC he felt that we should maintain the
>>>>> highlevel picking a board implies ARCH and other settings.
>>>>>
>>>>> However this seems like a lot of boards in one list.. To get a rough
>>>>> order of magnitude MAKEALL is ~880 lines. How can we reduce this to
>>>>> make it a bit more manageable?
>>>> I'd arrange them by vendor. The vendor kconfig variable doesn't need
>>>> to be used in code generation.
>>> Assuming boards/ is grouped by vendor today:
>>>
>>> $ ls -1 board/ | wc -l
>>> 269
>>>
>>> still seems like a long list.
>> Everyone will know the vendor of their board. You could alphabetize
>> and break the list into groups. I think there are some entries in
>> board/ that should be combined and moved into vendor subdirs.
>
> There are a lot of boards that could be moved into a vendor subdirs. I
> suspect we have less than 100 vendors. Maybe as few as 60.
>
> Don't some of these ads board belong in the freescale dir?
> jonsmirl at terra:/home/apps/u-boot/board$ ls *ads* -d
> ads5121 adsvix fads mpc8260ads mpc8266ads mpc8540ads mpc8560ads
> mx1ads mx31ads
I suspect there are also quite a few boards that don't have a vendor
attached to them or the vendor only has one or two boards in u-boot. I
would create a "vendor" named "other" to lump the miscellaneous boards into.
$ ls -1 board/*/*.mk | wc -l
211
OK, that says that, of the 269 directories, 58 are vendor subdirectories
and 211 are boards that should be stuffed into either an existing vendor
subdirectory, a new vendor subdirectory, or "other".
(Interesting... vendors appear to have 202 boards, so we have almost as
many vendor subdirectory boards as top level boards.)
$ ls -1 board/*/*/*.mk | wc -l
202
Best regards,
gvb
next prev parent reply other threads:[~2009-04-21 11:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 21:11 [U-Boot] Kconfig menu layout Kumar Gala
2009-04-20 22:01 ` Jon Smirl
2009-04-20 23:57 ` Kumar Gala
2009-04-21 0:06 ` Jon Smirl
2009-04-21 0:12 ` Jon Smirl
2009-04-21 11:59 ` Jerry Van Baren [this message]
2009-04-21 14:27 ` Wolfgang Denk
2009-04-21 14:46 ` Alessandro Rubini
2009-04-21 15:21 ` Alessandro Rubini
2009-04-21 15:41 ` Jon Smirl
2009-04-21 15:57 ` Scott Wood
2009-04-21 20:02 ` Wolfgang Denk
2009-04-21 20:17 ` Kumar Gala
2009-04-21 20:52 ` Wolfgang Denk
2009-04-21 21:05 ` Kumar Gala
2009-04-21 22:33 ` Jon Smirl
2009-04-21 23:14 ` Wolfgang Denk
2009-04-21 23:22 ` Jon Smirl
2009-04-21 23:56 ` Ben Warren
2009-04-22 7:11 ` Robert Schwebel
2009-04-21 22:59 ` Wolfgang Denk
2009-04-21 23:03 ` Kumar Gala
2009-04-22 12:44 ` [U-Boot] Kconfig menu layout (multiple ways to show the same Kconfig configs?) Kumar Gala
2009-04-22 19:43 ` Sam Ravnborg
2009-05-01 11:47 ` Sam Ravnborg
2009-06-02 16:08 ` Kumar Gala
2009-04-21 14:25 ` [U-Boot] Kconfig menu layout Wolfgang Denk
2009-04-21 15:33 ` Jon Smirl
2009-04-21 20:01 ` 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=49EDB53C.2050306@ge.com \
--to=gerald.vanbaren@ge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.