On 06/27/2014 09:55 AM, Otavio Salvador wrote:
meta-fsl-ppc
* Release Notes
* Technical implications
This is a 2nd forwarded email that documents some of the issues I
previously raised regarding meta-fsl-ppc. I hope these issues can be
included for discussion in our FSL Community BSP meetings.
Thank you,
Bob
-------- Original Message --------
Subject: RE: [meta-freescale] Freescale U-Boot User's Guide
Date: Tue, 3 Jun 2014 10:03:48 +0000
From: [email protected] <[email protected]>
To: Bob Cochran <[email protected]>
CC: [email protected] <[email protected]>,
Richard Schmitt <[email protected]>,
[email protected] <[email protected]>
Hi Bob,
Thanks for your suggestion. Please see my inline reply.
-----Original Message-----
From: Bob Cochran [mailto:[email protected]]
Sent: Friday, May 30, 2014 8:49 PM
On 05/29/2014 11:50 PM, [email protected] wrote:
> Hi Bob,
>
> For QorIQ PPC SDK, following is the mirror info.
> SDK
> ISOs:http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=SD
> KLINUX SDK public
> source/patch:http://git.freescale.com/git/cgit.cgi/ppc/sdk/
> Yocto:http://git.freescale.com/git/cgit.cgi/ppc/sdk/
> orhttp://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/
> SDK documentations:http://www.freescale.com/infocenter -> Software and
Tools Information Center -> QorIQ SDK Documentation
> or source ISO
Thank you for the reply Zhenhua.
Here's my fundamental problem (as I see it):
Let's say we're getting ready to release a product using the FSL SDK 1.5
for QorIQ. I assume there are many customers to the 1.5 SDK and bugs are
being found & reported on a regular basis. Some of these bugs will not
be seen here during development but eventually impact our product in the
field.
Freescale has a private service request (SR) system for supporting SDK
bug requests and also offers paid premium SDK support.
How can I use the systems in place (e.g., FSL public git and
Yoctoproject.org) to learn which SDK bugs have been reported and patched
and then grab the appropriate patches to create an incremental build?
It's not sufficient to only have a system in place to help resolve the
bugs we find ourselves.
[Luo Zhenhua-B19537] To support above requirement, the bug related info
needs to be included in the commit message for better patch finding, we
will consider the enhancement in future. In current SDK. The resolved
critical bugs can be got from SDK documentation(SDK Overview -> Known
Issues).
As far as I know, the yocto repos never contain enough data to build the
FSL SDK (some of the data on the SDK is kept private), and the FSL
public git seems to be significantly behind (at least meta-fsl-ppc).
[Luo Zhenhua-B19537] Currently the recipes update for meta-fsl-ppc in
public git(git.freescale.com and git.yoctoproject.org) are done when the
QorIQ SDK is formally released(two major releases per year). We are
working on the process of more frequent release for QorIQ SDK, and more
and more packages will be published in public git.
It seems to me that Freescale should have a customer visible bug
reporting system in place for their SDK and maintain a complete,
up-to-date SDK branch with patches in response to the bugs reported &
closed out.
[Luo Zhenhua-B19537] Good suggestion.
If IP protection is the reason to not do it, then deploy it on an
extranet that is password protected.
Lastly, is there a mail list for the FSL public git?
[Luo Zhenhua-B19537] There is no dedicated mail list for FSL public git.
Currently [email protected] is used by community for
discussion of FSL SDK. FSL community
website(https://community.freescale.com/) can also be leveraged to raise
issue and question.
Best Regards,
Zhenhua
Thank you,
Bob
>
> We are working on the integration of meta-fsl-ppc layer into FSL Yocto
community BSP(http://freescale.github.io/), hopefully it can be done in
1.7 release.
>
>
> Best Regards,
>
> Zhenhua
--
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale
