On 4/2/14, 8:20, "Stanacar, StefanX" <stefanx.stana...@intel.com> wrote:
>
>
>
>On Wed, 2014-04-02 at 18:11 +0300, Stefan Stanacar wrote:
>>
>>
>> On Wed, 2014-04-02 at 00:19 -0700, Darren Hart wrote:
>> > CONFIG_X86_32 is a non-selectable configuration item, automatically
>>set
>> > by ARCH and !CONFIG_64BIT. There are no users of the .cfg nor the
>>.scc.
>> > Delete them.
>> >
>> > Signed-off-by: Darren Hart <dvh...@linux.intel.com>
>> > ---
>> > meta/cfg/kernel-cache/cfg/x32.cfg | 1 -
>> > meta/cfg/kernel-cache/cfg/x32.scc | 4 ----
>> > 2 files changed, 5 deletions(-)
>> > delete mode 100644 meta/cfg/kernel-cache/cfg/x32.cfg
>> > delete mode 100644 meta/cfg/kernel-cache/cfg/x32.scc
>> >
>>
>> Does this mean oe-core will need an update on linux-yocto*.bb which has:
>>
>> KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32",
>> " cfg/x32.scc", "" ,d)}"
>>
>> ?
>>
>
>And on a second look, your commit message says CONFIG_X86_32 but this is
>about x32, which I don't think gets set like that.
>Kconfig says:
>
>config X86_X32
> bool "x32 ABI for 64-bit mode"
> depends on X86_64 && IA32_EMULATION
Ugh, you are correct. Thank you for catching that. Oh the difference an X
makes!
--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center
--
_______________________________________________
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
