On 14:48-20210304, Denys Dmytriyenko wrote: > BTW, you'd need to ensure updating cryptodev from 1.10 to 1.12 does not > affect > current 5.4-based builds and/or releases. I'm sure it will build fine against > this older kernel (most of Makefile changes), but concerned about any > run-time > regressions (the actual code changes).
Thank you, actually you bring out a very good point here. While I know we can create our own internal private fork of arago for upstream component testing, I am starting to wonder if creating either of: a) meta-ti-mainline that builds on top of meta-ti OR b) meta-arago-mainline on top of meta-arago is a smarter approach - personally, I prefer (a)? While, I don't want to end up creating too many layers, but your point is valid that I should also be careful to not mess with folks using the meta-arago in production environments having to deal with challenges we are trying to flush out by testing the bleeding edge of kernel - and I'd like to make sure TI ecosystem is able to leverage/contribute as well (an internal fork will not be that useful).. Any thoughts? -- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D _______________________________________________ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
