Hi,
I am working on an USB2 camera driver on Linux RH9,
kernel 2.4.20-xx. The driver works OK except that it
hangs the kernel when I hot-unplug the cable.
I found the hang happens as long as the urbs (bulk)
are submitted, even if the stream is not on. (In my
code, several urbs are submitted when
> First off, nice job. Thanks for sending this, but can you please send
> me a patch for 2.6? I need that before I can add this to the 2.4 kernel
> tree.
Of course :-)
> Some minor comments below:
>
> > +5. Driver installation
> > +==
>
>
>
> I don't think you need this
The device is reporting itself as a USB2 device at 480Mbps. I would be a
little surprised that a USB1 device would give 1MB/s (but I guess you said
it did), the maximum available is 12Mbps but there are overheads you need
to take out of that (generally you max you can see is 9Mbps which is a
little
well, if that's the case. there's not much I can do.
I would like to verify, if possible, that i'm not
doing something wrong on my part. How might i do
that, or is it for sure not the reader, but the card?
--- "Stephen J. Gowdy" <[EMAIL PROTECTED]>
wrote:
> Yes. Some cards are faster than other
Yes. Some cards are faster than others.
On Tue, 23 Sep 2003, Mr. Mailing List wrote:
> how do you mean, the 16mb card itself? Doesn't that
> kind of defeat the purpose of the reader being 2.0?:O
> --- "Stephen J. Gowdy" <[EMAIL PROTECTED]>
> wrote:
> > The bottleneck may the CompactFlash.
> >
>
how do you mean, the 16mb card itself? Doesn't that
kind of defeat the purpose of the reader being 2.0?:O
--- "Stephen J. Gowdy" <[EMAIL PROTECTED]>
wrote:
> The bottleneck may the CompactFlash.
>
> On Tue, 23 Sep 2003, Mr. Mailing List wrote:
>
> > I just copied the images using MToolsFM, but I
From [EMAIL PROTECTED] Tue Sep 23 16:05:21 2003
> Also "conservative mode" sounds like a flag that describes some
> way of being broken.
>
> On the other hand "hot-pluggable" describes a positive asset,
> and if we can conclude from that that it is unnecessary to ask
I tried the patch but it doesn't work for me using an USB-2 Memory stick
"DiskonKey" on an USB-2 port (with uhci_hcd & ehci_hcd loaded).
After a 3 minute time-out I get
"SCSI device sda: drive cache: write through"
and the device starts working just fine.
Unloading the ehci_hcd module doesn't
On Tue, 23 Sep 2003, Ruud Linders wrote:
>
> I tried the patch but it doesn't work for me using an USB-2 Memory stick
> "DiskonKey" on an USB-2 port (with uhci_hcd & ehci_hcd loaded).
>
> After a 3 minute time-out I get
> "SCSI device sda: drive cache: write through"
> and the device starts
First off, nice job. Thanks for sending this, but can you please send
me a patch for 2.6? I need that before I can add this to the 2.4 kernel
tree.
Some minor comments below:
> +5. Driver installation
> +==
I don't think you need this for the in-kernel documentation :)
>
On Mon, Sep 22, 2003 at 04:47:15PM +0200, Henning Meier-Geinitz wrote:
> Hi,
>
> Use static declarations for usb_scanner_init/usb_scanner_exit
> (Daniele Bellucci).
Applied, thanks.
greg k-h
---
This sf.net email is sponsored by:ThinkGeek
We
On Mon, Sep 22, 2003 at 04:50:20PM +0200, Henning Meier-Geinitz wrote:
> Hi,
>
> Balancing usb_register_dev/usb_deregister_dev in probe_scanner when a
> fail condition occours (Daniele Bellucci).
Applied, thanks.
greg k-h
---
This sf.net ema
On Mon, Sep 22, 2003 at 11:09:16AM -0400, Alan Stern wrote:
>
> Meanwhile, here's a simple patch to improve logging during suspend and
> resume. Greg, if David approves please apply it.
Applied, thanks.
greg k-h
---
This sf.net email is spo
On Mon, Sep 22, 2003 at 10:08:29PM +0200, Henning Meier-Geinitz wrote:
> Hi,
>
> On Mon, Sep 22, 2003 at 12:33:05PM -0700, Greg KH wrote:
> > On Mon, Sep 22, 2003 at 04:52:53PM +0200, Henning Meier-Geinitz wrote:
> > > @@ -961,6 +962,7 @@
> > >
> > > if (interface[0].desc.bInterfaceClass != U
On Tue, Sep 23, 2003 at 03:11:35PM -0700, David Brownell wrote:
> Minor updates:
>
> - Reduce memory utilization in two ways:
>
> * Dynamically, by pre-allocating all the usb_request objects
> that will be used; if the pre-allocated ones are in use,
> then tx will throttle down.
On Mon, Sep 22, 2003 at 04:51:35PM +0200, Henning Meier-Geinitz wrote:
> Hi,
>
> Added vendor/product ids for Canon, HP, Microtek, Mustek, Siemens,
> UMAX, and Visioneer scanners.
Applied, thanks.
greg k-h
---
This sf.net email is sponsored b
On Mon, Sep 22, 2003 at 04:49:00PM +0200, Henning Meier-Geinitz wrote:
> Hi,
>
> Report back return codes of usb_register and usb_usbmit_urb instead of
> -1 or -ENONMEM (Daniele Bellucci).
Applied, thanks.
greg k-h
---
This sf.net email is s
On Tue, Sep 23, 2003 at 02:54:38PM -0700, David Brownell wrote:
> Some small updates:
>
> - Sometimes read requests can be satisfied directly from
>the OUT fifo. This fixes a bug where the return code
>from usb_ep_queue() overwrite the transfer status, which
>in that case was set _be
Some small updates:
- Sometimes read requests can be satisfied directly from
the OUT fifo. This fixes a bug where the return code
from usb_ep_queue() overwrite the transfer status, which
in that case was set _before_ that call returned.
(Synchronous behavior; not the usual async comp
Alan Stern wrote:
On Fri, 19 Sep 2003, David Brownell wrote:
The tricky bits are recovering from "USB suspend" states ... which I
suspect usbcore should help with, to minimize the amount of code to
write into each HCD. Can't any hub suspend its ports? There are
things that are specific to root h
Minor updates:
- Reduce memory utilization in two ways:
* Dynamically, by pre-allocating all the usb_request objects
that will be used; if the pre-allocated ones are in use,
then tx will throttle down. This behaves better under
heavy load.
* Statically, by pre-allocati
The bottleneck may the CompactFlash.
On Tue, 23 Sep 2003, Mr. Mailing List wrote:
> I just copied the images using MToolsFM, but I did
> not, at all, see a difference in speed from my usb
> 1.1 device.
>
>
> T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3
> Spd=480 MxCh= 0
> D: Ver= 2.00 Cls=
I just copied the images using MToolsFM, but I did
not, at all, see a difference in speed from my usb
1.1 device.
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3
Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64
#Cfgs= 1
P: Vendor=0781 ProdID=9191 Rev= 1.19
S: Manufacturer
> Do I put the driver in the input directory and use the hid-core functions,
> or do I put it in the serial directory and use the usb-serial functions?
>
> At the time being, I have it in the serial directory and I am using the
> usb-serial functions. I added a few lines of code to the hid-core.c f
On Mon, Sep 22, 2003 at 05:44:49PM -0700, Neil Whelchel wrote:
> Hello,
> I am in the middle of writing a driver for the Cypress M8. This is a
> way-too-goofy USB to serial converter.
> I have a fairly clear understanding of what I need to do to make it work,
> but here is where I run into issues..
On Tue, 23 Sep 2003 [EMAIL PROTECTED] wrote:
>
> No, the design goal of "hot-pluggable" is that it indicates that
> the device can disappear any moment. Nothing at all about SCSI
> compliance.
You're talking past each other.
Server people think that "hot-pluggable" means "I will tell the system
On 23 Sep 2003, James Bottomley wrote:
> On Tue, 2003-09-23 at 09:37, [EMAIL PROTECTED] wrote:
>
> > Pulling out a device while it is actively reading or writing
> > will probably break something. But if a device is hot-pluggable
> > it should be OK to pull it out when it has been inactive for
>
On Tue, 2003-09-23 at 09:37, [EMAIL PROTECTED] wrote:
> No, the design goal of "hot-pluggable" is that it indicates that
> the device can disappear any moment. Nothing at all about SCSI
> compliance.
Actually, then, these are two issues...hotplug is being worked on
separately at the moment.
I tho
You'll get something like this;
[denise] ~ > usbtree
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=usb-uhci/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-hcd/5p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=usb-ohci/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driv
just check whether or not it says it's using ehci, or
it will say something about usb 2.0?(i ask this
because i don't have access to my linux machine at the
moment, but am on an XP machine).
thanks
--- "Stephen J. Gowdy" <[EMAIL PROTECTED]>
wrote:
> THere is a script here that'll tell you;
>
>
I know in test4 it was necessary to apply a patch, is
it still necessary in test5?
with 2.6test5, on boot
hub 1-0:0: new USB device on port 1, assigned address
2
drivers/usb/class/cdc-acm.c: ttyACM0: USB ACM device
Unable to handle kernel NULL pointer dereference at
virtual address 0040
THere is a script here that'll tell you;
http://www.linux-usb.org/usbtree
(this just scans /proc/bus/usb/devices but formats in an easy way to see).
On Tue, 23 Sep 2003, Mr. Mailing List wrote:
> sorry, that was dumb of me, but how can I make sure
> it's transferring at usb 2.0 speeds as oppose
sorry, that was dumb of me, but how can I make sure
it's transferring at usb 2.0 speeds as opposed to 1.1?
--- "Stephen J. Gowdy" <[EMAIL PROTECTED]>
wrote:
> It says it is sdb.
>
> On Tue, 23 Sep 2003, Mr. Mailing List wrote:
>
> > scsi5 : SCSI emulation for USB Mass Storage
> devices
> > Ve
On Mon, 2003-09-22 at 14:56, [EMAIL PROTECTED] wrote:
> I have seen proposals around here for flags that are far too specific
> (like "do not ask for mode page 8"). If we go to that level of detail
> then we'll soon have fifty flags.
> Black lists, and flags that describe various ways of being brok
sorry, forgot to say it's plugged into a usb 2.0 pci
card.
i have modules for uhci(for motherboard's 2 1.1
ports), ohci(i believe the card is ohci), and ehci.
thanks.
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebui
It says it is sdb.
On Tue, 23 Sep 2003, Mr. Mailing List wrote:
> scsi5 : SCSI emulation for USB Mass Storage devices
> Vendor: Generic Model: STORAGE DEVICERev: 0119
> Type: Direct-Access ANSI SCSI
> revision: 02
> Attached scsi removable disk sdb at scsi5, chann
scsi5 : SCSI emulation for USB Mass Storage devices
Vendor: Generic Model: STORAGE DEVICERev: 0119
Type: Direct-Access ANSI SCSI
revision: 02
Attached scsi removable disk sdb at scsi5, channel 0,
id 0, lun 0
Attached scsi generic sg1 at scsi5, channel 0, id 0,
lun 0
Title: POZ - PDA
■ 대용량
배터리(1400mAh) 사용으로 인한 더욱 길어진 사용 시간
■
우수한 확장성을 통한 다양한 기능(멀티미디어, 디지털 카메라, GPS)
■
첨단 기술이 만들어 낸 소형(129.5*70.5
38 matches
Mail list logo
