Re: [linux-usb-devel] Quickcam 4000 pro

Sorry, it's not the good mailing-list. Cyril Scetbon wrote: Hi all, I would like to get feedback about using this webcam under linux. Which soft was used ? Have you succeeded in communicating with windows users? (gnomemeeting, others ?) In using the integrated micro (feedback from others webcam ar

Re: [linux-usb-devel] OHCI driver for SL811HS chip

On Tuesday 07 September 2004 2:17 pm, Lothar Wassmann wrote: > Hi, > > here is a kernel [2.6.8.1] patch, that converts the SL811HS chip into > an (more or less) OHCI compatible host controller. It has been > developed and tested on a PXA255 platform, but should be easily > adoptable to other platf

[linux-usb-devel] Re: No disconnection with net2280

On Tuesday 07 September 2004 1:24 pm, Alan Stern wrote: > David and Alex: > > For a while now I've been seeing strange things with the net2280 driver. > When I rmmod the g_file_storage gadget, the connection isn't dropped. Not > even when I rmmod net2280. I actually have to unplug the cable b

Re: [linux-usb-devel] Request for Review

On Thu, Sep 02, 2004 at 08:43:23PM +0200, Hermann Kneissel wrote: > > The current version of my driver to connect a garmin gps receiver > is available here: > > http://cvs.sourceforge.net/viewcvs.py/garmin-gps/kernel/garmin_gps.c > > can someone review it and tell, if there are obvious problems

Re: [linux-usb-devel] Knowing when a device is removed...

On Fri, Sep 03, 2004 at 12:32:38AM +0700, Gustavo Amador Rios wrote: > Hi there. > > Do you know if there is some mechanism to get notification when a > device is unplugged through HOTPLUG? Yes, the hotplug call itself :) Look at /sbin/hotplug for documentation on how to add your script to get c

Re: [linux-usb-devel] HCD question: how to register multiple ports

On Wed, 8 Sep 2004, Kyle Harris wrote: > Can I look at urb->dev->devpath? It looks like this is constant and refers to > the port number? That's a great idea! It never would have occurred to me. Yes, the first character of that string will always be the port number below the root hub (so eith

Re: [linux-usb-devel] [PATCH] - ftdi_sio usb_kill_urb(), DTR handling

On Wed, 8 Sep 2004, Jan Capek wrote: > I also checked, how the read URB's are resubmitted, the logic in the > driver is correct. The upper layer (usb-serial.c) calls ftdi_close, only > when the port->open_count <= 0. The function ftdi_process_read(), that is > issued by the completion handler (ftd

[linux-usb-devel] Re: unusual_devs.h entry

On Thu, 26 Aug 2004, Martin Ehmsen wrote: > Hi... > > I had to add the following entry to drivers/usb/storage/unusual_devs.h > to get my Jens of Sweden MP-130 mp3/ogg player working under 2.6.8.1: > > --- /usr/src/linux-2.6.8-rc4/drivers/usb/storage/unusual_devs.h > 2004-08-11 08:44:31.000

Re: [linux-usb-devel] HCD question: how to register multiple ports

On Tuesday 07 September 2004 07:01 pm, Alan Stern wrote: > > The easiest thing for now is to ignore the second port in each pair. > Unless you can specify in a TD that it should use both ports? Can I look at urb->dev->devpath? It looks like this is constant and refers to the port number? Thank

[linux-usb-devel] PATCH: (as365) Unusual_devs entry for Panasonic cameras

Greg & Pete: Thanks to Tom Hughes for jogging my memory about this patch, which has been sitting here waiting for Greg's return. It adds an unusual_devs.h entry for the Panasonic DMC-LCx line of cameras, which incorrectly report the total number of blocks in response to READ CAPACITY rather th

Re: [linux-usb-devel] [PATCH] - usb-serial.c usb_kill_urb()

This is a similar issue as the one I just addressed in ftdi_sio.c. I didn't like the warning trace being generated by urb.c, when the usb_unlink_urb() has been used for synchronous removal of the port read URB. I am just wondering, why are the read URB's being removed synchronously and the others a

Re: [linux-usb-devel] Re: isp1160 driver for 2.6 kernel

--- Lothar Wassmann <[EMAIL PROTECTED]> wrote: > Hi, > > On Tue, 7 Sep 2004, Olav Kongas wrote: > > On Tue, 7 Sep 2004, Dimitris Lampridis wrote: > > > > > First of all, I'm not porting any existing driver. My opinion > is that > > > all drivers up to now are very "custom-made" and thus > erro

Re: [linux-usb-devel] [PATCH] - ftdi_sio usb_kill_urb(), DTR handling

yup, you were right, the check for NULL is not necessary, usb_kill_urb, handles everything for us. This yields even a lighter patch: - --- linux-2.6.9-rc1-mm1/drivers/usb/serial/ftdi_sio.c 2004-09-08 04:51:23.0 +02

