Hi,
I am new to USB world and looking for clarification on usb
printer's
behavior when transferring data with size multiple of wMaxPacketSize.
I have been running redhat 7.1 (linux kernel 2.4.2-2) on a x86 PC with a
USB 1.1 controller. There is a target mode printer driver running on the
Hi,
I am working on linux kernel 2.4.18. OHCI HCD. I have
the following doubt:
When the device enumeration fails (usb.c: USB device
not accepting new address), usb.c sets the devnum
field ( in the device data structure) to -1 and calls
the dev->bus->op->deallocate(dev);
This inturn calls sohci_f
On Mon, Mar 24, 2003 at 12:16:29PM -0700, Pat LaVarre wrote:
> In particular, passing CDB's thru sg will mark them
> Required, until/ unless we rev sg to let its client
> choose to say Required or not?
That was my intent, at least. The assumption being that a userspace
program should have done an
> > On Sat, Mar 22, 2003 at 11:39:05PM -0800, Linus
> > Torvalds wrote:
> >
> > > How about making the SCSI stuff pass a "common"
> > > flag (or "required") down with the command?
> > > Then, a emulated thing could just decide to
> > > punt all commands with an immediate failure if
> > > they aren'
shino korah wrote:
Hi
I'm using 2.4.18-3 (Redhat 7.3) . I have a USB 2.0
device which does DMA read and write. My problem is my
dma usb read is very very slow. Is it because my
kernel doesn't support bulk queuing for read?
When you say you have such a DMA device, what do you
mean: (a) Linux in
On Mon, Mar 24 2003, Pat LaVarre wrote:
> > For sd, we gauge the size of the command from the
> > size of the medium: <1Gb=> six byte, from 1Gb to
> > 2Tb 10 byte, over 2Tb 16 byte
>
> By now this theory we have completely disavowed?
Yes it was wrong, see earlier posting.
(BTW, top posting suc
> For sd, we gauge the size of the command from the
> size of the medium: <1Gb=> six byte, from 1Gb to
> 2Tb 10 byte, over 2Tb 16 byte
By now this theory we have completely disavowed?
I haven't seen our English yet mention that asking to
read/write more than xFF blocks triggers us to skip
past
On Mon, Mar 24, 2003 at 09:15:57AM -0600, James Bottomley wrote:
> On Mon, 2003-03-24 at 01:04, Matthew Dharm wrote:
> > Note that MODE_SENSE isn't on this list. How does the 'popular OS' test
> > for write-protect, you ask? It tries to write and then looks for a
> > failure, AFAICT.
>
> We use
On Mon, 2003-03-24 at 10:29, Linus Torvalds wrote:
> Really? The code was _supposed_ to always start off with READ/WRITE_10's,
> and then fall back to the old READ/WRITE_6 if it gets errors from that. Do
> we really have some broken random-number generator semantic still in teh
> SCSI layer? That
speedtch.c | 110 -
1 files changed, 51 insertions(+), 59 deletions(-)
diff -Nru a/drivers/usb/misc/speedtch.c b/drivers/usb/misc/speedtch.c
--- a/drivers/usb/misc/speedtch.c Mon Mar 24 18:00:56 2003
+++ b/drivers/usb/misc/speedtch
Hi
I'm using 2.4.18-3 (Redhat 7.3) . I have a USB 2.0
device which does DMA read and write. My problem is my
dma usb read is very very slow. Is it because my
kernel doesn't support bulk queuing for read?
My DMA USB write takes 20ms whereas read takes 350ms.
Any help will be appreciated
--Shin
On Mon, 2003-03-24 at 10:52, Jens Axboe wrote:
> It's not true, ->ten is set unconditionally and we only fall back to 6
> byte cdb's if we see an ILLEGAL_REQUEST on a READ_10/WRITE_10.
>
> So the logic is, always assume 10-byte commands. If an incoming request
> cannot be addressed with 10-byte co
On Mon, Mar 24 2003, Linus Torvalds wrote:
>
> On 24 Mar 2003, James Bottomley wrote:
> > >
> > > For disk-like media:
> > >
> > > READ_10
> > > WRITE_10
> >
> > We do about the best we can for read and write. For sd, we gauge the
> > size of the command from the size of the medium: <1Gb=> si
On 24 Mar 2003, James Bottomley wrote:
> >
> > For disk-like media:
> >
> > READ_10
> > WRITE_10
>
> We do about the best we can for read and write. For sd, we gauge the
> size of the command from the size of the medium: <1Gb=> six byte, from
> 1Gb to 2Tb 10 byte, over 2Tb 16 byte, so I think
Surely this patch (which calls hotplug for each interface on a device,
rather than once for the whole device) is going to break plenty of
hotplug scripts! It broke mine... Worse, there doesn't seem to be
a simple way to fix existing scripts. At least in 2.5 you can rummage
around in sysfs and wo
On Mon, 2003-03-24 at 01:04, Matthew Dharm wrote:
> Well, here's my list of what the 'popular OS' uses for all devices:
>
> INQUIRY (for only 36 bytes -- nothing else!)
> TEST_UNIT_READY
> REQUEST_SENSE
> ALLOW_MEDIUM_REMOVAL (mostly for eject purposes)
>
> For disk-like media:
>
> READ_10
> WRI
Patch against 2.5.65
regards
Oliver
> -Ursprüngliche Nachricht-
> Von: Greg KH [mailto:[EMAIL PROTECTED]
> Gesendet: Samstag, 22. März 2003 02:27
> An: Spang Oliver
> Cc: '[EMAIL PROTECTED]'
> Betreff: Re: [linux-usb-devel] Compiler error in cdc-acm when DEBUG
> defined
>
>
> On Fri, Ma
On Mon, 24 Mär 2003, Duncan Sands wrote:
> > Do you have any idea what may be the reason for this hang? The problem
>
> Does the whole system hang, or just the tool?
Just the tool, and it does not hang in the sense it does not return,
but not reading reasonable stuff and terminating after to many
Remove dead code from sarlib, reorganize live sarlib code (trivial transformations).
speedtch.c | 312 +++--
1 files changed, 100 insertions(+), 212 deletions(-)
diff -Nru a/drivers/usb/misc/speedtch.c b/drivers/usb/misc/speedtch.c
--- a/dr
> Do you have any idea what may be the reason for this hang? The problem
Does the whole system hang, or just the tool?
Thanks,
Duncan.
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Hi list, hi Nemosoft!
Chris Cheney bugged me for a bug I submitted long ago against usbutils
package (debian), and the bug is still present, but it looks like it is
a pwc/usb-subsys problem:
PWC webcam, lsusb -v breaks:
$ dpkg -l usbutils
ii usbutils 0.11-1 USB console utilities
$
21 matches
Mail list logo
