From: Greg KH <greg@kroah.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: Adrian Bunk <bunk@stusta.de>,
Andrew Morton <akpm@linux-foundation.org>,
linville@tuxdriver.com, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, dbrownell@users.sourceforge.net,
linux-usb-devel@lists.sourceforge.net
Subject: Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile
Date: Mon, 5 Mar 2007 10:26:10 -0800 [thread overview]
Message-ID: <20070305182610.GA14113@kroah.com> (raw)
In-Reply-To: <200703051226.46402.mb@bu3sch.de>
On Mon, Mar 05, 2007 at 12:26:45PM +0100, Michael Buesch wrote:
> On Monday 05 March 2007 11:57, Michael Buesch wrote:
> > > > CC drivers/usb/host/ohci-hcd.o
> > > > In file included from
> > > > /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-hcd.c:931:
> > > > /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-ssb.c:47: error: request for member 'hcd_priv_size' in something not a structure or union
> > >
> > > Seems like there was a comma missing.
> > > There also seems to be some Kconfig problem. will fix that.
> > >
> > > > /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-ssb.c:47: error: 'ssb_ohci_device' undeclared here (not in a function)
> > > > /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-ssb.c:52: error: 'ssb_ohci_reset' undeclared here (not in a function)
> > > > /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-ssb.c:53: error: 'ssb_ohci_start' undeclared here (not in a function)
> > > > ...
> > > > make[4]: *** [drivers/usb/host/ohci-hcd.o] Error 1
> > > >
> > > > <-- snip -->
> >
> > Actually, it seems like I will run into other kinds of nasty problems
> > due to stupid design of the HCD code. The OHCI code #includes
> > the various drivers, which have a module_init each. So if you
> > compile PCI and SSB support, you have two module_init for one
> > OHCI module. Not sure how to fix this. Any idea?
>
> A real problem is that the HCD core seems to have the assumption
> built-in that there can only be one OHCI driver per machine/arch.
> That's not the case for SSB, where we can have both PCI and SSB
> bus enabled, so both ohci drivers compiled.
> Any idea? Greg perhaps?
David has provided hints on how to do this in the past on the
linux-usb-devel list if I remember correctly.
thanks,
greg k-h
next prev parent reply other threads:[~2007-03-05 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070302030026.5eef0c92.akpm@linux-foundation.org>
2007-03-05 1:47 ` 2.6.21-rc2-mm1: drivers/net/wireless/ compile error Adrian Bunk
2007-03-05 10:41 ` Michael Buesch
2007-03-05 1:47 ` 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile Adrian Bunk
2007-03-05 10:49 ` Michael Buesch
2007-03-05 10:57 ` Michael Buesch
2007-03-05 11:26 ` Michael Buesch
2007-03-05 18:26 ` Greg KH [this message]
2007-03-05 18:37 ` Adrian Bunk
2007-03-05 18:42 ` David Brownell
2007-03-05 19:09 ` Michael Buesch
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=20070305182610.GA14113@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.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;
as well as URLs for NNTP newsgroup(s).