Re: issues with unknown/new alias

Re: issues with unknown/new alias

[Alan Jenkins]

On 13/09/12 08:25, Christoph Jung wrote:
> Hello,
>
> I am from the company "Code Mercenaries GmbH" from Germany. We have 
> some USB HID devices wich work with Linux.
> Since kernel version 2.6 our default products will be included in the 
> kernel.
>
> Devicedetails
> VendorID: 0x07C0
> ProductIDs: 0x1500, 0x1501, 0x1511, 0x1512, 0x1503
> Devicename: iowarrior
>
> Now we have some new custom product IDs but this two new devices get 
> no node in dev/usb/ , but I can find the with "lsusb".
> If I run "modinfo iowarrior" there will be 5 alias (with the default 
> pIDs) .
>
> The two new pIDs are: 0x158A, 0x158B
>
> I have not much experiance with linux (I work with Ubuntu 12.04).
Same OS and version, but I have no /dev/usb/ directory at all.  My guess 
is your problem isn't about modules.  I do have /dev/input/ though :).

What are you saying; does it not work?  If it has standard buttons 
(mouse/keyboard equiv), do they work under X?

Check out "ls-input" and "input-events" (apt-get install input-utils).  
"evtest" is similar, maybe slightly friendlier (apt-get install evtest).

You can check that your module has bound to the device by inspecting /sys/.

                  v-- try replacing usbhid with "iowarrior"

$ ls /sys/module/usbhid/drivers/usb:*/

3-2:1.0  bind  module  new_id  remove_id  uevent  unbind

^-- USB address of my standard device (mouse)


You could also see the device nodes created by udev, if you run "udevadm 
monitor --property" and plug the device in.  It's very verbose, but the 
last event should probably show DEVNAME=/dev/input/eventNN (and 
SUBSYSTEM=input near the end).

> What have be done to get the device nodes to work with them?
> Have I add some rules? Or have I edit the iowarrior.ko?

I don't think you need to add custom udev rules.

Alan

Re: issues with unknown/new alias [retraction]

[Alan Jenkins]

On 13/09/12 08:25, Christoph Jung wrote:
> Hello,
>
> I am from the company "Code Mercenaries GmbH" from Germany. We have 
> some USB HID devices wich work with Linux.
> Since kernel version 2.6 our default products will be included in the 
> kernel.
>
> Devicedetails
> VendorID: 0x07C0
> ProductIDs: 0x1500, 0x1501, 0x1511, 0x1512, 0x1503
> Devicename: iowarrior
>
> Now we have some new custom product IDs but this two new devices get 
> no node in dev/usb/ , but I can find the with "lsusb".
> If I run "modinfo iowarrior" there will be 5 alias (with the default 
> pIDs) .
>
> The two new pIDs are: 0x158A, 0x158B
>
> I have not much experiance with linux (I work with Ubuntu 12.04). What 
> have be done to get the device nodes to work with them?
> Have I add some rules? Or have I edit the iowarrior.ko?
>
Argh, sorry, I misread your email and went off on one.

You will indeed need to "edit iowarrior.ko".  I.e. change the C source 
code to include the new pIDs, recompile, test, get patches merged into 
the mainline kernel etc :).

It's also possible to test new devices with an old driver, i.e. before 
you modify it.  Possible instructions: http://www.ha19.no/usb/

Alan

Re: issues with unknown/new alias [retraction]

[Alan Jenkins]

On 13/09/12 09:57, Christoph Jung wrote:
> Am 13.09.2012 10:49, schrieb Alan Jenkins:
>> On 13/09/12 08:25, Christoph Jung wrote:
>>> Hello,
>>>
>>> I am from the company "Code Mercenaries GmbH" from Germany. We have 
>>> some USB HID devices wich work with Linux.
>>> Since kernel version 2.6 our default products will be included in 
>>> the kernel.
>>>
>>> Devicedetails
>>> VendorID: 0x07C0
>>> ProductIDs: 0x1500, 0x1501, 0x1511, 0x1512, 0x1503
>>> Devicename: iowarrior
>>>
>>> Now we have some new custom product IDs but this two new devices get 
>>> no node in dev/usb/ , but I can find the with "lsusb".
>>> If I run "modinfo iowarrior" there will be 5 alias (with the default 
>>> pIDs) .
>>>
>>> The two new pIDs are: 0x158A, 0x158B
>>>
>>> I have not much experiance with linux (I work with Ubuntu 12.04). 
>>> What have be done to get the device nodes to work with them?
>>> Have I add some rules? Or have I edit the iowarrior.ko?
>>>
>> Argh, sorry, I misread your email and went off on one.
>>
>> You will indeed need to "edit iowarrior.ko".  I.e. change the C 
>> source code to include the new pIDs, recompile, test, get patches 
>> merged into the mainline kernel etc :).
>>
>> It's also possible to test new devices with an old driver, i.e. 
>> before you modify it.  Possible instructions: http://www.ha19.no/usb/
>>
>> Alan
>>
>>
> Ah ok but where will I find the sourcecode for iowarrior.ko ?
> I have no idea about compiling, patching in linux
>
> Christoph
>

The kernel is all one big tree.  The file you're looking for is 
drivers/usb/misc/iowarrior.c.  (Preview at 
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/usb/misc/iowarrior.c). 
The change you're talking about should be fairly straightforward - just 
look for the existing ids.

Step 1 for me has always been to compile a whole kernel. Unfortunately 
that's a bit of learning curve.  I'm not sure which resources to recommend.

Alan

Re: issues with unknown/new alias

[Kay Sievers]

On Thu, Sep 13, 2012 at 10:27 AM, Alan Jenkins
<alan.christopher.jenkins@gmail.com> wrote:
> On 13/09/12 08:25, Christoph Jung wrote:

>> Now we have some new custom product IDs but this two new devices get no
>> node in dev/usb/ , but I can find the with "lsusb".
>> If I run "modinfo iowarrior" there will be 5 alias (with the default pIDs)
>> .
>>
>> The two new pIDs are: 0x158A, 0x158B
>>
>> I have not much experiance with linux (I work with Ubuntu 12.04).
>
> Same OS and version, but I have no /dev/usb/ directory at all.  My guess is
> your problem isn't about modules.  I do have /dev/input/ though :).

He probably meant: /dev/bus/usb/, which everybody should have these
days, while /dev/usb/ is no ususal place.

Kay