public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 21:57:44 +0100	[thread overview]
Message-ID: <20040326205744.GH16461@pengutronix.de> (raw)
In-Reply-To: <40648876.9050902@pacbell.net>

On Fri, Mar 26, 2004 at 11:45:58AM -0800, David Brownell wrote:
> Well, what I merge is necessarily going to work on more hardware than
> just PXA ... it'll work over net2280 (at high speed), goku, and surely
> other hardware.  In most cases that'll just require sanity testing.
> Maybe I can get Julian to test on SH3, and it sounds like Andrew is
> getting close on the MediaQ.

A broader variety of controllers would indeed be helpful. When you have
the stuff integrated the way you think it's right, just tell me and I'll
test if it still works on our testbed. 

> Once I can see it work, then it'll be ready for that more widespread
> testing. (Do penguins actually cry?)

Only if they have to read Microsoft specifications :-) 

> It's not as if the protocol actually _needs_ an interrupt endpoint,
> though the MSFT spec says it does. It's actually simpler for the host
> to poll for completion on the control endpoint; none of the requests
> should take very long to finish anyway. An RNDIS host might not even
> notice those "toggle broken" issues.

You probably underestimate the mental sensibility of Windows machines.
We have seen cases where the Windows host just floods you with
interrupts when it is not happy with things like these... 

> Did you have any evidence that the MSFT host was actually using that
> interrupt endpoint? Like CATC snooping showing it never tried to
> collect responses until the interrupt packet arrived?

We have seen the packets with the protocol analyzer. I think we agree
that using an interrupt endpoint just to announce that the gadget has a
message for the host available, but that's how M$ designed it... 

> Also, which versions of MS-Windows did you test against? Some of the
> MSFT docs suggest version-specific protocol quirks.

Win 98, XP, 2000. Auerswald currently tests all available other
variants, and the tests they invented are _really_ crazy ;)

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

  reply	other threads:[~2004-03-26 20:58 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
2004-03-26 19:45             ` David Brownell
2004-03-26 20:57               ` Robert Schwebel [this message]
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=20040326205744.GH16461@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