more observations on kernel dev manual

more observations on kernel dev manual

[Robert P. J. Day]

  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
========================================================================

Re: more observations on kernel dev manual

[Rifenbark, Scott M]

So I fixed the two obvious issues here.  I am working on getting clarification on the command -c item.  

Thanks,
Scott

>-----Original Message-----
>From: Robert P. J. Day [mailto:rpjday@crashcourse.ca]
>Sent: Wednesday, February 25, 2015 2:52 AM
>To: Yocto discussion list
>Cc: Rifenbark, Scott M
>Subject: more observations on kernel dev manual
>
>
>  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 ...

Holy Mackerel... how did this go unnoticed for so long.  Fixed.

>
>  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.

I am double checking on the behavior of this.  

>
>  also in that section, "are not't" should just say "aren't" in sample warning
>output.

I fixed this in the manual.  I grepped for that particular string in both poky and bitbake repos and came up empty.  So I am not sure where exactly (if even) that string appears in the actual source repo.

>
>  section 2.3.3: again, first para suggests that that command should process the
>kernel all the way "through" the kernel configuration.

Again, waiting on some clarification on this issue.

>
>  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
>===========================================================
>=============

Re: more observations on kernel dev manual

[Darren Hart]

On 2/25/15, 2:52 AM, "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:

>
>  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.

Thanks for your review of the document Robert. For future comments, please
do include the author on Cc.


...

>
>  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.

It will run everything necessary up to and including that task. If
everything, including that task, have already been run, it will run only
the specified task again.

You can verify this with:

1 $ bitbake virtual/kernel
2 $ bitbake virtual/kernel -c kernel_configme -f
3 $ bitbake virtual/kernel -c cleansstate
4 $ bitbake virtual/kernel -c kernel_configme -f


#2 will only run kernel_configme
#4 will run everything after fetch up to and including kernel_configme.
This usage helps us keep the documentation concise rather than having to
spell out how to get to a specific state in order for the command used to
work correctly.

>
>  also in that section, "are not't" should just say "aren't" in sample
>warning output.

This output should be updated for 1.8 as config warnings are now sent to
the console and not just buried in the logs. Yay!

-- 
Darren Hart
Intel Open Source Technology Center