Hi,
attached is the latest version, i'll send it for final review by tldp
this evening arround 23h GMT ( :) 24h German time) in case i don't get more
corections or comments before that.
Quoting Andreas Schuldei <an...@sc...>:
> about section 3.2: I have compiled ONLY the input section into
> the kernel, everything else as modules, both usb and other
> keyboards/mice.
>
> 3.4: if you compile your keyboard subsystems as modules, you can
> decide the order in which they will be detected by the order in
> which you load the modules, that is the order in your
> /etc/modules file on debian.
> the section on USBkeyboards is
> overly complicated, often it will not be an issue since many usb
> keyboards are not split in two.
do you think that i have to add this information ^^^^.
i still think it's a bad idea to have a kernel without integrated keyboard,
if one is enough comfortable with linux he'll find it himself.
> 6.3: this is not really needed, is it? i lived without this up
> untill now. you should mention that it is optional, and what the
> purpose is, really... (c: i did not understand why you did it.
now when i think 6.1 could also be marked as optional but probably it needs a
better name. Suggestions ?
i do not use it on my PC with Radeon AIW and Nvidia TNT2, i use:
snip
.......
Of course in this simple example with only 2 keyboards ( one USB and one PS2)
the problem could be easily avoided by using kernel with primary PS2 input
support. The PS2 keyboard would be found first and bound to VT0, the USB
keyboard would follow and it's real keyboard interface would be bound to VT1, so
there is no need for additional dumb consoles (for the multimedia interfaces of
usb keyboards).
......
snip
i do not use independent soundcards as well.
svetljo
|
