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: Thu, 25 Mar 2004 14:52:05 -0800	[thread overview]
Message-ID: <40636295.7000008@pacbell.net> (raw)
In-Reply-To: <20040325221145.GJ10711@pengutronix.de>

Robert Schwebel wrote:
> David, 
> 
> finally, here is our RNDIS USB Gadget Driver - see the attached patch
> against the gadget-2.4 BK tree as of now. It shouldn't be too difficult
> to port this to 2.6. 

Yowsza!  I've been looking forward to this ... :)

I'll look it over and see how the 2.6 merge goes, and probably run
some revisions by you.  The autoconfiguration updates will make this
more complicated, since g_ether is starting to support a more dynamic
configuration model; the HH.org crew need that, so PDA Linux distros
don't need to hard-wire as much knowledge about hardware targets
into their kernels.


> The patch adds support for Microsoft's RNDIS protocol to the standard
> g_ether driver. This makes it possible to connect a Linux USB gadget to
> any standard Windows machine and <*PALIM!*> there is a new USB network
> interface on the Windows side on which you can speak TCP/IP :-) 

Which is exactly what a lot of Linux solution providers need to see;
I'm sure this will get a lot of use.  Applause!

(Although I personally would prefer that Microsoft adopt vendor-neutral
protocols, instead of pushing the rest of the industry to adopt things
that are MSFT-biased ... for some reason, they haven't listened to almost
anyone on such topics.  Oh well.  ;)


> Unfortunately, although it works with the original Microsoft driver, you
> need an inf file on the windows side; you can download the template for
> that directly from M$. 
> 
> Thanks to Auerswald GmbH for sponsoring this work!

I'll add them to the official "thank you" list on the
http://www.linux-usb.org/gadget webpage.

- Dave


> Robert
> 
> 




  reply	other threads:[~2004-03-25 22:53 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 [this message]
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
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=40636295.7000008@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