François Revol <revol@xxxxxxx> wrote: > En réponse à Bruno van Dooren <bruno_van_dooren@xxxxxxxxxxx>: > > there has to be some way to do this right? > Depends if you talk about PS2 controller or the device plugged in > it... > > Anyway, > 1) > rescan kbmouse > is cleaner than moving your driver around. > (I think input_server does that when you restart it) > > 2) > Another thing you can do is publish a device anyway, and answer EIO > or ENODEV until there is a real mouse plugged. > > 3) > Another possibility is to keep your driver loaded and have it > self-rescanned if it gets an irq telling a mouse has been plugged. > > I'd go for 2), as 3) is more complex for not much better, besides the > PS/2 port isn't supposed to be plug-n-play (even if I do myself > hotplug my mouse sometimes :) I would recommend 1) or 2) - OpenBeOS will introduce a new driver module which makes the "rescan" command unnecessary. One way would be to have the PS/2 driver as a bus module which sits there and waits until a device is plugged in, and publishes the mouse/ keyboard driver, then. Anyway, as François already pointed out, PS/2 is not (meant to be) hot- pluggable, so a simple solution is preferred for now. Adios... Axel.