search for: eboot

...-cflags-$(CONFIG_X86_64) := -mcmodel=small +cflags-$(CONFIG_X86_64) := -mcmodel=small -mno-red-zone KBUILD_CFLAGS += $(cflags-y) KBUILD_CFLAGS += -mno-mmx -mno-sse KBUILD_CFLAGS += $(call cc-option,-ffreestanding) @@ -87,7 +87,7 @@ endif vmlinux-objs-$(CONFIG_ACPI) += $(obj)/acpi.o -$(obj)/eboot.o: KBUILD_CFLAGS += -fshort-wchar -mno-red-zone +$(obj)/eboot.o: KBUILD_CFLAGS += -fshort-wchar vmlinux-objs-$(CONFIG_EFI_STUB) += $(obj)/eboot.o \ $(objtree)/drivers/firmware/efi/libstub/lib.a -- 2.17.1

....IMG 04/28/2004 10:43 AM <DIR> otros 04/14/2004 07:09 AM 32,225 loadlin.exe 04/27/2004 10:48 AM 124 AUTOEXLI.bat 02/22/2004 09:31 PM 9,428 isolinux.bin 03/22/2004 10:46 AM 94 CONFIG.SYS 03/01/2003 05:11 PM 97,219 EBOOT.BIN 10/22/2002 03:27 PM 98,076 LOADCEPC.EXE 12/11/2003 01:58 PM 17,715,335 nk.bin 03/06/2003 09:16 PM 24,347 SBOOT.BIN 03/22/2004 12:56 PM <DIR> Settings 04/28/2004 02:27 PM 8,184 LDLINUX.SYS 04/27/2004 10:21 AM 720,425 vmli...

...the Mother Board (hinge-mounted in case) - slap forehead. 3) Remove cables, PCI NIC & MB - 2 minutes 4) Add RAM - 1 Minute 5) Get the %$#@ MB back in the case and aligned -- 15 Minutes 6) Reinstall NIC - 1 minute 7) Get the %$#@ case cover on and aligned - 4 Minutes. 8) Re-attach cables & eboot - 2 Minutes So much for my 15-minute downtime :-) -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

...times. However, it allows itself > to always call allocate_pool (in efi_get_memory_map) even after > exit_boot_services failed once. Which does not comply with the UEFI > specification. > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/x86/boot/compressed/eboot.c?id=e86328c489d7ecdca99410a06a3f448caf7857bf#n1299 > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/firmware/efi/libstub/efi-stub-helper.c?id=e86328c489d7ecdca99410a06a3f448caf7857bf#n66 > > > >> >>> + } while (status == EFI_BUFFER_TOO...

...om0 boots on Opteron boxes, but on my EMT64 blades, it does not. Has anyone else encountered this problem on EMT64 hardware? Here are the errors I am getting: This is on a SLES 9 box, gcc version 3.3.3 (SuSE Linux): kernel (hd0,0)/boot/xen.gz dom0_mem=256000 com2=19200,8n1 console=vga,com2 nor eboot [Multiboot-elf, <0x100000:0x5e358:0x22ca8>, shtab=0x181078, entry=0x100000] module (hd0,0)/boot/vmlinuz-2.6-xen0 root=/dev/sda6 ro console=tty0 [Multiboot-module @ 0x182000, 0x67e5f0 bytes] module (hd0,0)/initrd-2.6.11.12-xen0 __ __ _____ ___ _ _ \...

...ervices a maximum of two times. However, it allows itself to always call allocate_pool (in efi_get_memory_map) even after exit_boot_services failed once. Which does not comply with the UEFI specification. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/x86/boot/compressed/eboot.c?id=e86328c489d7ecdca99410a06a3f448caf7857bf#n1299 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/firmware/efi/libstub/efi-stub-helper.c?id=e86328c489d7ecdca99410a06a3f448caf7857bf#n66 > >> + } while (status == EFI_BUFFER_TOO_SMALL); >> + >&...

On Tue, Aug 25, 2015 at 11:54 PM, celelibi--- via Syslinux <syslinux at zytor.com> wrote: > From: Sylvain Gault <sylvain.gault at gmail.com> > > Some firmware implementations may need ExitBootServices to be called > twice. The second time with an updated memory map key. > > Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com> > --- > efi/main.c | 75

...allows itself >> to always call allocate_pool (in efi_get_memory_map) even after >> exit_boot_services failed once. Which does not comply with the UEFI >> specification. >> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/x86/boot/compressed/eboot.c?id=e86328c489d7ecdca99410a06a3f448caf7857bf#n1299 >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/firmware/efi/libstub/efi-stub-helper.c?id=e86328c489d7ecdca99410a06a3f448caf7857bf#n66 >> >> >> >>> >>>> + } while (...

Hi, here is the first public post of the patch-set to enable Linux to run under SEV-ES enabled hypervisors. The code is mostly feature-complete, but there are still a couple of bugs to fix. Nevertheless, given the size of the patch-set, I think it is about time to ask for initial feedback of the changes that come with it. To better understand the code here is a quick explanation of SEV-ES first.

Hi, here is the first public post of the patch-set to enable Linux to run under SEV-ES enabled hypervisors. The code is mostly feature-complete, but there are still a couple of bugs to fix. Nevertheless, given the size of the patch-set, I think it is about time to ask for initial feedback of the changes that come with it. To better understand the code here is a quick explanation of SEV-ES first.