Displaying 7 results from an estimated 7 matches for "smt_terminal".
2013 Jul 26
3
[syslinux:firmware] load_linux: dynamically calculate the cmdline region
...map = syslinux_memory_map();
> + if (mmap && !syslinux_memmap_highest(mmap, SMT_FREE, &start,
> + cmdline_size, 0xa0000, 16)) {
> + syslinux_free_memmap(mmap);
> + return start - base;
> + }
> +
> + if (mmap && !syslinux_memmap_highest(mmap, SMT_TERMINAL, &start,
> + cmdline_size, 0xa0000, 16)) {
> + syslinux_free_memmap(mmap);
> + return start - base;
> + }
> +
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.)...
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 example memory map where this would be a problem? I
> not sure I understand what...
2013 Jul 29
0
[syslinux:firmware] load_linux: dynamically calculate the cmdline region
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 example memory map where this would be a problem? I
not sure I understand what you mean. Perhaps somethin...
2013 Dec 04
0
Boot iPXE from syslinux/isolinux
...mmap;
-
- mmap = syslinux_memory_map();
- if (mmap && !syslinux_memmap_highest(mmap, SMT_FREE, &start,
- cmdline_size, 0xa0000, 16)) {
- syslinux_free_memmap(mmap);
- return start - base;
- }
+ size_t max_offset;
- if (mmap && !syslinux_memmap_highest(mmap, SMT_TERMINAL, &start,
- cmdline_size, 0xa0000, 16)) {
- syslinux_free_memmap(mmap);
- return start - base;
- }
+ if (hdr->version >= 0x0202 && (hdr->loadflags & LOAD_HIGH))
+ max_offset = 0x10000;
+ else
+ max_offset = 0xfff0 - cmdline_size;
+
+ if (!syslinux_m...
2013 Dec 04
2
Boot iPXE from syslinux/isolinux
"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
> >>
2016 Jun 16
2
[PATCH] Fix recognition of keeppxe option
> On Wed, Jun 15, 2016 at 1:02 PM, Ady via Syslinux <syslinux at zytor.com> wrote:
> >
> >> On Tue, Jun 14, 2016 at 12:33 PM, Ady via Syslinux <syslinux at zytor.com> wrote:
> >> >
> >> >> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because
> >> >> > there is no convenient way in new_linux_kernel() to
2016 Jun 16
0
[PATCH] Fix recognition of keeppxe option
...ND file=freeldr.sys seg=0x0F80 keeppxe
>
> which has been failing since Syslinux v.5.+.
chain.c32 has its own code to handle keeppxe. It looks like it's passing
the correct flag to syslinux_shuffle_boot_rm, but I wonder if the
problem is pxelinux_scan_memory is marking the PXE region as
SMT_TERMINAL?
-- Adam