search for: load_env32

...* There may be pending user input that wasn't processed by @@ -1383,8 +1385,10 @@ EFI_STATUS efi_main(EFI_HANDLE image, EFI_SYSTEM_TABLE *table) status = uefi_call_wrapper(in->ReadKeyStroke, 2, in, &key); } while (status == EFI_SUCCESS); + Print(L"load_env32 start\n"); if (!setjmp(load_error_buf)) load_env32(NULL); + Print(L"load_env32 done.\n"); /* load_env32() failed.. cancel timer and bailout */ status = cancel_timer(timer_ev); Untested

...g user input that wasn't processed by > @@ -1383,8 +1385,10 @@ EFI_STATUS efi_main(EFI_HANDLE image, EFI_SYSTEM_TABLE *table) > status = uefi_call_wrapper(in->ReadKeyStroke, 2, in, &key); > } while (status == EFI_SUCCESS); > > + Print(L"load_env32 start\n"); > if (!setjmp(load_error_buf)) > load_env32(NULL); > + Print(L"load_env32 done.\n"); > > /* load_env32() failed.. cancel timer and bailout */ > status = cancel_timer(timer_ev); > > > Untested (Ja...

...size in enter_cmdline elflink: Do clear screen even if we have no pDraw_Menu method elflink: Add Ctrl-p + Ctrl-n key binds core/elflink/cli.c | 10 +++++----- core/elflink/execute.c | 3 +++ core/elflink/get_key.c | 2 ++ core/elflink/getadv.c | 2 +- core/elflink/load_env32.c | 11 ++++++----- core/elflink/readconfig.c | 1 - 6 files changed, 17 insertions(+), 12 deletions(-)

...t of fixes about CLI on elflink branch. Liu Aleaxander (3): elflink: use 'input' as the prompt of the CLI elflink: Add ctrl-R key bind support elflink: handle the NULL return of edit_cmdline core/elflink/cli.c | 88 +++++++++++++++++++++++++++++++++++++++++--- core/elflink/load_env32.c | 4 ++- 2 files changed, 85 insertions(+), 7 deletions(-) -- 1.7.2.3

...le as argument. This call never return. In order to avoid stacking up the calls to start_ldlinux, this patch introduce a setjmp/longjmp to return to the first call to start_ldlinux, thus freeing all the stack space. Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com> --- core/elflink/load_env32.c | 58 ++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 57 insertions(+), 1 deletion(-) diff --git a/core/elflink/load_env32.c b/core/elflink/load_env32.c index 492cc09..db19c7a 100644 --- a/core/elflink/load_env32.c +++ b/core/elflink/load_env32.c @@ -55,7 +55,7 @@ void init_modul...

...er input that wasn't processed by @@ - > 1383,8 +1385,10 @@ EFI_STATUS efi_main(EFI_HANDLE image, > EFI_SYSTEM_TABLE *table) > status = uefi_call_wrapper(in->ReadKeyStroke, 2, in, &key); > } while (status == EFI_SUCCESS); > > + Print(L"load_env32 start\n"); > if (!setjmp(load_error_buf)) > load_env32(NULL); > + Print(L"load_env32 done.\n"); > > /* load_env32() failed.. cancel timer and bailout */ > status = cancel_timer(timer_ev); > > > Untested > ___...

...les might not be closed and some memory may not be freed. Sylvain Gault (2): ldlinux: fix stack overflow when running COM32 modules core: Fix stack overflow when reloading config com32/elflink/ldlinux/execute.c | 4 ++- com32/elflink/ldlinux/ldlinux.c | 28 ++++++++++++++------ core/elflink/load_env32.c | 58 ++++++++++++++++++++++++++++++++++++++++- 3 files changed, 80 insertions(+), 10 deletions(-) -- 2.6.1

...on't load ldlinux.c32 Clean up $(GPLLIB) leak ldlinux: Use stdcon instead of rawcon for the console Makefile | 10 ++++++---- com32/elflink/ldlinux/ldlinux.c | 2 +- com32/hdt/Makefile | 4 +--- com32/modules/Makefile | 5 +---- core/elflink/load_env32.c | 2 ++ mk/elf.mk | 2 +- 6 files changed, 12 insertions(+), 13 deletions(-) -- 1.7.11.7

On Wed, 12 Jun, at 11:17:44AM, Gerardo Exequiel Pozzi wrote: > Cool thanks!. Now looks better, but still not work. > > For some reason, "ldlinux.c32" is apparently sent but "Failed to load" > by PXELINUX and few seconds later, dnsmasq shows an error message > "failed sending": Argh! The patch was broken. I missed the new core/path.c file. My bad.

