On 2012-03-02 15:50, William Mills wrote:
On 03/02/2012 05:33 PM, Robert P. J. Day wrote:
On Fri, 2 Mar 2012, William Mills wrote:
... snip ...
Congratulations you are the first beta tester for the new README.txt
language :) (patched two days ago).
Denys: I suggest
change:
"Due to the above, it is now recommended to follow the instructions
at http://www.angstrom-distribution.org/building-angstrom";
to:
"When the other layer combinations are supported instructions will
be supplied here. Until that time please see the Angstrom setup
instructions below.
*** Angstrom w/ meta-ti Layer Stack setup: ***
Please follow the instructions at
http://www.angstrom-distribution.org/building-angstrom";
i might try something a bit different. given that angstrom is the
tested way to go, by all means, point that out and *strongly*
recommend that approach.
on the other hand, what is the current issue with the yocto/meta-ti
combo? is it *known* to be broken? or is it simply not sufficiently
tested? in cases like that, i see no problem in cautioning people
about it, but telling them that if they're feeling adventurous,
they're welcome to give it a shot but if it breaks, as they say, they
get to keep all the pieces.
don't discourage people from trying it, but make sure you give
proper instructions for how to use it, that's all. unless, as i said,
it's really and truly unusable.
We will update the README when it is merely in need of testing.
Today, we know there is code that does not work with GCC 4.6.
Today, we know there are features in the recipes that do not work w/o Angstrom.
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 point" for these platforms. So far, I've only
had to make a scant few tweaks to get this combo to work, in particular:
* In conf/local.conf, I use this to avoid parsing problems with some meta-ti
recipes (none of which I need at the moment)
# Ignore troublesome TI recipes
BBMASK = ".*/meta-ti/recipes-misc/"
* In distro.conf (I do have my own distro, but it's very close to poky), I
needed
# Allow hardware overrides, e.g. armv7a
OVERRIDES .= ":${SOC_FAMILY}"
With these minor additions, I've been able to use the meta-ti layer for [some]
kernel work, u-boot, DSP support, etc - all the stuff one expects the layer
to provide.
I know my setup is a bit outside pure poky+meta-ti, but it does show that
you don't actually have to have Angstrom to use meta-ti.
It would be nice to understand what your concerns are, certainly the details
of your two "Today,..." statements above, if they fall outside what I've
outlined
here.
As soon as we remove the above for even one platform we will update the README to
reflect an Alpha state for oc-core &| poky layer stack for that platform(s).
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
