similar to: Patch sensible callback framework

This patch modifies the simple menu com32 program to include integrated load progress. It also adds new options to the simple menu configuration MENU LOADMSG -- allows the user to specify the text to display when loading MENU LOADMSGROW -- controls where the text is written Example configuration: MENU LOADMSG Booting MENU LOADMSGROW 25 It works with my setup, please let me know if you find

>> Thanks. I've looked through all the links, and it seems everything is >> fine wrt. to what was mentioned there (I've disabled 64 bits in mke2fs, >> but it didn't help). I'd be glad to provide more details, but the error >> message is the only info I've got by now. It seems nothing else can be >> got from syslinux shell without modifiying the

Cleanup code/data sections definitions accordingly to include/linux/init.h. Signed-off-by: Daniel Kiper <dkiper@net-space.pl> --- arch/x86/xen/setup.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c index 90bac0a..d3663df 100644 --- a/arch/x86/xen/setup.c +++ b/arch/x86/xen/setup.c @@ -50,7 +50,7 @@ phys_addr_t

hpa at zytor.com writes: > On November 19, 2016 6:06:43 AM PST, wferi at niif.hu wrote: > >>"H. Peter Anvin" <hpa at zytor.com> writes: >> >>> On 11/10/16 04:38, Paul Emmerich via Syslinux wrote: >>> >>>> Ferenc W?gner <wferi at niif.hu>: >>>> >>>>> for reading configuration files from disk. Does it

On Fri, Jun 10, 2016 at 2:06 AM, Adam Goldman via Syslinux <syslinux at zytor.com> wrote: > PXELINUX has stopped recognizing the keeppxe option on the kernel > command line. Here is a patch to make it work again. > > With COM32, it is no longer possible to use preprocessor directives to > determine the SYSLINUX variant. The code inside the #if will never be > compiled. So,

PXELINUX has stopped recognizing the keeppxe option on the kernel command line. Here is a patch to make it work again. With COM32, it is no longer possible to use preprocessor directives to determine the SYSLINUX variant. The code inside the #if will never be compiled. So, I changed it to use syslinux_filesystem() to determine the variant. Also, I moved the relevant code from

Thanks. I've looked through all the links, and it seems everything is fine wrt. to what was mentioned there (I've disabled 64 bits in mke2fs, but it didn't help). I'd be glad to provide more details, but the error message is the only info I've got by now. It seems nothing else can be got from syslinux shell without modifiying the code. I've tried to make it load the kernel

On 11/20/16 00:13, Ferenc W?gner via Syslinux wrote: > > This indeed copies the data from the syslinux_file structure (which is > an opaque SYSLINUX_FILE object on the Lua side) into an (interned) Lua > string to make it available to the Lua string functions. > > You probably ask why we copy the data when we create those SYSLINUX_FILE > userdata objects. We don't, the

Hallo, Matt, Du meintest am 25.06.13: [compiling syslinux-6.00] >> Thanks - now it crashes later ... > What crash are you seeing? ------------- cite on ------------- [...] gcc -Wp,-MT,abort.o,-MD,./.abort.o.d -Os -march=x86-64 -falign- functions=0 -falign-jumps=0 -falign-labels=0 -ffast-math -fomit-frame- pointer -std=gnu99 -fno-stack-protector -fwrapv -freg-struct-return -

On Tue, 25 Jun, at 01:52:00PM, Helmut Hullen wrote: > Thanks - now it crashes later ... What crash are you seeing? > I don't have the ia64 files which are needed for a complete binary. But > maybe that's only my special problem. You shouldn't need ia64 files to build ia32 and x86-64 versions of gnu-efi or Syslinux. -- Matt Fleming, Intel Open Source Technology Center

(cc'ing non-legacy llvm-dev this time; apologies if you get this twice. Please don't reply-all to the first one.) On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg <hans at chromium.org> wrote: > Dear testers, > > Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at > r258223. (It took a little longer than I'd planned, sorry about that.) > > There

On Fri, Feb 20, 2015 at 8:08 AM, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: > This patch adds to the core EFI image booting capabilities. > It was tested on VMware EFI clients and HP Elitebook EFI notebooks, > only on PXE environments but it should work on non-PXE scenarios as well. > > Feedback appreciated. If you've made any changes to this, I'd

This patch adds to the core EFI image booting capabilities. It was tested on VMware EFI clients and HP Elitebook EFI notebooks, only on PXE environments but it should work on non-PXE scenarios as well. Feedback appreciated. Best, Patrick Signed-off-by: Patrick Masotta <masottaus at yahoo.com> --- diff -uprN a/com32/elflink/ldlinux/execute.c b/com32/elflink/ldlinux/execute.c ---

Unfortunately I'm having lots of trouble with rc1 at this point: * libcxxabi can't build, because it requires unwind.h, which we do not yet have on FreeBSD 10.x (Ed Maste is working on it for 11.x, but that is not ready for general consumption). * The test-release.sh script has no option to disable only libcxxabi, you can only disable libcxx, libcxxabi and libunwind together (maybe this

Hi, I just pushed out changes that fix pretty much all the compiler build warnings on the elflink branch. Also, I've added "auto extension" support so that if the user doesn't type the file name extension it will automatically be looked up, e.g. now typing "ls" will execute "ls.c32". The following changes since commit

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine

From: Matt Fleming <matt.fleming at intel.com> The following patch series is available at, git://git.zytor.com/users/mfleming/syslinux.git elflink All patches are against the 'elflink' branch. This series fixes a few serious bugs and some behavioural incompatibilities with the 4.x series. Matt Fleming (19): ldlinux: Initialise 'p' before using it. ldlinux: Parse

The following series of patches fill in most of the gaps in the OCaml bindings to libxl, to make them useful for clients such as xapi/xenopsd (from XCP). There are a number of bugfixes to the existing bindings as well. I have an experimental version of xenopsd that successfully uses the new bindings. An earlier version of the first half of the series was submitted to the last by Ian Campbell on

From: Matt Fleming <matt.fleming at linux.intel.com> This series fixes some bugs and switches the elflink branch to be entirely ELF modules. It applies on top of, http://syslinux.zytor.com/archives/2011-April/016369.html The deletions in the diff stat below are mainly from deleting com32/elflink/modules (finally!). Now there should be no duplicate code because we don't need COM32 and