From: Ben Warren <bwarren@qstreams.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] arm SoC code in U-Boot.
Date: Wed, 07 Mar 2007 09:27:23 -0500 [thread overview]
Message-ID: <1173277643.24846.129.camel@saruman.qstreams.net> (raw)
In-Reply-To: <1defaf580703070437x2d36edd8q52bc86a41d7df2f2@mail.gmail.com>
On Wed, 2007-03-07 at 13:37 +0100, Haavard Skinnemoen wrote:
> On 3/7/07, Stefan Roese <sr@denx.de> 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
next prev parent reply other threads:[~2007-03-07 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 17:02 [U-Boot-Users] arm SoC code in U-Boot Peter Pearse
2007-03-06 21:36 ` Wolfgang Denk
2007-03-06 21:55 ` Ulf Samuelsson
2007-03-06 22:32 ` Wolfgang Denk
2007-03-06 22:45 ` Ulf Samuelsson
2007-03-06 23:51 ` [U-Boot-Users] SDRAM cache inhibit David Clark
2007-03-07 0:06 ` Wolfgang Denk
2007-03-07 15:35 ` David Clark
2007-03-07 6:30 ` [U-Boot-Users] arm SoC code in U-Boot Stefan Roese
2007-03-07 12:37 ` Haavard Skinnemoen
2007-03-07 14:27 ` Ben Warren [this message]
2007-03-07 14:39 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2007-03-08 8:17 TXEMA LOPEZ
2007-03-08 8:40 ` Wolfgang Denk
2007-03-02 10:03 Txema Lopez
2007-03-05 11:38 ` Ulf Samuelsson
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=1173277643.24846.129.camel@saruman.qstreams.net \
--to=bwarren@qstreams.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