Date: Fri, 28 Mar 1997 10:05:30 -0700 (MST) From: Nate Williams <nate@mt.sri.com> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: Funny sc0 behaviour Message-ID: <199703281705.KAA17098@rocky.mt.sri.com> In-Reply-To: <19970328112019.PN39531@uriah.heep.sax.de> References: <19970328112019.PN39531@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
J Wunsch writes:
> sc0: the current keyboard controller command byte 0045
..
> sc0 at 0x60-0x6f irq 1 on motherboard
> sc0: MDA/hercules <16 virtual consoles, flags=0x0>
...
> Of course, most of the above is a lie. :-) This machine has neither
> a keyboard connected, nor a graphics card present at all.
>
> Shouldn't sc0 fail probing in this case?
Sure, but because of pst's 'DETECT_KBD' patch, it always returns true in
the failure mode.
return ((dev->id_flags & DETECT_KBD) ? 0 : IO_KBDSIZE);
----------------------------
revision 1.181
date: 1996/10/23 07:29:43; author: pst; state: Exp; lines: +8 -7
Remove SC_KBD_PROBE_WORKS option and replace it with a simple run-time flag
bit (0x0008) in the sc driver configuration line. This way it's easy to
boink a generic kernel.
Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703281705.KAA17098>