On Sep 30, 2008, at 12:21 PM, Sebastian Siewior wrote:
Milton Miller wrote:
|load: entry = 0x80053c flags = 0
|nr_segments = 2
|segment[0].buf = 0x1002b8f0
|segment[0].bufsz = 80
|segment[0].mem = (nil)
|segment[0].memsz = 1000
|segment[1].buf = 0x4803f008
|segment[1].bufsz = 3a3138
|segme
Milton Miller wrote:
|load: entry = 0x80053c flags = 0
|nr_segments = 2
|segment[0].buf = 0x1002b8f0
|segment[0].bufsz = 80
|segment[0].mem = (nil)
|segment[0].memsz = 1000
|segment[1].buf = 0x4803f008
|segment[1].bufsz = 3a3138
|segment[1].mem = 0x80
|segment[1].memsz = 3b
I w
On Sep 29, 2008, at 3:04 PM, Sebastian Siewior wrote:
* Milton Miller | 2008-09-23 20:24:02 [-0500]:
If you have any questions about kdump or what needs to happen,
please feel free to contact me
I copied most of the 64bit code to parse the device tree without the
pci
nodes & moved it to 3
* Milton Miller | 2008-09-23 20:24:02 [-0500]:
>If you have any questions about kdump or what needs to happen,
>please feel free to contact me either by email or on irc (sometimes
>I use mdm other times the email login as my nick, and when connected
>I tend to leave it well past the hours I am at
Milton Miller wrote:
On Wed Sep 24 at about 05:54:04 EST 2008, Sebastian Siewior wrote:
this could be used by the kexec userland code.
NACK.
[...]
Thanks for explanation. I just went through the kexec user land code and
saw that the 64bit code uses the device tree to obtain some address and
3
Kumar Gala wrote:
I missing why you are doing this? Do you plan on using it w/32-bit kexec?
Yes. I plan to kexec my mpc8544 board.
- k
Sebastian
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-de
On Sep 23, 2008, at 2:54 PM, Sebastian Siewior wrote:
this could be used by the kexec userland code.
Signed-off-by: Sebastian Siewior <[EMAIL PROTECTED]>
---
This is done by the 64bit kexec code allready. The 32bit doesn't use
the
device tree at all. I'm not sure whether the node has to be
