At 16:52 02.05.2006, Alan Stern wrote:
On Tue, 2 May 2006, Sancho Dauskardt wrote:
>
> when heavily pollig usb-storage devices with a TEST_UNIT_READY
> command and then removing the device occasionally causes an Oops
near khubd.
> Tried on Kernel 2.6.11.1 and 2.6.16.11.
...
Fr
Hi all,
when heavily pollig usb-storage devices with a TEST_UNIT_READY
command and then removing the device occasionally causes an Oops near khubd.
Tried on Kernel 2.6.11.1 and 2.6.16.11.
To reproduce, run following on a multi-lun card-reader:
- snip
while [ 1 ]; do
sg_tu
Hi,
FWIW, the attached patch gets my usb-serial toys working behind a USB 2.0
Hub under 2.4.26.
- sda
> You could work around that with this driver, making it use
> 2msec and 4msec periods.
It didn't work out, at least in 2.6 it still fails with 2 & 4. It's not a
big deal, just FYI.
Unfortunate
Hi,
T: Bus=05 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0d7d ProdID=0240 Rev= 1.00
S: Manufacturer=
S: Product=USB Reader
S: SerialNumber=0333020003A8
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #
At 22:05 26.05.2004, Gregory Gulik wrote:
I will re-build the kernel with USB debugging and will get back to you.
Please also post the contents of /proc/bus/usb/devices
- sda
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the
Hi,
I'm getting -ENOSPC when opening /dev/ttyUSB0 with following setup:
PL2303 --> USB 2.0 TT hub (Cypress CY7C65640) --> ehci PCI Card (NEC)
No other devices.
dmesg says:
pl2303.c: pl2303_open - failed submitting interrupt urb, error -28
Incase it helps, my pathetic debuging attem
Hi all,
attached is a patch against 2.4.25 for the Adaptec USB2Xchange USB 2.0
--> SCSI converter.
This does two things (two kernel config options):
1. Send Adaptec binary firmware (extracted from adpusbld.sys) to 0x03f3 /
0x2002
The protocol used for firmware upload is pretty much cypress EZ
At 10:52 01.04.2004, Brad Campbell wrote:
Alan Stern wrote:
On Wed, 31 Mar 2004, Brad Campbell wrote:
Well, I installed USB-Snoopy and guess what!
I can reproduce the lockups under windows on both machines, UHCI, EHCI
and OHCI interfaces.
I have just sent an E-mail to Vipower (The vendor of this
At 15:47 09.03.2004, Jesse Marlin wrote:
On Tue, 09 Mar 2004 00:05:34 +0100, Sancho Dauskardt <[EMAIL PROTECTED]> wrote:
At 23:53 08.03.2004, Jesse Marlin wrote:
[...]
Much too short. You're looking for something like this (in this case
parts of the USB2-XCHANGE firmware loader):
At
At 23:53 08.03.2004, Jesse Marlin wrote:
[...]
Much too short. You're looking for something like this (in this case
parts of the USB2-XCHANGE firmware loader):
At this point the device is already streaming audio/video and I see no other
traffic. With yours do you actually see this new device sho
At 22:24 08.03.2004, Jesse Marlin wrote:
On Mon, 08 Mar 2004 21:16:08 +0100, Sancho Dauskardt <[EMAIL PROTECTED]> wrote:
At 20:34 08.03.2004, Jesse Marlin wrote:
I have a USB 2.0 device (Adaptec AVC-2210 Audio/Video Capture) which I
want to write some deice drivers for. I have looked a
At 20:34 08.03.2004, Jesse Marlin wrote:
I have a USB 2.0 device (Adaptec AVC-2210 Audio/Video Capture) which I want
to write some deice drivers for. I have looked at past posts and some links
and have a pretty good idea of how to proceed, however my attempts to sniff
the device thus far have fail
dmesg with patch to fix VIA babble problem
http://virtual.shia.ws:8000/~informatica/otros/dmesg-withpatch3.txt
Hm, first machine where the bit already seems to be set.
Could you post a "lspci -v" for that machine ?
Also what BIOS is it running ?
Thanks,
- sda
---
...
> Please try the patch and let me know what happens.
Well, it didn't get worse, but it didn't get better either, I'm afraid.
What was this supposed to do? I didn't find byte 0x40 in UHCI specs...
Yes, I did get the message "babble workaround applied".
Could you please send lspci -v and logs of
[babble...]
That's liberal use of the term "feature", but this VIA problem is known.
I think even usb-uhci.c has a workaround for it (I don't know how well
it works).
Do you mean the Watchdog thing as in ehci ? IIRC there was a watchdog patch
floating around, but it never made it into the kernel
At 22:38 01.02.04 -0500, Alan Stern wrote:
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 prob
> Has anyone looked at why the reset failed? I assume that would clear the
> sense.
How could anyone attempt to find out why the reset failed?
Just some ideas:
a) not supported - AFAIK many storage devices don't seem to support the
bulk-reset, as the 'Other Popular OS' doesn't seem to issue them.
Hi,
fighting with a storage deivce which babbles bady under certian error
contitions, I stumbled over the open issue with VIA Chips + Babble (they
freeze internally).
Somwhere along 2.5.15 the alternate uhci driver got a watchdog feature to
reanimate dead uhci's. The two 2.4 uhci's and the rem
> > You must be a CompSci guy.
>
>Even worse: a mathematician.
Not by chance working on a digital camera kiosk project ???
> > An EE would have disassembled the device long before now
>
>In fact I opened it. The outside had no markings at all.
>Inside there were strings "HT B 94V-O" with fat "H
>
>Last Tuesday ("Queens Birthday" - a holiday in Holland)
>I did the reading part, and this evening the writing part
>for this animal. I see that you also did reading, more or
>less in the same way, but you did not have writing code?
Yep, me lazy animal. For our app we only needed read-access,
>
> > Forget datafab.c for this, as the protocoll is a little different.
>
>Hm. I used datafab.c successfully for the CF side.
>What precisely is different?
It's a while ago, but if I remember correctly, the ACOMdATA (actually
OnSpec Inc.) chip
has two short bulk data packets waiting to be read
>
> p.s. got a cat /proc/bus/usb/devices of the reader for us ?
>
>...
>
>P: Vendor=0c0b ProdID=a109 Rev=17.08
>S: Manufacturer=ACOMdATA
>S: Product=USB CF+SM
>P: Vendor=0c0b ProdID=a10c Rev= 2.00
>S: Manufacturer=ACOMdATA
>S: Product=USB SD+MS
Ah, that beast !
Check http://www.dauskar
>Of course I can have a special driver that knows that the SmartMedia
>extra data is at some given offset in us->extra, but otherwise
>this driver is completely identical to the driver of some other
>reader that only reads one type of card.
i.e. you want to use datafab.c for lun #0, but you own
>Is Linux can support multi-slot mass storage card reader??
>Because I have a multi-slot mass storage reader.
>When I plug in the device on Linux Red Hat 7.2 (kernel is 2.4.9)
>I can find the device correct at var/log/message but when I mount the
>device it is fail.
>So I want to know is Linux ca
Hi,
when using hub.c's usb_reset_device() on somthing connected to the
virtual root hub, the device 'dissapears' from the bus, instead of getting
reset.
With the device in question, the 'Connection' bit breaks away for a few ms.
As the uhci / usb-uhci virtual root hub signals all changes, h
>
> > If you say it's there, I'll believe you. On the other hand, if some kind
> > person would send me the source for hub.c I could check for myself. ;-)
>Looks like the delay is 10ms, not 100. [From hub.c, 2.4.18pre4]
>
>There is a 400ms delay for low speed device connection as well
Well I do
>...
>
>The obvious intention is to give kind of help for drivers to deal with
>devices which do return request_error (EP0-STALL) for SetInterface request
>on interfaces with single AS - as described in 9.4.10. However, I think
>this implementation has the potential to break USB standard conforma
After winning the reset fight with the OnSepc 90C36-LC1, I found a
different but related problem for the DataFab ML4-USB: an plain
usb_reset_device() doesn't change anything.
BUT, if I disable the connecting hub's port first, then wait 200-300 ms
before calling usb_hub_port_reset() it works gre
This resets the OnSpec 90C36-LC1 nicely now.
- sda
--- usb.c.vanilla-2.4.17Sat Jan 12 20:42:03 2002
+++ usb.c Sat Jan 12 20:45:45 2002
@@ -1952,6 +1952,14 @@
return -EINVAL;
}
+ /* 9.4.10 says devices don't need this, if the interface
+ only
While inverstigating, why usb_reset_device() doesn't work for me, if found
out that the OnSpec 90C36-LC1 can't handle usb_set_interface(). Since it
only has one interface (any only 1 alt-setting), i guess the asic designers
were to lazy to implement this.
For the first connection of a device t
>Methods (b) and (c) should both work. If (b) isn't working, the device
>must have crashed it's internal firmware pretty badly.
To true: i have to send the bulk urb's with a timeout, and then do the ugly
reset on -ECONNABORT.
If i don't set a timeout it hangs forever. No ETIMEDOUT, no EPIPE. B
Hi all,
in writing a driver for the OnSpec 90c36-LC1 CF/SM/MS/SD controller (aka.
DataFab 0xA109), I am currently stumbling over a big problem:
how should you really reset a device, for which no known reset command
exists (eg. after a card has been removed during a read access, and the
con
>A 10 second delay will cause the scsi error handler thread to fire. This
>should cause all sorts of things to happen, but often winds up resulting in
>a deadlock -- not just with usb-storage, but with lots of SCSI controllers,
>too.
10 seconds ?? Can this be changed somwhere in the Kernel easil
>
>At least 2.4.5-ac6 still generates this kernel hang, and can be made
>to do it for full speed devices too.
>
>How to reproduce with usb-storage and a USB 1.1 device and any
>host controller (well, at least all combinations I've tried):
>
> - add to usb-storage/transport.c, about line 1145,
>
>I've the same problem, my device driver ue a carry chips too. In november,
>i've
>ask how to solve this problem. For my driver (HH501, look last week archive),
>you load the firmware and the driver renumerate itsef. Then you can use
>it. For
>using this device, you can boot under windows, reb
> The HCD developers are
>trying pretty hard to fix all the bulk urb queuing bugs, so your help
>would be much appreciated. Have you applied the recently posted patches
>for uhci and usb-ohci. I think there might have been a usb-uhci patch,
>too,
>but I'm not sure.
Of course i'm using all th
Hi all,
attached is a patch against 2.4.4. for the 0x7CC Vendor ID family of card
readers (www.carry.com.tw).
These things are sold under all sorts of names (Lexar, PSI, Pixo-media...).
WARNING: kernel hacking & usb experience needed to get this going !
What the driver can do:
* R/W Compact
> I'm now starting to write a driver for DataFab Compact Flash+SmartMedia
> USB reader. Now I lack the technical information for the DataFab USB
> reader chipset. Heard that somebody has worked with similar chipset
> before, so could somebody help me providing the technical information???
Ch
>
>Is there a reason you can't submit the read urb to ep 2 before sending
>the command to ep 4? Or, how about having the completion handler for ep
>4 submit the read urb to ep 2? Then you _know_ the write command
>completed before trying to read (you can't rely on the status !=
>EINPROGRESS as
>Well, what can i say. mount'ing the 64MB SmartMedia now takes 8.5 sec (vs
>16.6) !
>But a 'cat /mnt/sm/* >/dev/null' still freezes the machine after 10-20 sec.
>I've tried it with both uhci + usb-uhci (2.4.4). Basically this is the
>same behavior as what i described under "a)" - except that th
> > Trying to optimize following sequence:
> > - send command to bulk ep 4. I call this the 'master-urb'
> > - recieve data from bulk ep 2. I call this the 'slave-urb'
>
>Is there a reason you can't submit the read urb to ep 2 before sending
>the command to ep 4?
Good idea...
Well, what can i s
Once again the turn-time issue, which is really serious for the usb-storage
device i'm fighting with, since it can only do max 4k transfers (again this
EZ-USB thing that doesn't enumerate and therfore doesn't change the
interfaces).
Trying to optimize following sequence:
- send command to bulk
> > The device I have, doesn't ReEnumerate upon new firmware, it just starts
> > working.
>
>A EZUSB device that doesn't ReEnumerate? That's their claim to fame! :)
>(and their patent, but that's a different issue.)
Yes, EzUSB for sure. I have a 'compatible' OEM device, which was sold with
dif
> Here is a first draft of a userland program for loading
>EZUSB "firmware" automatically through the hotplugging system.
>This should not only fix the copyright problems, but will also
>make the kernel a bit smaller and make it easier to but EZUSB device
>devlopment.
I need to do the sa
I had major performance problems reading the SSFDC mapping table: that
involed to usb_stor_bulk_msg() for each of the 4096 blocks and took around
17 sek (and only around 6 sek same device under Win98 ).. I guessed that
this could possibly be a schedluing issue, and tried following:
master_XXX
> > What happens when swapping different size CompactFlash cards ?
>
>It appears that, if a TEST_UNIT_READY fails with the right sense data to
>indicate a media-change, the disk is re-validated. But don't quote me on
>that...
Sounds good, but in a mount,umount,mount sequence only one TEST_UNIT_
>
>Re-reading the mapping:
>
>That's a problem. I'm not familiar enough with the way SCSI works to know
>how to tell it that the media changed. And if it knows that the media
>changed, will it get the capacity again? If no-one knows the answer to
>this off-hand, I'll read the source and find o
>>* when should the mapping table be rebuilt ?
>>START_STOP time & ALLOW_MEDIUM_REMOVAL time aren't quite suitable...
>>Or ist there just an easy mount option which forces READ_CAPACITY to
>> always be called ?
>
>Dunno... This is probably related to the "mount/umount/mount" problem in
>
>They are deprecated anyway since they don't use the same
>voltage as newer ones (ie all the new smartmedia readers
>since at least 1 year or more can not use them)
Um, sorry to object, but:
Dev-ID:
E8,EC -> 1MB-3.3V
6E -> 1MB 3.3V or 5V
EA -> 2MB-3.3V
64 -> 2MB-5V
E5 ->
I see it's not that easy to get a generic & fast abstract support for the
different command sets.
Check out the ssfdc_xx.x files attached. I'm still waiting for approval
concerning the NDA, so only some bits on the real driver included.
Stil some more problems:
* when should the mapping table
I'm currently waiting for an O.K. on publishing the Carry-specific bits.
But until I (hopefully) get that, I'll publish the ssfdc_info.c &.h
Since I'm new to Linux-USB, where should I send the source to (~20K) ?
>I've been trying to work on write-access, hoping to have it done by the
>end of th
Hi all,
I'm currently writing a driver for some Carry USB
CompactFlash/SmartMedia/MemoryStick Card readers (www.carry.com.tw,
USB-Vendor 0x7CC). I have some doc's under NDA and the CompactFlash part is
already working quite nicely under 2.4.2.
Now I'm doing the SSFDC stuff. Of course I coul
52 matches
Mail list logo
