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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/