f step-by-step guides if you do a web search for
"emulate Bluetooth Linux".
--
- Charles Lepple
https://ghz.cc/charles/
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman
On Jan 14, 2015, at 6:18 AM, Edgar Fuß e...@math.uni-bonn.de wrote:
Thanks for your quick reply.
To be honest, it should be using the output of `libusb-config --libs`
instead (which implicitly addresses both of those points).
Yes, probably.
But once you do that, you are still fighting
?) might
be the right way to go.
There is a maximum packet size in the lsusb output, but I wouldn't expect an
EPIPE error if that did not match. Still something to try, though - EP0 is a
little different than the other endpoints.
--
- Charles Lepple
http://ghz.cc/charles
to the USB device, but I am not sure if that is still an
option. At the very least, it probably requires a developer certificate.
You may want to check out the HIDAPI project instead - if I recall correctly,
it uses the native HID interface on OS X (probably on Windows as well).
--
- Charles Lepple
.
--
Charles Lepple
clepple@gmail
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/libhid-discuss
http://libhid.alioth.debian.org/
On Sep 9, 2011, at 9:37 AM, JamesPK wrote:
Great - thanks for the feedback. Comments online below:
On 09/09/11 03:22, Charles Lepple wrote:
Hi,
Apologies for what might be a basic libhid question.
I'm running Ubuntu, and using libhid via Python to communicate
with a HID device (and have
Note, please subscribe to the list before posting:
http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
On Feb 23, 2011, at 3:03 AM, Alberto Garau wrote:
Hello,
currently I'm working on the port of a stack of software including
libhid and pithon-hid.
I have a little doubt.
From
On Nov 2, 2010, at 12:08 PM, Jacques Dirac wrote:
Guess I'm messing up some addresses. Can someone help me out?
And is there some function to read the paths (to use in the
hid_..._report functions) from the hid tree?
hid_dump_tree(), which is already called by your test program.
Check the
On Oct 29, 2010, at 9:01 AM, Donald Kayser wrote:
Sure would be nice if it worked as claimed.
We can fix that...
I see one tangential mention of libhid and C++ in the home page (the
time of writing was 2005; this doesn't count the description of
SWIG). Where else should I remove any C++
Not supported
bNumDescriptors 1
bDescriptorType34 Report
wDescriptorLength 28
Report Descriptors:
** UNAVAILABLE **
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss
)
The libhid pkg-config file specifies the libusb dependencies for you.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
http://libhid.alioth.debian.org/
with something
innocuous like changing the state of an LED, but if you can power the
test machine from another power source, that would be best.
I won't have time to look at the Windows source code until later
tonight at the earliest.
--
Charles Lepple
On Apr 20, 2010, at 2:50 AM, Gary Briggs wrote:
It appears to be an HID device, and the source code available on that
website uses HID code on windows.
By the way, for browsing the Windows source code, I found the attached
Doxygen[*] configuration file handy.
[*] http://www.doxygen.org
On Sep 9, 2009, at 10:28 AM, Gabriel Rossetti wrote:
I am trying to compile libhid 0.2.16 with python support (using
SWIG) on Mac OS X 10.5.x. The configure fails with this :
Most of my testing was with the Python and SWIG included with Fink.
The framework-based builds of Python are a mess,
On Sep 9, 2009, at 10:35 AM, Gabriel Rossetti wrote:
Hello,
I have a problem where on linux the usbhid module claims my custom
device. I used the hid_force_open() function and it is able to
release the device and claim it but when I try to use
hid_interrupt_read() it says that the device
[please subscribe to the list: http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
]
On Sep 2, 2009, at 11:26 PM, William Good wrote:
Item(Local ): Usage Minimum, data= [ 0x01 ] 1
Button 1 (Primary)
On Sep 1, 2009, at 12:47 PM, Neil Sutton wrote:
On Tue, Sep 1, 2009 at 12:33 PM, Charles Lepple clep...@ghz.cc
wrote:
I would assume that if the argument to Convert.ToByte() is an
integer less than 255, then the C equivalent would be that same
integer. I think you would only use 0x35
On Aug 31, 2009, at 1:22 AM, sajjad gerami wrote:
i have problem with finding path to read and write with libhid
my device parsing :
path: 0xff01.0xff01; type: 0x90
path: 0xff01.0x; type: 0x90
path: 0xff01.0x; type: 0x90
path: 0xff01.0x; type:
On Aug 24, 2009, at 10:29 PM, Tom Isaacson wrote:
I've been looking around for an open source library that provides USB
HID support across Win32, Linux and OS X and libhid seems to fit the
bill, but the GPL is a bit of a problem. I went to look at the MGE
webpage for their HID Parser
On May 31, 2009, at 6:14 PM, george wietor wrote:
I am working on my first libhid project, and have come across a few
return code errors that i don't know what to do with. Is there a
list or document that explains what exactly the libhid return codes
mean?
Use hid_strerror():
On May 1, 2009, at 9:47 AM, Andreas Starlinger wrote:
I'm new to libhid and I have the following situation: I have a Wacom
tablet (it's recognized as a HID device in Windows) and I'm trying to
access the device on my linux system by using the libhid library
(package version 0.2.15, libusb
On May 5, 2009, at 7:14 PM, Felipe França wrote:
Hi, my name is Felipe and i'm a cumputer science student i'm doing a
work for my university. I was looking for libhid tutorials in c or c+
+, but i found only one.
I would like that you send me one tutorial[read/write] in c or c++,
if
On Mar 9, 2009, at 12:25 AM, Ali Asad wrote:
Does the use of libhid require root access?
No, but it does require write access to the USB device node
corresponding to your device, and that node is recreated every time
you plug the device in. (This is not something specific to libhid.)
?
thank you,
- Original Message - From: Charles Lepple clep...@ghz.cc
To: Ael Gain ael.g...@free.fr
Cc: libhid-discuss List libhid-discuss@lists.alioth.debian.org
Sent: Saturday, February 14, 2009 7:46 PM
Subject: Re: [libhid-discuss] simple output
On Feb 13, 2009, at 1:27 PM, Ael Gain
tree of USB device
004/003[0]...
NOTICE: hid_prepare_parser(): successfully set up the HID parser
for USB
device 004/003[0].
Thank you for your help,
cloud
- Original Message -
From: Charles Lepple clep...@ghz.cc
To: Ael Gain ael.g...@free.fr
Cc: libhid-discuss List libhid
On Feb 3, 2009, at 3:25 PM, Brent Bushnell wrote:
For what it's worth, we're having the same issue with a magnetic
stripe reader from ID Innovations.Of special interest also, is
that the report descriptors are unavailable.
Apologies if you've been down this road already, but lsusb won't
On Jan 25, 2009, at 5:14 PM, Adam Gregory wrote:
I am very new to HID on Linux, I am reading through the LIBHID
files now. I was wondering, is there any sample projects using
LIBHID or any beginner information available on the web?
You can refer to the test/ directory in the source tree
On Jan 14, 2009, at 3:18 PM, stdht.in...@gmail.com wrote:
Hello, Charles.
I've made some new experiments. I make hid_interrupt_read in a loop
as before:
while(1) {
ret = hid_interrupt_read(hid, 0x82, buf, 64, 100);
usleep(1000*300);
^ you shouldn't need the usleep() here - all
On Jan 13, 2009, at 5:48 PM, Peter Stuge wrote:
Charles Lepple wrote:
If you send me some pointers to the raw hid API, I will take a
look at it. I am in the process of rewriting the libhid backend to
not be tied to just raw libusb calls.
/usr/src/linux/Documentation/usb/hiddev.txt
I would
= hid_interrupt_read(hid, 0x82, buf, 64, 5000);
if (ret != HID_RET_SUCCESS) {
printf( hid_interrupt_read failed with return code %d\n,
ret);
You should be able to do the following:
printf( hid_interrupt_read failed with return code %d (%s)\n,
ret, hid_strerror(ret));
--
Charles Lepple
On Jan 8, 2009, at 12:31 PM, Ian Thompson wrote:
The reader has a vendor_id = 0x and a product_id = 0x0001.
When running test_libhid.py I get a number of errors.
It appears that the vendor_id = 0x is used as a MATCH_ANY
vendor_id in the library, which is a problem when using
this
Hey everyone,
I'm really confused and any suggestions would be very helpful. I
have a device, and I know (from USB Snoopy on Windows) what data
packets I need to send to it.
You may be interested in this program:
http://iki.fi/lindi/usb/usbsnoop2libusb.pl
It generates a skeleton
, 2008 at 10:25 PM, Charles Lepple clep...@ghz.cc
wrote:
On Dec 22, 2008, at 4:40 PM, Blaine Booher wrote:
Hey everyone,
I am getting the same error when trying to use libhid's python
module as described here: http://bugs.debian.org/cgi-bin/
bugreport.cgi?bug=476525
Sorry
On Nov 16, 2008, at 4:42 PM, Sarah Mount wrote:
Importing libhid.hid looks like it ought to work but actually gives
the following error:
import libhid.hid
Traceback (most recent call last):
File stdin, line 1, in module
File /usr//lib/python2.5/site-packages/libhid/__init__.py, line
On Dec 22, 2008, at 4:40 PM, Blaine Booher wrote:
Hey everyone,
I am getting the same error when trying to use libhid's python
module as described here: http://bugs.debian.org/cgi-bin/
bugreport.cgi?bug=476525
Sorry, this was the first time I heard about the need for a patch.
Usually,
) and after going through the 'apt-src install libhid' routine,
that patch should still apply.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
On Nov 17, 2008, at 10:12 AM, Sarah Mount wrote:
Which doesn't include files such as hid.py, so it looks like the
Canonical people have completely repackaged everything.
I think hid.py was included after 0.2.15.
--
Charles Lepple
___
libhid
any new threads until
after you have opened the devices. (I don't think thread safety was
considered there.)
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo
On Nov 16, 2008, at 4:42 PM, Sarah Mount wrote:
Importing libhid.hid looks like it ought to work but actually gives
the following error:
import libhid.hid
Traceback (most recent call last):
File stdin, line 1, in module
File /usr//lib/python2.5/site-packages/libhid/__init__.py, line
On Nov 16, 2008, at 4:42 PM, Sarah Mount wrote:
ImportError: /usr/lib/python2.5/site-packages/libhid/_hid.so:
undefined symbol: assert
Also, what does 'ldd /usr/lib/python2.5/site-packages/libhid/_hid.so'
return?
--
Charles Lepple
___
libhid
/trunk/swig/hid_ctypes.py
That should work with your existing libhid.so, with some minor path
adjustments in the beginning.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org
hid_set_feature_report (different USB request than sending output
reports).
Still not sure why you got a ValueError, though. Most of the SWIG
functions recognize that integers and longs can be cast to one another.
--
Charles Lepple
___
libhid
the Linux hiddev interface, or the kernel event interface:
http://www.frogmouth.net/hid-doco/p512.html
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/libhid
...
See http://libhid.alioth.debian.org/doc/
hid__opening_8c.html#1ca48853ebe890459271bdb99b8aaac6
The second parameter to hid_force_open() is the interface number.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
of the custom match
function but wanted to run this by somebody.
It's legacy code, due to be replaced sometime. You're on the right
track with the custom match function.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss
the lsusb-
style way of grabbing all of the USB descriptors (not just the HID
report descriptor), and using whichever is longer.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org
-
oriented, and hides some of the C heritage of the code.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
or libhid, you do not need to be concerned
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
Let's try this again.
comicinker, looks like the config.h that you sent is really an
unchanged copy of include/hid.h
Begin forwarded message:
From: Charles Lepple [EMAIL PROTECTED]
Date: September 7, 2008 3:49:17 PM EDT
To: comicinker [EMAIL PROTECTED]
Cc: libhid-discuss
Windows then
downloading all of Visual Studio Express and the platform SDK, or
learning enough German to decipher that log file :-)
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http
It's a known feature.
The original intent was to have bitmasks to match similar product/
vendor IDs, but somewhere along the line it got over-optimized into
what you see now.
If you want your code to work with libhid as it is shipped in various
distributions, you can use the custom matcher
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Device Status: 0x
(Bus Powered)
Charles Lepple wrote:
On Aug 26, 2008, at 2:54 AM, Christopher wrote:
Now that I've got my code compiling (thanks, Marian), I've
only just learning the
stuff.
Ciao, MM
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
--
Charles Lepple
up on email...
Which function are you using? Some of the functions prepend the
reportID, but others that were added later require you to format the
report yourself.
Looks like most of your other questions were answered - please email
if any are still outstanding.
--
Charles Lepple
with libusb-0.1 at this time.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
This same device was actually mentioned in the mailing list nearly
two years ago:
http://thread.gmane.org/gmane.comp.lib.libhid.general/52
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http
On Jul 7, 2008, at 1:27 AM, Aadit Shrestha wrote:
I have tried different Input Paths as specified in your example for
the
Phidgets Quad ServoController, but I have not quite gotten it right.
The problem here is that the HID descriptor uses the same usage and
usage page for some of the
On Jun 26, 2008, at 12:56 AM, shivaprasad javali wrote:
Will I have to write my own custom matcher function?
Most likely, yes.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http
are Linux specific.
Indeed.
Also, if it works in a test application, but not in the final
application, that tells me that you need to rewrite the test
application so that it better reflects what the final application is
doing.
--
Charles Lepple
the libhid API.
--
Charles Lepple
[EMAIL PROTECTED]
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
to get port no?
Look in src/hid_presentation.c for hid_write_identification() - it
prints a location which should probably work for your needs.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http
-and-replace in libhid to get things
to compile. I haven't had the time to find the minimal set of changes
necessary, though.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman
On Apr 21, 2008, at 8:21 PM, comicinker wrote:
Am Freitag, den 28.03.2008, 21:01 -0400 schrieb Charles Lepple:
AND: How can I get the RECV_PACKET_LEN for this address
automatically?
Or is it always the same length for each address (6)? The
test_libhid.c
doesn't tell where this value
On Mar 19, 2008, at 10:36 PM, comicinker wrote:
As I've read in the udev readme, a reboot should not be nevessary
after
saving that file in the udev/rules.d directory. What am I doing wrong?
Not sure - the file looks right.
I thought there was some step where you had to signal udev to
: 0xffa000a5.0x; type: 0x90
path: 0xffa000a5.0x; type: 0x90
path: 0xffa000a5.0x; type: 0x90
Greetings
Matthias Lohr
On Thursday 06 December 2007 21:00:23 Charles Lepple wrote:
Strange. What kernel version are you using?
Matthias Lohr wrote:
[EMAIL PROTECTED]:~$ sudo libhid
exclusively. Since the kernel hiddev
driver no longer sees the device, udev removes the device node. (The
usbdevfs node still remains, and that is what libusb and libhid use
to communicate with the device.)
--
Charles Lepple
___
libhid-discuss mailing
read more than wMaxPacketSize bytes at a time - the kernel will break
the request up into smaller URBs as appropriate. I would advise using
88 bytes, if that's what the minimum repeat length looks like.
--
Charles Lepple
[EMAIL PROTECTED
.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
-archive macros as the basis of the detection, but
you're right, there are definitely cases where it does not work.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo
of data transfer is encoded in the requesttype
parameter. Check the USB specification (chapter 9, I think) for details.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman
was not sent to the correct destination,
but your debug output does not show the diagnostic messages for the
set_report function.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org
On Jun 26, 2007, at 7:55 PM, Jorgen Lundman wrote:
Charles Lepple wrote:
Note that libhid can't claim it exclusively under OS X - it just
pretends it can. It works in some cases, but it looks like
something is
actually using the native HID calls to read from your device
(instead
. libHID was version 0.1, and Martin Krafft
rewrote most of the API and function names in libhid 0.2.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/libhid
some warnings about untested code. That it manages to
claim the
device is much further than I got with libusb.
The key on OS X is to make sure that nothing else might want to claim
the device at the same time.
--
Charles Lepple
___
libhid-discuss
- beats counting lines in
hid.h)
Can you generate any debug output on a platform where the code you're
porting actually runs properly? There's a new USB trace feature in
recent Linux kernels, if you can get the device to a Linux box.
--
Charles Lepple
: error sending control message: Broken pipe
--
Charles Lepple
[EMAIL PROTECTED]
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
there is
a new phone call.
It will block unless you specify a non-zero timeout. If no data is
received in that timeout window, the function will return without
filling the buffer.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss
to set up a cross-compiler first, if you can't compile
on the platform itself.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
to bundle independent functionality in one interface.)
It's hard to say definitively what events will not get through to X until
we see which events are on which interface.
--
Charles Lepple
___
libhid-discuss mailing list
libhid-discuss
79 matches
Mail list logo
