Em ter., 29 de set. de 2020 às 21:38, Jon Mason <[email protected]> escreveu: > > On Tue, Sep 29, 2020 at 5:58 PM Khem Raj <[email protected]> wrote: > > > > Lets not do it. For couple of reasons, > > > > There are BSPs including these include files which are using same > > branch across multiple yocto releases, this will break them > > files under include/<ARCH> are common at arch level, this moved the > > CPU implementation ( cortex* ) under it, seems odd and even more odd > > when you consider arm32 tunes. > > There are so many specific files and I'm about to add even more > (cortex-m). I agree that it should be done uniformly, instead of > doing just the armv8 ones. So, let's drop this patch (not the > series), and I'll address it after the gatesgarth release.
Could those tune files be generated? This could allow a hierarchical structure but easy maintenance. This might be a way to reduce the maintenance burden and avoid breaking old BSPs. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#142922): https://lists.openembedded.org/g/openembedded-core/message/142922 Mute This Topic: https://lists.openembedded.org/mt/77173565/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
