Displaying 8 results from an estimated 8 matches for "calc_cmdline_offset".
2013 Dec 04
2
Boot iPXE from syslinux/isolinux
...stantial payload (0x59f50 bytes.)
>
> I am guessing that that is the source of the problems, but I'm still
> at a loss from staring at the code. If you could try turning on
> debugging output by having debug.c32 installed on the system and running:
>
> debug bios_boot_linux calc_cmdline_offset
>
> ... from the command line before trying to load ipxe.lkrn?
>
> I should try it out myself if I can find the time...
Sure. Here we go:
boot: debug -e bios_boot_linux calc_cmdline_offset
boot: ipxe.lkrn
Loading ipxe.lkrn... ok
cmdline_offset at 0x9f7e0
Initial memory map:
Could no...
2013 Dec 04
0
Boot iPXE from syslinux/isolinux
On 12/04/2013 12:38 AM, Christian Hesse wrote:
>
> Sure. Here we go:
>
> boot: debug -e bios_boot_linux calc_cmdline_offset
> boot: ipxe.lkrn
> Loading ipxe.lkrn... ok
> cmdline_offset at 0x9f7e0
> Initial memory map:
> Could not find location for protected-mode code
> Booting kernel failed: Invalid argument
>
OK, that was a useful clue. I think I know what is going on. The
problem is that we...
2013 Oct 24
5
Boot iPXE from syslinux/isolinux
Christian Hesse <list at eworm.de> on Tue, 2013/10/22 13:14:
> Christian Hesse <list at eworm.de> on Tue, 2013/10/22 12:56:
> > Gene Cumm <gene.cumm at gmail.com> on Tue, 2013/10/22 06:35:
> > > On Tue, Oct 22, 2013 at 5:41 AM, Christian Hesse <list at eworm.de> wrote:
> > > > Hello everybody,
> > > >
> > > > iPXE builds
2013 Dec 04
0
Boot iPXE from syslinux/isolinux
...file), but
it does have a substantial payload (0x59f50 bytes.)
I am guessing that that is the source of the problems, but I'm still
at a loss from staring at the code. If you could try turning on
debugging output by having debug.c32 installed on the system and running:
debug bios_boot_linux calc_cmdline_offset
... from the command line before trying to load ipxe.lkrn?
I should try it out myself if I can find the time...
-hpa
2013 Dec 04
1
Boot iPXE from syslinux/isolinux
"H. Peter Anvin" <hpa at zytor.com> on Wed, 2013/12/04 09:43:
> On 12/04/2013 12:38 AM, Christian Hesse wrote:
> >
> > Sure. Here we go:
> >
> > boot: debug -e bios_boot_linux calc_cmdline_offset
> > boot: ipxe.lkrn
> > Loading ipxe.lkrn... ok
> > cmdline_offset at 0x9f7e0
> > Initial memory map:
> > Could not find location for protected-mode code
> > Booting kernel failed: Invalid argument
> >
>
> OK, that was a useful clue. I think I know...
2013 Jul 29
1
[syslinux:firmware] load_linux: dynamically calculate the cmdline region
On 07/29/2013 06:28 AM, Matt Fleming wrote:
> On Fri, 26 Jul, at 09:49:28AM, H. Peter Anvin wrote:
>> Hmm... this might constrain the heap excessively if the SMT_TERMINAL
>> cutoff is at the wrong place (because there will be just enough SMT_FREE
>> to fit.) I'm wondering if we shouldn't use the highest of these two
>> regions.
>
> Could you give an
2013 Jul 26
3
[syslinux:firmware] load_linux: dynamically calculate the cmdline region
...yslinux/load_linux.c b/com32/lib/syslinux/load_linux.c
> index 851d467..37c8df0 100644
> --- a/com32/lib/syslinux/load_linux.c
> +++ b/com32/lib/syslinux/load_linux.c
> @@ -125,10 +125,29 @@ static int map_initramfs(struct syslinux_movelist **fraglist,
> }
>
> static size_t calc_cmdline_offset(struct linux_header *hdr,
> - size_t cmdline_size)
> + size_t cmdline_size, addr_t base,
> + addr_t start)
> {
> - if (hdr->version < 0x0202 || !(hdr->loadflags & 0x01))
> + if (hdr->version < 0x0202 || !(hdr->loadflags & 0x01)) {
&g...
2015 Feb 10
6
[PATCH 0/6] fix some compiler warnings
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 +++---