Alan Stern wrote:
The patch below may help. Try it out and let us know what happens.
Yes, thats fine now. I am now a happy little 2.6 kernel user!
Thanks to all of you for the all the work on Linux USB.
Jon
---
This SF.net email is spon
Alan,
> > There is only one device connected to the host and it has only control
> > endpoint. This is not to intermix different control messages, see there
> > are some 10 TDs containing data from one control message, If the UHCI is
> > scheduling them vertically, every second TD in the frame cau
Hi, all
I am working on this driver (porting it to a custom hardware). It looks
like I am missing some files. I have source and header file to control
the chip, but I am missing the front end -- the stuff that wraps it into
a Linux driver. Can anyone send me those files, please or let me know
the
Greg:
This patch helped Jon Wilson. It allows devices to have a configuration
numbered 0, in spite of the standard convention that config #0 really
means unconfigured. Please apply.
Alan Stern
--- a/drivers/usb/core/message.c.orig Fri Oct 24 13:10:05 2003
+++ b/drivers/usb/core/message.c
This patch makes config.c more liberal about the sorts of interface
numbering it will accept when reading interface descriptors. The current
code only allows interfaces numbered 0..(bNumInterfaces-1), but a number
of devices erroneously number their interfaces starting at 1.
With this patch, t
Greg:
For a long time, I've been getting debug warnings about missing release()
methods in various kobjects. They come up because your usb-2.5 tree has
DEBUG defined in a number of driver-model source files.
It's not easy to track down exactly what the objects in question are; the
driver-model
On Sun, 2003-10-26 at 19:19, Joshua Wise wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> > I've got a samsung 16T202DA VFD which (has a parallel interface and) is
> > attached to a carrier board with a usb cable attached. I'm guessing the
> > carrier board does some type of seria
On Mon, 2003-10-27 at 10:06, Henry Culver wrote:
>
> I think this device is a Sasem OnAir Remocon IR/VFD combo. The VFD is
> a Samsung. I found a windoze driver for it. I suppose the best way to
> proceed is to plug it into a windows machine and load the driver and
> poke at it that way. Any
Hello,
I have a functional USB Gadget API (i.e. device-side) implementation
(net2280.o) for my NetChip Net2280 PCI card (it is actually part of the
standard Linux kernel distribution). This is great for development on a
PC-based desktop system.
Now, moving over to the embedded system -- Atmel AT91
Bahns, Christopher H wrote:
Hello,
I have a functional USB Gadget API (i.e. device-side) implementation
(net2280.o) for my NetChip Net2280 PCI card (it is actually part of the
standard Linux kernel distribution). This is great for development on a
PC-based desktop system.
Glad to hear that the not-
Alan,
With this patch prism2_usb works.
Great fix, thanks!!!
//lauri
On Monday 27 October 2003 18:10, Alan Stern wrote:
> This patch makes config.c more liberal about the sorts of interface
> numbering it will accept when reading interface descriptors. The current
> code only allows interfaces
On Mon, 27 Oct 2003, Lauri Ojantakanen wrote:
> Alan,
> With this patch prism2_usb works.
>
> Great fix, thanks!!!
That's good enough for me. Greg, I think this patch can be applied.
It's not a perfect solution, in that there are still drivers that directly
index the interfaces[] array. But
One-line summary: plug-in your USB keyboard, see your machine die.
So, I have this non-name USB keyboard (with built-in 2-port USB hub)
which reliably crashes 2.6.0-test{8,9} on both x86 and ia64. In
retrospect, it's clear to me that the same keyboard also occasionally
crashes 2.4 kernels, but th
On Fri, Oct 24, 2003 at 05:15:13PM -0400, Alan Stern wrote:
> On Thu, 23 Oct 2003, Pedro Larroy wrote:
> > abort.log -> 2.6.0test8
> > devices -> 2.6.0test8
> > kernel.log -> 2.6.0testx where x < 8
> >
> > In abort.log, is the paste of the log with kernel 2.6.0test8 in kern.log
> > there is a lo
Greg, this is a patch for 2.5/6 -- please apply. The description follows
in the forwarded message.
Matt
- Forwarded message from Alan Stern <[EMAIL PROTECTED]> -
Date: Fri, 24 Oct 2003 15:14:21 -0400 (EDT)
From: Alan Stern <[EMAIL PROTECTED]>
Subject: PATCH: (as118) Command failure code
On Mon, Oct 27, 2003 at 02:35:09PM -0800, David Mosberger wrote:
> One-line summary: plug-in your USB keyboard, see your machine die.
Any chance to know where the machine dies? Any oops you can help us out
with?
> So, I have this non-name USB keyboard (with built-in 2-port USB hub)
> which relia
Greg, this is a 2.5/6 patch -- please apply. The description is below.
The residue update shouldn't make much of a difference, as almost nobody
checks that value. But, it is reported via sg, so it should be accurate.
Matt
- Forwarded message from Alan Stern <[EMAIL PROTECTED]> -
Date:
> On Mon, 27 Oct 2003 17:30:13 -0800, Greg KH <[EMAIL PROTECTED]> said:
Greg> On Mon, Oct 27, 2003 at 02:35:09PM -0800, David Mosberger
Greg> wrote:
>> One-line summary: plug-in your USB keyboard, see your machine
>> die.
Greg> Any chance to know where the machine dies? Any oops y
---
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net
19 matches
Mail list logo
