Yes, you're right.  I think b) might be feasible.  I'll try and look at 
it when
I get time.

    -- Lennart

Matthias Drochner wrote:

>lennart@augustsson.net said:
>  
>
>>Just looking at this you can see that the USB keyboard is not your
>>console, the PS/2 keyboard is your console. This is a problem with the
>>PS/2 keyboard driver that claims there's a PS/2 keyboard even when
>>there is none.
>>    
>>
>
>Not quite. Console device selection is done early, before autoconfiguration,
>based on information passed by the bootloader.
>I see 2 ways to resolve this:
>a) find out early that the device which looks like a traditional
>   keyboard (to the BIOS at least) is really a USB keyboard, then either:
>   - don't call pckbdcnattach(), or
>   - add an argument to pckbdcnattach() telling it to take the console
>     for DDB (assuming hardware emulation works), but to abstain
>     from claiming it at autoconfiguration time
>b) in the USB code, find out that the ukbd is emulating a legacy device,
>   and set up a callback for after autoconfiguration which fixes up things
>
>  
>
>>I think it should be fixed, but it's not related to the 
>>USB code
>>    
>>
>
>There was sone discussion (or even a PR) suggesting that a pckbd
>should even be attached if no hardware was detected in _any_ case.
>(Ie, not only if it was designated as console.)
>People want to be able to plug in the kbd later.
>Of course, the KBC was never designed for hotplugging...
>But this is unrelated to console selection, as said.
>
>best regards
>Matthias
>
>
>  
>