From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: more observations on kernel dev manual
Date: Wed, 25 Feb 2015 05:52:11 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.11.1502250517500.32394@localhost> (raw)
been a while since i went through this manual so some probably
simple observations -- based on in-progress manual. if scott rifenbark
wants to process any of this, he has my blessing.
section 2.2.2: i'm assuming that list of SRC_URIs should actually
read?
... first-change...
... second-change ...
... third-change ...
section 2.2.3: should that note not refer to the "defconfig" file
and not the ".config" file? as in, the defconfig file is used as the
*basis* for the eventual .config file, no? so the note should be
discussing applying the changes from the "defconfig" file, should it
not?
section 2.3.2: hang on ...
"Complete a build at least through the kernel configuration task as follows:
$ bitbake linux-yocto -c kernel_configme -f"
but i thought that "-c <command>" would run *only* that bitbake task
... the wording suggests that that command will run everything *up to*
that task.
also in that section, "are not't" should just say "aren't" in sample
warning output.
section 2.3.3: again, first para suggests that that command should
process the kernel all the way "through" the kernel configuration.
that's it for chapter 2 ... more later.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2015-02-25 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 10:52 Robert P. J. Day [this message]
2015-02-25 16:47 ` more observations on kernel dev manual Rifenbark, Scott M
2015-02-25 17:05 ` Darren Hart
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.11.1502250517500.32394@localhost \
--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.