From: Robert Schwebel <robert@schwebel.de>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] RNDIS Gadget Driver
Date: Fri, 26 Mar 2004 19:41:42 +0100 [thread overview]
Message-ID: <20040326184142.GF16461@pengutronix.de> (raw)
In-Reply-To: <40646C2B.6020306@pacbell.net>
On Fri, Mar 26, 2004 at 09:45:15AM -0800, David Brownell wrote:
> >We have tried that, Windows does not like it. The only constellation
> >where it worked was setting the device descriptor's bConfigClass=0x02.
>
> Sorry, I meant "device" descriptors. Yes, I noticed their "spec"
> had strange things to say. Is there some reason you're not including
> the CDC header and union descriptors? That spec does talk about those,
> and the erratum I found also talks about better CDC ACM conformance.
USB_CLASS_COM is surely ok. The descriptors may be a relict from the
time where the CDC equivalents where not in the driver...
The problem is that, as it is now, it works. The whole RNDIS stuff is
extremely time intensive to debug: when you have one odd value in some
place, Windows just says "Error 10" and you have to guess what you did
wrong. No further information available. So the best way to be
successful may be to check it in as it is, maybe add some FIXMEs, and
let the masses test the code. Then cleanup the remaining issues step by
step and wait until nobody crys any more :-)
> Different topic: I noticed that on PXA you were using "ep5-int".
> That's documented as always using DATA0 -- data toggle not working.
> Was that making any trouble for you? I've never actually tried
> using those endpoints, because of that functional limitation.
Well, there is no other interrupt endpoint on the PXA, and it somehow
works :-)
> Also it looks like you've only tested this on PXA hardware.
It was hard enough :-)
> Most of the patch is the (R)NDIS support code, which is easy
> to merge, but the "g_ether" updates will take longer.
Ok. We have tried to make the design as minimal-invasive as possible...
Robert
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hornemannstraße 12, 31137 Hildesheim, Germany
Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4
next prev parent reply other threads:[~2004-03-26 18:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 22:11 [ANNOUNCE] RNDIS Gadget Driver Robert Schwebel
2004-03-25 22:52 ` David Brownell
2004-03-26 10:37 ` David Woodhouse
2004-03-26 15:44 ` David Brownell
2004-03-26 23:23 ` [linux-usb-devel] " don
2004-03-27 17:02 ` David Brownell
2004-03-28 2:47 ` don
2004-03-28 9:47 ` David Woodhouse
2004-03-28 15:34 ` David Brownell
2004-03-26 11:59 ` bert hubert
2004-03-26 12:19 ` Robert Schwebel
2004-03-26 12:26 ` bert hubert
2004-03-26 15:58 ` David Brownell
2004-03-26 16:35 ` Robert Schwebel
2004-03-26 17:45 ` David Brownell
2004-03-26 18:41 ` Robert Schwebel [this message]
2004-03-26 19:45 ` David Brownell
2004-03-26 20:57 ` Robert Schwebel
2004-03-26 21:09 ` David Brownell
2004-03-30 16:25 ` David Brownell
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=20040326184142.GF16461@pengutronix.de \
--to=robert@schwebel.de \
--cc=david-b@pacbell.net \
--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