From: Robert Schwebel <robert@schwebel.de>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel <linux-usb-devel@lists.sourceforge.net>,
Greg KH <greg@kroah.com>, Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Chosing the right Linux "USB Gadget" API and Driver Framework
Date: Wed, 16 Apr 2003 09:36:35 +0200 [thread overview]
Message-ID: <20030416073635.GA10886@pengutronix.de> (raw)
I'm currently working on support for the USB gadget controller inside
the Intel PXA25x XScale processor. David Brownell has recently published
a new USB gadget API which was discussed on linux-usb-devel and which
seems to be a good starting point.
As there is at least one other API (by Belcarra, former Lineo code) I'm
wondering what Greg's and Linus' position concerning the new USB gadget
API is. A comment from your side would be welcome.
Cheers,
Robert
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
next reply other threads:[~2003-04-16 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 7:36 Robert Schwebel [this message]
2003-04-16 17:08 ` Chosing the right Linux "USB Gadget" API and Driver Framework Greg KH
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=20030416073635.GA10886@pengutronix.de \
--to=robert@schwebel.de \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=torvalds@transmeta.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