Udev - Revision history

Esden at 19:59, 29 April 2016

2016-04-29T19:59:08Z

← Older revision		Revision as of 13:59, 29 April 2016
Line 21:		Line 21:
	To actually retrigger without having to re-plug it:		To actually retrigger without having to re-plug it:
	sudo udevadm trigger		sudo udevadm trigger

			To reload the udev rules without rebooting your computer:
			sudo udevadm control --reload-rules

	== examples ==		== examples ==

Flixr at 19:23, 1 February 2014

2014-02-01T19:23:53Z

← Older revision		Revision as of 13:23, 1 February 2014
Line 23:		Line 23:

	== examples ==		== examples ==
	udev rule for the floss-jtag serial interface		udev rule for the floss-jtag serial interface (will then be accessible under /dev/jtag-serial)
	SUBSYSTEM=="tty", ATTRS{interface}=="FLOSS-JTAG", ATTRS{bInterfaceNumber}=="01", SYMLINK+="jtag-serial"		SUBSYSTEM=="tty", ATTRS{interface}=="FLOSS-JTAG", ATTRS{bInterfaceNumber}=="01", SYMLINK+="jtag-serial"
	udev rule foe the BlackMagicProbe serial interface		udev rule foe the BlackMagicProbe serial interface (will then be accessible under /dev/bmp-serial)
	SUBSYSTEM=="tty", ATTRS{interface}=="Black Magic UART Port", SYMLINK+="bmp-serial"		SUBSYSTEM=="tty", ATTRS{interface}=="Black Magic UART Port", SYMLINK+="bmp-serial"

Flixr: add example for BMP serial port

2014-02-01T19:23:06Z

add example for BMP serial port

← Older revision		Revision as of 13:23, 1 February 2014
Line 22:		Line 22:
	sudo udevadm trigger		sudo udevadm trigger

	== ~~example~~ udev rule for the floss-jtag serial ==		== examples ==
			udev rule for the floss-jtag serial interface
	SUBSYSTEM=="tty", ATTRS{interface}=="FLOSS-JTAG", ATTRS{bInterfaceNumber}=="01", SYMLINK+="jtag-serial"		SUBSYSTEM=="tty", ATTRS{interface}=="FLOSS-JTAG", ATTRS{bInterfaceNumber}=="01", SYMLINK+="jtag-serial"
			udev rule foe the BlackMagicProbe serial interface
			SUBSYSTEM=="tty", ATTRS{interface}=="Black Magic UART Port", SYMLINK+="bmp-serial"

P0rc0 r0ss0 at 16:11, 14 June 2012

2012-06-14T16:11:58Z

← Older revision		Revision as of 10:11, 14 June 2012
Line 1:		Line 1:
	Also see [http://www.openuas.org/pub/writing_udev_rules.html writing udev rules].		Also see [http://www.openuas.org/pub/writing_udev_rules.html writing udev rules].

			Please see [[Installation/Linux/udev \| paparazzi naming description]] for understanding why do we need udev rules.

	You can get the serial number of your FTDI usb/serial converter		You can get the serial number of your FTDI usb/serial converter

Flixr at 19:22, 21 April 2012

2012-04-21T19:22:58Z

← Older revision		Revision as of 13:22, 21 April 2012
Line 1:		Line 1:
			Also see [http://www.openuas.org/pub/writing_udev_rules.html writing udev rules].


	You can get the serial number of your FTDI usb/serial converter		You can get the serial number of your FTDI usb/serial converter
	connected to your xbee via		connected to your xbee via

Flixr at 18:20, 11 March 2012

2012-03-11T18:20:38Z

← Older revision		Revision as of 12:20, 11 March 2012
Line 17:		Line 17:
	To actually retrigger without having to re-plug it:		To actually retrigger without having to re-plug it:
	sudo udevadm trigger		sudo udevadm trigger

			== example udev rule for the floss-jtag serial ==
			SUBSYSTEM=="tty", ATTRS{interface}=="FLOSS-JTAG", ATTRS{bInterfaceNumber}=="01", SYMLINK+="jtag-serial"

Flixr: Created page with "You can get the serial number of your FTDI usb/serial converter connected to your xbee via udevadm info --query=all --attribute-walk --name=/dev/ttyUSB0 and looking for the line…"

2012-02-06T21:20:24Z

Created page with "You can get the serial number of your FTDI usb/serial converter connected to your xbee via udevadm info --query=all --attribute-walk --name=/dev/ttyUSB0 and looking for the line…"

New page

You can get the serial number of your FTDI usb/serial converter
connected to your xbee via
udevadm info --query=all --attribute-walk --name=/dev/ttyUSB0
and looking for the lines
ATTRS{manufacturer}=="FTDI"
ATTRS{product}=="FT232R USB UART"
ATTRS{serial}=="A80081ej"
where the last one would be your serial you need to write into the rules file, e.g.
# your own XBee ground modem with FTDI USB adapter (adapt serial number)
SUBSYSTEM=="tty", ATTRS{product}=="FT232R USB UART", ATTRS{serial}=="A80081ej", SYMLINK+="paparazzi/xbee", GOTO="tty_FTDI232_end"

To see what udev rules would match (It may show incorrect results, because
some values may be different, or not available at a simulation run.)
udevadm test --action=add $(udevadm info --query=path --name /dev/ttyUSB0)

To actually retrigger without having to re-plug it:
sudo udevadm trigger