writing coustomized eudev rule

[parveensunaria]

Hi All,

I am working on detecting a USB dongle a performing mode switch on the application layer.
For this i dont want to use the default made switch rule given with the eudev package.
So, I am just passing the arguments such as vendor ID and Product ID of the USB and all other parameters which is needed for the mode switch.
The issue is the arguments are not passed correctly and due to this i am not able to perform the mode switch.

Are the pattern for passing the arguments is different from the udev rules that we used to perform earlier.

Can some one give me some lights so that i can follow that and complete my task ASAP.

With Regards,
Parveen

[szatox]

Why won't you show us some of the things you tried and their results? You know, old-fashioned glass balls have been out of business for ages.

[parveensunaria]

Hi,

Below is the rule i have written for the USB dongles:

SUBSYSTEM=="usb", ACTION=="add", RUN+="usb_device.sh" DEV_DETECT $env{SUBSYSTEM} $env{ACTION} $attr{devpath} $attr{idvendor} $attr{idproduct} $attr{bInterfaceClass} $attr{bInterfaceSubclass} $attr{bInterfaceProtocol} $attr{bInterfaceNumber}

The script is runned twice and the arguments are passed as:
First time ---> DEV_DETECT usb add 1.4 12d1 1446

Second time-----> DEV_DETECT usb add 08 06 50 00

but the same script was working when we were using udev and the arguments to our application goes as:
First time ---> DEV_DETECT usb add 1.4 12d1 1446

Second time-----> DEV_DETECT usb add 1.4 12d1 1446 08 06 50 00

I have deleted the default usb_modeswitch.rules file.

Do we have any document for writing rules and is this some argument issue. As the value of the arguments are correct but it is passed wrongly and hence the task is not completed.

With Regards,
Parveen