RE: [yocto] configuration fragments

["Monsees, Steven C (US)" <steven.monsees@baesystems.com>]

Thanks again...

-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf Of Khem Raj
Sent: Tuesday, March 15, 2022 11:48 AM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] configuration fragments

External Email Alert

This email has been sent from an account outside of the BAE Systems network.

Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros.  For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.


if you are using linux-yocto for kernel then it is surely supported , so as long as it is added to kernel recipe it should work ok.

On Tue, Mar 15, 2022 at 3:58 AM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@lists.yoctoproject.org> wrote:
>
>
> When you say:
>
> " you might have to look into this kernel recipe and ensure that it has enabled merging configs feature from kernel"
>
> Are you talking about inheriting from "kernel-yocto" in order to work with configuration fragments ?
>
> Thanks,
> Steve
>
> -----Original Message-----
> From: Khem Raj <raj.khem@gmail.com>
> Sent: Monday, March 14, 2022 4:13 PM
> To: Monsees, Steven C (US) <steven.monsees@baesystems.com>
> Cc: yocto@lists.yoctoproject.org
> Subject: Re: [yocto] configuration fragments
>
> External Email Alert
>
> This email has been sent from an account outside of the BAE Systems network.
>
> Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros.  For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.
>
>
> On Mon, Mar 14, 2022 at 12:57 PM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@lists.yoctoproject.org> wrote:
> >
> >
> >
> > Under my aarm64 platform ../recipes-core/images I have a file “aiox-swdebugfs.inc”
> >
> >
> >
> > Which basically contains:
> >
> >
> >
> > EXTRAPATHS_prepend := "$(THISDIR}/files:"
> >
> > LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
> >
> > SRC_URI += file://aiox-swdebugfs.cfg
> >
> >
> >
> > I include this in my aiox-swdebugfs.bb like so: “require aiox-swdebugfs.inc”
> >
> >
> >
> > It does not appear to apply my configuration fragments…
> >
> > (CONFIG_SCHED_TRACER, CONFIG_TRACER, etc. for additional perf 
> > support)
> >
> >
>
> these are some config files for doing what ? from what it looks like, this inc file is adding a kernel config fragment if so then it should be appended too kernel recipe so if aiox-swdebugfs.bb is kernel recipe then you are doing it right, but then you might have to look into this kernel recipe and ensure that it has enabled merging configs feature from kernel. Otherwise these cfgs wont be processed.
>
> >
> > I have the exact same implementation working under my intel platform.
> >
> >
> >
> > Can someone tell me what I might be doing wrong, or how I can get my configuration fragments to be applied properly ?
> >
> > Any ideas why it might work properly under one architecture and not on the other ?
> >
> >
> >
> > Thanks,
> >
> > Steve
> >
> >
> >
> >
>
> 
>