From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Warren Date: Wed, 07 Mar 2007 09:27:23 -0500 Subject: [U-Boot-Users] arm SoC code in U-Boot. In-Reply-To: <1defaf580703070437x2d36edd8q52bc86a41d7df2f2@mail.gmail.com> References: <20070306223220.22829352604@atlas.denx.de> <010201c76041$9a42fa90$01c4af0a@Glamdring> <200703070730.30835.sr@denx.de> <1defaf580703070437x2d36edd8q52bc86a41d7df2f2@mail.gmail.com> Message-ID: <1173277643.24846.129.camel@saruman.qstreams.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, 2007-03-07 at 13:37 +0100, Haavard Skinnemoen wrote: > On 3/7/07, Stefan Roese wrote: > > > Why not try to match this a little more to the Linux directory structure: > > > > drivers/net/netarm_eth.* > > drivers/net/qe/* > > drivers/i2c/omap1510_i2c.* > > ... > > I think this is a great idea. Grouping drivers together by function > makes them much easier to find, and it's also easier to find examples > when you're writing a new driver. With the current layout, you have to > grep through the drivers, cpu and board hierarchies to find existing > drivers similar to the one you're trying to write. Stellar idea. The more logically drivers are grouped, the easier it will to transition to a menuconfig-based system, which would be pretty cool, don't you think? Ben