On Mon, 2003-09-08 at 19:41, William L. Thomson Jr. wrote: > > > > I think that the drawer will have to use hiddev. > > > > > > I have no problem with that but I am not able to access the drawer under > > > /dev/usb/hiddev* > > > > > > I am not sure if there is something I must do to get the drawer > > > accessible under one of those devices. > > Probably upgrade your kernel, turning on HIDDEV support in the process. You > > should see hiddev0 entry in your logs. > > I am running the lastest kernel from RedHat, as part of the RH 9 distro. > I can try with a generic kernel straight from kernel.org.
I just downloaded and compiled kernel 2.4.22. When I do a cat /dev/usb/hidev* All say no such device > > > > Input events won't work > > > > because of the Application page for POS. I've posted a little > > > > information, but it isn't very good. > > > > Try http://www.frogmouth.net/hid-doco/examples/hiddev-misc/dump-events.c > > > > and http://www.frogmouth.net/hid-doco/examples/hiddev-misc/write-events.c > > > > as examples. > > > > > > Examples of what? Should I be looking at the code or compiling and > > > running it to see the output? I apologize if I am asking the obvious. > > Its a basic example. The write code plays with a keyboard (if you turn off HID > > input support - so you need a non-USB keyboard as well, or a remote login). > > Ok > > > > > I definitely recommend against writing a HID parser (in C or Java - its > > > > still HIDeous). > > > > > > I am not sure what you mean by that. For some reason I am still thinking > > > I will need a driver? > > I mean, do not try to write a HID parser. Use the one in the kernel through > > the hiddev interface. Since I am still unable to access the device via hiddev* what do you think about creating a HID driver instead of a regular usb driver. I am pretty sure the skeleton driver is straight USB. No hid*.h files are included nor hid functions etc called. I still think I need to do something to map the drawer to a device in /dev/usb/ I think I am able to do this with the driver so far. Now it's the hard part communication. If I am communicating with the cash drawer? According to usbview when I load the driver I am kludging together it shows the drawer mapped to the driver. I am able to specify a char device which I have created a test node crw-r--r-- 1 root root 180, 192 Sep 3 03:13 /dev/usb/apgcd When I cat or echo that device I get the read and write functions of the driver. Now I just need to deal with the communication aspect. Which is where I believe you are saying avoid writing a hid parser? -- Sincerely, William L. Thomson Jr. Obsidian-Studios, Inc. http://www.obsidian-studios.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
