Re: [linux-usb-devel] 2.6.23-rc1-mm2

2007-08-01 Thread Paul Mackerras
Mariusz Kozlowski writes: Second issue as reported earilier allmodconfig fails to build on imac g3. Do you really mean g3? If so it's a 32-bit kernel and it shouldn't be building lparmap.s. Or do you mean G5? CC arch/powerpc/kernel/lparmap.s AS arch/powerpc/kernel/head_64.o

Re: [linux-usb-devel] 2.6.19-rc1: known regressions (v3)

2006-10-11 Thread Paul Mackerras
Adrian Bunk writes: Subject: sleep/wakeup on powerbooks apparently busted References : http://lkml.org/lkml/2006/10/5/13 Submitter : Benjamin Herrenschmidt [EMAIL PROTECTED] Handled-By : Benjamin Herrenschmidt [EMAIL PROTECTED] Status : Benjamin will investigate Should be fixed

Re: [linux-usb-devel] Re: Commit [PATCH] USB: Always do usb-handoff breaks my powerbook

2005-10-31 Thread Paul Mackerras
David Brownell writes: Maybe you should first pay attention to what I pointed out: that the problem reports I've seen have ONLY been on PPC systems. Well, there is a problem in the code which is clearly visible just by inspection: that it is touching a pci device without having called

[linux-usb-devel] Commit [PATCH] USB: Always do usb-handoff breaks my powerbook

2005-10-30 Thread Paul Mackerras
My G4 powerbook gets a machine check on boot as a result of commit 478a3bab8c87a9ba4a4ba338314e32bb0c378e62. Putting a return at the start of quirk_usb_early_handoff fixes it. The code in quirk_usb_handoff_ohci looks rather bogus in that it doesn't do pci_enable_device before trying to access

[linux-usb-devel] [PATCH] Make sleep/wakeup work with USB on powerbooks

2005-03-16 Thread Paul Mackerras
I am currently using this patch on my powerbook to fix the problems that USB was causing with sleep and wakeup. Basically one of the USB controllers was getting a spurious wakeup immediately when put it into the suspend state. This would cause the resume routine to be run after we had turned off

[linux-usb-devel] [PATCH] Fix USB suspend in 2.6.0-test6

2003-10-05 Thread Paul Mackerras
In drivers/usb/core/hcd-pci.c, the code forgets to set hcd-state to USB_STATE_SUSPENDED on suspend. The effect is that on resume, the code refuses to wake the HCD up, and instead prints a message saying the interface hasn't been suspended. The patch below fixes this. It is against 2.6.0-test6.

[linux-usb-devel] Re: PATCH: (as31) USB root hub polling stops after suspend

2003-08-08 Thread Paul Mackerras
Alan Stern writes: How does this work? It's a smaller change, against BK-current. But maybe David will prefer to change ohci-pci.c instead. It works fine, and I have been using it for a while now. This, or something similar, needs to go in, since others have been complaining about the

[linux-usb-devel] Re: PATCH: (as31) USB root hub polling stops after suspend

2003-06-24 Thread Paul Mackerras
Alan Stern writes: The following patch addresses the problem the Paul raised, concerning whether the root hub status irq timer should be allowed to run during a suspend. I'm not sure that this does exactly what you would like. My reasoning is that the timer should run as long as the URB

[linux-usb-devel] USB root hub polling stops after suspend

2003-06-05 Thread Paul Mackerras
I'm running a 2.5.70 kernel (BK from a day or so ago) on my Apple titanium G4 powerbook, and it seems that the system stops polling the root hub registers when I suspend and resume the machine. The symptom is that nothing happens when I plug in a USB device after resuming. It's very annoying

[linux-usb-devel] problems with recent OHCI changes

2001-04-22 Thread Paul Mackerras
The recent changes to the usb-ohci.c driver in 2.4.4-pre5 seem to be causing serious problems on my G4 Cube powermac. I haven't tracked down exactly what the problem is, but the symptom is that I get an OHCI unrecoverable error; using the USB speakers seems to trigger this very quickly. The USB

Re: [linux-usb-devel] Keyspan copyright question

2001-04-16 Thread Paul Mackerras
Alan Cox writes: The question that wants asking is: Is the permission included sufficient to include the firmware as a mere aggregation. I think the concern is really the statement that says that the firmware "may not be reproduced, used, sold or transferred to any third party without