On Mon, Feb 02, 2004 at 12:52:52AM -0500, [EMAIL PROTECTED] wrote:
>
> I'll apologize in advance for posting this to both users and devel, but it
> didn't get much attention on the users list.
>
> I have a Casio 2000ux camera that worked fine under linux through 2.4.22:
>
> Jan 28 00:44:54 local
I'll apologize in advance for posting this to both users and devel, but it
didn't get much attention on the users list.
I have a Casio 2000ux camera that worked fine under linux through 2.4.22:
Jan 28 00:44:54 localhost kernel: Vendor: Casio Model: QV DigitalCamera Rev:
9009
Jan 28 00:44
Phil Dibowitz wrote:
Alan Stern wrote:
Have you changed your computer hardware since you last were able to
use the camera? A change in the system speed or the USB controller
speed would explain your problem.
I tried my old 2.4 kernel and it didn't pick up any of my USB devices
either. Nothin
I am using USB8IN1 card reader and have been looking in usb mass storage
driver from some time. Can somebody tell me, name of the function which
performs actual data transfer to/from the device. Is it usb_stor_bulk_msg?
Also where the LUN is stored? For example, my device has 4 LUNs. How and
where
Alan Stern wrote:
Have you changed your computer hardware since you last were able to use
the camera? A change in the system speed or the USB controller speed
would explain your problem.
I tried my old 2.4 kernel and it didn't pick up any of my USB devices
either. Nothing about my system, hardw
Johannes (or anyone else who can help):
I could use some advice on tracking this problem down. You can follow the
entire discussion in the thread going forward from
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107550399505642&w=2
Basically the problem goes like this. The device (a digita
On Sun, 1 Feb 2004, Gene Heskett wrote:
> Can I toss out that I have one device on my usb bus that violates
> the hell out of this spec if that 4 Alt limitation is what it says:
> --
> T: Bus=03 Lev=02 Prnt=02 Port=03 Cnt=03 Dev#= 5 Spd=12 MxCh= 0
> D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 Mx
On Sun, 1 Feb 2004, Guennadi Liakhovetski wrote:
> On Sun, 1 Feb 2004, Alan Stern wrote:
>
> > The patch below is nearly the same as the last one, and you should test it
> > in the same way. What's new about it is that it prints out the values
> > stored in the "terminating TD". That's the Tran
http://sinaraevent.com/bbs/zipcode/6.htm
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.
Hi,
as promised, here is a new version of the 2.4 storage deadlock fix.
It does a few things.
1. usb_get_configuration() is used in the reset path
2. in the synchronous API the task state is set to early, as memory
allocations in usb_submit_urb() can change it.
Comments?
Regards
Hi,
Since about 2.4.21 I've been getting random and intermintent usb
modem disconnects, condition is more frequent with the EHCI module
loaded and/or when my usb speakers are on, dmesg with usb-ohci.c
debugging enabled and system logs are from 2.4.25-pre8 kernel. Thanks.
Steve Bangert
Please
On Sun, 1 Feb 2004, Alan Stern wrote:
> The patch below is nearly the same as the last one, and you should test it
> in the same way. What's new about it is that it prints out the values
> stored in the "terminating TD". That's the Transaction Descriptor at the
> end of the USB schedule, and it'
Alan Stern wrote:
Have you changed your computer hardware since you last were able to use
the camera? A change in the system speed or the USB controller speed
would explain your problem.
Nope. Exactly the same machine.
You are correct about the reset timing out. That section of code is
really
On Sunday 01 February 2004 12:07, Frank Barknecht wrote:
>Hallo,
>
>Alan Stern hat gesagt: // Alan Stern wrote:
>> On Sun, 1 Feb 2004, Frank Barknecht wrote:
>>
>> Maybe I'm to blame, since I wrote the code that rejects your
>> device. It seemed like a good idea (and it still does) to alert
>> peo
On Sun, 1 Feb 2004, Frank Barknecht wrote:
> Alan Stern hat gesagt: // Alan Stern wrote:
>
> > That's right. If you can boot a 2.4 kernel and look at either the
> > /proc/bus/usb/devices file or else the output from lsusb, you should be
> > able to see all the alternate settings for interface 1.
On Sun, 1 Feb 2004, Guennadi Liakhovetski wrote:
> Hm. I can't interpret results of the test. Looks like at least not every
> set_nxt_interrupt does produce one, but some do...
This is good. It shows that set_next_interrupt works up until the time
the camera fails, then it doesn't work.
> Hop
>From Linus Torvalds on Friday, 30 January, 2004:
>The bulk of this is an ACPI update, but there's USB, ia-64, i2c, XFS and
>PCI hotplug updates here too.
>Please don't send in anything but critical fixes until after the final
>2.6.2 release.
Hmm. I just tried 2.6.2-rc3 (after having tried 2.6.
Hallo,
Alan Stern hat gesagt: // Alan Stern wrote:
> On Sun, 1 Feb 2004, Frank Barknecht wrote:
>
> Maybe I'm to blame, since I wrote the code that rejects your device. It
> seemed like a good idea (and it still does) to alert people to problematic
> devices rather than ignore any errors and
On Sun, 1 Feb 2004, Phil Dibowitz wrote:
> Folks,
>
> I haven't used my camera since I was on 2.6.0-t9 (which worked), and I'm
> now trying on 2.6.1 and its not getting recognized when I plug it in
> (i.e. usually it attaches to the /dev/sda1 device, but it's no longer
> attaching to anything)
On Sun, 1 Feb 2004, Frank Barknecht wrote:
> Hi all,
>
> I'm currently testing various USB audio devices for a German magazine,
> among these there also is the M-Audio Quattro. Now this one, plus
> several other M-Audio devices like the Audiophile USB, has a known
> bug: It's doesn't work with ke
Hi all,
I'm currently testing various USB audio devices for a German magazine,
among these there also is the M-Audio Quattro. Now this one, plus
several other M-Audio devices like the Audiophile USB, has a known
bug: It's doesn't work with kernel 2.6. it isn't even seen by the
kernel and lsusb. Th
On Sat, 31 Jan 2004, Alan Stern wrote:
> Almost... The URB was a SetInterface command, and the driver was waiting
> for a Start-of-Frame interrupt -- but basically you're right.
Thanks for the clarification!
> That's the real question, and here's another patch to try. You should
> remove the o
Folks,
I haven't used my camera since I was on 2.6.0-t9 (which worked), and I'm
now trying on 2.6.1 and its not getting recognized when I plug it in
(i.e. usually it attaches to the /dev/sda1 device, but it's no longer
attaching to anything).
Generally the required modules are usb-storage, scs
23 matches
Mail list logo
