> -----Original Message----- > From: [email protected] [mailto:meta-freescale- > [email protected]] On Behalf Of Bob Cochran > Sent: Wednesday, July 23, 2014 9:42 PM > > On 07/23/2014 03:16 AM, [email protected] wrote: > > Hi Daiane, > > > > Thanks for your comments. > > > > The details on how/what-to-do needs more discussion, especially for > documentation update, arm and ppc layer collaborate, testing, etc. Some > works in the item lists have been done, some works are being done, some > works are to be done. > > > > Regarding the name, I don't know what name is good, maybe FSL Community > Yocto Embedded Linux, any better idea? > > > How will QorIQ ARM specific (meta) data be organized / labeled? [Luo Zhenhua-B19537] All targets in fsl-ppc layer are QorIQ PPC machines, the targets in fsl-arm layer with "ls" prefix is QorIQ ARM, the others are i.mx.
> Is it going in meta-fsl-arm? [Luo Zhenhua-B19537] Yes. > Aren't there 3 different sets of data: fsl-imx-arm, fsl-qoriq-arm, and > fsl-qori-ppc? [Luo Zhenhua-B19537] Correct, maybe we can enhance the setup-environment script to category those targets and print them in the console when the script is executed. Best Regards, Zhenhua > Sorry if this has already been resolved, and I just didn't catch it. > > > > > > > > Best Regards, > > > > Zhenhua > > > > > >> -----Original Message----- > >> From: Angolini Daiane-B19406 > >> Sent: Wednesday, July 16, 2014 8:20 PM > >> To: Luo Zhenhua-B19537; [email protected] > >> Subject: RE: [meta-freescale] [RFC] The proposal of FSL QorIQ SDK > >> upstream > >> > >> > >> > >>> -----Original Message----- > >>> From: [email protected] > >>> [mailto:meta-freescale- [email protected]] On Behalf Of > >>> [email protected] > >>> Sent: Wednesday, July 16, 2014 3:01 AM > >>> To: [email protected] > >>> Subject: [meta-freescale] [RFC] The proposal of FSL QorIQ SDK > >>> upstream > >>> > >>> Hi all, > >>> > >>> Following is the proposal for FSL QorIQ SDK upstream, comment is > >> welcome. > >>> > >>> Upstream Plan > >>> • SDK 1.6 recipe upstream (Done) > >>> − http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/ > >>> • Optimize the recipes in meta-fsl-ppc (Done) • Resolve the PPC and > >>> ARM layer compatibility issue (31-Jul) > >>> − Replace fslmachine with qoriq for override implementation > >>> − Compatibility issue in bbappends • LS1 Alpha release upstream > >>> (15-Aug) > >>> − http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/ > >>> • Update and debug the initial script to support QorIQ targets (29- > Aug) > >>> − https://github.com/Freescale/fsl-community-bsp-base > >>> • Update repo config to facilitate the SDK fetch (29-Aug) > >>> − https://github.com/Freescale/fsl-community-bsp-platform > >>> • Add demo image in meta-fsl-demo (29-Aug) > >>> − https://github.com/Freescale/meta-fsl-demos > >>> • Update the documentation (10-Sep) > >>> − https://github.com/Freescale/Freescale.github.io > >>> − https://github.com/Freescale/Documentation > >>> • Regression test for FSL community BSP periodically (19-Sep) > >>> NOTE: the time and interval depends on the logistics readiness • > >>> Set up a public image mirror for community users' testing • LS1 > >>> August release > >>> upstream(30-Sep) • SDK 1.7 upstream (Jan-2015) • LS2 upstream (TBD) > >>> > >>> Regression Testing > >>> • Leverage repo(manifest project) to fetch code. > >>> • Weekly build for QorIQ PPC and LS ARM targets, the build is based > >>> on community layers, > >>> the issues of Yocto Community BSP and FSL SDK should be separated > >>> due to differentiation. > >>> • Periodically sanity test for typical boards that are randomly > >>> selected according to board resource availability. > >>> > >>> Infrastructure > >>> • Bug management for community SDK > >>> https://bugzilla.yoctoproject.org/ > >>> • Mailing list > >>> [email protected] > >>> FSL community SDK discussion, patch submit and review > >>> > >>> More to do > >>> • Setup public bug management system for FSL SDKs. > >>> • Push all modules to public git repository to ensure FSL community > >>> BSP sync with FSL released SDK. > >>> • Setup an external mailing list for external git repository for FSL > >>> SDK discussion, patch submission, patch review. > >>> • Setup an patch management tool(patchwork or gerrit) to manage > >>> patches from community. > >>> • Enhance the commit message in patch to facilitate the patch search > >>> for specific issue. > >>> > >> > >> I like your list, and I don´t remember (now) anything else to add. > >> I assume it´s a high level list, and details on how-to and what-to do > >> is for future discussion. > >> > >> However, your email highlighted a critical issue we (ARM+PPC) have. > >> You used 4 different names to call "the community source code". > >> > >> BSP - board support package [1] > >> " is a collection of information that defines how to support a > >> particular hardware device, set of devices, or hardware platform." > >> > >> It means that the current "FSL Community BSP" name is wrong. The > >> resultant code provides more that "info to define how to support HW". > >> To be very simplistic, in a BSP there is no image recipe. > >> > >> SDK - Software Development Kit [2] > >> > >> Being defined (in YP) as toolchain+sysroot+setup-env script. > >> > >> I assume meta-fsl-ppc does not provide *only* SDK. I assume it > >> provides both BSP and the tools to allow user to create the SDK. > >> > >> So, call meta-fsl-arm/extra+meta-fsl-pcc+meta-fsl- > >> demos+Documentation+fsl-community-bsp-base+fsl-community-bsp-platform > >> only as "FSL Community BSP" is not complete/right/cool. > >> > >> > >> Historically, we started to build the "FSL Community BSP" identity in > >> past one year. At first, I used to thought about it as "meta-fsl-arm" > >> (once upon a time, we cloned one by one the needed repos). Then > >> "meta- fsl-arm" became incomplete, and we created the super-set of > >> projects that, together, would form a bigger and stronger project, > >> and we decided to call it "FSL Community BSP" > >> > >> I think we can use the ARM+PCC technical union effort to start > >> building our identity as community. > >> > >> [1] > >> http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html#bsp > >> [2] http://www.yoctoproject.org/docs/current/ref-manual/ref- > >> manual.html#sdk-generation-dev-environment > >> > >> > >> Daiane > > -- > _______________________________________________ > meta-freescale mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/meta-freescale -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
