r variable.
Signed-off-by: Peter Chubb
---
kexec/arch/i386/kexec-multiboot-x86.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
Index: kexec-tools-2.0.4/kexec/arch/i386/kexec-multiboot-x86.c
===
--- kexec-t
anges from /proc/iomem, the code in
kexec/arch/i386/kexec-multiboot-x86.c never fills in mem_lower.
I think it's safe to assume that if a memory segment starts at 64k or
lower, it can be extended to location 0 because of the kernel
protection on a PC99-style architecture.
Peter C
-
ee
anything explicitly disabled during kexec that isn't reenabled
during boot of the subsequent kernel.
Voltages that I can measure look correct on the port.
Do you have any suggestions as to what else could be wrong?
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gel
>>>>> "Russell" == Russell King <- ARM Linux > writes:
Russell> On Wed, Dec 14, 2011 at 08:08:02AM +, Russell King - ARM
Russell> Linux wrote:
>> On Wed, Dec 14, 2011 at 03:02:10PM +1100, Peter Chubb wrote:
>> >
>> > When kex
l one.
+ */
+{
+void (*cpu_reset_phys)(unsigned long dest) =
+virt_to_phys(cpu_reset);
+cpu_reset_phys(reboot_code_buffer_phys);
+}
}
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au ERTOS w
