diff options
Diffstat (limited to 'src/doc')
| -rw-r--r-- | src/doc/src/b2qt.qdoc | 25 |
1 files changed, 4 insertions, 21 deletions
diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 207be78..a787c4d 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -213,29 +213,12 @@ \section1 Setting up Access to Development Hardware via USB On Ubuntu Linux you have to grant your development user access to - plugged in devices. This is done by creating a new \e{udev} rule that - allows access to the device via USB. In order to do that, you need to - find out the USB ID of your device. - - First, power up the device and connect it to your development - machine with a USB cable. Then, look for a line listing your - device in the output generated by the \c{lsusb} command. - - For example: - - \code - $ lsusb - ... - ... - Bus 001 Device 008: ID 18d1:9018 Google Inc. - ... - \endcode - - Take note of the numbers stated after \c{ID}, and replace them in the - following shell command: + plugged in devices. This is done by creating a new \e{udev} rule + that allows access to the device via USB. First, run the following + command in a shell: \code - echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="9018", TAG+="udev-acl"' | sudo tee -a /etc/udev/rules.d/70-boot2qt.rules + echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", TAG+="udev-acl"' | sudo tee -a /etc/udev/rules.d/70-boot2qt.rules \endcode Now disconnect and reconnect the USB cable. Confirm that the |