Re: [linux-usb-devel] HCD question: how to register multiple ports

On Tuesday 07 September 2004 07:01 pm, Alan Stern wrote: > > The easiest thing for now is to ignore the second port in each pair. > Unless you can specify in a TD that it should use both ports? You mean not use the second port at all? That's not an option. I have hw with all 4 ports. I had a 2.4

[linux-usb-devel] Re: [patch 2.6.9-rc] khubd looks at ports after probe

On Tue, Aug 31, 2004 at 10:07:33PM -0700, David Brownell wrote: > I happened across a problem that came up with modified OHCI > root hub code ... looks like hub probing has misbehaved for a > long time, this might affect other configs too. > > Does this patch look good to you? If so, please merge

[linux-usb-devel] Re: PATCH: change how INQUIRY is fixed up

On Sat, Sep 04, 2004 at 01:04:52PM -0700, Matthew Dharm wrote: > The usb-storage driver 'fixes up' the INQUIRY data returned by a device so > that it reads SCSI rev 2 by intercepting the data in-flight. This was done > to make various SCSI drivers (sd, sr, etc.) work with the device. > > However,

[linux-usb-devel] Re: [PATCH 2.6.9-rc1-mm1] SN9C10x driver update

On Sat, Aug 28, 2004 at 08:35:50AM +0200, Luca Risolia wrote: > Changes: > > - Add support for SN9C103 based devices. The audio capability is already > supported but not released in this version. I will release > it once someone donates two SN9C103 based devices. > - Implement VIDIOC_G_CTRL fo

Re: [linux-usb-devel] Re: input troubles with synaptics

On Wednesday 08 September 2004 8:46 am, Vojtech Pavlik wrote: > On Wed, Sep 08, 2004 at 06:18:11AM -0700, David Brownell wrote: > > On Wednesday 08 September 2004 12:07 am, Vojtech Pavlik wrote: > > emphasized that something seems to have changed in recent BK kernels, > > unrelated (or at least no

Re: [linux-usb-devel] How to handle string descriptor request from usb-uhci

On Wednesday 08 September 2004 7:28 am, Alan Stern wrote: > > I imagine the closest thing to a "lingua franca" would be U.S.-English, > but obviously my viewpoint is biased. Surely you jest. By definition, it's French - right? :) - Dave --

Re: [linux-usb-devel] HCD question: how to register multiple ports

On Wednesday 08 September 2004 7:29 am, Alan Stern wrote: > On Tue, 7 Sep 2004, David Brownell wrote: > > > On Tuesday 07 September 2004 4:01 pm, Alan Stern wrote: > > > > > > A cleaner solution is to treat the pair of ports as a single root hub, and > > > keep track of which port each device li

Re: [linux-usb-devel] [PATCH] - ftdi_sio usb_kill_urb(), DTR handling

On Wed, 8 Sep 2004, Jan Capek wrote: > Attached is a patch that replaces the use of usb_unlink_urb() of the read > URB when the device is being closed with usb_kill_urb(). The second call > is more appropriate and recommended by urb.c. In fact, the ftdi_close() > tries to shut down the URB's synch

Re: [linux-usb-devel] usb_unlink_urb() makes missing data on a pipe (IN)

On Wed, 8 Sep 2004 [EMAIL PROTECTED] wrote: > Configuration: > Distribution:Linux Fedora Core 2 > Kernel:2.6.7 > Problem occured also with the RedHat 7.3 distribution (kernel 2.4.18) > HCD:uhci_hcd > > Hi, > I'm writing an USB driver for a specific device. > If I terminate an IO (a read on a BULK

[linux-usb-devel] [PATCH] - ftdi_sio usb_kill_urb(), DTR handling

Hi, 1) Attached is a patch that replaces the use of usb_unlink_urb() of the read URB when the device is being closed with usb_kill_urb(). The second call is more appropriate and recommended by urb.c. In fact, the ftdi_close() tries to shut down the URB's synchronously since the URB_ASYNC_UNLINK fl

Re: [linux-usb-devel] Re: input troubles with synaptics

On Wed, Sep 08, 2004 at 06:18:11AM -0700, David Brownell wrote: > On Wednesday 08 September 2004 12:07 am, Vojtech Pavlik wrote: > > > > On the other hand, I have a machine that works OK with the SuSE 9.1 kernel > > > but not with the latest BK kernel ... something other than USB changes > > > see

Re: [linux-usb-devel] IRQ sharing "screwed up" (was: Re: [ck] Re: newbie question)

