From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386 arch subdivision into machine types for 2.5.8
Date: Tue, 16 Apr 2002 18:27:23 -0500 [thread overview]
Message-ID: <200204162327.g3GNRO606562@localhost.localdomain> (raw)
In-Reply-To: Message from ebiederm@xmission.com (Eric W. Biederman) of "16 Apr 2002 15:44:37 MDT." <m1n0w3iaii.fsf@frodo.biederman.org>
ebiederm@xmission.com said:
> Yes. I'm totally for the ability to select from config.in. But at
> the same time having being able to build a kernel that works in all
> kinds of configurations comes in quite handy. I know the alpha does
> this I'm not quite certain about ARM.
The alpha uses a machine type function table switch to achieve this. It's
certainly possible, just slightly more than I bargained for.
The issue will become more interesting with Patrick's cpu/bus/mtrr switch,
where self configuration does become more of an issue. Can I just wait to see
what he comes up with and then copy it?
> Do you have boot problems on the NCR voyagers? If so I'd be
> interested in hearing what the issues are.
The 8 byte GDT alignment requirement in boot/setup.S was the biggest problem
(until I found it empirically), if that's not done, they crash when jumping to
protected mode.
Not all boot managers work on voyager: grub and syslinux don't, lilo does (for
now) but complains that EBDA is too big.
I think it's because they actually have a larger than 384k hole (low memory
seems to end at 588k instead of 640k), but I was just so relieved to get them
to boot finally that I've never explored the problems in detail.
This is the actual memory map:
BIOS-provided physical RAM map:
Voyager-SUS: 0000000000000000 - 0000000000093000 (usable)
^^^^^ usually around 9fffff
Voyager-SUS: 0000000000100000 - 000000003ffff000 (usable)
James
next prev parent reply other threads:[~2002-04-16 23:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 15:55 James Bottomley
2002-04-16 16:46 ` Patrick Mochel
2002-04-17 0:55 ` Keith Owens
2002-04-16 19:30 ` Eric W. Biederman
2002-04-16 20:51 ` James Bottomley
2002-04-16 21:06 ` Dave Jones
2002-04-16 21:44 ` Eric W. Biederman
2002-04-16 23:27 ` James Bottomley [this message]
2002-04-16 23:43 ` H. Peter Anvin
2002-04-17 7:00 ` Eric W. Biederman
2002-04-17 16:31 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200204162327.g3GNRO606562@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®