linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: "Li Yang-R58472" <LeoLi@freescale.com>
Cc: greg@kroah.com, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] usb: add Freescale QE/CPM USB peripheral controllerdriver
Date: Wed, 24 Sep 2008 13:26:29 -0700	[thread overview]
Message-ID: <200809241326.30167.david-b@pacbell.net> (raw)
In-Reply-To: <0C69E0CDED15E4469A445DE244C1B9F708CEE6@zch01exm26.fsl.freescale.net>

On Tuesday 02 September 2008, Li Yang-R58472 wrote:
> 
> > Does RNDIS work too? If not, is it possible to add or doesn't 
> > the HW support it?
> 
> RNDIS is a gadget(protocol) level thing.  I believe it can work with
> this driver although not tested myself.

It should, so long as the QE hardware doesn't try to manage
too many USB protocol details.  Examples would be caring
at all about "config change events" -- SET_CONFIGURATION
picking between one of N configurations, and SET_INTERFACE
picking between altsettings of a given interface.


> Noted:  AFAIK, RNDIS gadget in Linux doesn't interoperate with windows
> well enough to be production level.  Use at your own risk.

Something in the past few releases broke so it may not be
operating much at all, for that matter...

However, it's a fair point that the interoperation requirements
for RNDIS are so badly defined that non-Microsoft code has a
very hard time being robust.

Somewhere in the linux-usb archives is someone's fairly careful
summary of a dozen extremely rude ways the MSFT RNDIS stack
misbehaves.  It'll do things like deciding to stop forwarding
packets to certain applications for a while ... then continuing
after a few minutes as if nothing was wrong.  Blue screens are
a possibility.  Best to wait a few minutes between plugging
and unplugging, while the races between the USB and NET stacks
sort themselves out.

- Dave

      parent reply	other threads:[~2008-09-24 20:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  9:43 [PATCH] usb: add Freescale QE/CPM USB peripheral controller driver Li Yang
2008-08-28 15:04 ` Arnd Bergmann
2008-08-28 17:22   ` Alan Stern
2008-08-28 17:53     ` Scott Wood
2008-08-28 20:16       ` Alan Stern
2008-08-28 22:27         ` Arnd Bergmann
2008-08-29 16:05           ` Alan Stern
2008-08-29 16:29             ` Arnd Bergmann
2008-08-29 17:19               ` Alan Stern
2008-08-29 17:38                 ` Arnd Bergmann
2008-08-29 21:22                   ` Alan Stern
2008-09-24 20:15           ` David Brownell
2008-08-29  8:57   ` Li Yang
2008-08-29  8:57     ` Arnd Bergmann
2008-09-24 20:10   ` David Brownell
2008-08-28 16:39 ` Scott Wood
2008-08-29  9:35   ` Li Yang
2008-09-01 13:52 ` Anton Vorontsov
2008-09-02  7:08   ` Li Yang
2008-09-01 16:34 ` Anton Vorontsov
2008-09-01 17:11 ` Anton Vorontsov
2008-09-02  7:35   ` Li Yang
2008-09-02  7:57     ` Joakim Tjernlund
2008-09-02  8:12       ` [PATCH] usb: add Freescale QE/CPM USB peripheral controllerdriver Li Yang-R58472
2008-09-02  8:15         ` Joakim Tjernlund
2008-09-24 20:28           ` David Brownell
2008-09-24 21:30             ` Joakim Tjernlund
2008-09-24 21:42               ` David Brownell
2008-09-24 20:26         ` David Brownell [this message]

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=200809241326.30167.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=LeoLi@freescale.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).