[PATCH 0/2] Add support for kexec-hardboot to Nexus 7 kernel

[Vojtech Bocek]

Hello,
I don't think there's gonna be any changes - I am just porting this from TF201.
This is not the full hardboot patch, these two patches are needed for
this kernel
to be bootable via kexec-hardboot, _not_ to be the host kernel (the one
on which "kexec -e" call happens). Full hardboot patch is a bit bigger [1].

I know at least of Samsung Epic 4G and Asus Tranformer TF201 having
the same issues with normal kexec. Host kernel simply says
"Loading new kernel, bye." and then just freezes. I don't really see any
way to debug that.
TF201 and Nexus 7 kexec-hardboot patches are the same, only thing which
is different are the memory locations. Not sure if TF201 is officially supported
by Ubuntu.

I am not involved with Ubuntu developement in any way yet, so no, I don't
have any PPA, here is the original patch for kexec-tools 2.0.2 though: [2].
Needs to be applied by hand, the paths do not match.

PS: Sorry to Tim Gardner, I accidentally sent this message just to him,
gmail likes to change receivers by itself.

[1]: https://github.com/Tasssadar/android_kernel_asus_grouper/commit/bee734f61ffa97577bfbcdd9a8cd567bd2d89f32
[2]: https://gist.github.com/4164675

---
On 11/28/2012 6:38 PM, Jani Monoses wrote:
>
> Hi,
>
> if the patches are final and you don't expect further updates due to
> user-space kexec-hardboot changes in this cycle I am fine with having
> this and will defer the final decision to Tim and the rest of the kernel
> team.
> I wonder though if this could not be made more generic - do you know
> whether the Nexus7 is unique among platforms or ARM machs supported by
> Ubuntu that does not work with vanilla kexec? Is finding and fixing the
> faulty drivers that prevent kexec from working unfeasible?
>
> Do you have a PPA with your userspace bits? Other developers too may
> find kexec-hardboot improves their debugging workflow too if you think so :)