Date: Wed, 12 Apr 2006 09:56:12 -0700 From: Wes Peters <wes@opensail.org> To: John Baldwin <jhb@FreeBSD.org> Cc: Maxim Sobolev <sobomax@FreeBSD.org>, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, cvs-src@FreeBSD.org Subject: Re: cvs commit: src/sys/boot/i386/cdboot cdboot.s Message-ID: <4F4CF4E1-6A65-4129-9F21-ED466E433BAA@opensail.org> In-Reply-To: <200604110818.20705.jhb@freebsd.org> References: <200604110439.k3B4dTOD072774@repoman.freebsd.org> <200604110818.20705.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 11, 2006, at 5:18 AM, John Baldwin wrote:
> On Tuesday 11 April 2006 12:39 am, Maxim Sobolev wrote:
>> sobomax 2006-04-11 04:39:29 UTC
>>
>> FreeBSD src repository
>>
>> Modified files:
>> sys/boot/i386/cdboot cdboot.s
>> Log:
>> When enabling A20 put upper limit on amount of time we wait for the
>> keyboard controller to get ready (65K x ISA access time, visually
>> around 1
>> second). If we have wait more than that amount it's likely that the
>> hardware is a legacy-free one and simply doesn't have keyboard
>> controller
>> and doesn't require enabling A20 at all.
>>
>> This makes cdboot working for MacBook Pro with Boot Camp.
>
> You'll probably need to do the same for boot1 and I think BTX.
> Alternatively, you should see how the loader is handling A20 and
> do that in the various boot programs instead (I think there's a PR
> somewhere about using a BIOS call instead of frobbing the keyboard
> controller directly that supposedly fixes things like USB keyboards
> in the loader.)
Do you think this might also be the problem that prevents FreeBSD
from booting on Virtual PC for Mac OS/PPC? That's been frustrating
me for months, but I haven't had time to do anything about it.
--
Where am I, and what am I doing in this handbasket?
Wes Peters
wes@softweyr.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F4CF4E1-6A65-4129-9F21-ED466E433BAA>
