-----Original Message-----

> 
> Olivier Blin <[EMAIL PROTECTED]> writes:
> 
> > How can harddrake detect the mouse/keyboard type ?
> > It is easy ?
> 
> it's not.
> see:
> - the issues with detecting the wheel of ps/2 mice

wrt to kernel it is irrelevant. we speak about detecting correct
driver (module) for mouse. To this extent we have (on 2.6)

"psmouse" - for any sort of PS/2 (type is autodetected by driver)
"amimouse" - not relevant for x86
"inport" - busmouse (Microsoft) whatever it is :)
"lgibm" - Logitech bus mouse
"logips2pp" - Logitech PS/2++ - no idea what it is
"maplemouse" - irrelevant
"pc110pad" - IBM touchpad (one of)
"rpcmouse" - irrelevant
"sermouse" - requires user-level helper :(
"synaptics" - for synaptics

what I meant is that harddrake could - automatically or manually -
store mouse driver somewhere, probably in /etc/default/mouse,
for later use by mkinitrd or some otehr script, e.g. gpm

same for keyboard where we really have choice between

"atkbd"
"xtkbd"
"98kbd" - anyone knows waht it is?

> - the recent issues in kernel-2.6.0-test9 with sharing mouse &
>   keyboard box for several machine
> 
> 

Reply via email to