From: Nicolas DET <nicolas@det-net.org>
To: Sven Luther <sven@genesi-usa.com>
Cc: linux-usb-devel@lists.sourceforge.net, Greg KH <greg@kroah.com>,
sl@bplan-gmbh.de, linuxppc-dev@ozlabs.org,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH 1/2] Fixed compiled issue tu to new of_platform.h header
Date: Sun, 3 Dec 2006 10:13:41 +0100 (MET) [thread overview]
Message-ID: <20061203101343.6ceda991.nicolas@det-net.org> (raw)
In-Reply-To: <20061203082303.GA9129@powerlinux.fr>
On Sun, 3 Dec 2006 09:23:03 +0100
S0ven Luther <sven@genesi-usa.com> wrote:
> > 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.
>
In my mind, this is the correct approch.
> Hi, ...
>
> I am just wondering if i got dropped from the CCs or if there was no further
> discussion on this.
>
> The 2.6.19 kernel doesn't build when the efika patches are applied and the
> ohci modules are built. We need a solution for this. Even disabling the patch
> for ohci fails to build the ohci driver, but this could be a bad manipulation.
>
"Efika OHCI patches" does not exist. There is a new OHCI glue for OpenFrimware.
> Is there any hint on the right way to go for this ?
>
I'm currently running on 2.6.19 (the whole USB in kernel not kmod). It compiles and works fine.
Regards.
next prev parent reply other threads:[~2006-12-03 9:20 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
2006-12-03 8:23 ` Sven Luther
2006-12-03 9:13 ` Nicolas DET [this message]
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=20061203101343.6ceda991.nicolas@det-net.org \
--to=nicolas@det-net.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 \
--cc=sven@genesi-usa.com \
/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).