minor updates to the documentation files

This commit is contained in:
Daniel Pavel 2013-05-21 00:46:07 +03:00
parent 843d2a224d
commit 11ba96103c
3 changed files with 16 additions and 14 deletions

View File

@ -80,6 +80,8 @@ who also provided some internal
- [Alexander Hofbauer](http://derhofbauer.at/blog/blog/2012/08/28/logitech-performance-mx) - [Alexander Hofbauer](http://derhofbauer.at/blog/blog/2012/08/28/logitech-performance-mx)
- [Clach04](http://bitbucket.org/clach04/logitech-unifying-receiver-tools) - [Clach04](http://bitbucket.org/clach04/logitech-unifying-receiver-tools)
- [Peter Wu](https://lekensteyn.nl/logitech-unifying.html) - [Peter Wu](https://lekensteyn.nl/logitech-unifying.html)
- [Nestor Lopez Casado](http://drive.google.com/folderview?id=0BxbRzx7vEV7eWmgwazJ3NUFfQ28)
provided some more Logitech specifications for the HID++ protocol
Also thanks to Douglas Wagner, Julien Gascard and Peter Wu for helping with Also thanks to Douglas Wagner, Julien Gascard and Peter Wu for helping with
application testing and supporting new devices. application testing and supporting new devices.

View File

@ -7,9 +7,9 @@ For some devices, extra settings (usually not available through the standard
Linux system configuration) are supported: Linux system configuration) are supported:
* The [K750 Solar Keyboard][K750] is also queried for its solar charge status. * The [K750 Solar Keyboard][K750] is also queried for its solar charge status.
Pressing the `Solar` key on the keyboard will pop-up the application window Pressing the `Light-Check` button on the keyboard will pop-up the application
and display the current lighting value (Lux) as reported by the keyboard, window and display the current lighting value (Lux) as reported by the
similar to Logitech's *Solar.app* for Windows. keyboard, similar to Logitech's *Solar.app* for Windows.
* The state of the `FN` key can be toggled on some keyboards ([K750][K750] and * The state of the `FN` key can be toggled on some keyboards ([K750][K750] and
[K800][K800]). It changes the way the function keys (`F1`..`F12`) work, i.e. [K800][K800]). It changes the way the function keys (`F1`..`F12`) work, i.e.

View File

@ -28,22 +28,22 @@ automatically (it will switch to root when necessary), or you can do all the
required steps by hand, as the root user: required steps by hand, as the root user:
1. copy `rules.d/99-logitech-unfiying-receiver.rules` from Solaar to 1. copy `rules.d/99-logitech-unfiying-receiver.rules` from Solaar to
`/etc/udev/rules.d/` `/etc/udev/rules.d/`
By default, the rule makes the Unifying Receiver device available for r/w by By default, the rule makes the Unifying Receiver device available for r/w by
all users belonging to the `plugdev` system group (standard Debian/Ubuntu all users belonging to the `plugdev` system group (standard Debian/Ubuntu
group for pluggable devices). It may need changes, specific to your group for pluggable devices). It may need changes, specific to your
particular system's configuration. If in doubt, replacing `GROUP="plugdev"` particular system's configuration. If in doubt, replacing `GROUP="plugdev"`
with `GROUP="<your username>"` should just work. with `GROUP="<your username>"` should just work.
2. run `udevadm control --reload-rules` to let the udev daemon know about the 2. run `udevadm control --reload-rules` to let the udev daemon know about the
new rule new rule
3. physically remove the Unifying Receiver, wait 10 seconds and re-insert it 3. physically remove the Unifying Receiver, wait 10 seconds and re-insert it
This is necessary because if the receiver is already plugged-in, it already This is necessary because if the receiver is already plugged-in, it already
has a `/dev/hidraw?` device node, but with the old (`root:root`) permissions. has a `/dev/hidraw?` device node, but with the old (`root:root`) permissions.
Plugging it again will re-create the device node with the right permissions. Plugging it again will re-create the device node with the right permissions.
4. make sure your desktop users are part of the `plugdev` group, by running 4. make sure your desktop users are part of the `plugdev` group, by running
`adduser <linux user> plugdev` as root `adduser <linux user> plugdev` as root