From: David Brownell <david-b@pacbell.net>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org, greg@kroah.com,
linux-usb-devel@lists.sourceforge.net
Subject: Re: 2.4.23-pre8: link error with multiple USB Gadget drivers
Date: Fri, 24 Oct 2003 09:47:47 -0700 [thread overview]
Message-ID: <3F9957B3.8000801@pacbell.net> (raw)
In-Reply-To: <20031023195945.GJ11807@fs.tum.de>
Adrian Bunk wrote:
> I'm getting the following link error when trying to compile multiple
> Gadget drivers statically into the kernel:
... which is not a reasonable configuration, since only one
of them could be active ...
> ...
> IIRC this issue was fixed many months ago in 2.6, and a similar fix
> (disallowing multiple Gadget drivers) is also needed in 2.4 .
Do you know a good way to do that? This is an example of something
where the 2.4 "Config.in" commands don't seem to offer even a vaguely
sensible way to constrain the configuration. Or maybe you need to
be more expert in it than I am.
The rules for the moment should -- but AFAICT can't -- enforce:
- Only one gadget controller driver, linked statically or as
a module. (Example: net2280 or goku_udc, both on PCI.)
- If controller driver is statically linked, either:
* at most one gadget driver statically linked
* any number of gadget drivers, linked as modules
- Else if controller driver is linked as a module:
* any number of gadget drivers, linked as modules
The 2.6 Kconfig is closest to supporting those rules, though I
don't know how to restrict it to "only one controller driver"
regardless of how it's linked.
I'd be open to a better solution than relying on the person
configuring the system to not make mistakes.
- Dave
next prev parent reply other threads:[~2003-10-24 16:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 23:24 Linux 2.4.23-pre8 Marcelo Tosatti
2003-10-23 1:53 ` viro
2003-10-23 15:45 ` Matt Zimmerman
2003-10-23 7:05 ` Jeff Chua
2003-10-23 11:26 ` Marcelo Tosatti
2003-10-23 14:07 ` [patch] 2.4.23-pre8: link error with both megaraid drivers Adrian Bunk
2003-10-23 14:18 ` Matthew Wilcox
2003-10-23 19:42 ` Adrian Bunk
2003-10-23 15:22 ` Linux 2.4.23-pre8 laurent.ml
2003-10-23 20:23 ` Olaf Hering
2003-10-23 17:05 ` Peter Osterlund
2003-10-23 17:48 ` Marcelo Tosatti
2003-10-23 18:12 ` Philipp Matthias Hahn
2003-10-23 18:59 ` Trond Myklebust
2003-10-23 21:20 ` Andre Tomt
2003-10-23 21:55 ` Trond Myklebust
2003-10-23 19:47 ` 2.4.23-pre8: usbnet.c doesn't compile with gcc 2.95 Adrian Bunk
2003-10-23 22:03 ` Greg KH
2003-10-23 22:43 ` Adrian Bunk
2003-10-23 19:59 ` 2.4.23-pre8: link error with multiple USB Gadget drivers Adrian Bunk
2003-10-24 16:47 ` David Brownell [this message]
2003-10-23 23:09 ` Linux 2.4.23-pre8 Lukasz Trabinski
2003-10-24 0:26 ` Andre Tomt
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=3F9957B3.8000801@pacbell.net \
--to=david-b@pacbell.net \
--cc=bunk@fs.tum.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=marcelo.tosatti@cyclades.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).