[oe] [PATHC] ATAG export for the linux kernel

Richard Purdie rpurdie at rpsys.net
Mon Dec 10 08:27:34 UTC 2007


Hi,

On Fri, 2007-12-07 at 08:18 -0800, Hans Henry von Tresckow wrote:
> I updated http://bugs.openembedded.org/show_bug.cgi?id=3397 with a new
> patch to filter out the Sharp command line (for poodle at least). Let
> me know if that approach makes more sense.
>
> http://bugs.openembedded.org/show_bug.cgi?id=3430 has the userspace
> kexec patch.
>
> Thanks for taking a look at this.

I've had a look at the patches, have given them a lot of thought and I'm
not convinced the approach is quite right. I do have an alternative
proposal however.

I agree we need access to the existing atags from the kernel. To get
them I think we should memcpy them as per the existing code but do this
after any old style boot params have been converted into atags.

When it comes to kexec'ing the new kernel, we setup the new kernel at
the 32kiB offset as we currently to but we copy our new set of atags
into the first 16kiB region. We then point r2 of the new kernel at this
memory address and the new kernel should use this set of tags.

This means we don't have to mess around trying to work out what address
to put the atags, boot_params etc. at and also it means we know for
certain that the options passed from kexec are the ones used, not some
other random options. It also means no modifications are required to
existing machines such as the zaurus.

I'd also consider having kexec extract the commandline from the running
kernel is none is specified.

I will try and implement this if I get a chance and see how it works...

Cheers,

Richard






More information about the Openembedded-devel mailing list