On Tue, Nov 20, 2012 at 06:10:17PM +0100, Nicolas Dechesne wrote: > well.. obviously, with the libdrm update, and our .bbappend in meta-ti > things are even worse than I had thought... and the tree doesn't even build > anymore, at least for panda, as we have: > > COMPATIBLE_MACHINE = "omap4|omap5" > > in the .bbappend > > so now that brings another question... should we start a 'danny' branch on > meta-ti? if we remove the libdrm and xf86-video-omap recipes from > meta-ti/master, then we break meta-ti/master with poky/danny...
Yes, creating danny branch was on my list - was waiting for any specific requirements like this one... :) -- Denys > On Tue, Nov 20, 2012 at 5:50 PM, Nicolas Dechesne <[email protected]> wrote: > > > hi > > > > i just noticed that the recipe for xf86-video-omap was just merged into > > poky/master, and that libdrm was updated as well (and OMAP experimental > > support was enabled too): > > > > 0ed7c53 xf86-video-omap: add new recipe to follow the maintained repo > > cb758f9 libdrm: upgrade to 2.4.40 > > > > from a quick review, i believe this should supersede the recipes from > > meta-ti that got merged recently: > > > > 410dc02 xf86-video-omap: add new recipe for OMAP4/5 X11 video driver > > cce5a7a libdrm: enable omap experimental api support > > > > i won't be able to get that tested in the next couple of days, very > > likely, so i wanted to know: > > > > - if anyone tested poky/master (or oe-core as this came from oe-core) on > > panda and/or beagle? > > - what is the policy in this situation? should we simply remove our > > recipes from meta-ti? > > > > cheers > > > > nicolas > > > > > > > > > _______________________________________________ > meta-ti mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/meta-ti _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
