On Fri, 2007-02-02 at 10:40 -0500, David Hollis wrote:
[snip]
> Great to hear. Now we just need to figure out that memory allocation
> issue in usbnet.
Yes, could you have a look the memory allocation issue in usbnet? TIA.
Dave
Pete Zaitcev wrote:
> On Thu, 01 Feb 2007 22:48:02 -0800, Phil Dibowitz <[EMAIL PROTECTED]> wrote:
>
>> So at a relatively blind guess, I'm thinking a few setup commands and a data
>> transfer is about all there is to this thing. That is of course without
>> having used any USB sniffers or anythin
Am Freitag 02 Februar 2007 schrieb Alan Stern:
> When you have a chance, please try hooking the scanner up to that bad hub
> port again, and use the usbmon facility. Instructions are in the kernel
> source file Documentation/usb/usbmon.txt. Start acquiring the usbmon log
> before running sane, an
Original cialis from Pfizer for Sale Now :-))
Here: http://www.vodafonecellulars.info
N.B.: Tax free prices, Worldwide shipping and No prescription!
--
unpiqoqupmpquopfpkqkukqsqupsqoqgotqinooholofrpolnoohopnpnunsniounonpstouomnm
According to the USB CDC class specification, line state control
is an optional feature for ACM devices. However, the cdc-acm driver
bails out when acm_set_control() fails while opening the device.
The proposed patch changes that behaviour: Failure of acm_set_control
is now only considered an erro
It seems that the CDC-ACM driver can get stuck in a throttling
condition.
This happens when the device is closed while acm->throttle is active;
the ldisc flushes its buffer but the driver remains throttled. If the
device is reopened later, the driver will still be throttled while the
tty ldisc thi
There seems to be a bug in the handling of device throttling in the
CDC-ACM driver. When the tty requests throttling, the same packet
is sometimes delivered to the tty and also pushed back on the list
of pending packets, resulting in delivery of duplicate data.
The problem is inside acm_rx_tasklet
Am Samstag, 3. Februar 2007 15:51 schrieb Joris van Rantwijk:
> There seems to be a bug in the handling of device throttling in the
> CDC-ACM driver. When the tty requests throttling, the same packet
> is sometimes delivered to the tty and also pushed back on the list
> of pending packets, resultin
On Sat, Feb 03, 2007 at 04:18:24PM +0100, Oliver Neukum wrote:
> 1. Why not simply take the lock earlier?
And call the tty layer under acm->throttle_lock? I think not.
We could of course read acm->throttle once under the lock and
store its value in a local variable. I can write it like that if
yo
Pete:
Here's an idea for an improvement to the text interface in usbmon which
should be easy to implement. I'd like to know for certain when and where
events are missing from the log. Something as simple as a line containing
nothing but a '*' could mark the absence of one or more events.
The dr
On Sat, 3 Feb 2007, Prakash Punnoor wrote:
> Am Freitag 02 Februar 2007 schrieb Alan Stern:
> > When you have a chance, please try hooking the scanner up to that bad hub
> > port again, and use the usbmon facility. Instructions are in the kernel
> > source file Documentation/usb/usbmon.txt. Star
Am Samstag 03 Februar 2007 schrieb Alan Stern:
> So here's what I'd like you to do. First, apply the diagnostic patch
> below, and make sure you have CONFIG_USB_DEBUG turned on. Then run your
> test just like before, and do it enough times to get some examples where
> sane-find-scanner doesn't f
On Sat, 3 Feb 2007 11:43:50 -0500 (EST), Alan Stern <[EMAIL PROTECTED]> wrote:
> Here's an idea for an improvement to the text interface in usbmon which
> should be easy to implement. I'd like to know for certain when and where
> events are missing from the log. Something as simple as a line con
This email lists some known regressions in 2.6.20-rc7 compared to 2.6.19
that are not yet fixed in Linus' tree.
If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering
On 1 February 2007 at 10:20, Alan Stern wrote:
| On Wed, 31 Jan 2007, Dirk Eddelbuettel wrote:
|
| > Alan Stern rowland.harvard.edu> writes:
| > > In fact, it's possible that these problems are caused by bad USB cable
| > > connections. They certainly could result in intermittent disconnects.
On Sat, 3 Feb 2007, Pete Zaitcev wrote:
> On Sat, 3 Feb 2007 11:43:50 -0500 (EST), Alan Stern <[EMAIL PROTECTED]> wrote:
>
> > Here's an idea for an improvement to the text interface in usbmon which
> > should be easy to implement. I'd like to know for certain when and where
> > events are missi
On Sat, 3 Feb 2007, Prakash Punnoor wrote:
> Ok, here you go. I hope I did everything correctly. I applied the patch.
> recompiled and installed the modules unloaded present modules and put the
> newly compiled in. Attached the usbmon log and dmesg. calling
> sane-find-scanner 2x success, 2x fa
Am Samstag, 3. Februar 2007 23:02 schrieb Alan Stern:
> Obviously we can't afford to use a single dedicated buffer like this.
> Each thread reading a hub's port status will have to provide its own
> buffer, or more simply, we will have to allocate a buffer dynamically for
> every read instead of
Am Samstag, 3. Februar 2007 23:02 schrieb Alan Stern:
> That's not a problem as far as the hardware is concerned. But both
> threads call hub_port_status(), which reads the status into a dedicated
> buffer at hub->status->port. Even though the URBs are serialized, on
> non-cache-coherent archi
On Sat, 3 Feb 2007, Oliver Neukum wrote:
> Am Samstag, 3. Februar 2007 23:02 schrieb Alan Stern:
> > Obviously we can't afford to use a single dedicated buffer like this.
> > Each thread reading a hub's port status will have to provide its own
> > buffer, or more simply, we will have to allocate
On Sat, 3 Feb 2007 17:02:27 -0500 (EST), Alan Stern <[EMAIL PROTECTED]> wrote:
> + buffer = kmalloc(sizeof(*buffer), GFP_NOIO);
Why is this GFP_NOIO, if it's not in the path of block I/O? Or is it?
-- Pete
-
Using Tomca
21 matches
Mail list logo
