[coreboot] How coreboot passes e820-style system memory map to the OS?

Hi, I wonder how coreboot passes the "e820-style" system memory map to the OS. I found the following data structure pointer in the coreboot source code: static struct parameters *faked_real_mode = (void *)REAL_MODE_DATA_LOC; and also this line: void append_command_line(struct parameters *real_m

Re: [coreboot] How coreboot passes e820-style system memory map to the OS?

On 3/25/10 5:39 PM, Darmawan Salihun wrote: > Hi, > > I wonder how coreboot passes the "e820-style" system memory map to the OS. > With SeaBIOS, the OS or bootloader just calls an e820 int call. With FILO or Grub2 the linux kernel takes a parameter structure that is filled with the memory map,

Re: [coreboot] How coreboot passes e820-style system memory map to the OS?

Thanks, all clear now :) On 3/26/10, Stefan Reinauer wrote: > On 3/25/10 5:39 PM, Darmawan Salihun wrote: >> Hi, >> >> I wonder how coreboot passes the "e820-style" system memory map to the OS. >> > With SeaBIOS, the OS or bootloader just calls an e820 int call. > > With FILO or Grub2 the linux k