Re: [pwc] Does the saillard pwc driver work on amd64?

[matthieu castet <>]

Hi,

Sebastian Barthelmess wrote:
> Trust me!  I'm a developer, this driver is broken with ohci. I am certain I
> am using the correct driver for this webcam!  READ from my first post: "I
> have tons of other computers kicking around and it [this driver] works on
> all of them (with the same kernel versions)."
>
> As to the camera name, it's the Philips PCVC680 Vesta Pro webcam.  Again, I
> am POSITIVE it is an issue between the pwc module and the ohci module.  My
pwc driver shouldn't care if it is uhci or ohci.
It should be related to your hardware or ohci host controller driver.

> USB mouse works fine under ohci, so I know that ohci is functioning - you
> can see it in the log I posted previously: (usb 3-1: Product: PS2/USB
> Browser Combo Mouse).
Yes but a mouse and a webcam are very different device :
- different power consomation
- different urb type
- ....


> ++GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES CCS
> ++usb 3-2: device descriptor read/64, error -110
> ++ohci_hcd 0000:01:00.1: urb ffff81003fd90600 path 2 ep0in 5ec20000 cc 5 -->
> status -110
> ++ohci_hcd 0000:01:00.1: urb ffff81003fd90600 path 2 ep0in 5ec20000 cc 5 -->
> status -110
> ++ohci_hcd 0000:01:00.1: urb ffff81003fd90600 path 2 ep0in 5ec20000 cc 5 -->
> status -110
>
> I am currently researching this "error status -110".  Please let me know if
search in Documentation/usb/error-codes.txt ...

-ETIMEDOUT (**)         No response packet received within the prescribed
                        bus turn-around time.  This error may instead be
                        reported as -EPROTO or -EILSEQ.

                        Note that the synchronous USB message functions
                        also use this code to indicate timeout expired
                        before the transfer completed.

(**) This is also one of several codes that different kinds of host
controller use to to indicate a transfer has failed because of device
disconnect.  In the interval before the hub driver starts disconnect
processing, devices may receive such fault reports for every request.



Maybe your controller don't provide enough power...


Matthieu
_______________________________________________
pwc mailing list

http://lists.saillard.org/mailman/listinfo/pwc