[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#497230: [alpha] legacy and generic package descriptions

That's, what, 5MB of space? It seems to me we have it backwards -- legacy should be the default, and folks on newer hardware can apt-get install the "non-legacy" kernel if they want to free up 5mb of physical memory. Or am I missing something?

Matthew W. S. Bell wrote:
On Tue, 2008-09-02 at 00:32 +0100, Matthew W. S. Bell wrote:   
Well, I still don't entirely know what the -legacy package is for nor 
what constitutes an "Alpha Legacy Machine". Looking at the linux-2.6 
Debian changelog it appears it may be something to do with MILO.
Further investigation eventually reveals that the only change in the
kernels is the CONFIG_ALPHA_LEGACY_START_ADDRESS. This option has the
following help:
The 2.4 kernel changed the kernel start address from 0x310000 to
0x810000 to make room for the Wildfire's larger SRM console. Recent
consoles on Titan and Marvel machines also require the extra room.

If you're using aboot 0.7 or later, the bootloader will examine the ELF
headers to determine where to transfer control. Unfortunately, most
older bootloaders -- APB or MILO -- hardcoded the kernel start address
rather than examining the ELF headers, and the result is a hard lockup.

Say Y if you have a broken bootloader.  Say N if you do not, or if `you
wish to run on Wildfire, Titan, or Marvel.

Hopefully this should be informative enough for the creation of some
explanatory prose for -legacy and -generic.



Brian Szymanski
email:  skibrianski@gmail.com
skype:  xbrianskix
cell:   +1 202 747 4019
jabber: skibrianski@gmail.com
aim:    xbrianskix

Ex cibus merda

Reply to: