linux-kernel - Re: [linux-usb-devel] [PATCH] PXA27x UDC driver.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 10 Jul 2007 11:16:48 -0700
From:	David Brownell <david-b@...bell.net>
To:	Rodolfo Giometti <giometti@...eenne.com>
Cc:	Dmitry Krivoschekov <dmitry.krivoschekov@...il.com>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Li Yang-r58472 <LeoLi@...escale.com>,
	linux-usb-devel@...ts.sourceforge.net,
	linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: [linux-usb-devel] [PATCH] PXA27x UDC driver.

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/