Displaying 8 results from an estimated 8 matches for "image_type_com32".
2016 Mar 20
0
[PATCH 0/1] EFI image booting capabilities
...om32/elflink/ldlinux/execute.c 2014-10-06 10:27:44.000000000 -0600
> +++ b/com32/elflink/ldlinux/execute.c 2015-02-18 18:46:02.193886584 -0700
> @@ -41,6 +41,7 @@ const struct image_types image_boot_type
> { "fdimage", IMAGE_TYPE_FDIMAGE },
> { "com32", IMAGE_TYPE_COM32 },
> { "config", IMAGE_TYPE_CONFIG },
> + { "efi", IMAGE_TYPE_EFI },
> { NULL, 0 },
> };
>
> @@ -89,6 +90,13 @@ __export void execute(const char *cmdlin
> do_sysappend(q);
> }
>
> +#ifdef __FIRMWARE_BIOS__
>...
2015 Feb 20
6
[PATCH 0/1] EFI image booting capabilities
...dlinux/execute.c
--- a/com32/elflink/ldlinux/execute.c 2014-10-06 10:27:44.000000000 -0600
+++ b/com32/elflink/ldlinux/execute.c 2015-02-18 18:46:02.193886584 -0700
@@ -41,6 +41,7 @@ const struct image_types image_boot_type
{ "fdimage", IMAGE_TYPE_FDIMAGE },
{ "com32", IMAGE_TYPE_COM32 },
{ "config", IMAGE_TYPE_CONFIG },
+ { "efi", IMAGE_TYPE_EFI },
{ NULL, 0 },
};
@@ -89,6 +90,13 @@ __export void execute(const char *cmdlin
do_sysappend(q);
}
+#ifdef __FIRMWARE_BIOS__
+ if(type==IMAGE_TYPE_EFI) {
+ printf("Bios...
2014 Jun 30
2
lua not working on syslinux-6.03-pre18
I've upgraded from syslinux-4.05 to syslinux-6.03-pre18 (pre11 was the same)
and am having some issues getting lua.c32 to work. I'm using lpxelinux.0
if that's relevant.
My boot file and the contents of default.lua are below. As you can see they
are fantastically simple. Essentially I'm just using lua to put the results
of ipappend in the right place on the command line.
The
2014 Jun 30
0
lua not working on syslinux-6.03-pre18
...that this ALSO won't work, because run_kernel_image is now
(it seems) much more fussy about image types, so the required
code is actually:
local sl = require "syslinux"
sl.run_kernel_image("mboot.c32", bootstr, 0, 7)
with 7 being the magic number as per:
#define IMAGE_TYPE_COM32 7
It would be useful if there were some Lua constants for that or even
better if it could be persuaded to autodetect based on file extension
as the rest of the system does.
--
Alex Bligh
2014 Jul 01
1
lua not working on syslinux-6.03-pre18
...n_kernel_image is now
> (it seems) much more fussy about image types, so the required
> code is actually:
>
> local sl = require "syslinux"
> sl.run_kernel_image("mboot.c32", bootstr, 0, 7)
>
> with 7 being the magic number as per:
>
> #define IMAGE_TYPE_COM32 7
>
> It would be useful if there were some Lua constants for that
OK, I'll queue a patch for that.
> or even better if it could be persuaded to autodetect based on file
> extension as the rest of the system does.
I'm not sure what changed exactly, but you can use run_...
2012 Jul 16
5
[PATCH 0/5] Deleting __intcall() from Syslinux
From: Matt Fleming <matt.fleming at intel.com>
Since we can't use __intcall() for EFI, and since we can now have the
ELF module code resolve all our symbols at runtime, we should delete
as many references to __intcall() as possible and just access the
symbols directly.
The most interesting patch is the support for weak symbols. We need to
be able to reference derivative-specific
2012 Aug 14
1
[GIT PULL] elflink fixes
...+ { "linux", IMAGE_TYPE_LINUX },
+ { "boot", IMAGE_TYPE_BOOT },
+ { "bss", IMAGE_TYPE_BSS },
+ { "pxe", IMAGE_TYPE_PXE },
+ { "fdimage", IMAGE_TYPE_FDIMAGE },
+ { "comboot", IMAGE_TYPE_COMBOOT },
+ { "com32", IMAGE_TYPE_COM32 },
+ { "config", IMAGE_TYPE_CONFIG },
+ { NULL, 0 },
};
extern int create_args_and_load(char *);
-void execute(const char *cmdline, enum kernel_type type)
+void execute(const char *cmdline, uint32_t type)
{
- const char *p, *const *pp;
const char *kernel, *args;
+ const cha...
2013 Mar 13
6
Syslinux 5.10pre1 - Failed to load COM32 file .c32
Hello everyone,
Since I have some some adventures in UEFI PXE booting ahead I tried to
go with the latest syslinux development snapshot in this case 5.10pre1.
But I already fail when booting from CD with
Failed to load COM32 file .c32
I am a bit perplex since no name of COM32 files is given. I am trying to
trace down the issue as good as I can. COM32 files present are: