Oliver Neukum wrote:
Like this version better?
No, it still has that "arbitrary timeout" pessimization. The only
difference is a bigger timeout.
If progress in the typical case is clearly forward, the call will very
likely succeed. But that doesn't mean that the atypical case where
no progr
John Wilkins wrote:
Hi,
I've just read your posting to the usb-devel list. I too have an FTDI
based device (my internet provider uses it - strange, I know). I have
been using the ftdi_sio driver but can't get it to work above around
400k bits / sec even though my internet service is 1Mbit/s.
I'm developing a driver for a USB device and have the
user level driver working with libusb.
My problem is I want to make the kernel level driver
also and got stuck at a urb data transfer.
I'm doing DMA chunks of data using an array of urbs.
urb * write_urb[20];
I do the DMA write in a loop and I
This is a minor cleanup to let per-request memory allocations block,
when the caller allows (it provided the bitmask). The driver used
to work that way until something like 2.4.3; an update (a few months
back) to how the "dma_addr_t" hashes to a "struct ohci_td *" lets us
simplify things again. A
On Sun, Jan 19, 2003 at 05:16:02PM -0800, Matthew Dharm wrote:
> This patch goes on top of the last one. It fixes a typo in the test for
> scsi_register() failure.
With these two patches applied, when plugging in a usb-storage device I
get the following oops. So I've backed the changes out :)
A
On Mon, Jan 20, 2003 at 09:23:55PM +0100, Henning Meier-Geinitz wrote:
> Hi,
>
> This patch adds vendor/product ids for Artec, Canon, Compaq, Epson,
> HP, and Microtek scanners. Further more, the device list was cleaned
> up, sorted and duplicated entries have been removed.
Applied, thanks.
greg
I've applied all 6 speedtouch patches, thanks.
greg k-h
---
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linu
On Mon, Jan 20, 2003 at 09:21:46PM +0100, Henning Meier-Geinitz wrote:
> Hi,
>
> This patch adds vendor/product ids for Artec, Canon, Compaq, Epson,
> HP, and Microtek scanners. Further more, the device list was cleaned
> up, sorted and duplicated entries have been removed.
Applied, thanks.
greg
On Mon, Jan 20, 2003 at 11:17:09AM +0100, Duncan Sands wrote:
> speedtouch: simplify the receive urb lifecycle: allocate them in the usb probe
>function,
> free them on disconnect.
Oops, make that 7 patches applied :)
thanks,
greg k-h
--
Hi,
I am running Suse 8.1, Kernel 2.4.19. I have an Adaptec USB2 card and
Ikebana external hard drives. Booting gives me "starting hotplugging
services [net pci usb...].
My external drive then beeps. It works great !
Good to hear that. Though I'd plan on updating your kernel,
If I umount
I think I have already made the virtual root hub connect to the usbcore, but
after that,when I attach a device,I don't know what function(interrupt
handler?) is triggered. I've look at ohci_irq, but there is no case there
where it checks for the status of the root hub(the RHSC bit). Can you tell
On Wed, 22 Jan 2003, BLACKSON Jim wrote:
| The get_string routine of lsusb does not include the language ID in the USB
| request to get the string. Instead, get_string is setting the language ID
| field of the request to zero. Is there some reason for this?
|
| Section 9.4.3 of the USB 2.0 spec
Thanks, those are the ones I was thinking of.
--Doug
Randy.Dunlap wrote:
On Wed, 22 Jan 2003, Pei Liu wrote:
|
| >I've forgotton the name of the program or programs that can query a usb
| >device on a linux box and report on the usages, endpoints, etc. that it
| >finds. Can someone please re
> > Whose responsibility is it to fail these interactions?
>
> The transport.
>
> When a device is plugged to the SAN/fabric (wlg) it may not be the case
> that all initiators will know about it. For this reason the transport
> itself, not SCSI Core, not LLDD*, will decide if the CDB is deliverab
Am Mittwoch, 22. Januar 2003 22:32 schrieb Alan Stern:
> Here is my patch to implement proper timing of synchronous unlinks.
> Basically it just uses a spinlock to cause unlink requests during a
> completion handler to wait until the handler has returned before carrying
> out the unlink. This seem
Tyson D Sawyer wrote:
Though I'm not real useful when it comes to contributing code at this
time, I'd like to add my voice to those that feel the lack of decent
topological names has real user impact and limits usability.
For us it isn't printers, but rather serial ports.
Just for the record,
Luben Tuikov wrote:
When the Low Level Device Driver (LLDD), being the transport portal,
notices that the device is going away or has gone away from the
``fabric'' (wlg), it will fire a device-gone event with the kernel.
*Not* necessarily with SCSI Core, in fact I'd rather it didn't,
but with a w
On Wed, 22 Jan 2003, Pei Liu wrote:
|
| >I've forgotton the name of the program or programs that can query a usb
| >device on a linux box and report on the usages, endpoints, etc. that it
| >finds. Can someone please remind me?
| >
| >Thanks,
| >
| >--Doug
|
| you can access device information u
See my prior message for background.
Additions for hid-core.c blacklist.
Diffs for kernel 2.4.20 and 2.5.54 follow.
Thanks to all for their assistance.
John Homppi
Diff for 2.4.20
--- hid-core.c.orig 2003-01-22 16:37:55.0 -0500
+++ hid-core.c 2003-01-22 16:41:06.0 -0500
@@
Alan Stern wrote:
Here's another question to add to your discussion.
When a device is unplugged, the system's representation of that device
can't be removed immediately; there may be open fd's, mounts, pointers,
and so on. Until the time comes when all these handles are released, all
interaction
>I've forgotton the name of the program or programs that can query a usb
>device on a linux box and report on the usages, endpoints, etc. that it
>finds. Can someone please remind me?
>
>Thanks,
>
>--Doug
>
you can access device information using the usbdevfs. type the following
mount -t usbd
Here is my patch to implement proper timing of synchronous unlinks.
Basically it just uses a spinlock to cause unlink requests during a
completion handler to wait until the handler has returned before carrying
out the unlink. This seems like a pretty small and uninvasive sort of
change.
Alan
From: James Balcom <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
<[EMAIL PROTECTED]>
Subject: external hard drive swapping problem
Date: Monday, January 20, 2003 12:04 PM
Greg Kroah-Hartman suggested that I post this problem on linux-usb-devel:
I'm not a driver expert.
I am running Suse 8.1, Kernel 2
Thanks to all for the prompt, courteous and constructive comments.
I will re-do the diffs in correct format and resubmit them when ready.
(as Randy pointed out, I will include [EMAIL PROTECTED] in the address
list).
Thanks again,
John Homppi
---
I've forgotton the name of the program or programs that can query a usb
device on a linux box and report on the usages, endpoints, etc. that it
finds. Can someone please remind me?
Thanks,
--Doug
---
This SF.net email is sponsored by: Sch
Hi,
I am experiencing Greg's new tree failing to work with shared libraries.
Greg, have you smoked strange patches? Does anybody else see this?
Regards
Oliver
---
This SF.net email is sponsored by: Scholarships for Tec
On Wed, 22 Jan 2003, John Homppi wrote:
| I would like to expand the blacklist in the hid-core.c function.
| Is this the right place to send the changes?
Yes, but please send patches in "unified" (-u) format, i.e., use
diff -u oldfile newfile > patchfile
See linux/Documentation/SubmittingP
I would like to expand the blacklist in the hid-core.c function.
Is this the right place to send the changes?
Details
The ADU devices from Ontrak Control Systems do not support
bulk end-points and this prevents the existing HID routines from
talking to them. To allow a custom driv
This should apply to 2.5.59 too. It seems to get rid of some pesky
hangs, on at least some hardware, but I won't have time to test it
on either VIA version ... maybe someone else will make the time? :)
New QH state prevents a re-activation race
- nobody can un-halt a qh before its cleanup i
On Tue, 21 Jan 2003, Tom Collins wrote:
> When copying large amounts of data to a drive:
>
> Logs show:
>
> usb-storage: Command WRITE_10 (10 bytes)
> usb-storage: 2a 00 00 05 eb f0 00 00 40 00 2d 80
> usb-storage: Bulk command S 0x43425355 T 0x174a Trg 0 LUN 0 L 32768 F 0
> CL 10
> usb-storage
Alan Stern wrote:
What is the cause of all these problems relating to device resetting and
probing?
IMO the root cause was an assumption that there'd be only one
config, or at least only one usable. There are a number of
assumptions inside usbcore which turn up trouble when changing
device con
On Tue, 21 Jan 2003, Oliver Neukum wrote:
>
> > > It would be great if we could eleminate the need for handling unlinking
> > > during completion at all. Is there a reason you cannot make them mutually
> > > exclusive? IMHO it should be possible to do that if you make it a
> > > requirement to ca
Oliver Neukum wrote:
Ok one more question.
There are only 16 devices. But does this limit the driver to 16 physical
devices outside the computer?
Or can I handle more than 16 devices.
Yes and no.
If you register your own device, you can handle 256 devices. You can
repeat this process for
Am Mittwoch, 22. Januar 2003 13:54 schrieb Heinrich du Toit:
> Thanks for your quick reply.
>
> Oliver Neukum wrote:
> >>Question1: How do I make my device show up automatically in the devfs?
> >>or procfs?
> >
> >You register with devfs. To do so you need a call like this:
> > usblp->devfs = d
Hi all,
I just became the proud owner of the aforementioned external USB CD-RW drive.
It didn't work out of the box with my 2.4.20 or 2.4.21-pre3 kernels, but a
tip from Ralf Rösch helped me greatly.
He suggested the following addition to unusual_dev.h:
UNUSUAL_DEV( 0x07ab, 0xfc03, 0x, 0
Attached file:
Thanks for your quick reply.
Oliver Neukum wrote:
Question1: How do I make my device show up automatically in the devfs?
or procfs?
You register with devfs. To do so you need a call like this:
usblp->devfs = devfs_register(usb_devfs_handle, name, ...
in your probe method.
usblp ? sorry
Am Mittwoch, 22. Januar 2003 09:14 schrieb Rom M:
> Hi!,I've been working on an ohci usb host controller not yet supported by
> linux. I want to enumerate the device that is attached after I detect a
> connection on the root hub, the problem is, I don't know how to do it. Are
> there existing funct
> Question1: How do I make my device show up automatically in the devfs?
> or procfs?
You register with devfs. To do so you need a call like this:
usblp->devfs = devfs_register(usb_devfs_handle, name, ...
in your probe method.
> There doesn't seem to be much documentation on the fops par
> The suggestion is that someone who wants to teach the sl811 HCD how
> to use the "hcd.c" infrastructure should do so, but to do so on the
> 2.5 kernel (it has better testing infrastructure) in a way that's
> easily backported.
If I try that --- and I'm not sure I can do it, then I would need hel
Hi,
The get_string routine of lsusb does not include the language ID in the USB
request to get the string. Instead, get_string is setting the language ID
field of the request to zero. Is there some reason for this?
Section 9.4.3 of the USB 2.0 spec says this field should be the LANGID. See
a
Hi!,I've been working on an ohci usb host controller not yet supported by
linux. I want to enumerate the device that is attached after I detect a
connection on the root hub, the problem is, I don't know how to do it. Are
there existing functions that I will call in the kernel in sequence? Or do
42 matches
Mail list logo
