Q: I have a (non Acer) notebook which is not recognized by your driver but I
think it should. What information do you need?

A: If it is a non-Acer laptop I would like to know, what makes you think that
your laptop would work with my driver. A windows driver/utility package of the
name "LaunchManager" or "EasyButton" is a good hint. If it is clear that your
hardware is okay, I need the string with your model name from BIOS. Please
don't ask me how to do it. To find out which functions of your laptop the
driver will support, it is best, if you can tell me where to get this
"LaunchManager" package.

Q: Why can't I activate my wireless hardware on Acer TM 420/430/6000/8000 ...?

A: On many newer laptops (Dritek type) I do not now how to do this,
sorry. Someone would need to find out how windows does it. Volunteers?

Q: Why do I always get 0x00 from /proc/driver/acerhk/key?

A1: Check the type of your laptop if /proc/driver/acerhk/info. If it is
"Dritek", you cannot read the keys from the driver. Starting from version
0.5.17 you get "n/a" out of the key file in this case.
A2: If you have polling enabled (default) you will almost always read 0x00
from this file. This is because in every polling cycle it is checked for key
events and if there is one, it is instantly translated and sent to the kernel
input system. Starting with version 0.5.20 you get "n/a" out of the key file
in this case.

Q: When I press a key, nothing happens. Why are they not working?

A: Most keys won't do anything by themself. If nothing happens, that is
because no programm knows what to do with the new keys. You need to assign
actions to them, use the hotkey manager of your desktop to do that. If
using Gnome, you find it under desktop settings - keyboard shortcuts.

Q: My keys do not work, I only get kernel messages of the form:
atkbd.c: Unknown key pressed (translated set 2, code 0xf4 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e074 <keycode>' to make it known.

A: Press each of the buttons and note the mentioned
code for it (e074 in this example). You should get a list like this:
P1	e074
P2	e075
...
If you are finished with it, look into /usr/include/linux/input.h, using
your favourite text viewer/editor. Search for "KEY_STOP". You should see
the following line in the file:

#define KEY_STOP                128

After it many more lines with equal #defines should be visible. Look for
key names which best match the names of your buttons, e.g. KEY_PROG1,
KEY_WWW and so on. Note the numbers assigned to the names, for KEY_STOP
this would be 128, for KEY_PROG1 148.
Now you have a list with three items per entry, your button, a code
from the kernel messages and a corresponding number from the file
linux.h:
P1	e074	148
P2	e075	149
...
For each line in this list, issue the setkeycodes command as mentioned
in the kernel message:
setkeycodes e074 148
setkeycodes e075 149
...
After doing that, the keys should be available for your hotkey manager.
