Date: Thu, 2 Mar 1995 14:39:45 -0800 (PST) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: phk@ref.tfs.com (Poul-Henning Kamp) Cc: davidg@Root.COM, wpaul@freefall.cdrom.com, CVS-commiters@freefall.cdrom.com, cvs-sys@freefall.cdrom.com Subject: Re: cvs commit: src/sys/i386/boot/biosboot probe_keyboard.c Message-ID: <199503022239.OAA15284@gndrsh.aac.dev.com> In-Reply-To: <199503022146.NAA08185@ref.tfs.com> from "Poul-Henning Kamp" at Mar 2, 95 01:46:48 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > Modified: sys/i386/boot/biosboot probe_keyboard.c > > > Log: > > > Some people have complained that they were unable to boot the > > > Feb. 10th snapshot. The keyboard probe in the bootblock seems to > > > have been singled out as the cause of these problems, so I've beefed it > > > up alittle. This pushes us right up to the edge of the size limit: > > > the second stage boot is now 7152 bytes in size, just 8 bytes under > > > the wire. On the other hand, the new probe now does almost exactly > > > what syscons does, so hopefully this will do the trick. It seems > > > to work properly on my hardware, but then so did the old probe. > > > > This is going to be a problem...there are some (other) bugs that I need to > > fix that will require some bytes themselves. > > There is plenty of bytes to spare, if we get all the "date16 ; mov this,that" > turned into real 16 bit instrs. Any takers ? There is no such thing as ``real 16 bit instrs''. You have 8 bit inst and you have current mode inst, which are either 16bit or 32bit depending on the CS GDT entry size bit. You have to use data16; mov this, that when dealing with 16 bit values running in a 32 bit code segment. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503022239.OAA15284>