All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Monsees, Steven C (US)" <steven.monsees@baesystems.com>
To: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: configuration fragments
Date: Mon, 14 Mar 2022 19:57:33 +0000	[thread overview]
Message-ID: <20220314195739.69F0AC433EF@smtp.lore.kernel.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]


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)

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

[-- Attachment #2: Type: text/html, Size: 3273 bytes --]

             reply	other threads:[~2022-03-14 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 19:57 Monsees, Steven C (US) [this message]
2022-08-17 13:10 [PATCH 1/5] bitbake-layers: add a command to save the active build configuration as a template into a layer Alexander Kanavin
2022-08-17 13:10 ` [PATCH 2/5] meta/files: add layer setup JSON schema and example Alexander Kanavin
2022-08-17 20:52   ` [OE-core] " Richard Purdie
2022-08-17 21:36     ` Alexander Kanavin
2022-08-17 22:27       ` Richard Purdie
2022-08-18  8:24         ` Alexander Kanavin
2022-08-18  9:27           ` Richard Purdie
2022-09-01 15:29             ` Configuration fragments Alexander Kanavin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220314195739.69F0AC433EF@smtp.lore.kernel.org \
    --to=steven.monsees@baesystems.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.