From: David Brownell <david-b@pacbell.net>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [2.5 patch] let USB_GADGET depend on USB
Date: Sun, 01 Jun 2003 07:18:54 -0700 [thread overview]
Message-ID: <3EDA0B4E.504@pacbell.net> (raw)
In-Reply-To: 20030601111303.GV29425@fs.tum.de
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
Adrian Bunk wrote:
> On Sat, May 31, 2003 at 04:39:28PM -0700, David Brownell wrote:
>
>>Adrian Bunk wrote:
>>
>>>USB_GADGET is still selectable even with USB disabled. It seems the
>>>following is intended:
>>
>>This is wrong.
>>
>>CONFIG_USB has always represented the master/host side ... while
>>CONFIG_USB_GADGET represents just the slave/gadget side.
>>
>>The two are completely independent. Hardware that supports
>>one will typically _not_ support the other. And systems
>>that support [only] the slave/gadget side will have no use at all
>>for the 100KB+ of "usbcore".
>>...
>
>
> Well, CONFIG_USB_GADGET without CONFIG_USB gives me the following link
> error in 2.5.70-mm3:
As I had already said (in response to your email that reported
that problem), the fix is to revert the recent changeset that
links gadget code twice. Here's a patch that undoes it.
- Dave
[-- Attachment #2: link.patch --]
[-- Type: text/plain, Size: 302 bytes --]
--- a/drivers/usb/Makefile Sun Jun 1 07:14:50 2003
+++ b/drivers/usb/Makefile Sun Jun 1 07:14:50 2003
@@ -59,6 +59,3 @@
obj-$(CONFIG_USB_TIGL) += misc/
obj-$(CONFIG_USB_USS720) += misc/
-obj-$(CONFIG_USB_NET2280) += gadget/
-obj-$(CONFIG_USB_ZERO) += gadget/
-obj-$(CONFIG_USB_ETH) += gadget/
next prev parent reply other threads:[~2003-06-01 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 22:18 [2.5 patch] let USB_GADGET depend on USB Adrian Bunk
2003-05-31 23:39 ` David Brownell
2003-06-01 11:13 ` Adrian Bunk
2003-06-01 14:18 ` David Brownell [this message]
2003-06-01 18:10 ` Greg KH
2003-06-01 18:40 ` Adrian Bunk
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=3EDA0B4E.504@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 \
/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