On Thursday 01 June 2006 8:46 pm, Andrew Morton wrote:
>
> fyi, I continue to revert this patch from Greg's tree.
Here's a somewhat better version, FYI. Still has some issues,
but seemingly nothing quite as nasty as Rafael reported.
This teaches OHCI to use the root hub status change (RHSC) IR
From: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
The Sierra Wireless MC5720 is an embedded EV-DO module which is shipping
with a number of laptops. This change adds its ID to the airprime.c usb
serial driver, so that it appears as a serial device.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECT
From: Olivier Galibert <[EMAIL PROTECTED]>
Some bluetooth adapters return an incorrect number of sco packets in
READ_BUFFER_SIZE. Fix it.
This is the worst possible way to fix it for several reasons:
- this is not a generic fix, it has to me activated explicitely by the
driver
- this is not
From: Philippe Retornaz <[EMAIL PROTECTED]>
See http://bugzilla.kernel.org/show_bug.cgi?id=6617.
This function dereference a __user pointer.
(akpm: this code is deeply fishy. Are the types correct?)
Signed-off-by: Philippe Retornaz <[EMAIL PROTECTED]>
Cc: Greg KH <[EMAIL PROTECTED]>
Signed-of
From: Eric Sesterhenn <[EMAIL PROTECTED]>
This fixes coverity Bug #390.
With the following code
ret = ep->branch = balance(isp116x, ep->period, ep->load);
if (ret < 0)
goto fail;
the problem is that ret and balance are of the type int, and ep->branch is u16.
so
fyi, I continue to revert this patch from Greg's tree.
From: Andrew Morton <[EMAIL PROTECTED]>
It makes Rafael's machine lock up on resume.
Cc: "Rafael J. Wysocki" <[EMAIL PROTECTED]>
Cc: David Brownell <[EMAIL PROTECTED]>
Cc: Greg KH <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PR
This patch will break all USB-Serial drivers. It's big, but most of the
changes are just deletions.
I didn't write a document explaning how to make the port yet, will do when
I get enough feedback about this work. For now, the important points regarding
the port are:
1. The registration proce
Most of the changes are just error/debug messages improvements and the
addition of uart_port statatistics.
Additionally, pl2303_update_line_status() was completely ported and
pl2303_read_bulk_callback() modified to to handle -ECONNRESET and -ENOENT.
Signed-off-by: Luiz Fernando N. Capitulino <[
This patch directly ports pl2303's tty functions to their Serial Core
version. Those function are:
pl2303_open()-> pl2303_startup()
pl2303_close() -> pl2303_shutdown()
pl2303_write() -> pl2303_start_tx()
pl2303_break_ctl() -> pl2303_break()
pl2303_tiocmget()
usbserial's mutex, open_count and tty_struct pointer in
struct usb_serial_port have been obsolated by the Serial Core port.
Note that was necessary to change some bits in the generic code to
make it compile.
Signed-off-by: Luiz Fernando N. Capitulino <[EMAIL PROTECTED]>
---
drivers/usb/serial/
This patch introduces new methods needed by the USB-Serial Serial Core
version. The methods are:
pl2303_stop_tx(), pl2303_send_xchar(), pl2303_stop_rx(), pl2303_type(),
pl2303_enable_ms(), pl2303_release_port(), pl2303_request_port(),
pl2303_config_port(), pl2303_verify_port().
Note that, howe
The following functions:
pl2303_write_room(), pl2303_chars_in_buffer(), pl2303_ioctl(),
wait_modem_info().
are not needed in the pl2303 Serial Core version, mostly because the Serial
Core implements them for us.
Signed-off-by: Luiz Fernando N. Capitulino <[EMAIL PROTECTED]>
---
drivers/usb/s
This patch ports the pl2303 USB-Serial's attach() and shutdown() methods to
the Serial Core version of the USB-Serial's core.
Also note that they have been renamed to avoid name collision in the next
patches:
pl2303_startup() -> pl2303_attach()
pl2303_shutdown() -> pl2303_usb_shutdown()
This new dbg() macro has the following features:
o Adds a '[USBSERIAL]' prefix to every debug message, that way usbserial
debug messages are not mixed up with other debug messages like kernel
timming information
o Also prints the function name (__FUNCTION__), that way dbg() calls
doesn
USB's core err() macro doesn't print the function name making the call,
that way is necessary to pass __FUNCTION__ to every err() call.
This change introduces usbserial's own err() macro, which prints the
function name. Aditionally, usbserial module's err() calls are converted
to the new one.
Sig
Converts some info and debug messages into errors ones, and also adds
missing errors reports.
Those messages cannot be hiding/omited, otherwise we could run in
trouble in silence.
Signed-off-by: Luiz Fernando N. Capitulino <[EMAIL PROTECTED]>
---
drivers/usb/serial/usb-serial.c | 21 ++
Hi folks.
This patch series is my first attempt to port the USB-Serial layer to the
Serial Core API. Currently USB-Serial uses the TTY layer directly, duplicating
code and solutions from the Serial Core implementation.
The final (ported) USB-Serial code is simpler and cleaner. Now I'd like to
fixup_generic() will not compile when usbserial driver is ported to the
Serial Core API. We need to disable for now.
Yes, the #if/#endif are ugly, but it's a good way to be explicit about the
missing work.
Signed-off-by: Luiz Fernando N. Capitulino <[EMAIL PROTECTED]>
---
drivers/usb/serial/usb-
On Thursday 01 June 2006 5:03 pm, David Liontooth wrote:
>
> However, obeying the USB power rules is not an end in itself -- the
> relevant question is the minimum power the device requires to operate
> correctly and without damage.
We don't know the minimum, or much care about it since the minim
Greg KH wrote:
> On Thu, Jun 01, 2006 at 10:58:43AM -0400, Alan Stern wrote:
>
>> On Thu, 1 Jun 2006, Andrew Morton wrote:
>>
>>
>>> On Thu, 01 Jun 2006 02:18:20 -0700
>>> David Liontooth <[EMAIL PROTECTED]> wrote:
>>>
>>>
Starting with 2.6.16, some USB devices fail unnecessaril
Lennart Sorensen <[EMAIL PROTECTED]> writes:
> A scanner certainly uses more power with the scanner light on than with
> it off, and it starts out off until it is in use on most scanners. Of
> course I have never seen a usb powered scanner, so it doesn't seem to
> matter.
Oh, they've been around
Alan
I used usbmon to gain more visibility and i see some interesting points in it.
I am reproducing a small and relevent portion of usbmon log below. Note that
the test comprises of writing about 12Mbytes of data to 2.0 external USB hard
disk.
1 810c73e0 1314291816 C Bi:002:01
Intel is pleased to announce the launch of a project to
implement Linux kernel support for upcoming hardware that
complies with the WiMedia Ultra Wide Band (UWB) and Wireless
USB standards.
UWB is a high-bandwidth, low-power, point-to-point radio
technology using a wide spectrum (3.1-10.6HGz). I
On Mon, May 22, 2006 at 10:23:39PM -0700, Pete Zaitcev wrote:
> Hi, Greg:
>
> I looked at RMK's UART infrastructure and it seemed a little too
> fine-grained to me. It does not seem like a good match for things
> like edgeport and keyspan. So, my enthusiasm about "us" has diminished.
Sometimes it
On Wed, May 31, 2006 at 03:46:24PM -0700, Greg KH wrote:
> On Thu, Jun 01, 2006 at 12:42:45AM +0200, Frank Gevaerts wrote:
> > +
> > +module_param(connect_retries, int, KP_RETRIES);
>
> I really do not think that you want KP_RETRIES as a mode value in sysfs
> :)
>
> This is not how you pre-initia
On Thu, Jun 01, 2006 at 12:42:45AM +0200, Frank Gevaerts wrote:
> This patch fixes several problems in the ipaq.c driver with connecting
> and disconnecting pocketpc devices:
Unfortunately, it is apparently not the whole story.
There are some problems:
With this patch, whenever the usb_control_
Andrew Morton wrote:
> On Thu, 01 Jun 2006 02:18:20 -0700
> ..
>> This is generating a lot of grief and appears to be unnecessarily
>> strict. Common USB sticks with a MaxPower value just above 100mA, for
>> instance, typically work fine on unpowered hubs supplying 100mA.
>>
>> Is a more user-frien
Greg:
This patch (as703) improves the error handling when a Set-Configuration
request fails. The old interfaces are all unregistered before the request
is sent, and if the request fails then we don't know what config the
device is using. So it makes no sense to leave actconfig pointing to the
Greg et al.:
This patch (as702) makes usbhid use the new usb_reset_composite_device
API. Now HID interfaces can coexist with other interfaces on the same
device, and a reset can safely be requested by any of the drivers.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
---
Index:
On Sun, May 28, 2006 at 07:22:59PM +0100, Bryan O'Donoghue wrote:
> Greetings list.
>
> I hate for my first posting here to be a question, however.
>
> Would the list have an objection were I to submit a patch to Das U-Boot
> the Embedded Bootloader which used VendorID 0x0525 and ProductID 0xa4
On Thu, 1 Jun 2006, Andrew Morton wrote:
> On Thu, 1 Jun 2006 10:58:43 -0400 (EDT)
> Alan Stern <[EMAIL PROTECTED]> wrote:
>
> > As an alternative, we could allow an "over-budget window" of say 10%.
>
> That, plus we should provide a suitable i-know-what-im-doing user override,
> with the appr
Greg and Matt:
This patch (as701) modifies usb-storage to take advantage of the new
usb_reset_composite_device() API. Now we will be able to safely request
port resets even if other drivers are bound to a mass-storage device.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
---
Ch
On Thu, 1 Jun 2006, Oliver Neukum wrote:
> Am Donnerstag, 1. Juni 2006 17:09 schrieb linux-os (Dick Johnson):
>> Many, most, perhaps all such devices don't take more power when they
>> are "enabled". Everything is already running and sucking up maximum
>> current when you plug it in! If the mothe
Greg:
This patch (as699) adds usb_reset_composite_device(), a routine for
sending a USB port reset to a device with multiple interfaces owned by
different drivers. Drivers are notified about impending and completed
resets through two new methods in the usb_driver structure.
The patch modifieds
Greg:
This patch (as700) modifies the hub driver to take advantage of the new
usb_reset_composite_device API. The existing code had special-case calls
stuck into usb_reset_device, just before and after the reset. With the
new version there's no need for special-case stuff; it all happens
natura
On Thu, 1 Jun 2006, linux-os (Dick Johnson) wrote:
> > If they do, they are violating the spec. A device in the unconfigured
> > (state 0)
> > state must not draw more than 100mA.
...
> Hmmm, the USB-IF recommends 100 mA per port, not requires.
See section 7.2.1 of the USB 2.0 specification (p.
On Thu, 1 Jun 2006, Bart Whiteley wrote:
> On Wed, 2006-05-31 at 16:17 -0400, Alan Stern wrote:
> > There's no obvious reason why the device should crash like this.
> > Apparently it just doesn't like 120 KB writes. You wouldn't think
> > something like that would bother a flash device, but in
On Thu, 1 Jun 2006, linux-os (Dick Johnson) wrote:
> >> Yes, it sounds like we're being non-real-worldly here. This change
> >> apparently broke things. Did it actually fix anything as well?
> >
> > Yes. At least, I think so. The change directly addresses a complaint
> > filed here:
> >
> > ht
On Thu, 1 Jun 2006 10:58:43 -0400 (EDT)
Alan Stern <[EMAIL PROTECTED]> wrote:
> As an alternative, we could allow an "over-budget window" of say 10%.
That, plus we should provide a suitable i-know-what-im-doing user override,
with the appropriate warnings, as well as a printk which directs user
On Thu, Jun 01, 2006 at 10:58:43AM -0400, Alan Stern wrote:
> On Thu, 1 Jun 2006, Andrew Morton wrote:
>
> > On Thu, 01 Jun 2006 02:18:20 -0700
> > David Liontooth <[EMAIL PROTECTED]> wrote:
> >
> > > Starting with 2.6.16, some USB devices fail unnecessarily on unpowered
> > > hubs. Alan Stern ex
On Thu, Jun 01, 2006 at 03:25:46PM +0530, pratapg wrote:
> I am Pratap.G from PUNE IIIT and I am currently working on the web
> camera based digital image acquisition system. I havent choosen vendor for
> web camera and I need multiple cameras to have the multiple views of the
> image
Am Donnerstag, 1. Juni 2006 17:09 schrieb linux-os (Dick Johnson):
> Many, most, perhaps all such devices don't take more power when they
> are "enabled". Everything is already running and sucking up maximum
> current when you plug it in! If the motherboard didn't smoke when
If they do, they are v
On Wed, 2006-05-31 at 16:17 -0400, Alan Stern wrote:
> There's no obvious reason why the device should crash like this.
> Apparently it just doesn't like 120 KB writes. You wouldn't think
> something like that would bother a flash device, but in this case it
> does.
>
> Perhaps if you set max_s
On Thu, Jun 01, 2006 at 11:09:46AM -0400, linux-os (Dick Johnson) wrote:
> Many, most, perhaps all such devices don't take more power when they
> are "enabled". Everything is already running and sucking up maximum
> current when you plug it in! If the motherboard didn't smoke when
> the device was
On Thu, 1 Jun 2006, Alan Stern wrote:
> On Thu, 1 Jun 2006, Andrew Morton wrote:
>
>> On Thu, 01 Jun 2006 02:18:20 -0700
>> David Liontooth <[EMAIL PROTECTED]> wrote:
>>
>>> Starting with 2.6.16, some USB devices fail unnecessarily on unpowered
>>> hubs. Alan Stern explains,
>>>
>>> "The idea is
On Thu, 1 Jun 2006, Andrew Morton wrote:
> On Thu, 01 Jun 2006 02:18:20 -0700
> David Liontooth <[EMAIL PROTECTED]> wrote:
>
> > Starting with 2.6.16, some USB devices fail unnecessarily on unpowered
> > hubs. Alan Stern explains,
> >
> > "The idea is that the kernel now keeps track of USB power
Andrew Morton wrote:
(added linux-usb cc)
Yes, it sounds like we're being non-real-worldly here. This change
apparently broke things. Did it actually fix anything as well?
Gentoo recieved several reports of this. It appears that certain vendors
are worse than others (Verbatim flash drives a
CONGRATULATIONS!!!.YOU HAVE WON Â750,000 Euros
You have have been awarded Â750,000 Euros in the SWISS-LOTTO Satellite software
email lottery in which e-mail addresses are picked Randomly by software powered
by the Internet through the worldwide website.
Your email address was amongst th
On Thu, Jun 01, 2006 at 12:36:45PM +0200, Milan Svoboda wrote:
> > > From: Milan Svoboda <[EMAIL PROTECTED]>
> > >
> > > This patch adds support for pxa2xx_udc. This driver then will be
> > > usable on ixp4xx platform.
> >
> > Great work!
> >
> > One thought: if adding ixp4xx support to pxa2xx_
Lennert Buytenhek <[EMAIL PROTECTED]>
05/29/2006 11:09 AM
To: Milan Svoboda <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED],
linux-usb-devel@lists.sourceforge.net
Subject:Re: [PATCH] ixp4xx: Add platform specific device -
pxa2xx_udc
On Mon, May 29, 2006 at 1
On Thu, 01 Jun 2006 02:18:20 -0700
David Liontooth <[EMAIL PROTECTED]> wrote:
> Starting with 2.6.16, some USB devices fail unnecessarily on unpowered
> hubs. Alan Stern explains,
>
> "The idea is that the kernel now keeps track of USB power budgets. When a
> bus-powered device requires more cu
Jun 1 10:25:21 hostname kernel: usb 2-4: new high speed USB device using
address 2
Jun 1 10:25:22 hostname kernel: Initializing USB Mass Storage driver...
Jun 1 10:25:22 hostname kernel: usb-storage: This device (05ab,0060,1106 S 06
P 50) has unneeded SubClass and Protocol entries in unusual_
> -Original Message-
> From: David Brownell [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 01, 2006 7:28 AM
> To: linux-usb-devel@lists.sourceforge.net
> Cc: Rasmit Ranjan (WT01 - Semiconductors & Consumer Electronics)
> Subject: Re: [linux-usb-devel] RWE and RWC bits of OHCI
> contro
I am Pratap.G from PUNE IIIT and I am currently working on the web
camera based digital image acquisition system. I havent choosen vendor for
web camera and I need multiple cameras to have the multiple views of the
image in visual monitoring systems.
I am working on RH linux2
54 matches
Mail list logo
