public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Robert Schwebel <robert@schwebel.de>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] RNDIS Gadget Driver
Date: Fri, 26 Mar 2004 09:45:15 -0800	[thread overview]
Message-ID: <40646C2B.6020306@pacbell.net> (raw)
In-Reply-To: <20040326163543.GD16461@pengutronix.de>

Robert Schwebel wrote:
> On Fri, Mar 26, 2004 at 07:58:04AM -0800, David Brownell wrote:
> 
>>>>>-	.bDeviceClass =		DEV_CONFIG_CLASS,
>>>>>+	.bDeviceClass =		0x02,
>>>>
>>>>Is this wise?
>>>
>>>
>>>Until now DEV_CONFIG_CLASS was 0xFF, which results in Windows getting
>>>hickup. If you directly set this to 0x02 (Network Device) Win is happy.
>>
>>Actually I suspect setting it to USB_CLASS_COMM would be preferred, in
>>RNDIS-specific config descriptors....

(since:  #define USB_CLASS_COMM                  2)


> 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.


> RNDIS is a sensitive beast. Do one bit different results in that uggly
> "Error 10" message on the Windows side. We saw it when we started with
> the driver, we saw it when the driver was half way finished and we will
> see it again if somebody tweaks the driver without exactly knowing what
> the guys at Microsoft smoked when they designed that protocol :-) 

I thought it was "just say no to vendor-neutral protocols" crack ...
although that close to BC they would have much better options! ;)

The purist in me is annoyed that rather than just defining a purely
vendor-specific protocol, they re-used bits and pieces of the USB-IF
CDC-ACM spec.  It's not like they needed _any_ of it.  (Unless maybe
subtle sabotoge of CDC was a goal?)



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.

Also it looks like you've only tested this on PXA hardware.
Most of the patch is the (R)NDIS support code, which is easy
to merge, but the "g_ether" updates will take longer.

- Dave



> Robert



  reply	other threads:[~2004-03-26 17:46 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 [this message]
2004-03-26 18:41           ` Robert Schwebel
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=40646C2B.6020306@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=robert@schwebel.de \
    /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