All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: questions about KBUILD_DEFCONFIG explanation in kernel-dev manual
Date: Tue, 20 Dec 2016 06:27:35 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1612200615540.5678@localhost.localdomain> (raw)


  (yes, i really am digging through the user guides these days ...)

from kernel-dev manual, section 2.2.4:

  "To specify an "in-tree" defconfig file, edit the recipe that builds
   your kernel so that it has the following command form:

     KBUILD_DEFCONFIG_KMACHINE ?= defconfig_file

   You need to append the variable with KMACHINE and then supply the
   path to your "in-tree" defconfig file."

first, i'm going to tag the "KMACHINE" part above with
<replaceable>, since it pretty clearly needs it.

  next, you need to "supply the path" to the defconfig file? uh, don't
you just need to give the simple name of the in-tree defconfig file
you want to use as it is somewhere under arch/<arch>/configs in the
kernel source tree? here's a snippet from the meta-altera layer:

   KBUILD_DEFCONFIG ?= "socfpga_defconfig"
   KBUILD_DEFCONFIG_stratix10swvp ?= "defconfig"
   KBUILD_DEFCONFIG_10m50 ?= "10m50_defconfig"

seems like one needs just the name of the defconfig file to be used,
there's no concept of needing a "path" to the file, is there?

  next, it appears that one does *not* "need to append the variable
with KMACHINE", given one of the lines from meta-altera above, is that
correct? this just sets a default, no?

   KBUILD_DEFCONFIG ?= "socfpga_defconfig"

  and finally, must all defconfig files identified via
KBUILD_DEFCONFIG be an "in-tree" file? i ask since this line above:

   KBUILD_DEFCONFIG_stratix10swvp ?= "defconfig"

is potentially confusing, and might make someone perusing the source
to think that's an alternative way to point at their "out-of-tree"
defconfig file. but it's not, is it?

  i checked that machine type, and it's armv8, so i'm *assuming* that
line would refer to the in-tree file arch/arm64/configs/defconfig, is
that right?

  i think that will do it for now.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



                 reply	other threads:[~2016-12-20 11:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LFD.2.20.1612200615540.5678@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=yocto@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.