From: Vojtech P. <vo...@su...> - 2002-09-17 15:35:36
|
On Tue, Sep 17, 2002 at 02:06:45PM +0300, Aivils Stoss wrote: > Hi, Vojtech > > How to is safer register new keyboard without necessary VT. > Into kdb_connect() keyboard.c we have James comment: > /* If we have more keyboards than VTs we still register the handler. > * It is possible someone might add a graphics card thus needing the > * keyboard later */ > With this we have: > handle->private == 0 ,if can't find VT. > Can I solve this with single line in kbd_event() > if(!handle->private) return; > So this keyboard still registered, but no process any event. > Or kbd_connect() return NULL pointer? Is it allowable? If you return NULL, that means you're not interested in that device for now and ever. > Allow Your i386 arch oriented drivers hot remove/replug? Yes. > Perform removing automatic unregistering? Not always - PS/2 mice and AT keyboards are not unregistered until a new device is plugged in. > What should happen if keyboard replugged under linux-ruby? You get a disconnect for the old one and a connect for the new one. It might be the same keyboard, of course. > How many USB keyboards should work independ? Any number. > Should work USBBP simultaneous with USB-HID keyboard? BootProtocol shouldn't be used at all. -- Vojtech Pavlik SuSE Labs |