On Tue, May 30, 2017 at 11:48 AM, Aníbal Limón <anibal.li...@linux.intel.com > wrote:
> The oe-core provides kexec-tools recipe, since we don't > have a manner to enable automatically a kernel feature by > recipe request, this is the best place to enable it in > a kernel developer mode. > Yah, the separation of kernels, images and distros triggers issues like this. To actually make kexec work, you need the right tools, a kexec target kernel, configuration, etc. That makes me think that it really should be a distro or image feature, and from there we could trigger a KERNEL_FEATURE that pulled this in. That's more work that this really needs a the moment, so I've merged this patch as-is. Bruce > > Signed-off-by: Aníbal Limón <anibal.li...@linux.intel.com> > --- > ktypes/developer/developer.cfg | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/ktypes/developer/developer.cfg b/ktypes/developer/developer. > cfg > index ee04ec7..360ca9c 100644 > --- a/ktypes/developer/developer.cfg > +++ b/ktypes/developer/developer.cfg > @@ -17,3 +17,9 @@ > CONFIG_EXPERT=y > CONFIG_EMBEDDED=y > CONFIG_DEBUG_KERNEL=y > + > +# > +# Enables kexec support because oe-core contains kexec-tools and requires > +# this support > +# > +CONFIG_KEXEC=y > -- > 2.1.4 > > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
-- _______________________________________________ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto