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] Creation of PCI USB driver
Date: Fri, 23 Mar 2007 18:02:33 +0100	[thread overview]
Message-ID: <87ejnf99li.fsf@denx.de> (raw)
In-Reply-To: <loom.20070323T151458-861@post.gmane.org> (Lance Ware's message of "Fri, 23 Mar 2007 14:17:07 +0000 (UTC)")

Dear Lance,

Lance Ware <lancee.ware@gmail.com> writes:

> I wanted to add support for a USB OHCI NEC chip driver to the u-boot source 
> code.  Wanted to know if anyone has started a port.  I have 405 board
> with a 

If you search the archives, you'll find some posts of people working on
PCI USB drivers, but I don't think any patches have been posted yet.

> nec OHCI compliant chip.  I was thinking about using the current PPC4xx ohci 
> driver and changing the read and write calls to pci calls. Just wanted to know 
> does anyone else have a better idea

If you can avoid it, please try not to create a new OHCI driver. We're
currently trying to make the existing OHCI drivers generic by adding
board and cpu dependent hooks (see doc/README.generic_usb_ohci). Usually
very little cpu and board dependent code is necessary.

This code is currently still in the testing-USB branch (I'm in the
process of merging it to the new u-boot-usb repository right now) and
will sooner or later will be merged into the main branch. Maybe you can
find a clean way to add PCI USB support the generic driver?

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-03-23 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-23 14:17 [U-Boot-Users] Creation of PCI USB driver Lance Ware
2007-03-23 17:02 ` Markus Klotzbücher [this message]

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=87ejnf99li.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