[OE-core] what are the major phases of do_patch() for the kernel?

Robert P. J. Day rpjday at crashcourse.ca
Thu Jul 19 21:50:21 UTC 2012


  short version: what happens during each major processing step of the
do_patch function for the kernel?

  longer version: i'm stepping through what happens when i do a
"bitbake linux-yocto", and documenting what happens at each step --
currently looking at do_patch().

  after having run the previous validate_branches target, what i
appear to have is the source directory containing the kernel source
with the (for me) standard/arm-versatile-926ejs branch checked out,
and no top-level "meta" directory.  so far, so good.

  now, i'm building core-image-minimal for qemuarm, so i'm being as
unexciting and non-exotic as possible -- not selecting any special
parameters or corner cases or anything.

  so as i peruse do_patch() in kernel-yocto.bbclass, i'm following
along to functions like createme and updateme and patchme, and with
createme, further into decheckpoint and check_defconfig and ... you
get the idea.  and i'm kind of getting lost in the weeds of details.

  given that i'm building an absolutely stock target with a supported
machine, all i really need for the moment is a very high-level
explanation of what each of those main routines does.

  so if my initial understanding is correct (that before i start
do_patch), i have the stock yocto kernel checked out to the
appropriate machine branch and nothing else), what does each
subsequent step accomplish?

  don't need horrific detail, just one line or less as to what's
accomplished by each step like:

  * createme
    * decheckpoint
    * checkdefconfig
    * check_branch
    * metaize
  * updateme

... etc, etc.  and at the end of the patch step, i know that i'll have
that untracked top-level "meta" directory, still not sure what will
have been done with it yet.  i guess that's for the next step, which
appears to be "kernel_configme".  but one thing at a time.

rday

-- 

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

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




More information about the Openembedded-core mailing list