From: David Brownell <david-b@pacbell.net>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Li Yang-r58472 <LeoLi@freescale.com>,
linux-usb-devel@lists.sourceforge.net,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [linux-usb-devel] [PATCH] PXA27x UDC driver.
Date: Tue, 10 Jul 2007 11:16:48 -0700 [thread overview]
Message-ID: <200707101116.48900.david-b@pacbell.net> (raw)
In-Reply-To: <20070709135109.GO11451@enneenne.com>
On Monday 09 July 2007, Rodolfo Giometti wrote:
> On Sat, Jun 30, 2007 at 06:46:14AM -0700, David Brownell wrote:
> >
> > Has someone actually signed up to develop and maintain such a
> > controller driver? If so, that would be a Fine Thing, but not
> > one I've heard rumored before. I've assumed that the best we'd
> > have is someone (Rodolfo?!) finally cleaning up a pxa27x version
> > so it could be merged.
>
> That's what I wish to do... I wish cleaning up as much possible my
> pxa27x version af the driver so we can have something common where we
> can work on.
Good!
> Sorry for the delay but in these next days I'll read back all your
> suggestions and I'll provide a new patch ASAP.
>
> However I would like avoiding to remove what I did on
> usb_ep_autoconfig() since I got functional g_ether device with RNDIS
> support... there could be another way to resolve this problem?
I *really* don't want to change the whole gadget stack just to
make one excessively quirky bit of hardware work with it ... when
we know there's a simple solution that doesn't involve that.
(Changing the whole gadget stack would involve retesting a boatload
of systems... not all of which are easily tested. Plus, those changes
would need far more review than they can get just now.)
So for now, just do what I outlined before: set up the pxa27x UDC
to resemble the pxa2[156] chips: a bunch of bulk endpoint with no
altsettings and acting the same in all three hardware-supported configs.
That will support RNDIS. In fact the only thing it _won't_ handle is
the "real CDC Ethernet" mode.
Once that's working, we can revisit the issue of how to configure
endpoint hardware ... focussing on just that issue, and with enough
flexibility that non-pxa27x hardware can also be addressed.
- Dave
next prev parent reply other threads:[~2007-07-10 18:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 10:36 [PATCH] PXA27x UDC driver Rodolfo Giometti
2007-06-28 11:15 ` Li Yang-r58472
2007-06-28 14:12 ` Rodolfo Giometti
2007-06-28 21:29 ` Andrew Morton
2007-06-28 22:44 ` David Brownell
2007-06-30 14:28 ` [linux-usb-devel] " David Brownell
2007-07-10 15:49 ` Rodolfo Giometti
2007-07-10 16:16 ` Lothar Wassmann
2007-06-28 21:53 ` David Brownell
2007-06-29 8:58 ` Rodolfo Giometti
2007-06-29 9:33 ` [linux-usb-devel] " Dmitry Krivoschekov
2007-06-30 14:25 ` David Brownell
2007-06-29 9:03 ` [linux-usb-devel] " Dmitry Krivoschekov
2007-06-30 13:46 ` David Brownell
2007-07-02 11:42 ` Dmitry Krivoschekov
2007-07-09 13:51 ` Rodolfo Giometti
2007-07-10 14:50 ` Vernon Sauder
2007-07-10 18:16 ` David Brownell [this message]
2007-06-29 17:04 ` Andy Isaacson
2007-07-01 14:55 ` Lennert Buytenhek
2007-07-01 15:00 ` Russell King - ARM Linux
2007-07-01 17:49 ` 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=200707101116.48900.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=LeoLi@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=dmitry.krivoschekov@gmail.com \
--cc=giometti@enneenne.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--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