On Sun, 11 Aug 2002 23:46:01 +0200 (CEST) Ingo Molnar <mingo@elte.hu> wrote:
>
> /*
> * The APM segments have byte granularity and their bases
> * and limits are set at run time.
> */
> - .quad 0x0040920000000000 /* 0x40 APM set up for bad BIOS's */
> - .quad 0x00409a0000000000 /* 0x48 APM CS code */
> - .quad 0x00009a0000000000 /* 0x50 APM CS 16 code (16 bit) */
> - .quad 0x0040920000000000 /* 0x58 APM DS data */
> + .quad 0x0040920000000000 /* 0x80 APM set up for bad BIOS's */
> + .quad 0x00409a0000000000 /* 0x88 APM CS code */
> + .quad 0x00009a0000000000 /* 0x90 APM CS 16 code (16 bit) */
> + .quad 0x0040920000000000 /* 0x98 APM DS data */
I just lost 0x40 which needs to be exactly 0x40 if it is do its job (i.e.
cope with brain dead BIOS writers using 0x40 as a segment offset in
protected mode ...
The idea is that segment 0x40 maps from physical address 0x400 to the end
of the first physical page. As a real mode program would (more or less)
expect it to.
The other three segments don't matter as longs as they are in that order
and contiguous.
-- Cheers, Stephen Rothwell sfr@canb.auug.org.au http://www.canb.auug.org.au/~sfr/ - 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/