>>> FWIW: For the reason other meta's seem to me either unmaintained for >>> long time or bloated or both, I created another very simple layer [1] >>> with current beagleboard.org kernel and dt.overlays. No meta-ti >>> dependency / only sw-rendered mesa - works just fine for me. >>> >>> [1] https://github.com/schnitzeltony/meta-bbone >> >> And i probally break it weekly: > Yes I noticed that already when building on different machines trying > to checkout non existent commits. Up to now I thought that happened by > accident. > >> >> https://github.com/schnitzeltony/meta-bbone/blob/master/recipes-kernel/linux/linux-bbone_4.1.bb#L12 >> >> I never got it working 100%, but you should be able to use the git tag's > > As far as I can remember: tags in yocto SRC_URI are causing trouble - > something like a broken or weak network connection causes recipe > parsing to fail - even when building for another machine. > >> >> https://github.com/RobertCNelson/meta-beagleboard-kernel/blob/master/recipes-kernel/linux/linux-beagleboard.org_4.1.bb#L46-L58 > > Wow - so many people doing the same thing - what a waste of resources. > My excuse: We have many different machines to build images for and use > yocto for very long time. Now I was forced to get something to work on > bbb...
I just setup it for an example.. (haven't touched *.bb files in years) >> So it'll break less often.. >> > Is there a more stable source available (probably in near future)? The "4.1" branch get's rebased every thursday... The git tag's "4.1.12-ti-r26" will never be modified after they are pushed.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
