On Mon, 2010-05-24 at 13:38 -0500, Kumar Gala wrote:
> When we build with ftrace enabled its possible that loadcam_entry would
> have used the stack pointer (even though the code doesn't need it). We
> call loadcam_entry in __secondary_start before the stack is setup. To
> ensure that loadcam_ent
When we build with ftrace enabled its possible that loadcam_entry would
have used the stack pointer (even though the code doesn't need it). We
call loadcam_entry in __secondary_start before the stack is setup. To
ensure that loadcam_entry doesn't use the stack pointer the easiest
solution is to j
On May 13, 2010, at 11:25 PM, Kumar Gala wrote:
When we build with ftrace enabled its possible that loadcam_entry
would
have used the stack pointer (even though the code doesn't need it).
We
call loadcam_entry in __secondary_start before the stack is setup. To
ensure that loadcam_entry do
When we build with ftrace enabled its possible that loadcam_entry would
have used the stack pointer (even though the code doesn't need it). We
call loadcam_entry in __secondary_start before the stack is setup. To
ensure that loadcam_entry doesn't use the stack pointer the easiest
solution is to j
