From: David Brownell <david-b@pacbell.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [Fwd: [PATCH 2.5.68] USB Gadget framework (0/6)]
Date: Sat, 03 May 2003 18:27:28 -0700 [thread overview]
Message-ID: <3EB46C80.3010500@pacbell.net> (raw)
FYI: sent this morning to linux-usb-devel.
-------- Original Message --------
Subject: [PATCH 2.5.68] USB Gadget framework (0/6)
Date: Sat, 03 May 2003 11:45:06 -0700
From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>, linux-usb-devel@lists.sourceforge.net
Followups to this message will include patches with the core
of a "USB Gadget" framework. As you know, this is something
we've wanted for the 2.5 kernel. I see this as a good seed,
the Linux developer community as fertile ground, and with
spring here (Northern hemisphere, y'all), it's time to see
what we'll grow!
The API is hardware-neutral, and passes straight down to drivers
for device-side USB controllers. The "gadget drivers" implement
USB device functionality using that API, including "endpoint zero"
policies to configure that hardware for the desired functionality.
They talk to host-side USB device drivers, such as those found
today in all mainstream Linux kernels.
1 <linux/usb_gadget.h> ... API, and inlined implementation.
2 drivers/usb/gadget/net2280.[hc] ... implements that API,
for the Net2280 peripheral controller. This connects
using PCI, and supports USB 2.0 high speed. So it's
relatively demanding of that API.
3 drivers/usb/gadget/zero.c ... simple gadget driver for
testing
4 drivers/usb/gadget/ether.c ... CDC Ethernet gadget driver,
supports high speed link
5 drivers/usb/gadget/usbstring.c ... optional utility code,
for use by gadget drivers
6 kconfig/kbuild support for all the above.
These patches are against 2.5.68 current. Please merge them
towards Linus' tree.
- Dave
reply other threads:[~2003-05-04 1:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3EB46C80.3010500@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
/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