From owner-freebsd-current  Fri Mar 28 09:06:12 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA20957
          for current-outgoing; Fri, 28 Mar 1997 09:06:12 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA20949
          for <freebsd-current@freebsd.org>; Fri, 28 Mar 1997 09:06:05 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA17098; Fri, 28 Mar 1997 10:05:30 -0700 (MST)
Date: Fri, 28 Mar 1997 10:05:30 -0700 (MST)
Message-Id: <199703281705.KAA17098@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
Cc: freebsd-current@freebsd.org (FreeBSD-current users)
Subject: Re: Funny sc0 behaviour
In-Reply-To: <19970328112019.PN39531@uriah.heep.sax.de>
References: <19970328112019.PN39531@uriah.heep.sax.de>
X-Mailer: VM 6.22 under 19.14 XEmacs Lucid
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

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