more nitpicky pedantry ... i mentioned this once upon a long time ago, but i thought i'd revisit it. there is a fair bit of inconsistency in the docbook markup in the YP docs such that, even though th

as i claw my through the bsp guide, i notice the occasional confusion between referring to the BSP layer itself and a machine supported by that layer. a couple times, i've found references to the alle

in canada, distributors are charging over $400 (CAD) for either of those, which you'd normally think would be outside the bounds for a YP reference board, but it may be that that's what you have to ac

i would start with the machine definition files in the meta-fsl-ppc layer: http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/tree/conf/machine and see what looks promising. however, IIRC, one of

not at the moment ... perhaps the powerpc or freescale folks can weigh in. i'm not a powerpc expert, but it does seem pointless to have a reference board that no one can get. rday

oh, i understand how the poky layers are structured, but i was quoting from the para in the bsp guide that starts, "Some layers function as a layer to hold other BSP layers." and, technically speaking

it seems of limited value for YP to have a powerpc reference board, mpc8315e-rdb, that is essentially impossible to procure. is there any effort being made to look around for a newer powerpc reference

Collection of minor cleanups to BSP Guide: * Standardize on spelling of "BSP layer" rather than "BSP Layer" * Describe YP reference boards in more detail (architecture, ...) * Bump up several referenc

in section 1.2.9: "Suppose you are using the linux-yocto_4.4.bb recipe to build the kernel. In other words, you have selected the kernel in your bsp_name.conf file by adding these types of statements:

still in BSP Guide: "Note If the BSP's binary directory is missing or the directory has no images, an existing README.sources file is meaningless." yet the meta-intel layer has that file but no binary

in current BSP Guide: "Some layers function as a layer to hold other BSP layers. An example of this type of layer is the meta-intel layer, which contains a number of individual BSP sub-layers, as well

jsut one of those things that starts to grate on me after a while ... while reading BSP guide, the text bounces back and forth between "BSP Layer" and "BSP layer." personally, i'm not a huge fan of up

if my earlier patches for kernel-dev manual have not already been applied, feel free to toss them, and i'll resubmit a newer patch right from the beginning with updated version numbers and everything

in that case, one can drop those earlier patches i sent in, and i will submit newer ones. rday

okey dokey. rday

i might have skipped those possibilities since they produced no output, which made the examples rather vacuous. :-) i'll check again, want to make sure one picks a branch that actually generates outpu

section 2.6.2 refers to how to display changes based on a tag, and uses the alleged tag name "systemtap" ... do tags like that even exist anymore? i see no such tag in my current build directories. rd

Update the remaining references to kernel version 3.19 to version 4.4, restricted to the section "kernel-dev-common.xml". Signed-off-by: Robert P. J. Day <rpjday@...> --- if my earlier patc

still working my way through the kernel-dev manual, and a couple oddities in section 2.6. first, the example given uses the (alleged) standard/emenlow branch, which i'm pretty sure doesn't exist anymo

just noticed this in kernel dev manual, section 2.3.1: "To force a pickup and commit of all such pending changes, enter the following: $ git add . $ git commit -s -a -m "getting rid of -dirty" the "-a