On Wed, Mar 04, 2020 at 05:49:37PM -0800, Khem Raj wrote: > On Wed, Mar 4, 2020 at 5:43 PM Leo Yan <[email protected]> wrote: > > > > Hi all, > > > > On Wed, Mar 04, 2020 at 11:19:37AM -0800, Khem Raj wrote: > > > > > > > > > On 3/4/20 8:05 AM, Scott Murray wrote: > > > > On Wed, 4 Mar 2020, Leo Yan wrote: > > > > > > > > > This recipe is to support OpenCSD, which is an open source > > > > > CoreSight trace decode library and utility. > > > > > > > > Just a thought, this seems like the kind of thing that might make sense > > > > for the new meta-arm layer that Jon has been working up? > > > > Thanks for the suggestion, Scott. > > > > To be honest, I didn't know meta-arm layer before; seems to me it makes > > sense to integrate this recipe into meta-arm rather than > > meta-openembedded. Will explain more for Khem's question. > > > > > it also says x86_64 in COMPATIBLE_HOST, while coresight seems to be arm > > > specific is this not supposed to be so ? > > > > OpenCSD lib is dedicated to be used for Arm CoreSight IP, but it can > > be built both for x86_64's and Arm64's distro. > > > > The main usage case is to enable OpenCSD lib for Arm64 building, and the > > users can decode the trace data with Perf/OpenCSD in the same distro. > > Though I set COMPATIBLE_HOST for x86_64, it would be seldom to do cross > > analysis (e.g. capture trace data in OE/Arm64 and copy the perf data to > > OE/x86_64 for analysis). > > > > For this reason, it's good to maintain this recipe in meta-arm. If no > > objection, I will prepare patch for meta-arm. > > Makes sense in meta-arm
Thanks for confirmation, Khem. And thanks all :) Will do it. Leo -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
