From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Date: Tue, 21 Apr 2009 10:57:54 -0500 Subject: [U-Boot] Kconfig menu layout In-Reply-To: <9e4733910904210841n6c7f0db5s57eee23520dc10a@mail.gmail.com> References: <8528E0E6-DEEC-49A4-9500-FC0B2C5C543B@kernel.crashing.org> <9e4733910904201501m7d3934fbje6b66acacfb7c306@mail.gmail.com> <9e4733910904201706u58387d5fod231dd4b8ac88d74@mail.gmail.com> <9e4733910904201712x68658ddfk3c18298deb82bd9f@mail.gmail.com> <20090421142730.35CCA83420E8@gemini.denx.de> <9e4733910904210841n6c7f0db5s57eee23520dc10a@mail.gmail.com> Message-ID: <49EDED02.20705@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Jon Smirl wrote: > My vote would be to require all boards in the board/ directory to be > in a vendor directory. When you buy the board it is pretty obvious > from the accompanying packaging/manuals who the vendor is. Companies and product lines get bought, names change... IMHO, architecture (selected by kconfig, not ARCH=) and CPU family are a more robust and managable way of sorting the menu -- and would be familiar to those used to configuring Linux. We could still pull in a defconfig from the command line based on a board name alone (in addition to the search functionality you mention). > This would also assign some responsibility to the vendor to maintain the > subdirectory for their products. Assuming the vendor cares. :-) -Scott