From owner-freebsd-hackers Thu Aug 29 23:50:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA13717 for hackers-outgoing; Thu, 29 Aug 1996 23:50:39 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA13712; Thu, 29 Aug 1996 23:50:36 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id IAA13048; Fri, 30 Aug 1996 08:50:34 +0200 Message-Id: <199608300650.IAA13048@ra.dkuug.dk> Subject: Re: Specs on a Hitachi CM2085me monitor anybody ?? To: durham@durham (Jim Durham) Date: Fri, 30 Aug 1996 08:50:34 +0200 (MET DST) Cc: sos@freebsd.org, regnauld@tetard.glou.eu.org, hackers@freebsd.org In-Reply-To: from "Jim Durham" at Aug 29, 96 10:28:43 pm From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to Jim Durham who wrote: > > On Thu, 29 Aug 1996 sos@freebsd.org wrote: > > > > > Of course, the absolute topper would be to hack the BIOS rom so that > > > > it natively boots to something your monitor can handle! ;-) . > > > > > > Well, a shareware BIOS (Dr.Bios) exists out there -- does it come > > > with sources ? > > > > You don't need to hack the video BIOS (its the one on the video > > card you would want to change not the motherboard one :) ), it > > should do it by makeing an extra BIOS rom whith the needed code > > in it, at let it register AFTER the std video BIOS has done its trick. > > > > > Hmmm... where would you plug it in? Maybe in an empty bootprom socket on a netcard :) > I wasn't aware that you could replace the video mode set routines > in the BIOS with code from another ROM, as you do with drivers, etc. You can do all kinds of nasty things like this i a PC architecture that is exactly why its such a pain in the a... > Just where does syscons.c start functioning in the boot process? What > messages would you see if you just hacked the starting mode in the > syscons.c file to work with the fixed-freq monitors? Would you only > miss the AMI BIOS messages about system config? You would get output from where syscons takes over, that is after the first call to scinit. In effect it would look like what you get from a dmesg. You would miss everything up to that point. You could also hack the boot manager to do resonable things to you video mode, then you would be in business even earlier... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time.