From owner-freebsd-hackers Mon Aug 18 00:55:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA05368 for hackers-outgoing; Mon, 18 Aug 1997 00:55:48 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA05360 for ; Mon, 18 Aug 1997 00:55:44 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id RAA19957; Mon, 18 Aug 1997 17:55:05 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id RAA10910; Mon, 18 Aug 1997 17:25:05 +0930 (CST) Message-ID: <19970818172504.50471@lemis.com> Date: Mon, 18 Aug 1997 17:25:04 +0930 From: Greg Lehey To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: hackers@FreeBSD.ORG Subject: Re: reset screen hardware? References: <19970818122939.30413@lemis.com> <199708180645.IAA01679@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 0.81e In-Reply-To: =?iso-8859-1?Q?=3C199708180645=2EIAA01679=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Mon=2C_Aug_18=2C_1997_at_08=3A45=3A2?= =?iso-8859-1?Q?6AM_+0200?= Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-MIME-Autoconverted: from 8bit to quoted-printable by freebie.lemis.com id RAA10910 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id AAA05361 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Aug 18, 1997 at 08:45:26AM +0200, Søren Schmidt wrote: > In reply to Greg Lehey who wrote: >> There is, BTW, a potential problem with the "call the BIOS" approach >> (which I consider marginally more of a hack, since the driver doesn't >> know what's going on): what if the driver has set a different mode for >> the board, like 50 line or some such? That would have to be redone >> after the BIOS call. > > Sigh, the call BIOS is the only option we've got, (well besides making > it possible to use win95/NT drivers, which is a HUGE task if at all > feasible). I think the BIOS calls are bad enough without incorporating all the Microslop stuff. To do it halfway right, we probably need to reset the board and then replay any changes that the driver has made since then. Obviously, the first step is to reset the board. > There is no problem in using the BIOS (except that we dont have the > code to do it, yet). Syscons allways know exactly where it has its > video card, except in the case of X where the app reprograms > the card. Now when we have the BIOS calls working syscons takes over the > task of modifying the cards regs etc. via the BIOS, and the apps are > denied acces to the ports. Then syscons always knows where and how > the card is and can restore whatever mode it (and of cause the BIOS) > understand. Yes, it would be even nicer if we could get the X server to call syscons to set the registers... > Pretty simple actually, once you have the means to call the BIOS... > > Now, who volounteers the diffs ?? OK, I'll take a look at it. Mike sent me the URL ftp://sumatra.americantv.com/pub/vm86-970814.tar.gz; anything else I should look at? Greg