i am getting some strange situation.. perhaps the timing is wrong
what i saw was that the PL2303 serial converter usb driver sends
a "BULK MESSAGE" then a "INTERRUPT MESSAGE" one after another...
BOTH are queued to a the specific end-point queue... and the
interrupt packet is sent out first... wh
Am Samstag, 18. Januar 2003 02:00 schrieb David Brownell:
> Oliver Neukum wrote:
> > Hi,
> >
> > regarding this piece of code:
> > spin_lock_irqsave (&ehci->lock, flags);
> > ...
> >
> > Does this mean that any call to usb_unlink_urb() for an URB on EHCI
> > with a spinlock held will fail?
Oliver Neukum wrote:
Hi,
regarding this piece of code:
spin_lock_irqsave (&ehci->lock, flags);
...
Does this mean that any call to usb_unlink_urb() for an URB on EHCI
with a spinlock held will fail?
No, but a _synchronous_ one might need to wait_ms(1) for the relevant
hardware resource to be
Hi,
This patch prints the vendor + product ids of the scanner after it has
been successfully detected.
Also the annoying error message about "Scanner device is already open"
was downgraded to a dbg. Scanning for devices while one scanner device
was open produced several 100 error messages in sysl
Hi,
This patch changes the maintainer from Brian Beattie to Henning
Meier-Geinitz and adds a link to the documentation and website.
Bye,
Henning
diff -u -r linux-2.5.59/drivers/usb/image/scanner.c
linux-2.5.59-maintainer2/drivers/usb/image/scanner.c
--- linux-2.5.59/drivers/usb/image/scanner.
Am Freitag, 17. Januar 2003 23:36 schrieb Matthias Bruestle:
> Mahlzeit
>
>
> When attaching 52 readers only a part is recognized and numbered.
> The used kernel is probably a 2.4.20-pre19 or a 2.4.20. I've appended
> excerpts from the log, (full log I have is about 15kB) which contains
> messages
Hi,
regarding this piece of code:
spin_lock_irqsave (&ehci->lock, flags);
switch (usb_pipetype (urb->pipe)) {
// case PIPE_CONTROL:
// case PIPE_BULK:
default:
qh = (struct ehci_qh *) urb->hcpriv;
if (!qh)
Mahlzeit
When attaching 52 readers only a part is recognized and numbered.
The used kernel is probably a 2.4.20-pre19 or a 2.4.20. I've appended
excerpts from the log, (full log I have is about 15kB) which contains
messages I've never seen. Do the provide information about where the
problem is?
Hi,
This patch prints the vendor + product ids of the scanner after it has
been successfully detected.
Also the annoying error message about "Scanner device is already open"
was downgraded to a dbg. Scanning for devices while one scanner device
was open produced several 100 error messages in sysl
> > The way this should work is that the LLD calls scsi_remove_device(), and
> > that cuts off the flow of commands. The LLD can promise to error-out any
> > pending commands in the device command queue.
> >
> > That is, unless scsi_block_requests() and scsi_unblock_requests() are
> > more useful
On Fri, 17 Jan 2003, Oliver Neukum wrote:
> I've been thinking somewhat especially about David's points of criticism.
> Perhaps I am overdesigning.
It can't be that much of an overdesign. You've only added a state
variable and a spinlock.
> Would a spinlock held during a call to the
> completi
Oliver Neukum [[EMAIL PROTECTED]] wrote:
>
> > In a separate discussion with Mike, he mentioned that you can't
> > scsi_remove_device() unless there are no pending commands.
> >
> > How the hell is an LLD supposed to assure that!?!?
> >
> > The minute I error a command and call scsi_done(), I can
> In a separate discussion with Mike, he mentioned that you can't
> scsi_remove_device() unless there are no pending commands.
>
> How the hell is an LLD supposed to assure that!?!?
>
> The minute I error a command and call scsi_done(), I can get a new one.
> Unless I lock out requests with scsi_b
Oliver and Alan I am trying to catch up on this thread so I did not
reply directly to your concerns, but I think they are covered below.
Matthew Dharm [[EMAIL PROTECTED]] wrote:
> On Fri, Jan 17, 2003 at 11:55:36AM +0100, Oliver Neukum wrote:
> > That is simply wrong. Reporting somebody having pul
On Thu, Jan 16, 2003 at 06:56:08PM +0530, V Ganesh wrote:
> hi,
> this adds the dell axim and toshiba e740 vendor/product ids to the
> ipaq driver.
Applied, thanks.
greg k-h
---
This SF.NET email is sponsored by: Thawte.com - A 128-bit
On Fri, Jan 17, 2003 at 01:50:25PM +0100, Henning Meier-Geinitz wrote:
> Hi,
>
> This patch changes the maintainer from Brian Beattie to Henning
> Meier-Geinitz and adds a link to the documentation and website.
Applied, thanks.
greg k-h
---
T
On Fri, Jan 17, 2003 at 03:14:59PM +0100, Duncan Sands wrote:
> speedtouch: restore use of MODULE_DEVICE_TABLE to export usb info. There may have
> been a problem with older 2.4 kernels, but there is none now.
Applied, thanks,
greg k-h
--
> > How do you like this version?
>
> Aside from the things mentioned above, it looks fine.
I've been thinking somewhat especially about David's points of criticism.
Perhaps I am overdesigning. Would a spinlock held during a call to the
completion handler and while hcd_unlink_urb() holds urb.lock
On Fri, Jan 17, 2003 at 11:55:36AM +0100, Oliver Neukum wrote:
> That is simply wrong. Reporting somebody having pulled a plug must
> not fail. What are you supposed to do with an error here?
>
> There must be a way for a LLD to report that reliably.
> If the answer is, take that lock, call that f
Does the device have a BULK-IN endpoint?
The SL811HS driver does not set the PID value for bulk transfers, it is up
to the device driver or class driver that sets the PID value. You might
want to look at the class driver to see if there is something wrong.
Pei
-Original Message-
From: T
> I volunteer to investigate the problem.
>
> Can anyone tell me what to do (e.g. how to recompile modules
> with debugging turned on, etc.) and what informations to look
> for in order to determine exactly the nature of the problem ?
>
> I can then post the results to this list.
Very well, you n
devnum 1 is assigned to the root hub, and Devnum 2 is assigned to the first
device connected to the root hub. Any subsequence device attached to the
root hub via USB hub will increment the devnum by 1. In your case, I believe
the PL2303 device would be the first device connected to the root hub, h
=3Chtml=3E
=3Chead=3E
=3Ctitle=3EDo you remember me=3F=3C=2Ftitle=3E
=3Cmeta http-equiv=3D=22Content-Type=22 content=3D=22text=2Fhtml=3B
charset=3Dwindows-1252=22=3E
=3C=2Fhead=3E
=3Cbody bgcolor=3D=22#FF=22 text=3D=22#00=22=3E
=3Cfont size=3D=225=22=3E=3Ca
href=3D=22http=3A=2F=2Fwww=2El
Thomas,
I've been debug using logic analyzer with hardware traces. You designate a
specific memory address to be used for hardware traces, then view the trace
with the logic analyzer. In addition, you should use a CATC USB analyzer
to see which USB transaction you've stuck on, match that with t
As a host... why would the driver be receiving request with the
PID_IN bit set (bit 7)
i dont underatnd why any application/stack would be generating a request
with that bit ON??? what is the purpose???
how should driver handle it??? if the driver (SL811) does not push
the data to the devic
On Fri, 17 Jan 2003, Oliver Neukum wrote:
> Am Freitag, 17. Januar 2003 09:50 schrieb Mike Anderson:
> >
> > If the device disappears the host needs to return all IOs in flight with
> > an error, and we need to ensure new ones do not start ( setting the
> > device offline and maybe host_self_bloc
On Thu, 16 Jan 2003, Greg KH wrote:
> On Thu, Jan 16, 2003 at 03:14:39PM -0500, Bill Davidsen wrote:
> > On Wed, 15 Jan 2003, Greg KH wrote:
> >
> > Would it be possible to post patches in general instead of pointing to bk:
> > links? Some people can't use bk and would like the patches (legal opi
speedtouch: restore use of MODULE_DEVICE_TABLE to export usb info. There may have
been a problem with older 2.4 kernels, but there is none now.
speedtouch.c |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff -Nru a/drivers/usb/misc/speedtouch.c b/drivers/usb/misc/speedto
As it has been already reported in the linux-usb-users list,
the IBM USB 2.0 Memory Key (0x0a16/0x9989) does not seem to
work with Linux.
Ben Liblit reports the following (IBM ThinkPad X24 laptop,
stock Red Hat 8.0 kernel 2.4.18):
00:58:20 kernel: hub.c: USB new device connect on bus2/1, assigned
Hi,
This patch changes the maintainer from Brian Beattie to Henning
Meier-Geinitz and adds a link to the documentation and website.
Bye,
Henning
diff -u -r linux-2.4.21-pre3.move-ioctls/drivers/usb/scanner.c
linux-2.4.21-pre3.maintainer2/drivers/usb/scanner.c
--- linux-2.4.21-pre3.move-ioct
on 1/16/03 9:25 PM, Randy.Dunlap at [EMAIL PROTECTED] wrote:
> On Thu, 16 Jan 2003, Thomas Chen wrote:
>
> | > like you say:v
> | > | so... if that is the case... from PC/host point of view... we SHOULD
> | > | never send out any packet that is has OUT bit set why am i seeing
> | > | BULK mes
Am Freitag, 17. Januar 2003 09:50 schrieb Mike Anderson:
> Oliver Neukum [[EMAIL PROTECTED]] wrote:
> > Am Donnerstag, 16. Januar 2003 21:48 schrieb Mike Anderson:
> > > David Brownell [[EMAIL PROTECTED]] wrote:
> > > > Have any of the SCSI people been looking much at SCSI hotplug on 2.5?
> > > > I
** Proprietary **
Hi,
I'm intending to use a USB-Ethernet Driver (CDCEther or pegasus).
Can any one tell me how do I get my network interface up.(something similar to "eth0")
?How do I force the IP with ifconfig ?
I believe the above drivers are compliant to the Standard CDC (Ethernet Control Mo
Oliver Neukum [[EMAIL PROTECTED]] wrote:
> Am Donnerstag, 16. Januar 2003 21:48 schrieb Mike Anderson:
> > David Brownell [[EMAIL PROTECTED]] wrote:
> > > Have any of the SCSI people been looking much at SCSI hotplug on 2.5?
> > > I attach "/etc/hotplug/scsi.agent" from one of my desktops; all it
>
David Brownell wrote:
>
>> Further investigations (making procfs outputs from usb-ohci) have
>> uncovered that the 'Skip' flag for the frozen usb mouse is set even
>> though there are still transfer descriptors pending.
>
> Descriptors, multiple? My initial guess is that you're getting
> bit by on
35 matches
Mail list logo
