All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Markus Klotzbücher" <mk@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PXA27x USB device
Date: Mon, 07 May 2007 15:23:21 +0200	[thread overview]
Message-ID: <87ejlssr7a.fsf@denx.de> (raw)
In-Reply-To: <200705071422.38411.sr@denx.de> (Stefan Roese's message of "Mon, 7 May 2007 14:22:38 +0200")

Hi Stefan,

Stefan Roese <sr@denx.de> writes:

> On Monday 07 May 2007, Markus Klotzb?cher wrote:
>> > But I see your point. By moving those cpu-specific files into the drivers
>> > directory, the architecture custodians need to maintain files distributed
>> > all over the drivers directory and not specifically in the cpu/xxx
>> > directory. I never thought of this before.
>>
>> This is why I favor the old way of storing cpu dependant drivers in the
>> appropriate cpu directory. This makes the responsibility clear and
>> allows to cleanly seperate arch and generic code. Isn't this similar to
>> linux where cpu dependant drivers are found in "arch/cpu/"?
>
> No, quite the contrary. In Linux you will find even the cpu-specific drivers 
> (like ethernet, uart, i2c driver etc) in the "drivers" directory. Only the 
> board- and cpu-specific setup code and some additional code like interrupt 
> controller implementation etc is normally found in the Linux "arch" 
> directories.

There are complete drivers in arch/ppc/8260_io or arch/ppc/8xx_io for
example, but I agree you're right in general.

>> What do you think?
>
> I still think we should move to implementing drivers in the drivers directory, 
> even if the responsibility for the files is not so easily visible anymore.

Ok, if this is what was agreed upon I can live with it. (Don't get me
wrong, I don't think this is a big mistake or so, I just fail to see any
real benefit beside of beeing more Linux-like)

Best regards

     Markus

--
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany

  reply	other threads:[~2007-05-07 13:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 14:05 [U-Boot-Users] PXA27x USB device Rodolfo Giometti
2007-05-02 22:05 ` Bryan O'Donoghue
2007-05-03  7:49 ` Markus Klotzbücher
2007-05-03  8:29   ` Stefan Roese
2007-05-03 10:15     ` Rodolfo Giometti
2007-05-04 10:20     ` Markus Klotzbücher
2007-05-04 11:47       ` Stefan Roese
2007-05-04 12:31         ` Wolfgang Denk
2007-05-07 11:55         ` Markus Klotzbücher
2007-05-07 12:22           ` Stefan Roese
2007-05-07 13:23             ` Markus Klotzbücher [this message]
2007-05-07 15:22               ` Robert Schwebel
2007-05-07 19:58               ` Wolfgang Denk
2007-05-08  6:39                 ` Markus Klotzbücher
2007-05-08  8:47                   ` Rodolfo Giometti
2007-05-08 10:04                     ` Markus Klotzbücher
2007-05-08 12:49                       ` Rodolfo Giometti
2007-05-08 14:14                         ` Loeliger Jon-LOELIGER

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=87ejlssr7a.fsf@denx.de \
    --to=mk@denx.de \
    --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.