i have a breakout board with an FT232RL. when the board is
attached to ubuntu 12.04lts, udev (i think) grabs it and
assigns the ftdi_sio module.
udevadm info --attribute-walk --name=/dev/ttyUSB0
was used to get the attributes for the device.
with that, wrote the following rule:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001",
ATTRS{serial}=="A800f3Pu", OPTIONS+="ignore_device"
that rule does not work. after much research, found
http://lwn.net/Articles/364728/:
udev 148
========
The option "ignore_device" does no longer exist. There is no way to
ignore an event, as libudev events can not be suppressed by rules.
It only prevented RUN keys from being executed, which results in an
inconsistent behavior in current setups.
that statement suggests there is not a way to block an action.
blacklisting i suppose. but if i blacklisted ftdi_sio, then no
ftdi device could be used.
i'm searching for a way to keep one specific board/chip from being
assigned a module so i can work with it in bitbang mode.
On 5/10/14, E.S. Rosenberg <es.rosenberg+libftdi.i2net@xxxxxxxxx> wrote:
> blacklist the module?
> udev syntax may have changed but udev rules should still work too...
> You need to be a bit more specific...
>
>
>
> 2014-05-11 0:33 GMT+03:00 gobo <gobo770@xxxxxxxxx>:
>
>> can anyone offer suggestions on how to stop the assignment of a
>> specific device to a module?
>>
>> i've tried to write a udev rule, but it seems OPTIONS+="ignore_device"
>> is no longer valid.
>>
>> thanks.
>>
>> --
>> libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
>> To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
>>
>>
>
>
> --
> libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
> To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
