From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linuxppc-dev@ozlabs.org, Greg KH <greg@kroah.com>,
sl@bplan-gmbh.de, linux-usb-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/2] Fixed compiled issue tu to new of_platform.h header
Date: Sat, 25 Nov 2006 08:19:05 +1100 [thread overview]
Message-ID: <1164403145.5653.93.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0611241557080.16422-100000@netrider.rowland.org>
> I haven't been following this very closely. The problem is that you have
> a system with two different kinds of OHCI controllers, thus requiring two
> different and incompatible versions of the driver?
Sort-of. Basically, PowerPC can (and must in some case) build a single
kernel image that can be booted on a variety of platforms. There are at
least 3 platforms coming in now (this Efika is one of them) where that
includes a non-PCI OHCI or EHCI (big endian even) while the same kernel
must also contain the normal PCI OHCI/EHCI driver.
It's generally not a problem as the endian thingy is a runtime bit, and
in general, the whole code allows for this just fine, with, afaik, the
exception of the multiple module_init() bits...
> If the only source of incompatibility is the module_init() and
> module_exit() routines, then your suggestion would be a simple fix.
> Ugly, yes, but I don't think anyone will really mind.
>
> Is there anything else to prevent you from combining multiple HCIs into a
> single driver?
Not that I know. But we could have a cleaner approach. The #include one
dates a bit... we could have for example an ohci-core.ko with the core
bits, and ochi-pci.ko, ohci-patform.ko etc... be separate modules linked
on the first and instanciating it.
I'll have a look and will come up with either solution.
Ben.
next prev parent reply other threads:[~2006-11-24 21:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 16:11 [RFC] USB OHCI glue for PowerPC/Openfirmware nd
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 [this message]
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=1164403145.5653.93.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--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 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.