On Wed, 8 Sep 2004, Andreas Mohr wrote: > > since the HC drivers always > > leave their devices on unless they encounter an unrecoverable error. > ...e.g. triggering USB over-current monitoring by connecting one of my > trusty and bulky HDDs. Well, maybe. By itself an overcurrent error isn't unr

[linux-usb-devel] usb_unlink_urb() makes missing data on a pipe (IN)

Configuration: Distribution:Linux Fedora Core 2 Kernel:2.6.7 Problem occured also with the RedHat 7.3 distribution (kernel 2.4.18) HCD:uhci_hcd Hi, I'm writing an USB driver for a specific device. If I terminate an IO (a read on a BULK or an interrupt pipe) by calling usb_unlink_urb() then I submi

RE: [linux-usb-devel] RE: isp1161 ISOC timeout problems

Ok, so I should be getting an order of 'a,11,a,11,a' - but at the moment I am getting 'a,11,10,a,11,10' Unfortunately my webcam to test on is loaned to another person at the moment so I cannot check your latest printk request. I have also aquired another board which I can test. An arcom board wi

Re: [linux-usb-devel] genesys usb2 storage device still stuck

On Wed, 8 Sep 2004, Olaf Hering wrote: > Here is the result from a static kernel. Okay, I give up. Those messages about ep0in timeouts are gone but the device crashes anyway. It's not surprising that the final call to usb_reset_device() hangs; Greg KH still hasn't applied the patches I sent in

Re: [linux-usb-devel] IRQ sharing "screwed up" (was: Re: [ck] Re: newbie question)

Hi, On Wed, Sep 08, 2004 at 10:41:09AM -0400, Alan Stern wrote: > On Wed, 8 Sep 2004, Andreas Mohr wrote: > > Also, it unnecessarily calculates hdc->state *twice* before and > > during the IRQ sharing check, so in total it should use > > if (start == USB_STATE_HALT)/* irq sharing? */ > >

[linux-usb-devel] Re: USB Resume problems

[I forgot to cc: linux-usb-devel in the original message] On Tue, 7 Sep 2004, David Brownell wrote: > On Tuesday 07 September 2004 3:50 pm, you wrote: > > David: > > > > I just tracked down several problems with USB Resume: > > > > 1. The UHCI driver shouldn't try to resume a port that isn

[linux-usb-devel] RE: isp1161 ISOC timeout problems

Hi Dominic Evans I have a intrerest in this sequance shown as below from you. >Yes I did try your modified printk's. I still got same results with >wrong order. > >E.g. > >a >11 >10 >a >11 >10 It seems ITL0,1Done is getting..!? But not send Next PTD? (My pattern is start from 11,a,... it's de

Re: [linux-usb-devel] Bulk transfer problems with usb-uhci (what do error messages mean?)

On Wed, 8 Sep 2004, Toralf Lund wrote: > >and according to > >Documentation/usb/error-codes.txt, -EILSEQ is a CRC mismatch. > > > ... but this does, of course. The problem was that it never occured to > me to look in the Documentation directory. > > > In other > >words, the received packet wa

Re: [linux-usb-devel] Re: input troubles with synaptics

On Die, 07 Sep 2004, David Brownell wrote: > I noticed a recent patch to use ACPI probing for the i8042, which > seemed to help on some systems. If you mean the CONFIG_SERIAL_8250_ACPI stuff, it doesn't help here on my Acer laptop. Best wishes Norbert --

Re: [linux-usb-devel] IRQ sharing "screwed up" (was: Re: [ck] Re: newbie question)