...ions before 5.11 will need to change their config file when upgrading. Signed-off-by: Matt Fleming <matt.fleming at intel.com> --- com32/elflink/ldlinux/readconfig.c | 53 +++++++++++++++++++++++++------------- com32/lib/sys/module/common.c | 36 +++++++++----------------- core/elflink/load_env32.c | 26 +++---------------- core/fs/fs.c | 2 -- core/include/fs.h | 10 ++++++- doc/syslinux.txt | 2 +- 6 files changed, 61 insertions(+), 68 deletions(-) diff --git a/com32/elflink/ldlinux/readconfig.c b/com32/elflink/ldlinux/r...

...s the same way.. I'm quite sure it isn't the printf that causes the crashing. It just doesn't appear. At one time I had this in efi/main.c: if (!setjmp(load_error_buf)) { printf("Is printf still working?\n"); Print(L"Entering: load_env32\n"); load_env32(NULL); } The output for this is: | Entering: load_env32 The printf's i put in load_env32 itself didn't output anything either, but now i can see the output of dprintf's on COM2. (Grammar question, is printf's the correct plural of...

...ions before 5.11 will need to change their config file when upgrading. Signed-off-by: Matt Fleming <matt.fleming at intel.com> --- com32/elflink/ldlinux/readconfig.c | 53 +++++++++++++++++++++++++------------- com32/lib/sys/module/common.c | 36 +++++++++----------------- core/elflink/load_env32.c | 26 +++---------------- core/fs/fs.c | 2 -- core/include/fs.h | 10 ++++++- core/path.c | 42 ++++++++++++++++++++++++++++++ doc/syslinux.txt | 2 +- 7 files changed, 103 insertions(+), 68 deletions(-)...

On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote: > Either that or make the path a list rather than a string, using the > normal word separators when entered on the command line, a bit like the > (t)csh does. That is a bigger change but is probably a better solution. How would this solution handle filenames containing spaces? Would we need to escape (presumably with a backslash)

>>> > On 05-08-15 12:05, Gene Cumm wrote: >> >>? > I recompiled with this in mk/devel.mk <http://devel.mk>: >>? >? GCCWARN += -DDEBUG_PORT=0x2f8 -DCORE_DEBUG=1 >> >> 0x2f8 is a BIOSism. > Is this a problem? The example in the comments said 0x3f8 which is COM1. It means that a BIOS IO port for a UART won't work for EFI.? No

...e > their config file when upgrading. > > Signed-off-by: Matt Fleming <matt.fleming at intel.com> > --- > com32/elflink/ldlinux/readconfig.c | 53 +++++++++++++++++++++++++------------- > com32/lib/sys/module/common.c | 36 +++++++++----------------- > core/elflink/load_env32.c | 26 +++---------------- > core/fs/fs.c | 2 -- > core/include/fs.h | 10 ++++++- > doc/syslinux.txt | 2 +- > 6 files changed, 61 insertions(+), 68 deletions(-) > > diff --git a/com32/elflink/ldlinux/readconf...

...| 6 +- com32/menu/execute.c | 69 ------------------------- core/Makefile | 2 +- core/comboot.inc | 6 ++- core/conio.c | 6 ++- core/elflink/config.c | 41 --------------- core/elflink/load_env32.c | 62 +++++++++++++++++++++-- core/font.c | 20 ++++--- core/fs/fs.c | 2 +- core/fs/iso9660/iso9660.c | 2 +- core/fs/lib/loadconfig.c | 2 +- core/fs/lib/searchconfig.c | 19 ++++--- core/graphics.c...

> On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James via Syslinux > wrote: > > > On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux > wrote: > > > is for BIOS, not for EFI. So that suggestion can be scraped. > > > > > > Which makes > > > * text which is on the screen of the netbooting (virtual) machine > > >

...>> On Mon, Aug 31, 2015 at 2:49 PM, Derrick M <derrick.martinez at gmail.com> > >> wrote: > >> > Gene, > >> > > >> > Also, I wanted to point out there the code is freezing at in main.c. > >> > It's > >> > right at load_env32(NULL); at that point status has a numerical value of > >> > 6. > >> > >> That's excellent to know. Thanks. > > And numerical value of 6 is EFI_NOT_READY, indicating the keyboard > buffer is empty, as expected. > Gene, Yeah I guess that could be goo...

...ata. > > Does your HP DL160 G9 have an iLO with remote KVM function? If not and you > feel a screenshot from a real camera is too big for the list, feel free to > send it to me directly. > Gene, Also, I wanted to point out there the code is freezing at in main.c. It's right at load_env32(NULL); at that point status has a numerical value of 6.

...efi > > > > > > > > > > > > > > Test it on your EFI environment and report back. > > > > > > > > [ ... feedback on previous version ... ] > > > > > > > > > > Now compiling with a modified core/elflink/load_env32.c > > > > > > When you see this message, it should be ready for a test. > > > > > > Report succes to the ML. > > > > > > > Where can I download it from? > > > > At the same place. > That is where the build system puts it. >...