UPDATE: Minor update in Copyright assignment in misc_32.S
Added requirement of upstream kexec-tools.
Changes from v1: Uses a tmp mapping in the other address space to setup
the 1:1 mapping (suggested by Sebastian Andrzej Siewior).
Note 1: Should we do the same for kernel
On 07/12/11 12:14, Suzuki K. Poulose wrote:
Changes from V1: Uses a tmp mapping in the other address space to setup
the 1:1 mapping (suggested by Sebastian Andrzej Siewior).
Note: Should we do the same for kernel entry code for PPC44x ?
This patch adds kexec support for PPC440
* Suzuki K. Poulose | 2011-07-12 12:14:16 [+0530]:
>Changes from V1: Uses a tmp mapping in the other address space to setup
>the 1:1 mapping (suggested by Sebastian Andrzej Siewior).
>
>Note: Should we do the same for kernel entry code for PPC44x ?
You have one the kernel mapping.
On Wed, Jul 13, 2011 at 12:28:36AM -0500, Kumar Gala wrote:
>
>On Jul 12, 2011, at 1:44 AM, Suzuki K. Poulose wrote:
>
>> Changes from V1: Uses a tmp mapping in the other address space to setup
>> the 1:1 mapping (suggested by Sebastian Andrzej Siewior).
>>
>> Note: Should we do the
On 07/13/11 10:58, Kumar Gala wrote:
On Jul 12, 2011, at 1:44 AM, Suzuki K. Poulose wrote:
Changes from V1: Uses a tmp mapping in the other address space to setup
the 1:1 mapping (suggested by Sebastian Andrzej Siewior).
Note: Should we do the same for kernel entry code for P
On Jul 12, 2011, at 1:44 AM, Suzuki K. Poulose wrote:
> Changes from V1: Uses a tmp mapping in the other address space to setup
>the 1:1 mapping (suggested by Sebastian Andrzej Siewior).
>
> Note: Should we do the same for kernel entry code for PPC44x ?
>
> This patch adds kexec
Changes from V1: Uses a tmp mapping in the other address space to setup
the 1:1 mapping (suggested by Sebastian Andrzej Siewior).
Note: Should we do the same for kernel entry code for PPC44x ?
This patch adds kexec support for PPC440 based chipsets.This work is based
on the KEXEC
