On Wed, 2013-01-16 at 08:46 -0700, Chris Larson wrote: > > On Wed, Jan 16, 2013 at 8:38 AM, Tom Zanussi <tom.zanu...@intel.com> > wrote: > > lttng-ust had PE="1", bump PE to fix upgrade path: > > Technically, that isn't going to "fix" the upgrade path. lttng 1.x > requires kernel patches and isn't compatible with lttng 2.x, as far as > I'm aware. So any machine with lttng 1.x that upgrades to this > wouldn't be a real 'upgrade', it would switch interfaces, and > potentially break compatibility with the kernel running on that > device. At mentor we have bsp layers for 1.x and for 2.x, and both > work. I'm glad we aren't binary package feed based, or we'd be in > serious trouble with this. >
This is for the userspace tracing part, lttng-ust, which AFAIK doesn't require any kernel patches. The other lttng 2.x recipes weren't changed, just moved, so that shouldn't break anything. The lttng 1.x recipes were removed, however, since they do require extensive kernel patches, and at least the recent Yocto kernels didn't have those applied, mainly IIRC because the transition of the lttng project in the meantime to version 2.0 made that difficult. But now that 2.0 is available there doesn't seem to be a good reason to keep 1.x around especially considering the work involved in patching the kernel and the fact that the functionality is mostly replaced by 2.0. Tom _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
