public inbox for u-boot@lists.denx.de
 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: Tue, 08 May 2007 12:04:59 +0200	[thread overview]
Message-ID: <87bqgv6378.fsf@denx.de> (raw)
In-Reply-To: <20070508084700.GB11009@enneenne.com> (Rodolfo Giometti's message of "Tue, 8 May 2007 10:47:00 +0200")

Hi Rodolfo,

Rodolfo Giometti <giometti@enneenne.com> writes:

> On Tue, May 08, 2007 at 08:39:23AM +0200, Markus Klotzb?cher wrote:
>> Hi,
>> 
>> Wolfgang Denk <wd@denx.de> writes:
>> > in message <87ejlssr7a.fsf@denx.de> you wrote:
>> 
>> >> 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)
>> >
>> > Both versionshave their pros and cons, so  doing  it  like  Linux  is
>> > probably a reasonable thing.
>> 
>> Ok, then so it be.
>
> So we should put there even on-chip devices supports? Like on-chip USB
> OHCI controllers and USB devices?

Yes. If it's a driver, it should go into drivers/

>> How shall we structure the drivers/usb/ directory? How about something
>> like this:
>> 
>> drivers/usb/host/
>> 
>>         - generic and specific host controller drivers (ohci, uhci)
>> 
>> drivers/usb/core/
>>         
>>         - usb core logic
>> 
>> drivers/usb/storage/
>> 
>>         - storage class related code
>> 
>> drivers/usb/input/
>> 
>>         - e.g. keyboard support etc.        
>
> Since I'm working on USB device I think we need also:
>
> drivers/usb/gadget/
>
> 	- usb gadget drivers
>
> Also I think we should also move usbtty support there...

Ok, fine!

>> As said before it needn't be done in one go, but just to make clear
>> where usb stuff shall be placed from now on.
>
> Currently I'm developing my PXA27x USB device support in
> cpu/pxa/usbd.c file but as soon as the new tree structure is available
> I can move it accordingly.

Just create the directories you need while your working on your
driver. AFAIK you can't add empty directories with git.

Best regards

Markus Klotzb?cher

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

  reply	other threads:[~2007-05-08 10:04 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
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 [this message]
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=87bqgv6378.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox