On Fri, 20 Aug 2004, Alan Stern wrote:
>
> You're right about the command sequences. Maybe what's going on is
> that either the USB controller on your computer or the controller on the
> camera is slightly out-of-spec, with the result that they don't work with
> each other but they each do work with other cameras/computers.
>
Obviously, it could be both which are slightly out-of-spec. As to the
camera, I cannot even be sure that S&Q Technologies (www.sq.tw) is even a
real manufacturer. Could even be the case that they package chips that
somebody else makes, and I have no way to find out. As to documentation,
there is practically none worthy of mention on their website, And they
even did not answer an official request a few months ago, concerning
how to dump the memory of the camera. The request was from the National
Forensic Institute of the Netherlands. Anyway without doing some testing
that I currently do not know how to do, I don't know if their chips are
within spec, or not.
But, as to VIA I have picked up a lot of discussion, and there are those
who claim there are problems with VIA USB implementation, especially with
some of their older chips. So I was wondering about that. I also have the
understanding that there has been a great deal of information given by VIA
to the kernel development people.
What I actually have is the VIA 82C686 chipset, and here's what lspci -v
says about my USB controllers:
00:14.2 USB Controller: VIA Technologies, Inc. USB (rev 10) (prog-if 00
[UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at d800 [size=32]
Capabilities: [80] Power Management version 2
00:14.3 USB Controller: VIA Technologies, Inc. USB (rev 10) (prog-if 00
[UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at dc00 [size=32]
Capabilities: [80] Power Management version 2
Sorry, I have no idea what is meant by "(Wrong ID)".
So if anyone has an idea where the problem might be addressed, I am
willing to try to tweak something in the USB setup.
>
> I don't think libusb is your problem. It just passes the program's
> requests to the kernel.
>
Well, that does further narrow things down, too.
Theodore Kilgore
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