On Wed, 8 Sep 2004, Andreas Mohr wrote: > Uhoh, I just found one (linux-2.6.8.1/drivers/usb/core/hcd.c): > > irqreturn_t usb_hcd_irq (int irq, void *__hcd, struct pt_regs * r) > { > struct usb_hcd *hcd = __hcd; > int start = hcd->state; > > if

Re: [linux-usb-devel] HCD question: how to register multiple ports

On Tue, 7 Sep 2004, David Brownell wrote: > On Tuesday 07 September 2004 4:01 pm, Alan Stern wrote: > > > > A cleaner solution is to treat the pair of ports as a single root hub, and > > keep track of which port each device lies below. The problem with this > > approach is that the existing data

Re: [linux-usb-devel] How to handle string descriptor request from usb-uhci

On Tue, 7 Sep 2004, Toralf Lund wrote: > >Well, do your best. Try to use whatever language the names are native to. > >Hint: If a name contains a special character that doesn't belong to a > >language, then the name isn't in that language! > > > > > Actually, our company name is strictly speak

Re: [linux-usb-devel] genesys usb2 storage device still stuck

Here is the result from a static kernel. BOOTP S = 1 FILE: lemon Load Addr=0x4000 Max Size=0xbfc000 FINAL Packet Count = 3316 FINAL File Size = 1697344 bytes. chrpboot starting: loaded at 0x0080 gunzipping (0x0001 <- 0x00806c4c:0x0098c482)...done 3517428 bytes 49352 bytes of heap consume

Re: [linux-usb-devel] Re: input troubles with synaptics

On Wednesday 08 September 2004 12:07 am, Vojtech Pavlik wrote: > > On the other hand, I have a machine that works OK with the SuSE 9.1 kernel > > but not with the latest BK kernel ... something other than USB changes > > seems > > to have changed the behavior in the past couple weeks (2.6.9-rc1-b

Re: [linux-usb-devel] Bulk transfer problems with usb-uhci (what do error messages mean?)

Alan Stern wrote: On Fri, 3 Sep 2004, Toralf Lund wrote: I'm having some problems with a custom USB device that communicates with a Linux host running usb-uhci (Red Hat Linux 9, kernel-2.4.20-31.9) Simply put, bulk read (via libusb usb_bulk_read()) from the device will sometimes fail. [ ... ]

Re: [linux-usb-devel] Re: IRQ sharing "screwed up"

On Wed, Sep 08, 2004 at 08:09:57PM +1000, Con Kolivas wrote: > Andreas Mohr wrote: > >Hi, > > > >On Wed, Sep 08, 2004 at 07:21:06PM +1000, Con Kolivas wrote: > > > >>Andreas Mohr wrote: > >> > >>>Some more explanation: > >>>AFAIK unlikely() should only be used when you're damn sure that this will >

[linux-usb-devel] Re: IRQ sharing "screwed up"

Andreas Mohr wrote: Hi, On Wed, Sep 08, 2004 at 07:21:06PM +1000, Con Kolivas wrote: Andreas Mohr wrote: Some more explanation: AFAIK unlikely() should only be used when you're damn sure that this will NEVER occur (e.g. failure cases), since it will artificially aggravate penalty of this check in c

[linux-usb-devel] Re: IRQ sharing "screwed up"

Hi, On Wed, Sep 08, 2004 at 07:21:06PM +1000, Con Kolivas wrote: > Andreas Mohr wrote: > >Some more explanation: > >AFAIK unlikely() should only be used when you're damn sure that this will > >NEVER occur (e.g. failure cases), since it will artificially aggravate > >penalty of this check in case i

Re: [linux-usb-devel] Re: isp1160 driver for 2.6 kernel

On Tue, 7 Sep 2004, Dimitris Lampridis wrote: > On Tue, 2004-09-07 at 17:32, Olav Kongas wrote: > > OK, in this case I'll have to look at porting some existing > > 2.4 driver to 2.6. Some people have said they got Troy > > Kisky's (BoundaryDevices) driver working nicely on 2.4. > > Could you Dim

[linux-usb-devel] Re: IRQ sharing "screwed up"

Andreas Mohr wrote: Some more explanation: AFAIK unlikely() should only be used when you're damn sure that this will NEVER occur (e.g. failure cases), since it will artificially aggravate penalty of this check in case it does occur. IRQ sharing is *much* too common to justify using unlikely() here.

[linux-usb-devel] IRQ sharing "screwed up" (was: Re: [ck] Re: newbie question)

Hi, On Tue, Sep 07, 2004 at 10:00:24PM -0400, [EMAIL PROTECTED] wrote: > Message: 15 > Date: Tue, 7 Sep 2004 23:16:59 +0100 > From: Colin J Thomson <[EMAIL PROTECTED]> > Subject: Re: [ck] Re: newbie question > To: Mark Knecht <[EMAIL PROTECTED]> > Cc: ck kernel mailing list <[EMAIL PROTECTED]> > M

[linux-usb-devel] OHCI bug introduced in 2.6.7-rc1

[This bug report was originally sent to the user mailing list as suggested by . Someone replied that it should go to the -devel list instead; if that's true the FAQ apparently needs updated.] With these ingredients: HP OfficeJet 4110 printer/scanner combo

Re: [linux-usb-devel] Fw: [Bugme-new] [Bug 3331] New: USB Modem not recognised since 2.6.8-pre1

Am Dienstag, 7. September 2004 07:49 schrieb Ben Castricum: > > On Mon, 6 Sep 2004, Oliver Neukum wrote: > > OK. So I thought. > > Please try this one to be applied on top of the earlier patch. > > That patch doesn't seem to change anything to the output, results are the > same: > > Sep 7 06:05

Re: [linux-usb-devel] Re: input troubles with synaptics

On Tue, Sep 07, 2004 at 09:15:49PM -0700, David Brownell wrote: > On Tuesday 07 September 2004 10:30 am, Vojtech Pavlik wrote: > > > > But: If I plug it in prior to detection of the synaptics, the synaptics > > > is not detected at all: > > > input: PS/2 Generic Mouse on isa0060/serio1 > > > > >