Title: no driver for USB device
Dear all,
I have a 3Com USB bluetooth adapter... I am trying to make it works on a RedHat 7.2 box.
When i tried to plug the adapter into the linux box. >From the file "/var/log/messages", it shows that there is no driver for the USB product. please read the co
Hi Greg,
Here's the 2.4 version of that usbnet patch I sent yesterday.
Same patch except it uses dev->devnum, not dev->devpath
(since that doesn't exist on 2.4 -- yet :).
Can you merge into Marcelo's tree? TIA.
- Dave
> - adds ethtool support (based on code from Brad Hards)
> - makes
This patch merely cleans up the code a little and doesn't fix any bugs.
It makes a couple of code paths a bit easier to understand, removes an
unused variable (uhci_list) and some procfs variables when not using
procfs.
Greg, please apply to 2.4 and 2.5.
JE
--- linux-2.4.19-pre6.orig/drivers/us
This fixes a problem that I've not run into and is difficult to trigger,
but definately a bug. We locked urb->lock, when we meant u->lock. It also
cleans up the code a little to make it easier to understand and removes
an obsolete comment.
Greg, please apply to 2.4 and 2.5.
JE
--- linux-2.4.19-
The dangers of not ensuring important fields are properly set.
Some, if not all, of the speed problems with uhci.c were caused because
some important fields were not set and as a result, FSBR was never
turned on.
This patch also ensures is_suspended is set to 0 properly. This could
cause some pr
Here are some fragments of my (1.try) code:
I used some professional USB sniffer (CATC USBChief) to get an idea what
the computer says to the camera and vice versa.
Then I replayed the packets (at least I hope so) to
achieve the same behaviour.
As I mentioned the TOC works.
- snip
On Sun, Apr 07, 2002, Dominik Kuhlen <[EMAIL PROTECTED]> wrote:
> Here are some fragments of my (1.try) code:
>
> I used some professional USB sniffer (CATC USBChief) to get an idea what
> the computer says to the camera and vice versa.
> Then I replayed the packets (at least I hope so) to
> ach
This patch fixes a bug reported by Greg and David, as well as some other
people recently.
uhci.c would call wait_ms, which can sleep, with spinlocks held. There
are two places where this happens, but only one was the cause of the
problem.
Greg, please apply to 2.4 and 2.5. Thanks!
JE
--- linux
On Sun, Apr 07, 2002, Dominik Kuhlen <[EMAIL PROTECTED]> wrote:
> I'm new to Kernel- and USB programming.
>
> My digital camera does some USB Spec violation (eg : Request type 0x04
> (reserved for future use)), so I'm not sure if its a good idea to write a
> driver.
>
> The next question is ho
Hi,
when using hub.c's usb_reset_device() on somthing connected to the
virtual root hub, the device 'dissapears' from the bus, instead of getting
reset.
With the device in question, the 'Connection' bit breaks away for a few ms.
As the uhci / usb-uhci virtual root hub signals all changes, h
KY Lui wrote:
> I am trying very hard to make the 3com USB Bluetooth works on my Linux
> box.
> I think there are some problems, please help. please read below the
> status.
> 1) I can see that the 3Com SUB device is detected and mounted to ttyUB0
> (when the linux box is booting up)
> 2) I ch
Dear all,
I am trying very hard to make the 3com USB Bluetooth works on my Linux
box.
I think there are some problems, please help. please read below the
status.
1) I can see that the 3Com SUB device is detected and mounted to ttyUB0
(when the linux box is booting up)
2) I checked the file (/
Hello List!
I'm new to Kernel- and USB programming.
My digital camera does some USB Spec violation (eg : Request type 0x04
(reserved for future use)), so I'm not sure if its a good idea to write a
driver.
The next question is how to implement it.
Best would be libusb support -> gphoto support
13 matches
Mail list logo
