> Is it desirable for this check to be run for each iteration of the loop.
thats is not really the case. that statemet is executed exactly once.
the first check in the loop body looks for the multiboot header
signature and continues the loop if not found. once that check
passes the iteration ends
On Thu, Aug 02, 2018 at 04:05:30PM +0200, cinap_len...@felloff.net wrote:
> When the kernel requests video information, pass it the
> framebuffer information in the multiboot header from
> the linux framebuffer ioctl's.
>
> With the arch specific --reset-vga or --consolve-vga
> options, purgatory
SD.
>
> Signed-off-by: Friedemann Gerold
This seems reasonable to me, but I would value a third-party review
of this change.
Reviewed-by: Simon Horman
> ---
> diff --git a/kexec/arch/i386/kexec-multiboot-x86.c
> b/kexec/arch/i386/kexec-multiboot-x86.c
> index 69027e2..afa09
> diff --git a/kexec/arch/i386/kexec-multiboot-x86.c
> b/kexec/arch/i386/kexec-multiboot-x86.c
> index 69027e2..afa0959 100644
> --- a/kexec/arch/i386/kexec-multiboot-x86.c
> +++ b/kexec/arch/i386/kexec-multiboot-x86.c
> @@ -8,7 +8,6 @@
> * TODO:
> *- smarter
Hello,
I'v posted 3 patches on august and did not receive a response.
http://lists.infradead.org/pipermail/kexec/2018-August/021357.html
http://lists.infradead.org/pipermail/kexec/2018-August/021358.html
http://lists.infradead.org/pipermail/kexec/2018-August/021359.html
what is the issue? how do
E_RGB1
+#define MB_FRAMEBUFFER_TYPE_EGA_TEXT 2
/*
* The following value must be present in the EAX register.
diff --git a/kexec/arch/i386/kexec-multiboot-x86.c
b/kexec/arch/i386/kexec-multiboot-x86.c
index 69027e2..e566be7 100644
--- a/kexec/arch/i386/kexec-multiboot-x86.c
+++ b/kexec
Use the appropriate types for ACPI reclaim and ACPI NVS
ranges in the multiboot memory map.
This allows the kernel to locate ACPI tables on UEFI
systems without having a explicit pointer to the RSD.
Signed-off-by: Friedemann Gerold
---
diff --git a/kexec/arch/i386/kexec-multiboot-x86.c
b/kexec
the multiboot header are used load the
memory image.
Signed-off-by: Friedemann Gerold
---
diff --git a/kexec/arch/i386/kexec-multiboot-x86.c
b/kexec/arch/i386/kexec-multiboot-x86.c
index 69027e2..afa0959 100644
--- a/kexec/arch/i386/kexec-multiboot-x86.c
+++ b/kexec/arch/i386/kexec-multiboot-x86.c
he usual case), then a hole is inserted into kernel's physical
> memory map at zero, so the test to find the size of this region in
> kexec/arch/i386/kexec-multiboot-x86.c never succeeds, so the value is
> always zero.
>
> On a PC99 architecture, there is always memory at physy
ro, so the test to find the size of this region in
kexec/arch/i386/kexec-multiboot-x86.c never succeeds, so the value is
always zero.
On a PC99 architecture, there is always memory at physycal address zero;
assume that a region that starts below 64k actually starts at zero,
and use it for the mem_lowe
10 matches
Mail list logo
