Johannes Erdfelt wrote:
On Thu, Nov 07, 2002, Michal Cihar [EMAIL PROTECTED] wrote:
This is DIVA MP3 player, but AFAIK this patch solves simmilar problem
with some card reader.
The device has a hub builtin?
No
Michal Cihar
---
This
Hi,
This patch against 2.4.20-rc1 adds some vendor/product ids for Mustek
and Lexmark scanners. Also, the names of the existing Mustek scanners
were fixed and the product id of the Bearpaw 1200 F was corrected.
I think that's a rather low-risk patch that can be applied. That's why
I splitted it
Hi,
There was a question about if the generic USB scanner driver should go
away in future and if the user-space tools can cope with this.
I guess the main users of the generic driver are SANE and Vuescan. I
can't speak for Vuescan but it is reported to use the generic scanner
driver currently.
On Fri, Nov 08, 2002, Michal Cihar [EMAIL PROTECTED] wrote:
Johannes Erdfelt wrote:
On Thu, Nov 07, 2002, Michal Cihar [EMAIL PROTECTED] wrote:
This is DIVA MP3 player, but AFAIK this patch solves simmilar problem
with some card reader.
The device has a hub builtin?
No
But the
Johannes Erdfelt wrote:
On Fri, Nov 08, 2002, Michal Cihar [EMAIL PROTECTED] wrote:
Johannes Erdfelt wrote:
On Thu, Nov 07, 2002, Michal Cihar [EMAIL PROTECTED] wrote:
This is DIVA MP3 player, but AFAIK this patch solves simmilar problem
with some card reader.
The device has a hub
On Thu, 2002-11-07 at 16:09, Thomas Wahrenbruch wrote:
Because this is my first Linux driver, I don't think that it's perfect...
(especially the kobil_write method...) But it worked very well on my machine.
Its a lot better than most my first driver's
+
+ // allocate memory for
As well as updating some internal docs so they're current,
this patch adds the physical path to the data available
through hotplugging. This feature was requested at the
LinuxKongress hotplug BOF, and was also on my 2.5 list.
And is already present with the DEVPATH environment variable, right?
Pavel, Johannes --
Looks like I can confirm Pavel's report that usbnet now talks
happily to the Zaurus SL-5500 (way to go!) ... but it does make
uhci-hcd get unhappy very quickly:
Well, it works as good as my old does, on 2.5.43. [For some reason, it
does not work any more on 2.5.43 -- host
Hi,
Included in this patch:
- Move allocation of memory out of send_control_msg. With the
allocation moved to open, control messages are less expensive
since they don't allocate and free memory every time.
- Change the behaviour of send_control_msg to return 0
Todd Lyons wrote:
Now USB 2.0 will be interesting if it can sustain the throughput that
it's rated at.
Certainly seems to be able to keep up with typical IDE disks.
I've heard some numbers over 40 MByte/sec, though that's
for newer hardware.
Yes, that gets reasonable to boot or run from.
-
This more or less syncs the 2.4 version with the 2.5 one.
It teaches usbnet how to talk to the SL-5000D/SL-5500,
and the A-300. It's got some cleanups of how it talks
to other StrongArm PDAs -- which is most of the patch by
volume, other than making the GPL explicit.
This will make Zaurus
On Fri, 8 Nov 2002, Johannes Erdfelt wrote:
But the hub is what is disconnecting the port. What hub are you using?
Hm, IMHO the hub doesn't disconnect (how would it?) it merely reports the
device gets disconnected. Sure, it's minor nitpicking, but IMHO important
for understanding the problem.
On Sat, Nov 09, 2002, Martin Diehl [EMAIL PROTECTED] wrote:
On Fri, 8 Nov 2002, Johannes Erdfelt wrote:
But the hub is what is disconnecting the port. What hub are you using?
Hm, IMHO the hub doesn't disconnect (how would it?) it merely reports the
device gets disconnected. Sure, it's
uhci-hcd (PIIX4)
- ping worked
- ssh root@zaurus halted it, seemingly at first TX
The uhci-hcd dmesg output was un-informative, as it's been
before when I've hit this failure. Just two messages:
- host controller process error, something bad happened
- host controller halted. very bad
For
On Fri, 8 Nov 2002, David Brownell wrote:
The uhci-hcd dmesg output was un-informative, as it's been
before when I've hit this failure. Just two messages:
- host controller process error, something bad happened
- host controller halted. very bad
was the /proc/driver/uhci/pci addr output
One thing I noticed while prepareing that 63K patch was that some of the
config options appear to not do anything.
I grep-ed for CONFIG_USB_OHCI_SA CONFIG_USB_UHCI_ALT CONFIG_USB_UHCI_HCD
CONFIG_USB_UHCI and did not find them in elsewhere so these may be left over
from earlier work. I may also
16 matches
Mail list logo
