similar to: [PATCH] gfxboot: add include and menu include support

Displaying 17 results from an estimated 17 matches similar to: "[PATCH] gfxboot: add include and menu include support"

2010 Apr 09
2
[PATCH] gfxboot: support MENU LABEL statement
The config file parser now accepts MENU LABEL. Also, make config statements case-insensitive. Signed-off-by: Steffen Winterfeldt <wfeldt at opensuse.org> --- com32/gfxboot/gfxboot.c | 69 ++++++++++++++++++++++++++++++++++------------- 1 files changed, 50 insertions(+), 19 deletions(-) diff --git a/com32/gfxboot/gfxboot.c b/com32/gfxboot/gfxboot.c index bfdd8cc..640422b 100644 ---
2010 Jul 14
1
[PATCH] gfxboot: allow boot entry to start with label instead of menu_label
menu_ptr->menu_label is human-readable (perhaps even translatable!) text if the MENU LABEL command is used, which isn't very convenient at the start of a boot entry. Allow the entry to start with menu_ptr->label (an identifier) as an alternative. Signed-off-by: Colin Watson <cjwatson at ubuntu.com> --- com32/gfxboot/gfxboot.c | 16 ++++++++++------ 1 files changed, 10
2011 Aug 17
1
[patch 1/1] syslinux: add suport for com32 entries in the menu
From: Jorge D Cisneros <jorge.cisneros at hp.com> Problem: The actual code only check for entries with kernel or linux, so this example will not work, this patch is to add support to gfxboot to detect the entry COM32 and use any module, in this case the module is chain.c32 Version: Syslinux 4.04 Example: UI gfxboot.c32 LABEL boot_hd0 MENU LABEL Boot from first hard drive COM32 chain.c32
2009 Apr 09
0
[PATCH] gfxboot: parse DEFAULT keywork in syslinux config file
The gfxboot COM module currently ignores the DEFAULT entry set in syslinux config file and always default to 0 instead. This patch parses DEFAULT entries in the config file and set the default entry accordingly. Signed-off-by: Christophe Fergeau <cfergeau at mandriva.com> --- modules/gfxboot.asm | 34 ++++++++++++++++++++++++++++++++-- 1 files changed, 32 insertions(+), 2 deletions(-)
2011 Aug 18
0
[patch 1/1] syslinux: add suport for com32 entries inthe menu
No, we can use that, because I want to use the com32 module, in this case I want to use the chain.c32 to boot to Winpe. Cisneros, Jorge (George) wrote: > Problem: The actual code only check for entries with kernel or linux, so this example will not work, this patch is to > add support to gfxboot to detect the entry COM32 and use any module, in this case the module is chain.c32 >
2009 Apr 05
3
[PATCH] Gfxboot COMBOOT module
This is the latest version of the gfxboot module. It's supposed to work on all Syslinux derivatives. I am not sure about the copyright notice and would appreciate any input. - Sebastian Index: syslinux-3.74-pre17-2-g2a9ddec/modules/Makefile =================================================================== --- syslinux-3.74-pre17-2-g2a9ddec.orig/modules/Makefile +++
2008 Nov 22
5
[RFC][PATCH] Gfxboot COMBOOT module
So here it is. Ugly and far from acceptable shape but nonetheless it seems to work. Parts are borrowed from syslinux core and of course the gfxboot patch for syslinux 3.63. Syntax: gfxboot.com <bootlogo file> - Sebastian --- /dev/null 2007-09-21 23:50:58.000000000 +0200 +++ syslinux-3.73-pre6/modules/gfxboot.asm 2008-11-22 19:01:10.000000000 +0100 @@ -0,0 +1,883 @@ + absolute 0
2009 Jul 13
0
[PATCH] gfxboot: change handling of keywords
Makes handling of keywords more flexible. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> Index: syslinux-3.82-440-g6483c80/modules/gfxboot.asm =================================================================== --- syslinux-3.82-440-g6483c80.orig/modules/gfxboot.asm +++ syslinux-3.82-440-g6483c80/modules/gfxboot.asm @@ -699,33 +699,39 @@ parse_config: mov bx, msg_crlf int 22h
2020 Sep 10
0
Re: Two questions about NVDIMM devices
On Thu, Sep 10, 2020 at 04:26:40PM +0200, Milan Zamazal wrote: > Daniel P. Berrangé <berrange@redhat.com> writes: > > > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: > >> Hi, > >> > > > >> I've met two situations with NVDIMM support in libvirt where I'm not > >> sure all the parties (libvirt & I) do the
2020 Sep 10
2
Re: Two questions about NVDIMM devices
Daniel P. Berrangé <berrange@redhat.com> writes: > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: >> Hi, >> > >> I've met two situations with NVDIMM support in libvirt where I'm not >> sure all the parties (libvirt & I) do the things correctly. >> >> The first problem is with memory alignment and size changes. In
2020 Sep 14
0
Re: Two questions about NVDIMM devices
On Thu, 2020-09-10 at 20:53 +0200, Michal Privoznik wrote: > On 9/10/20 4:56 PM, Daniel P. Berrangé wrote: > > On Thu, Sep 10, 2020 at 04:54:08PM +0200, Milan Zamazal wrote: > > > Daniel P. Berrangé <berrange@redhat.com> writes: > > > > > > If we're enforcing this 1 MB rounding though, we really should be > > > > > > documenting it
2020 Sep 10
0
Re: Two questions about NVDIMM devices
On Thu, Sep 10, 2020 at 04:54:08PM +0200, Milan Zamazal wrote: > Daniel P. Berrangé <berrange@redhat.com> writes: > > > On Thu, Sep 10, 2020 at 04:26:40PM +0200, Milan Zamazal wrote: > >> Daniel P. Berrangé <berrange@redhat.com> writes: > >> > > > >> > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: > >> >>
2020 Sep 10
2
Re: Two questions about NVDIMM devices
On 9/10/20 4:56 PM, Daniel P. Berrangé wrote: > On Thu, Sep 10, 2020 at 04:54:08PM +0200, Milan Zamazal wrote: >> Daniel P. Berrangé <berrange@redhat.com> writes: >> >>> On Thu, Sep 10, 2020 at 04:26:40PM +0200, Milan Zamazal wrote: >>>> Daniel P. Berrangé <berrange@redhat.com> writes: >>>> >>> >>>>> On Thu, Jul
2020 Sep 10
2
Re: Two questions about NVDIMM devices
Daniel P. Berrangé <berrange@redhat.com> writes: > On Thu, Sep 10, 2020 at 04:26:40PM +0200, Milan Zamazal wrote: >> Daniel P. Berrangé <berrange@redhat.com> writes: >> > >> > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: >> >> Hi, >> >> >> > >> >> I've met two situations with NVDIMM support
2009 Oct 29
5
[PATCH] gfxboot.c32
Ok, here is the first try to turn the gfxboot wrapper into a com32 module. I had to extend the interface to the gfxboot core a bit to get it working. So it works only with latest gfxboot from git://gitorious.org/gfxboot/gfxboot.git Steffen -------------- next part -------------- A non-text attachment was scrubbed... Name: gfxboot_c32.diff.gz Type: application/x-gzip Size: 7220 bytes Desc: URL:
2020 Jul 02
3
Two questions about NVDIMM devices
Hi, I've met two situations with NVDIMM support in libvirt where I'm not sure all the parties (libvirt & I) do the things correctly. The first problem is with memory alignment and size changes. In addition to the size changes applied to NVDIMMs by QEMU, libvirt also makes some NVDIMM size changes for better alignments, in qemuDomainMemoryDeviceAlignSize. This can lead to the size
2011 Mar 09
14
[PATCH 00/12] elflink shrinkage
From: Matt Fleming <matt.fleming at linux.intel.com> This is a series of patches that, * shrink the core by moving things into an ldlinux ELF module * begin wiring up some of the C versions of various functions The core now only contains essential code and loads the ldlinux module to do everything else, like providing a command line interface and loading kernels. The config file parsing