From owner-freebsd-hackers Fri Aug 30 21:00:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA18078 for hackers-outgoing; Fri, 30 Aug 1996 21:00:09 -0700 (PDT) Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA18070; Fri, 30 Aug 1996 21:00:05 -0700 (PDT) Received: (from durham@localhost) by w2xo.pgh.pa.us (8.6.12/8.6.9) id AAA07403; Sat, 31 Aug 1996 00:00:15 -0400 Date: Sat, 31 Aug 1996 00:00:15 -0400 (EDT) From: Jim Durham X-Sender: durham@w2xo.pgh.pa.us To: sos@freebsd.org cc: regnauld@tetard.glou.eu.org, hackers@freebsd.org Subject: Re: Specs on a Hitachi CM2085me monitor anybody ?? In-Reply-To: <199608300650.IAA13048@ra.dkuug.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 30 Aug 1996 sos@freebsd.org wrote: > > > 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 > 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... > That might not be all bad. Hacking the bios is certainly better, but having all the Unix boot messages would solve most problems, except hardware ones. If you wanted to hack some BIOS code, I guess you could probably use an old MFM disk controller with a rom on board and just unplug or otherwise disable all the controller chips and just use it for a ROM card... or any old controller card that had a ROM on board. I guess you'd want a 16 bit card. (I have a ton of old 8 bit HD controllers 8-) ). How hard would it be to find the mode set in the BIOS roms themselves? I know there's a High and Low rom and all that (I've hacked a little on an old AT bios). Would it be possible to recognize the mode setting values in the ROM without the source? That would be a cleaner job than hanging another ROM in there, but no nearly as portable! Jim Durham