I was building the default kernel selected by the layer, not the dev kernel as Mike refers to it. Had no problems once Nathan’s patch was added. Peter
From: [email protected] [mailto:[email protected]] On Behalf Of Mike Looijmans Sent: 05 September 2016 07:05 To: Nathan Rossi Cc: [email protected] Subject: Re: [meta-xilinx] Warnings that items did not make it into the final kernel configuration On 02-09-16 12:42, Mike Looijmans wrote: > On 02-09-16 12:12, Nathan Rossi wrote: > > On Fri, Sep 2, 2016 at 8:02 PM, Mike Looijmans > <[email protected]<mailto:[email protected]>> wrote: > >> > >> On 01-09-16 08:53, Nathan Rossi wrote: > >>> On Thu, Sep 1, 2016 at 3:12 AM, Peter Smith > <[email protected]<mailto:[email protected]>> wrote: > >>>> Glad its not just me. Do you think it could be related to my use of the > >>>> master branch rather than a released version? > >>>> > >>>> On 31 August 2016 at 15:00, Mike Looijmans > <[email protected]<mailto:[email protected]>> wrote: > >>>>> > >>>>> On 31-08-16 15:40, SMITH Peter T wrote: > >>>>>> > >>>>>> Hi, > >>>>>> > >>>>>> I am trying to build core image minimal for the ZCU102 using the > master > >>>>>> branches poky and meta-xilinx and I am receiving lots of warnings > about > >>>>>> kernel > >>>>>> configurations not making it into the final kernel configurations. Is > >>>>>> this > >>>>>> normal or I have I done something wrong? > >>>>> > >>>>> > >>>>> Well I noticed that the kernel config doesn't quite work as expected on > >>>>> that particular board but I'm still investigating the "why" myself. > >>> > >>> Found the bug, it relates to a change in oe-core/kernel-yocto.bbclass > >>> that was made recently 0f698dfd1c8bbc0d53ae7977e26685a7a3df52a3. The > >>> values for KCONFIG_MODE changed, such that it is defaulting to > >>> "allnoconfig". This only applies to zcu102-zynqmp because its the only > >>> machine that uses a KBUILD_DEFCONFIG as the base. > >>> > >>> I've staged the following patch > >>> > https://github.com/nathanrossi/meta-xilinx/commit/34e08e9f6635d4365058a96ea13bf8286d9930a8. > >>> Could one of you confirm that it resolves the issue and that the built > >>> kernel works? > >> > >> Hmm, it seems to break my build: > >> > >> | [INFO] Configuring target/machine combo: "alldefconfig/--reconfig" > >> | No build dir specified. Use "-o" to specify one. > >> | config of "alldefconfig/--reconfig" failed > >> > >> so apparently this is for a newer OE master? > > > > Yes the oe change was committed ~2.5 weeks ago, specifically on > > 2016-08-18 08:27:13 (GMT). But it is odd that you are seeing issues > > with configs before this patch was applied to master, maybe a separate > > issue with the configs? > > So far the problem I was having was that in the "dev" kernel the "defconfig" > from the kernel itself would be mostly ignored, so almost no drivers were > selected. I worked around that by copying most of the kernel 4.6 defconfig > into the zynqmp.cfg files. > > I'm re-building with today's OE master to see if that issue is related. Not related. If I build the "dev" kernel (current master of linux-xlnx), the "defconfig" for the ZynqMP doesn't actually get parsed somehow, and I end up with a kernel that won't compile due to conflicting defines (for example "CONFIG_SOC_XILINX_ZYNQMP" is not set, causing drivers/soc/xilinx/zynqmp/tap_delays.c, which somehow still triggers to be compiled, to fail because the header contains blank implementations. What does work is manually copy the defconfig contents into a cfg file. But that's not how it's supposed to work I guess. Kind regards, Mike Looijmans System Expert [cid:[email protected]] TOPIC Products Materiaalweg 4 5681 RJ Best T: +31 (0) 499 33 69 69 Postbus 440 E: [email protected]<mailto:[email protected]> 5680 AK Best W: www.topicproducts.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.topicproducts.com&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=-0xOp6WEUxZEZ28IafXrMa3oLhGTFvyj7y8nzyNrgGo&m=bAfoHsD4ACCwR1CX2EhpjrbRWxRvqhWxMRwd5ZC4omA&s=POYIuKNHUEg2AUG9_pxLlXQQ5Qpkr03lFrCIVobVqBc&e=> The Netherlands [cid:[email protected]]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_TopicProducts&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=-0xOp6WEUxZEZ28IafXrMa3oLhGTFvyj7y8nzyNrgGo&m=bAfoHsD4ACCwR1CX2EhpjrbRWxRvqhWxMRwd5ZC4omA&s=6kYYdHLnA3G7yKlVkle5wjZ9cGZVn4Qsfgth6AS_iGk&e=>[cid:[email protected]]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_TopicProducts&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=-0xOp6WEUxZEZ28IafXrMa3oLhGTFvyj7y8nzyNrgGo&m=bAfoHsD4ACCwR1CX2EhpjrbRWxRvqhWxMRwd5ZC4omA&s=v7JcS8F80nwFZTA8CrfZpJFmZ5tTpwrgTSxgtwdpL7M&e=>[cid:[email protected]]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_topic-2Dembedded-2Dproducts&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=-0xOp6WEUxZEZ28IafXrMa3oLhGTFvyj7y8nzyNrgGo&m=bAfoHsD4ACCwR1CX2EhpjrbRWxRvqhWxMRwd5ZC4omA&s=osyKA4fMn_1IsNo2ptdy2W-OJIhFg97DFmn_Yjm4Qso&e=> Please consider the environment before printing this e-mail Topic zoekt gedreven (embedded) software specialisten!<https://urldefense.proofpoint.com/v2/url?u=http-3A__topic.nl_vacancy_topic-2Dzoekt-2Dtechnische-2Dsoftware-2Dengineers_&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=-0xOp6WEUxZEZ28IafXrMa3oLhGTFvyj7y8nzyNrgGo&m=bAfoHsD4ACCwR1CX2EhpjrbRWxRvqhWxMRwd5ZC4omA&s=CIqMeZrlOhTujj6_5bCqsGZlzL04wplcofhwLOy87UY&e=> ________________________________ CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
-- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
