"poduct/init" ? rday

just listed git tags for poky, and a couple that show up that screw up the ordering: ... yocot-1.4.2 <----- yocto-1.4.1 yocto-1.4.2 ... yocto-2.1.2 yocto-2.2 yocto-2.2.1 yocto_1.5_M5.rc8 <----- ... rd

* Outside of a title, use "BSP layer", not "BSP Layer" * Add details about YP reference boards. * Minor grammatical clarification in places. * Add <para> to even single paragraph notes for consistency

it might be worth asking why zsh is doing that in the first place. if one doesn't want all that stuff, *that* is where an append could be used to remove it. i think zsh removing it by default is inapp

i know i was working on some tweaks but can't find if i submitted any yet. can anyone verify that what's up under "in progress/latest" is the current version, as git pull'ed from yocto docs? thanks. r

true, but the wording in the BSP Guide is: "Some BSPs require additional layers on top of the BSP's root layer in ^^^^^^^^^ order to be functional. " that particular phrasing suggests that perhaps wha

pretty sure i asked this before, but again in 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

perusing current BSP Guide: "Some BSPs require additional layers on top of the BSP's root layer in order to be functional. For these cases, you also need to add those layers to the BBLAYERS variable i

In machine configuration files, there is no need to use OVERRIDES that match the precise machine being defined, so remove them for clarity and consistency from these lines in those respective files: P

i just noticed that the machine config file for mpc8315e-rdb still lists "uImage" as the default image type: KERNEL_IMAGETYPE = "uImage" IMAGE_BOOT_FILES ?= "u-boot.bin uImage uImage-mpc8315erdb.dtb;d

i'll check later to see where it would seem to belong, unless someone has a suggestion. actually, i take back that suggestion, as i think it would overly complicate kernel.bbclass (at least the way i

that *appears* to have solved the problem ... so why is it i didn't realize that? where is that written up that i somehow missed it? and would it not make sense that selecting FIT image in one variabl

... snip ... i would still love to figure out how to generate a simple FIT image when building core-image-minimal for mpc8315e-rdb. first, based on what i read, my first attempt was to add the followi

just updated my poky layer, tried to build core-image-minimal for mpc8315e-rdb, and: ERROR: 171 unbuildable tasks were found.############ | ETA: 0:00:04 These are usually caused by circular dependenci

i'll start a new thread to focus on just this issue. again, building core-image-minimal for mpc8315e-rdb, adding this to local.conf: INHERIT += "kernel-fitimage" <-- do i need this line? KERNEL_IMAGET

ah, that does, in fact, fix the missing "whoami" issue (i'm fascinated that that glitch wasn't triggered until i asked for a FIT image). however, i'm still getting this: ... snip ... | HOSTCC arch/pow

trying for the first time to build a FIT image, so started with current poky checkout, configured and built for mpc8315e-rdb and core-image-minimal, everything worked fine (as it always does). now, as

first advice is to use meaningful subject lines ... simply yelling "help" is a good way to get people to not take you seriously right from the beginning. rday

not sure if i'm misreading this, but i note that an addition was made to the ref manual back in dec 2016: commit 5d2bdf49e569e44d02602501d72418f04dbe6e4a Author: Scott Rifenbark <srifenbark@...>

Collection of aesthetic/formatting/clarification fixes to BSP Guide, including: * Adjust some directory names to have trailing slash * Reword some paragraphs for clarity * Add <para>s inside <note>s f