[yocto] observations on current BSP developer's guide

Robert P. J. Day rpjday at crashcourse.ca
Mon Apr 22 06:48:42 PDT 2013


  brief notes on BSP dev guide, someone else higher up the food chain
can decide if any of this merits changes or clarifications.

1.1 BSP Layers

* emphasize that name of "meta-*" is only convention, but a really
well-established one

* remove lines of meta-yocto/meta-yocto-bsp from example, has
potential for giving readers wrong impression. also that whole
BBLAYERS_NON_REMOVABLE thing is debatable. pick simpler example.

1.2 Example Filesystem Layout

* clarify what is *actually* required to be an official OE/YP layer,
as some layers don't have things like README, README.sources, etc.

1.2.5 Layer Configuration File

* "here are the last three statements from the Crown Bay
conf/layer.conf file" -- those aren't actually the last three lines,
there's also the "_depends" line but someone else can decide how to
word that.

* wait, that sample layer.conf file seems wrong, aren't the BBFILES
entries missing a wildcard directory layer?

1.2.6 Hardware Configuration Options

* "For example, the ia32-base.inc file resides in the meta-intel BSP
Layer in conf/machine/include." hmmmm ... pedantic, yes, but should
meta-intel really be described as a "BSP" layer? what's the proper way
to describe it?

* also, that statement is simply wrong as that directory contains only
meta-intel.inc, not ia32-base.inc. and last para might also mention
the include of meta-intel.inc in addition to the other two "require"s.


1.2.7 Miscellaneous Recipe Files

* Might rename this to "Miscellaneous BSP-specific Recipe Files", to
distinguish it from the *other* recipe-related sections that follow?

1.2.9 Linux Kernel Configuration

* Worth upgrading the example shown to 3.8 instead of 3.4? and the
source shown there doesn't exactly match what's in the current file.

* "The file also uses the optional KBRANCH variable to ensure the
build process uses the standard/default/crownbay kernel branch."
sorry, "standard/default/crownbay"? shouldn't that say just
"standard/crownbay"?

* "you had a some" -> "you had some"

1.3.1 Released BSP Requirements

* again, a number of existing layers don't fully comply with this list

* File System Layout: "recipe-*" -> "recipes-*"

* Machine Configuration File: should probably say that you need to
include one *or more* machine config files, not just one.

* Note: "It is completely possible for a developer to structure the
working repository as a conglomeration of unrelated BSP files..."
might be worth pointing out that this is exactly what meta-yocto-bsp
does, but that's a special case.

1.4 Customizing a Recipe for a BSP

* based on recent discussion, probably don't want to use the netbase
recipe as the example here :-) besides, point 1 erroneously refers to
the "netbases" directory instead of "netbase".

  that's enough for now, i'll finish reading the bsp tools section
later.

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 yocto mailing list