On Mon, 24 Oct 2005, Pete Zaitcev wrote:
> Well, that's fine, but this is certainly overdoing it:
>
> > -#define HIDDEV_BUFFER_SIZE 64
> > +#define HIDDEV_BUFFER_SIZE 1024
>
> That's 24 KILOBYTES of zeroes. Not to mention that anything larger than
> two pages worth is nearly impossible to allocate
On Fri, 7 Oct 2005 04:00:51 -0400 (EDT), Keith Winstein <[EMAIL PROTECTED]>
wrote:
> Unfortunately, for devices with more than 64 elements in their reports
> (such as the X-keys Jog & Shuttle Editor, which has a wDescriptorLength of
> 91, and the X-keys Joystick Controller, with wDescriptorLength
On Wed, 19 Oct 2005 12:52:02 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote:
> This revised patch (as586b) makes usb-handoff permanently true and no
> longer a kernel boot parameter. [...]
This looks all right. I thought it was a good thing to do, though
I did not want to get rid of the parame
linux-usb-devel，您好！
Can you tell me how to write the hid device under Linux ?
I can open("/dev/hiddev0",O_RDWR),but wrong write(fd, buff, sizeof(buff)) ,why?
thank you!
致
礼！
闫石磊
[EMAIL PROTECTED]
2005-10-25
On Mon, 24 Oct 2005 16:28:25 PDT, Paul Stewart <[EMAIL PROTECTED]> wrote:
> I've backported the FT2232C driver mods to ftdi_sio in the 2.4.32-rc1
> kernel.
I can take it. But don't set your hopes too high, Marcelo is
suspiciously quiet recently.
-- Pete
---
On Mon, 24 Oct 2005 16:26:29 -0700 (PDT), gary clark <[EMAIL PROTECTED]> wrote:
> 1) Does libusb support notification of usb devices
> connected/disconnected?
You can do select() on fd of /proc/bus/usb/devices
-- Pete
---
This SF.Net email is
Pete Zaitcev wrote:
There's not much reply which weren't replied a 1000 times, so I suppose
fatigue sets in.
I did search the archives for several relevant things (like "HID") but
didn't find much...
You have to find out how to control the device. If
it's a HID device, it tells you.
It
I've backported the FT2232C driver mods to ftdi_sio in the 2.4.32-rc1
kernel. I've tested it against my home-built FT2232C-based board and
both ports are functional as far as bit rate and I/O is concerned,
although I haven't tested that all the control lines; however these
code changes are der
Hello,
I have two questions for the gurus:
1) Does libusb support notification of usb devices
connected/disconnected?
2) What is the correct API to disable/enable a usb
device
in libusb?
Much appreciated,
Garyc
---
This SF.Net email is spo
On Tue, 25 Oct 2005 00:01:33 +0100, Gervase Markham <[EMAIL PROTECTED]> wrote:
> Gervase Markham wrote:
> > The Griffin AirClick USB is a five-button RF remote control, with a USB
> > receiver dongle. Having won one at EuroOSCON, it would be nice if it
> > could be made to work on an OS OS ;-)
>
Gervase Markham wrote:
The Griffin AirClick USB is a five-button RF remote control, with a USB
receiver dongle. Having won one at EuroOSCON, it would be nice if it
could be made to work on an OS OS ;-)
Given that I've had no response, could someone tell me if this is the
wrong list to ask su
On Mon, 24 Oct 2005 23:48:06 +0200, Laurent Pinchart <[EMAIL PROTECTED]> wrote:
> USB drivers usually use a driver specific structure to hold all kind of
> information about a device instance. Depending on the driver, those
> structures are stored in a static array, or are allocated in the probe
Hi everybody,
it didn't take long before I ran into a problem and need your help.
Fortunately, it's a small problem.
USB drivers usually use a driver specific structure to hold all kind of
information about a device instance. Depending on the driver, those
structures are stored in a static arr
Hi Greg,
another one to use kzalloc. Please apply.
Regards
Oliver
Signed-off-by: Oliver Neukum <[EMAIL PROTECTED]>
--- a/drivers/usb/class/cdc-acm.c 2005-10-20 08:23:05.0 +0200
+++ b/drivers/usb/class/cdc-acm.c 2005-10-24 22:38:36.0 +0200
@@ -
Hi Greg, hi list,
here is another one to use kzalloc. Please apply.
Regards
Oliver
Signed-off-by: Oliver Neukum <[EMAIL PROTECTED]>
--- a/drivers/usb/image/microtek.c 2005-10-20 08:23:05.0 +0200
+++ b/drivers/usb/image/microtek.c 2005-10-24 22:32:10.000
Greg:
This patch (as592) makes a few small improvements to the way device
strings are handled, and it fixes some bugs in a couple of other sysfs
attribute routines. (Look at show_configuration_string() to see what I
mean.)
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
---
Inde
Greg:
This patch (as591) fixes a rather innocuous bug that has been around for
quite a long time: Virtual root hubs should have a maxpacket length of 64
for endpoint 0. I didn't realize it was wrong until I started looking
through the endpoint attribute files.
Alan Stern
Signed-off-by: Alan
Greg:
This patch (as590) fixes up all the remaining places where usbcore can
use kzalloc rather than kmalloc/memset.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
---
Index: usb-2.6/drivers/usb/core/devio.c
===
--- us
Greg:
I can't stand text lines that wrap-around in my 80-column windows. This
patch (as589) makes cosmetic changes to a couple of source files.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
---
Index: usb-2.6/drivers/usb/core/sysfs.c
=
Greg:
This patch (as588) fixes the way endpoint attribute files are registered
and unregistered. Now they will correctly track along with altsetting
changes. This fixes bugzilla entry #5467.
In a separate but related change, when a usb_reset_configuration call
fails, the device state is not c
Greg:
This patch (as587) improves the implementation of USB endpoint sysfs
files. Instead of storing a whole bunch of attributes for every single
endpoint, each endpoint now gets its own kobject and they can share a
static list of attributes. The number of extra fields added to struct
usb_ho
Greg:
The patches that follow fix the problem of endpoint sysfs files not
getting updated properly, and they clean up a bunch of other things in
usbcore as well. Although they are mostly independent, a few of them
touch the same files so it will be best to apply them in sequence by their
patch
Phil Dibowitz <[EMAIL PROTECTED]> writes:
> Vendor: 10d6
> Product: 1100
> bcd: 0100-0100
>
> Then you cover only your device. Much better.
Sure. I understood that will propose a new patch in comming days. I'm
only trying to pick up the stick since mine friend isn't callable
those days. I should
On Monday 24 October 2005 17:04, Philip Hindman wrote:
> I'll assume that if usb_submit_urb() fails, my complete routine
> wasn't called.
Yes.
Philip, I don't like this also...
In my driver, if usb_submit_urb() fails, I set urb->status to contain
the error code, and the call the completion routi
On Fri, 21 Oct 2005, Franck wrote:
> But the HCD can decide to not add the urb into the ep's queue if
> something is going wrong...In that case it refuses to own the urb.
> What I was thinking of is: the usbcore initialized the urb then passes
> it to HCD through hcd->urb_enqueue. the HCD initiail
On Mon, 24 Oct 2005, Savita H. Neelannava wrote:
> Hi,
>
> i hv written a USB Driver for scanner. Evrything works fine except one thing,
> which is surprisal removal of USB device. If manually unload the driver, it
> will bw loaded properly, but when i disconnect device when application is
> o
On Mon, 24 Oct 2005, vishal wrote:
> I moved a majority of the changes from the 2.6.13 file_storage gadget driver
> into 2.6.5 . A few things like msleep_interruptible() & try_to_freeze()
> which were supported in 2.6.13 i didnt try to move. A pecular problem i am
> seeing is that my file_stora
Hi Savitha,
Which version of Kernel are you using?
If you are facing problem while disconnecting, please check disconnect
function what all data structure you need to clear after disconnecting
the device that would solve your problem.
It may be clearing data structure is not happening at the ri
Hi everybody,
I've done it. I decided to take the big step, and started hacking a USB Video
Class driver for the Linux kernel.
My first goal is to support the Logitech Quickcam Fusion, which is the only
UVC device I currently own. When I'll be done with it, I will try to extend
the code to sup
On 10/21/05, Pete Zaitcev <[EMAIL PROTECTED]> wrote:
> On Fri, 21 Oct 2005 14:42:39 -0500, Philip Hindman <[EMAIL PROTECTED]> wrote:
>
> > I ask because the WDM analog to usb_submit_urb() actually guarantees
> > that my completion routine *will* be called, even in error conditions,
> > and looking
Am Montag, 24. Oktober 2005 15:39 schrieb Savita H. Neelannava:
>
> Hi,
>
> i hv written a USB Driver for scanner. Evrything works fine except one thing,
> which is surprisal removal of USB device. If manually unload the driver, it
> will bw loaded properly, but when i disconnect device when ap
Hi,
i hv written a USB Driver for scanner. Evrything works fine except one thing,
which is surprisal removal of USB device. If manually unload the driver, it
will bw loaded properly, but when i disconnect device when application is open,
control comes in scanner_disconnect function where i a
32 matches
Mail list logo
