search for: real_mode_base

...dline_size) & ~15; /* Legacy value: pure hope... */ } int bios_boot_linux(void *kernel_buf, size_t kernel_size, @@ -159,7 +156,7 @@ int bios_boot_linux(void *kernel_buf, size_t kernel_size, { struct linux_header hdr, *whdr; size_t real_mode_size, prot_mode_size, base; - addr_t real_mode_base, prot_mode_base; + addr_t real_mode_base, prot_mode_base, prot_mode_max; addr_t irf_size; size_t cmdline_size, cmdline_offset; struct setup_data *sdp; @@ -243,9 +240,19 @@ int bios_boot_linux(void *kernel_buf, size_t kernel_size, real_mode_size = (hdr.setup_sects + 1) <&lt...

"H. Peter Anvin" <hpa at zytor.com> on Tue, 2013/12/03 20:26: > On 10/24/2013 01:09 AM, Christian Hesse wrote: > >>> > >>> version 6.02-pre5 works, 6.02-pre6 does not. > >> > >> Struggled with git bisect, but finally succeeded: > >> > >> 8f470e7bfe75f6401f6c5432988c620b863ad274 is the first bad commit > >>

...ae2a9..ac73729 100644 --- a/com32/lib/syslinux/load_linux.c +++ b/com32/lib/syslinux/load_linux.c @@ -155,8 +155,8 @@ int bios_boot_linux(void *kernel_buf, size_t kernel_size, char *cmdline) { struct linux_header hdr, *whdr; - size_t real_mode_size, prot_mode_size, base; - addr_t real_mode_base, prot_mode_base, prot_mode_max; + size_t real_mode_size, prot_mode_size; + addr_t real_mode_base, prot_mode_base, prot_mode_max, base; addr_t irf_size; size_t cmdline_size, cmdline_offset; struct setup_data *sdp; -- 2.3.0-rc2

...wo regions. Now, for old kernels, there is an additional constraint, which is that the cmdline needs to be part of the same segment as the real mode code, so the above is incorrect for the case of 2.00 or 2.01 kernels loaded high, when the real mode code is loaded low... if we get an address above real_mode_base + 64K those kernels will fail. 2.02+ kernels do not have that limitation. -hpa

...r old kernels, there is an additional constraint, which is that > the cmdline needs to be part of the same segment as the real mode code, > so the above is incorrect for the case of 2.00 or 2.01 kernels loaded > high, when the real mode code is loaded low... if we get an address > above real_mode_base + 64K those kernels will fail. 2.02+ kernels do > not have that limitation. I don't understand the implications of loading the kernel high and real mode code low, what does the location of the kernel have to do with the cmdline? Allocating the cmdline within the same segment as the real mo...

...ib/syslinux/load_linux.c +++ b/com32/lib/syslinux/load_linux.c @@ -323,6 +323,7 @@ int bios_boot_linux(void *kernel_buf, size_t kernel_size, } whdr->code32_start += base - prot_mode_base; + prot_mode_base = base; /* Real mode code */ if (syslinux_memmap_find(amap, &real_mode_base, -- 2.3.0-rc2

...here is an additional constraint, which is that >> the cmdline needs to be part of the same segment as the real mode code, >> so the above is incorrect for the case of 2.00 or 2.01 kernels loaded >> high, when the real mode code is loaded low... if we get an address >> above real_mode_base + 64K those kernels will fail. 2.02+ kernels do >> not have that limitation. > > I don't understand the implications of loading the kernel high and real > mode code low, what does the location of the kernel have to do with the > cmdline? Allocating the cmdline within the sam...

These patches fix a few compiler warnings. Tested on top of commit aee0dc5565711ef5be7c30fb5fc1c5f3f98db09f Jonathan Boeing (6): Use z width specifier when printing size_t variable pxe: fix truncation warning gpllib: fix sizeof(char *) misuse hdt: fix sizeof(char *) misuse hdt: fix sizeof(char *) misuse hdt: fix sizeof(char *) misuse com32/gpllib/dmi/dmi.c | 24 +++---