Dear Sirs, I am dumping this mail to ask for some clarifications. I am looking closely to yocto as environment for building embedded linux distro for omap based boards.
In particular, I do have AM3517 and DM3730 custom boards to support. I am seeing that TI has made available meta-ti on yocto git that looks like a good starting point for me. But at same time the readme.txt does spot incompatibilities with the current yocto structure and points to open embeded and angstron layers. I am confused. When do you plan full compatibility with yocto? Would the gcc-4.5 toolchain grant full compatibility with neon? I am asking this because other players such as Denx (with its own ELDK www.denx.de) are providing an armv7a based on gcc-4.6 that I could test with "CFLAGS= -march=armv7-a -fno-tree-vectorize -mthumb-interwork -mfloat-abi=softfp -mfpu=neon" and observe operating fine on AM3517. I am wondering what is the best way to go: - attempt integrating meta-ti with yocto for portions I need (davinci support for sure on DM3730) - or stick with meta-ti as it is and develop my own recipes for custom hw as meta-ti bsp. Thanks in advance for your time. Regards, Marco Monguzzi
_______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
