From: nd@bplan-gmbh.de
To: nd@bplan-gmbh.de
Cc: linux-usb-devel@lists.sourceforge.net, greg@kroah.com,
sl@bplan-gmbh.de, linuxppc-dev@ozlabs.org,
stern@rowland.harvard.edu
Subject: [RFC] USB OHCI glue for PowerPC/Openfirmware
Date: Thu, 23 Nov 2006 17:11:59 +0100 (MET) [thread overview]
Message-ID: <11642982453599-git-send-email-nd@bplan-gmbh.de> (raw)
Theses patches add USB/OHCI HC glue for OpenFirmware. This allows to support any kind of USB/OHCI controller which is present in an OpenFirmware device tree.
By the way, I noticed that ohci-hcd.c module compilation is broken when multiple HC glues are selected. The glues sources files are directly include into ohci-hcd.c. Then, multiple module_init/exit in the same kmod cause compile issue. This news HC glue triggers this issue but is not the issue itself.
At least, this is how I understood the issue. I may be wrong but I just wanted to spot this issue.
Could you please review/comment this patch for submission in 2.6.20?
Regards
next reply other threads:[~2006-11-23 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 16:11 nd [this message]
2006-11-23 16:12 ` [PATCH 1/2] Fixed compiled issue tu to new of_platform.h header nd
2006-11-23 16:12 ` [PATCH 2/2] USB OHCI OpenFirmware support nd
2006-11-24 8:57 ` [PATCH 1/2] Fixed compiled issue tu to new of_platform.h header Greg KH
2006-11-24 20:48 ` Benjamin Herrenschmidt
2006-11-24 21:06 ` Alan Stern
2006-11-24 21:19 ` Benjamin Herrenschmidt
2006-12-03 8:23 ` Sven Luther
2006-12-03 9:13 ` Nicolas DET
2006-12-03 14:57 ` Sven Luther
2006-12-07 1:19 ` [linux-usb-devel] " David Brownell
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=11642982453599-git-send-email-nd@bplan-gmbh.de \
--to=nd@bplan-gmbh.de \
--cc=greg@kroah.com \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=sl@bplan-gmbh.de \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).