Hello!
Recently, I had problems using NFS with my kaweth device, tcpdump showed
fragmented packages. The reason, I found, was the MTU, which is 1514
by default for kaweth. Setting it to 1500 solved the problems. The
attached patch sets the MTU to 1500 by default.
Greetings,
Oliver
--
.''`.
Clemens Ladisch wrote:
OK, here are further changes for 2.4.
... and now, hopefully, with correct formatting.
sync with Nagano's version:
- protect vendor ids against multiple definitions
- sort Roland device ids
- add SC-8820 table entry for hotplugging
- add quirk for the MOTU Fastlane
---
Le Lundi 03 Mars 2003 17:43, David Brownell a écrit :
Since those are USB 1.1 devices they can't be high bandwidth.
That term has a specific meaning, for USB 2.0 high speed periodic
transfers (lets them get up to 24 Mbyte/second each).
Ok, didn't know that.
I'm using 6 hubs, 2 of them
On Friday 28 February 2003 17:06, Greg KH wrote:
On Fri, Feb 28, 2003 at 03:44:11PM +, Ian Abbott wrote:
when the FTDI USB to serial converter (I have tried FT8U232AM
and FT232BM) is connected to a UHCI hub using the alternate
UHCI driver (uhci.o).
Does the same thing happen on 2.5?
Here is a slightly updated patch for usb-skeleton.c. It has been tested
minimally with real hardware, but David Brownell would like to see some
more tests using gadget zero.
There are a couple of small changes that were not included in previous
patches I sent in. The driver now just looks for
Hi,
Could you bk mv drivers/usb/hcd drivers/usb/host and then apply
this patch? That will let most 2.5 host controller driver patches
apply directly to 2.4 ... helping both releases, since 2.5 has more
fixes while 2.4 has more users. (And testers!)
I've got a few other 2.4 patches in the queue,
Ian Abbott said:
I'll let you know when/if I finally manage to get the kernel to boot
up! (I'm not getting much further than the Okay, booting the
kernel message at the moment.) If I don't get anywhere with that soon,
I'll try and delve a little deeper into where it's going
wrong on 2.4.
Hi,
This is the 2.4 version of a fix that's been in 2.4 for some
time now: when an HCD dies a premature death, its cleanup
needs to be done in a task context. The most likely case for
that would be physical cardbus eject without driver shutdown.
Please merge.
- Dave
--- 1.13/drivers/usb/hcd.c
This patch syncs the 2.4 version with the latest from 2.5 ...
to make it easier for folk to use this before the host
directory rename, I decided not to depend on that patch yet.
VIA users will see the most benefit from this, as well as
anyone rebooting with usb-only configurations.
- uses reboot
David Brownell wrote:
This patch syncs the 2.4 version with the latest from 2.5 ...
to make it easier for folk to use this before the host
directory rename, I decided not to depend on that patch yet.
Whoops ... apologies. This is the version that applies
to generic 2.4.21-pre5, the preceding
On Mon, 3 Mar 2003, Charles Lepple wrote:
In case I'm way off on this one, I'm copying the linux-usb-devel list to
see if any kind souls out there wouldn't mind posting a working .config
for recent 2.5 kernels.
Here's a .config I compiled last Friday. It's pretty minimal, so it
ought to
David,
Thanks for the patch. I applied it against 2.4.21-pre4-ac6 and found that
writing to the USB 2.0 HDD on the VT8235 was still perfect, but the
computer would still hang (lock up completely) after reading the same
amount of data from USB 2.0 HDD.
For what it's worth, I'll try applying this
Jonathan Thorpe wrote:
David,
Thanks for the patch. I applied it against 2.4.21-pre4-ac6 and found that
writing to the USB 2.0 HDD on the VT8235 was still perfect, but the
computer would still hang (lock up completely) after reading the same
amount of data from USB 2.0 HDD.
So what did the
Or instead use USB 2.0 hubs connected to a USB 2.0 root hub,
where ((480 Mbit/sec net)/24 devices) == 20 Mbit/sec per
device means there's plenty of bulk bandwidth (since no
DSL technology I've heard of goes above around 6 Mbit/sec)
hmm, I should've known this earlier. I thought that only USB2
Renaud Guérin wrote:
Hello,
I'm in a situation where I need to plug 24 high bandwidths USB devices into
the same machine (they're DSL modems actually).
I'm using 6 hubs, 2 of them plugged directly on the PC, and the fours others
on the first hubs. Every hub has in turn 4 devices plugged
Hello,
I'm in a situation where I need to plug 24 high bandwidths USB devices into
the same machine (they're DSL modems actually).
I'm using 6 hubs, 2 of them plugged directly on the PC, and the fours others
on the first hubs. Every hub has in turn 4 devices plugged in.
The trouble is that
Le Lundi 03 Mars 2003 22:07, Gary A. Gorgen a écrit :
I have a system that I just built that has 6 pci HC's.
So, nothing particular is needed to have usb-uhci detect and use them all,
right ?
If your devices and hubs, are USB-1.1,
the hubs are going to kill you.
That looks like whats
Renaud Guérin wrote:
Le Lundi 03 Mars 2003 22:07, Gary A. Gorgen a écrit :
I have a system that I just built that has 6 pci HC's.
So, nothing particular is needed to have usb-uhci detect and use them all,
right ?
Nope, plug them in go.
Are the HC's in your system UHCI only?
If your
18 matches
Mail list logo
