From: Bob Cochran <yocto@mindchasers.com>
To: "zhenhua.luo@freescale.com" <zhenhua.luo@freescale.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Freescale U-Boot User's Guide
Date: Fri, 30 May 2014 08:49:21 -0400 [thread overview]
Message-ID: <53887E51.9080404@mindchasers.com> (raw)
In-Reply-To: <4c8f07f672e040a3a58cab0edef5bf50@BL2PR03MB388.namprd03.prod.outlook.com>
On 05/29/2014 11:50 PM, zhenhua.luo@freescale.com 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=SDKLINUX
> 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.
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).
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.
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?
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
next prev parent reply other threads:[~2014-05-30 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 14:21 Freescale U-Boot User's Guide tom campbell
2014-05-29 16:23 ` Bob Cochran
2014-05-30 3:50 ` zhenhua.luo
2014-05-30 12:49 ` Bob Cochran [this message]
2014-06-03 10:03 ` zhenhua.luo
[not found] ` <53875812.8000702@mindchasers.com>
2014-05-30 14:36 ` tom campbell
2014-05-30 15:35 ` Daiane Angolini
2014-05-30 15:47 ` Bob Cochran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53887E51.9080404@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=meta-freescale@yoctoproject.org \
--cc=zhenhua.luo@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.