First: -EWRONGLIST Second: Upstream calls it bonescript https://github.com/jadonk/bonescript

Apparently, they're still useful to people, so I think updating rather than retiring them makes more sense at this point (or they or something similar get merged into the Developer's guide? For now,

Yeah, just because poky appears in the URL doesn't mean we need to reference it beyond that. Yeah, definitely, I need to update these pages for for edison, which I'll do now that I know somebody's

just wandering through the yocto/poky reference manual, and it seems that some of the lists there are missing a few entries. first, in the images

Yeah, the example is pretty old, dating back to the 1.0 (bernard) release. Tom - it might be time to retire it, you think?

Signed-off-by: Robert P. J. Day <rpjday@...> --- diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index 2a93ec6..5627c82

yes, i know it's an editable wiki but i'd rather someone else make the changes just in case i'm misreading something. it's early, and there's only decaf in the place. this is bad. anyway, using

... much snipping below to get to the gist of it ... regardless of the fix, i would think that the proper name for that recipe file would be something like "beaglescript.bb" and

Oops, that's one more workaround I forgot to mention. This file is in OE-core, but not in poky. I made a local copy in my distro layer, but there must be a better way to handle it. --

not sure if you're suggesting i should now be able to build for, say, beagleboard with the meta-ti layer, but i cloned meta-ti into my yocto tree, added that layer to bblayers.conf, and tried to $

i'm perfectly prepared to be told this is not the right forum to mention this, but i just cloned the meta-ti layer and in conf/machine, there appear to be two pandaboard-related files:

Gary, Clearly, the README is meant for the new people, who might find it too complicated for the above fixes to be applied in order for them to avoid using Angstrom. But you are correct, besides

Actually, he is the first one to complain about the meat (i.e. added one paragraph with 3 statements) - everyone else before him was complaining about not enough info in the README, hence the

Perfect. Thanks for the confirmation. Bruce

thought i'd point out that, if people are confusing yocto and poky, it doesn't help that the yocto reference manual is found

Nothing major, just some simple cleanup in the QS Guide. Signed-off-by: Robert P. J. Day <rpjday@...> --- diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml

while playing with "runqemu", i noticed that the generated "qemu-system-arm" command contained two "-no-reboot" options in it, apparently because of this in runqemu-internal: first: if [ "$MACHINE"

If we can make some simple changes (or document workarounds) that enable bare bones support for poky/oe-core that does not break full support in Angstrom, I'm all for it. Even if we have to limit it

Hi Joshua, The error message however does not seem to print the correct problematic path.. but I was able to find the problem using your tips. Thanks ! Rahul

Can you elaborate on the above? I have been [I think] successfully using poky+meta-ti to support internal platform based on DM8148 and DM3730 - meta-ti is the best choice for a kernel "jumping off