This changeset upgrades the ov511 driver in kernel 2.5.6-pre1 to version
1.52. It compiles cleanly but has not been otherwise tested (under
2.5.6-pre1). Please apply.
Summary of changes:
1.49 -> 1.50:
- Increased size of directory name string in /proc code, to allow >13
bit minor
numbers.
-
This upgrades the ov511 driver in the 2.4 kernel to version 1.50. This
has been checked for regressions and tested with a number of devices.
Greg, please apply.
Summary of changes:
1.48a -> 1.49:
- Massive cleanup and renaming of functions/variables
- Most functions that took a usb_device take
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
> I was thinking that this would be a good idea too (a usb subsystem wide
> urb pool). ...
A driver-wide cache of pre-initialized URBs could make some
sense, but a USB-wide one would just duplicate kmem_cache
functionality so far as I can tell.
>(right now everyone usually just creates them
On Thu, Feb 28, 2002 at 01:00:59AM +0100, Oliver Neukum wrote:
> On Thursday 28 February 2002 00:29, Greg KH wrote:
> > On Thu, Feb 28, 2002 at 12:18:41AM +0100, Oliver Neukum wrote:
> > > Why ?
> > > If the pool is formed by allocating the memory for urbs in chunks
> > > the positive effect on TL
All of these patches have been seen on the mailing list, so I'll just
point to where they are stored for those who might be curious:
On Wed, Feb 27, 2002 at 03:34:06PM -0800, Greg KH wrote:
> --
> [EMAIL PROTECTED], 2002-02-27 15:02:44-08:00, [EMAIL PROTECTED]
> USB auerswald driver:
>
On Thursday 28 February 2002 00:29, Greg KH wrote:
> On Thu, Feb 28, 2002 at 12:18:41AM +0100, Oliver Neukum wrote:
> > Why ?
> > If the pool is formed by allocating the memory for urbs in chunks
> > the positive effect on TLB and cache is there whether the allocation
> > in the drivers is dynamic
Pull from: bk://linuxusb.bkbits.net/linus-2.5
Documentation/usb/auerswald.txt |4
Documentation/usb/usb-serial.txt | 22 +-
drivers/usb/audio.c | 22 --
drivers/usb/auerswald.c |2
drivers/usb/devices.c|8
drivers/usb/hcd.c
On Thu, Feb 28, 2002 at 12:18:41AM +0100, Oliver Neukum wrote:
>
> Why ?
> If the pool is formed by allocating the memory for urbs in chunks
> the positive effect on TLB and cache is there whether the allocation
> in the drivers is dynamic or not.
> In fact, could we use the slab cache as is ?
W
> > > Comments?
> >>
> > How about abstracting the code and let usb_alloc_urb()
> > take urbs from a pool ?
> > Though I have no idea on how to find a sensible size for
> > the pool. How bad for the TLB are we ?
>
> I don't know.
>
> I was thinking that this would be a good idea too (a usb subsyst
On Wed, Feb 27, 2002 at 11:30:50PM +0100, Oliver Neukum wrote:
>
> > In testing I could not measure any speed differences with this patch,
> > and without it. I would not recommend this approach for drivers that
> > really care about speed (we are doing to kmalloc() calls for every
> > write), b
> In testing I could not measure any speed differences with this patch,
> and without it. I would not recommend this approach for drivers that
> really care about speed (we are doing to kmalloc() calls for every
> write), but the visor driver does not have to worry about things like
> this (the
> Date: Tue, 26 Feb 2002 22:38:57 -0800
> From: Greg KH <[EMAIL PROTECTED]>
> On Tue, Feb 26, 2002 at 10:38:56AM -0800, Geoff Keating wrote:
> >
> > Starting a command-line mp3 player on a system with USB speakers,
> > and then trying to stop it with control-C, didn't work; at best it
> > didn't
Hi all,
Now that we have proper reference counting logic in the USB core code, I
rewrote how the visor driver handles urbs. Instead of having a urb pool
which gets recycled, we create a new urb for every transfer, and then
let the host controller clean up the urb when it is finished.
This shrin
The stuff that needs some more testing is exactly the
second stage loader support, yes. That never worked
before ... so since it works for at least some cases now,
it's an improvement!
If you run into any cases where code that only uses a
single stage loader (the 0xA0 hardware loader, and
on-chi
Hello,
My name is Jean-Pierre LAURENT, my company OLITEC.
We are modem's manufacturer in FRANCE.
I have tested our USB CDC Modem with Linux Mandrake 8.1.
I can send some AT commands and modem respond OK.
But when I use kppp, I can dial, modem stop after 8 carac sent ("ATDT0806")
Do you know thi
On Tue, Feb 26, 2002 at 09:05:36PM -0500, Hugo Haas wrote:
> * Greg KH <[EMAIL PROTECTED]> [2002-02-26 15:02-0800]
> > > Can't usb_serial_disconnect() take the semaphore visor_close() takes ?
> >
> > Yes it could, but there would still be a small race window. I would
> > have to push "down (&por
Here's a patch against 2.5.6-pre1 for the usb-serial drivers that
changes the way the locking code works. Now the usbserial core locks
the individual port semaphores, instead of having the drivers doing the
locking.
This should fix a number of potential and real race conditions, and
makes the us
Thank you for your quick answers.
Greetings
Wolfgang
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
19 matches
Mail list logo
