> > > HIDIOCGSTRING - struct hiddev_string_descriptor (read/write) Gets a
> > > string descriptor from the device. The caller must fill in the "index"
> > > field to indicate which descriptor should be returned.
> > Can you please tell me in what range this index is?
>
> Please refer to USB spec
On Fri, 10 Aug 2007, Folkert van Heusden wrote:
> > HIDIOCGSTRING - struct hiddev_string_descriptor (read/write) Gets a
> > string descriptor from the device. The caller must fill in the "index"
> > field to indicate which descriptor should be returned.
> Can you please tell me in what range thi
Hi,
In linux/Documentation/usb/hiddev.txt I read the following:
> HIDIOCGSTRING - struct hiddev_string_descriptor (read/write)
> Gets a string descriptor from the device. The caller must fill in the
> "index" field to indicate which descriptor should be returned.
Can you please tell me in what r
I am currently looking at using a MegTek USB insertion reader and I have
run into a problem with the current hiddev. The card reader returns a
338 byte Input report on the interrupt in channel everytime a card is
inserted. The data contains basically all the information needed from
the card. The
I'm currently looking at developing a way to interface with a couple of
HID devices. Specifically a bill acceptor and a swipe card reader.
Both devices are detected and picked up by the hiddev kernel module, but
as far as I can see the hiddev doesn't provide everything I need to get
full support
> Hey,,thank you for the help. But what you told me I already knew. My
> question now is, how can I give a byte like 0xb1 to the device? Have I to
> split it up,or have I to adapt the hiddev.h?
You can't modify hiddev.h.
uref.value = (unsigned char)*report++;
should do the job.
Laurent Pinchart
Am Donnerstag, 3. November 2005 15:27 schrieben Sie:
> > The second value is on ffb1 and not on b1, that must be because value
> > is defined as __s32, or not? How can I modify this in linux, because I
> > think it is not enough to adapt the hiddev.h and set "_u32 value" in the
> > hiddev_usage
> The second value is on ffb1 and not on b1, that must be because value
> is defined as __s32, or not? How can I modify this in linux, because I
> think it is not enough to adapt the hiddev.h and set "_u32 value" in the
> hiddev_usage_ref
> int knx_send( const char report[5], int fd )
> {
Hi!
I am working on a hid under Linux Suse and i want to communicate with it. it
is working under Windows, I have to adapt it also for Linux. I was able to
read out some device infos, but I have some problem with sending and
recieving data from the device.
I wrote a little c-program to handle a
Hi!
I am working on a hid under Linux Suse and i want to communicate with it. it
is working under Windows, I have to adapt it also for Linux. I was able to
read out some device infos, but I have some problem with sending and
recieving data from the device.
I wrote a little c-program to handle a
Jeff Lange wrote:
Johannes, the device is fully HID
compliant, it is just a vendor defined usage. The reason for this was
to make Windows driver a lot easier to write. I think I'm just going
to have to write my own kernel driver for this thing and create a char
dev that my app can read the dat
Ken,
I too am writing a USB MSR =). Johannes, the device is fully HID
compliant, it is just a vendor defined usage. The reason for this was
to make Windows driver a lot easier to write. I think I'm just going
to have to write my own kernel driver for this thing and create a char
dev that my a
Jeff Lange wrote:
Hi all,
I'm developing a simple USB device that reports itself as a HID
device, and uses interrupt transfers to send about 250 bytes of data
whenever an event occurs on the device. I've managed to communicate
with it and get the data using libusb, but I've found that if the
On Wed, 2005-06-08 at 12:37 -0400, Jeff Lange wrote:
> I'm developing a simple USB device that reports itself as a HID
> device, and uses interrupt transfers to send about 250 bytes of data
> whenever an event occurs on the device.
Why do you do this as opposed to *not* identifying as a HID dev
Hi all,
I'm developing a simple USB device that reports itself as a HID
device, and uses interrupt transfers to send about 250 bytes of data
whenever an event occurs on the device. I've managed to communicate
with it and get the data using libusb, but I've found that if the hid
module is insert
Hi Ken,
If you look at the bug filed in the Linux Kernel Bugzilla
(http://bugzilla.kernel.org/show_bug.cgi?id=1048),
there is an explanation of the problem and a proposed patch.
In hid-core.c, in function hid_input_field(), there is the
following code:
if (field->flags & HID_MAIN_ITEM_RELATIVE) {
Hi,
Does anybody know the reason why hid input report "caching" /
"duplicate elimination" is really needed? That is, if a HID
device sends a report with the same absolute value twice, the
second report gets swallowed in hid_input_field(). Similarly,
relative values of zero never make it through t
hello,
I have a problem with my device who works under linux with usb.
I have read 'the USB HID for Linux USB' of Brad Hards which had really help above all
the part entitled "the hid device interface'.
Nevertheless I can't write on dev/usv/hiddev0, I don't know why.
So, I am interested in the
On Thu, May 06, 2004 at 08:15:15PM +1000, herbert wrote:
>
> The current code is applying the maxusage limit to GUSAGE/SUSAGE. This
> is incorrect as the number of values is stored in field->report_count,
> not field->maxusage. The USB phone from www.virbiage.com is one device
> where report_cou
Hi:
The current code is applying the maxusage limit to GUSAGE/SUSAGE. This
is incorrect as the number of values is stored in field->report_count,
not field->maxusage. The USB phone from www.virbiage.com is one device
where report_count exceeds maxusage.
The following patch corrects the check fo
Hi:
The current code is applying the maxusage limit to GUSAGE/SUSAGE. This
is incorrect as the number of values is stored in field->report_count,
not field->maxusage. The USB phone from www.virbiage.com is one device
where report_count exceeds maxusage.
The following patch corrects the check fo
I have a problem reading from my hid-device using the hid module.
I managed to send commands to the device using the CSREPORT and
CSUSAGE, but i cant seem to get the information back from the device.
As i have writen the firmware myself, i know that the device responds to command
through
endpoin
I've noticed in 2.6 kernels that HIDIOCGREPORT does not wait for io
completion before returning to the caller. This creates a few unpleasant
issues for userspace:
First, code sequences such as...
ioctl(fd, HIDIOCGREPORT, &rinfo);
ioctl(fd, HIDIOCGUSAGE, &uinfo);
ioctl(fd,
Hi folks,
following my recent posts on libusb-devel and hidups, here's
a patch to disable hiddev support for MGE UPSs. It only
declares VID/PID as QUIRK_IGNORE in hid-core's blacklist.
This simply prevent hiddev to be loaded when plugging
an MGE UPS.
As always, due to my brain damaged Notes mai
Hi, all
Greetings.
I am trying to program a USB GPS device through HIDDEV interface on
Linux. I believe the device is built upon Cypress CY7C64013 full speed
USB-to-Serial chip and it shows as a generic HID device when plugged
in. It require a feature report with char[5] data to change sett
Hi !
I haven written a small prog to handle a HID keyboard (standard mouse +
keyboard + special keys/sliders) we are developping. Mouse and keyboard are
managed by X, special keys are handled through hiddev by my small prog.
This prog reads report from hiddev ( we have 3 In-Endpoints on our keyboa
David Brownell wrote:
Wes Janzen wrote:
I can't seem to open the hiddev device... The driver appears to
install and the APC UPS is listed in lsusb with the driver HID, but I
can't open it.
I suspect it is caused by this:
<7>drivers/usb/host/ehci-q.c: clear tt 00:0a.2-3 p3 buffer, a4 ep0
<3>
Wes Janzen wrote:
I can't seem to open the hiddev device... The driver appears to install
and the APC UPS is listed in lsusb with the driver HID, but I can't open
it.
I suspect it is caused by this:
<7>drivers/usb/host/ehci-q.c: clear tt 00:0a.2-3 p3 buffer, a4 ep0
<3>drivers/usb/core/hub.c: us
I can't seem to open the hiddev device... The driver appears to install
and the APC UPS is listed in lsusb with the driver HID, but I can't open it.
I suspect it is caused by this:
<7>drivers/usb/host/ehci-q.c: clear tt 00:0a.2-3 p3 buffer, a4 ep0
<3>drivers/usb/core/hub.c: usb-00:0a.2-3 clear t
> From: Jackson Chan <[EMAIL PROTECTED]>
> Date: Mon, 9 Jun 2003 11:57:36 -0600
> > I have been trying to solve this problem for a long time and any help
> > would be greatly appreciated.
In such case you would be well advised to stop being a jerk
and cross-post the same stupid question everywher
> Hi,
>
> I have been trying to solve this problem for a long time and any help
> would be greatly appreciated.
>
> Problem: I am having difficulty trying to connect a USB
> SMARTBoard(digital whiteboard) to my Linux machine.
> Specifically: HID/HIDDEV is not claiming the device.
>
> I am u
> Thanx to the help of gregkh I've figured out that the feature reports
> I tried to generate are generating an EPIPE, which is a babble, which
> means that I'm babbeling. Which is true.
It'd be really nice if babbling were consistently EOVERFLOW,
with EPIPE reserved exclusively for stall. OHCI
Hello,
Thanx to the help of gregkh I've figured out that the feature reports
I tried to generate are generating an EPIPE, which is a babble, which
means that I'm babbeling. Which is true.
The feature description says that I should send two bytes in a feature
report. According to the specificatio
Hello,
If I'm understanding everything correct you should do this to get a
feature report to a usb device:
/* set report_type and report_id in rinfo */
IOCGREPORTINFO(struct hiddev_report_info* rinfo)
IOCGREPORT(struct hiddev_report_info* rinfo)
/* set uref's report_id, report_type field_index
On Fri, Jun 08, 2001 at 07:43:31AM +1000, root wrote:
> While running a descriptor dump (code attached) on my USB speakers with
> the hiddev ioctl()s in 2.4.5-ac7, I hit the following oops using JE's
> UHCI. Repeatable on this HCD, not tried on OHCI or GA's UHCI.
>
> >>EIP; Before first
While running a descriptor dump (code attached) on my USB speakers with
the hiddev ioctl()s in 2.4.5-ac7, I hit the following oops using JE's
UHCI. Repeatable on this HCD, not tried on OHCI or GA's UHCI.
>>EIP; Before first symbol
Trace; c885d423 <[hid]hiddev_ioctl+293/920>
Trace; c019a7
36 matches
Mail list logo
