On Sat, Jul 21, 2007 at 02:47:22PM -0700, David Brownell wrote:
> On Saturday 21 July 2007, Rodolfo Giometti wrote:
> > I reworked the driver according to latest suggestions from you.
>
> ... except for the most important one, which is to remove the
> requirement to change
Hello,
as promised I just published my version of the driver for PXA27x USB
device controller.
You can find all references om my wiki at:
http://wiki.enneenne.com/index.php/PXA27x_UDC
I reworked the driver according to latest suggestions from you. It's
far from perfection but it's still func
On Thu, Jun 28, 2007 at 02:29:49PM -0700, Andrew Morton wrote:
> >
> > +
> > +static int
> > +write_packet(volatile u32 * uddr, struct pxa27x_request *req, unsigned max)
>
> Please review Documentation/volatile-considered-harmful.txt
The attibute volatile here is necessary in order to avoid getti
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
On Thu, Jun 28, 2007 at 02:53:22PM -0700, David Brownell wrote:
>
> Let's start with *JUST* a driver, not trying to update everything
> else in the USB Gadget stack so that it looks like it's designed
> specifically to handle all of Intel's design botches related to
> endpoint config ... and work
On Tue, Feb 27, 2007 at 10:36:20AM -0500, Jeff Lackey wrote:
> Alas, I must use usbser.sys on a Windows host and my gadget has a PXA270
> UDC. I'm running a 2.6.17 kernel with the pxa27x_udc driver dated
> 20-Nov-2006 and last modified by Rodolfo Giometti patched in. I checked
On Fri, Sep 01, 2006 at 11:07:14AM -0400, Alan Stern wrote:
> On Fri, 1 Sep 2006, Rodolfo Giometti wrote:
>
> > I see but:
> >
> > 1) the system may use the vendor & product ID, the product string and
> > serial number to identify the device reducing conflicts.
On Fri, Sep 01, 2006 at 10:30:41AM -0400, Alan Stern wrote:
>
> That's not possible. As far as the computer is concerned, after the
> resume there is a _new_ key plugged in. The old name is still in use,
> because it is mounted, so the new device _cannot_ be assigned the old
> name.
But it co
On Fri, Sep 01, 2006 at 10:06:02AM -0400, Alan Stern wrote:
>
> I don't understand what you are asking.
>
> usb-storage _does_ know when the system is resuming. It does not assign
> device names (sda, sdb, etc.) -- the SCSI disk driver does that.
> Remember, usb-storage handles all sorts of ma
On Thu, Aug 31, 2006 at 10:34:51AM -0400, Alan Stern wrote:
>
> Not if the USB ports lose power during the suspend. That's equivalent to
> keeping your rootfs on a USB key and then unplugging the key. It just
> won't work.
Ok, I see. So the devices must be re-enumerated, but in this situation
On Thu, Aug 31, 2006 at 03:36:42AM -0700, David Brownell wrote:
>
> USB on many system-on-chip processors also has less aggressive sleep
> states, where for example USB port power might be maintained, and
> the root hub clocked enough to detect simple events like "remote
> wakeup", "connect new de
Hello,
I'm working on sleep for USB host on au1x00 CPUs and I have the
following problem.
When I put the system to sleep and then it wakes up everything works
well _if_ the USB key is not mounted before the sleep. For instance,
if I mount partition "/dev/sda1" (first USB key partition) and then g
On Tue, Jun 13, 2006 at 09:00:51PM -0700, David Brownell wrote:
> On Monday 29 May 2006 6:29 am, Rodolfo Giometti wrote:
> > + .suspend = ohci_au1xxx_suspend,
> > + .resume = ohci_au1xxx_resume,
>
> You shouldn't add both the P
@@
* by Durgesh Pattamatta <[EMAIL PROTECTED]>
* Modified for AMD Alchemy Au1xxx
* by Matt Porter <[EMAIL PROTECTED]>
+ * Modified to add PM support
+ * by Rodolfo Giometti <[EMAIL PROTECTED]> on May 2006
*
* This file is licenced under the GPL.
*/
@@ -229,6 +231
14 matches
Mail list logo
