Hi
I just looked over the latest changes to the airprime and option drivers.
First, Novatel EV620 was added to the airprime driver.
Next, it was found that another Novatel device needed RTS/DTR handling.
RTS/DTR handling was added to airprime, using code grabbed from option.
Finally, all
Am Samstag, 17. März 2007 00:50 schrieb Pete Zaitcev:
On Fri, 16 Mar 2007 22:27:20 +0100, Oliver Neukum [EMAIL PROTECTED] wrote:
Originally, I considered freeing more memory at disconnect().
It turned out harder than I thought. I can add it to the port's data
if you like.
There's no
Am Dienstag, 20. März 2007 00:56 schrieb John:
This is a fix for race condition in usb-serial.c
between serial_open and usb_serial_disconnect
(kernel version 2.6.21-rc3)
Prior to this patch instances of usb_serial were not
ref-counted consistently, which caused serial_open
to reuse already
Am Montag, 19. März 2007 19:38 schrieb Alan Stern:
Judging from the bug report, it sounds like a problem with the userspace
tools -- apparently either scanimage or sane exits before the scanner is
ready. Or maybe the problem lies in the scanner itself; it can't finish
its reset procedure
Jon K Hellan wrote:
This makes me wonder: could the option driver handle the rest of the
airprime driver's devices as well? Just like the anydata driver was
dropped and the devices added to option.
In fact, both airprime and option now want to handle vendor ID 0x1410,
device ID 0x1100.
Hi,
memory allocated must be freed in the error case.
Regards
Oliver
Signed-off-by: Oliver Neukum [EMAIL PROTECTED]
--
--- linux-2.6.21-rc4/drivers/usb/serial/omninet.c.alt 2007-03-20
13:09:01.0 +0100
+++ linux-2.6.21-rc4/drivers/usb/serial/omninet.c
Hi,
the option driver does not directly use usb_kill_urb(). It uses a wrapper.
This wrapper means that callbacks which are running are not killed during
close, resubmitting and illicitly pushing data into the tty layer.
The whole purpose of usb_kill_urb() is subverted. The wrapper must be
Hi,
the sierra driver does not directly use usb_kill_urb(). It uses a wrapper.
This wrapper means that callbacks which are running are not killed during
close, resubmitting and illicitly pushing data into the tty layer.
The whole purpose of usb_kill_urb() is subverted. The wrapper must be
Hi,
Oliver Neukum:
the option driver does not directly use usb_kill_urb(). It uses a wrapper.
This wrapper means that callbacks which are running are not killed during
close, resubmitting and illicitly pushing data into the tty layer.
The whole purpose of usb_kill_urb() is subverted. The
Am Dienstag, 20. März 2007 14:11 schrieb [EMAIL PROTECTED]:
Hi,
Oliver Neukum:
the option driver does not directly use usb_kill_urb(). It uses a wrapper.
This wrapper means that callbacks which are running are not killed during
close, resubmitting and illicitly pushing data into the tty
Is this safe from a compiler point of view?
Might a compiler actually evaluate the inner expression and then invert
the result?
Sorry. Thinko. Forget the question.
Regards
Oliver
-
Take Surveys.
Hi,
from urb.c::usb_kill_urb():
if (!(urb urb-dev urb-dev-bus))
return;
Is this safe from a compiler point of view?
Might a compiler actually evaluate the inner expression and then invert
the result?
Regards
Oliver
Hi,
Oliver Neukum:
usb_kill_urb() may be called with NULL. It turns into a nop.
Ah. Thanks.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
I never cheated an honest man, only
Em Seg, 2007-03-19 às 20:59 +, ext Paulo Marques escreveu:
Ragner Magalhaes wrote:
USB Video Class Support
The following patch implements USB Video Class 1.1 as defined at
USB Device Class Definition for
On Mon, 19 Mar 2007, Allen Curtis wrote:
Desirable solution would be to poll for media and generate hotplug
events so this device can be handled like the other USB interface in
the system. We have registered this an an unusual device and created
a custom initialization function. What is
Let's not bore people running -rc kernels with regressions that have
patches available - let's get this patches into the tree for giving
them the pure exciting experience of the many unfixed regressions.
This email lists some known regressions in Linus' tree compared to 2.6.20
with patches
Jim Gettys wrote:
On Sun, 2007-03-18 at 17:07 +0100, Ingo Molnar wrote:
* Pavel Machek [EMAIL PROTECTED] wrote:
Some day we may have modesetting support in the kernel for some
graphics hw, right now it's pretty damn spotty.
Yep, that's the way to go.
hey, i wildly supported this approach
On Mon, 2007-03-19 at 16:33 -0400, Bill Davidsen wrote:
What you say sounds good, assuming that the cost of a sleep is less than
the cost of the busy wait. But this may be hardware, the waits may be
very small and frequent, and if it's hitting a small hardware window
like retrace, delays
Jim Gettys wrote:
On Mon, 2007-03-19 at 16:33 -0400, Bill Davidsen wrote:
What you say sounds good, assuming that the cost of a sleep is less than
the cost of the busy wait. But this may be hardware, the waits may be
very small and frequent, and if it's hitting a small hardware window
The USB HID driver fails to reset its error-retry timeout when there
has been a long time interval between I/O errors with no successful URB
completions in the meantime. As a result, the very next error would
trigger an immediate reset, even if it was a chance event occurring
long after the
On Tue, 20 Mar 2007, Alan Stern wrote:
The USB HID driver fails to reset its error-retry timeout when there
has been a long time interval between I/O errors with no successful URB
completions in the meantime. As a result, the very next error would
trigger an immediate reset, even if it was a
On Tue, 20 Mar 2007, Oliver Neukum wrote:
Am Montag, 19. März 2007 19:38 schrieb Alan Stern:
Judging from the bug report, it sounds like a problem with the userspace
tools -- apparently either scanimage or sane exits before the scanner is
ready. Or maybe the problem lies in the scanner
Em Seg, 2007-03-19 às 15:09 -0700, ext David Brownell escreveu:
On Monday 19 March 2007 1:29 pm, Ragner Magalhaes wrote:
The following patch implements USB Video Class 1.1 as defined at
USB Device Class Definition for Video Devices, available at:
No it doesn't ... it declares on-the-wire
Am Dienstag, 20. März 2007 16:06 schrieb Alan Stern:
Whenever a new capability is added to the kernel, one runs across devices
which ought to support it but do not. One doesn't want to penalize the
vast majority of devices that have no problem for the sake of a few. We
have blacklists and
Hi,
I am looking at doing autosuspend support for usb storage along those lines.
Regards
Oliver
-- Weitergeleitete Nachricht --
Subject: Re: [PATCH 3/4] libata: reimplement suspend/resume support using
sdev-manage_start_stop
Date: Dienstag, 20. März
On Tuesday 20 March 2007 8:29 am, Ragner N Magalhães wrote:
Em Seg, 2007-03-19 às 15:09 -0700, ext David Brownell escreveu:
I see a lot of *_UNDEFINED symbols, which seem dubious. If it's
not defined, then it shouldn't be defined! Wouldn't want to see
anyone assume that if a value
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I'm writing a driver for my NYKO Airflo gamepad. Mainly to learn about
USB driver writing, but am having a problem and wondered if someone
could help:
Currently I have keyboard events hard coded to varous buttons on the
gamepad and
USB Video Class Support
This patch holds USB constants and structures defined
by the USB Device Class Definition for Video Devices.
Signed-off-by: Ragner N Magalhaes [EMAIL PROTECTED]
---
Index: 2.6-dev/include/linux/usb/video.h
USB Video Class Support
This patch holds USB constants and structures defined
by the USB Device Class Definition for Video Devices.
Signed-off-by: Ragner N Magalhaes [EMAIL PROTECTED]
---
Index: 2.6-dev/include/linux/usb/video.h
Ragner Magalhaes wrote:
[...]
+
+#ifndef __LINUX_USB_VIDEO_H
+#define __LINUX_USB_VIDEO_H
+
[...]
+#define USB_VC_HEADER_SIZE(n)(12+(n))
+
+/* As above, but more useful for defining your own descriptors: */
+#define DECLARE_USB_VC_HEADER_DESCRIPTOR(n) \
USB Video Class Support
This patch holds USB constants and structures defined
by the USB Device Class Definition for Video Devices.
Signed-off-by: Ragner N Magalhaes [EMAIL PROTECTED]
---
Index: 2.6-dev/include/linux/usb/video.h
On Tue, 20 Mar 2007, Jiri Kosina wrote:
On Tue, 20 Mar 2007, Alan Stern wrote:
The USB HID driver fails to reset its error-retry timeout when there
has been a long time interval between I/O errors with no successful URB
completions in the meantime. As a result, the very next error would
On Tuesday 20 March 2007 7:49 am, Alan Stern wrote:
I am sorry. HAL? Where do I get this daemon?
It's part of the hal package, which is included in Fedora and presumably
other distributions as well. See
http://www.freedesktop.org/Software/hal
What would an embedded distro use
Hello everyone
I want to test my usb driver. to see whether it work properly, when
more than one device plug into host. but i have only one device. is there a
tools can simulate USB device like a printer. or how to write the module to
call the driver.
Best regard!
DuRui
I am sorry. HAL? Where do I get this daemon?
It's part of the hal package, which is included in Fedora and
presumably
other distributions as well. See
http://www.freedesktop.org/Software/hal
What would an embedded distro use though? HAL takes up
multi-megabytes.
A swapless
On Tue, 20 Mar 2007 12:01:11 -0500, Chris Browning [EMAIL PROTECTED] wrote:
input_report_rel(dev, REL_X, (signed char) mouseX);
input_report_rel(dev, REL_Y, (signed char) mouseY);
and the probe function reports EV_REL and REL_X | REL_Y.
http://browning.homelinux.com/airflo.c.txt
I see you
http://www.freedesktop.org/Software/hal
What would an embedded distro use though? HAL takes up
multi-megabytes.
A swapless system, with say 32 MB total RAM, probably won't find that
to be a usable solution ...
Gee Dave,
How did you know? That is exactly what we have, an
37 matches
Mail list logo
