re: kern/53599: Can't enter ddb using USB keyboard because console

[matthew green <mrg%eterna.com.au@localhost>]

The following reply was made to PR kern/53599; it has been noted by GNATS.

From: matthew green <mrg%eterna.com.au@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
    netbsd-bugs%netbsd.org@localhost, gson%gson.org@localhost (Andreas Gustafsson)
Subject: re: kern/53599: Can't enter ddb using USB keyboard because console
Date: Thu, 13 Sep 2018 06:20:02 +1000

 >  Martin Husemann wrote:
 >  >  Try
 >  >  	userconf=disable pcbkc*
 >  >  
 >  >  in your /boot.cfg.
 >  
 >  I think you mean pckbc*, not pcbkc*.
 >  
 >  But that doesn't work, either: with "userconf=disable pckbc*" in
 >  boot.cfg, the dmesg shows
 >  
 >    [130] pckbc* disabled
 >  
 >  but pckbc0 attaches anyway:
 >  
 >    pckbc0 at isa0 port 0x60-0x64 
 >    pckbd0 at pckbc0 (kbd slot) 
 >    pckbc0: using irq 1 for kbd slot 
 >    wskbd0 at pckbd0: console keyboard, using wsdisplay0
 >  
 >  If I add the two lines
 >  
 >    userconf=disable pckbc0
 >    userconf=disable pckbc*
 >  
 >  no pckbc attaches, but I still get the "HP Virtual Keyboard" as
 >  wskbd0:
 
 yes - the "pckbc*" is a literal match here.  it matches the
 configuration "pckbc*", which itself is able to attach to
 any instance, but it doesn't stop the literal pckbc0 at isa
 that is in GENERIC.  so, this is entirely "as designed".
 
 the base problem - i wonder if we can have a wsconcstl or
 wsconscfg based method (ioctl) to enable console/ddb.  then
 we can at least have a simple method to enable this while
 not actually affecting security.
 
 
 .mrg.