From owner-freebsd-hackers Mon Sep 9 10:47:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA07430 for hackers-outgoing; Mon, 9 Sep 1996 10:47:03 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA07423 for ; Mon, 9 Sep 1996 10:47:00 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id DAA23167; Tue, 10 Sep 1996 03:32:44 +1000 Date: Tue, 10 Sep 1996 03:32:44 +1000 From: Bruce Evans Message-Id: <199609091732.DAA23167@godzilla.zeta.org.au> To: freebsd-hackers@FreeBSD.org, j@uriah.heep.sax.de Subject: Re: Support for fixed-scan monitors Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> > Syscons (and pcvt) should start the same device as the BIOS, anyway. > >> Given the quirks of BIOSes, that would have to be the [CEV]GA. I Or mono. >> don't think syscons knows which device is being used by BIOS (please No, but it's easy to decide: using_mono = *(u_short *)0x463 == 0x3b4; >> correct me if I'm wrong here). I haven't checked pcvt. So, I believe >> this is mostly a matter of choice (and not of using what BIOS uses). > >This is a mistake of motherboard and BIOS vendors. There used to be a This is a mistake of console driver authors :-). >jumper on the motherboards back in the old days, denoting the prefered >graphics console. (The BIOSes usually complained if it was set wrong, >i.e. choose a nonexistant adapter.) > >pcvt correctly honors it, but i agree that this feature is now almost >worthless. pcvt actually looks in the CMOS RAM to determine the adaptor that the BIOS is supposed to use. The jumper method was worse, except possibly for bootstrapping the screen/monitor combination. It may be wrong to use the CMOS value because the bootstrap may have changed the mode (I'm not sure of the BIOS changes the CMOS to match the mode). Bruce