All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: FSL Community BSP Meeting - 07/03/2014 - 18:00 GMT
Date: Wed, 02 Jul 2014 09:06:05 -0400	[thread overview]
Message-ID: <53B403BD.3050604@mindchasers.com> (raw)
In-Reply-To: <CAP9ODKoegV_Nfex19EhOUBL8ycgQQztU6dqQhNwBeQKe++uXSA@mail.gmail.com>

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: zhenhua.luo@freescale.com <zhenhua.luo@freescale.com>
To: Bob Cochran <yocto@mindchasers.com>
CC: meta-freescale@yoctoproject.org <meta-freescale@yoctoproject.org>, 
Richard Schmitt <richard.schmitt@freescale.com>, 
White.Weng@freescale.com <White.Weng@freescale.com>

Hi Bob,

Thanks for your suggestion. Please see my inline reply.

> -----Original Message-----
> From: Bob Cochran [mailto:yocto@mindchasers.com]
> Sent: Friday, May 30, 2014 8:49 PM
>
> 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=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 meta-freescale@yoctoproject.org 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






      parent reply	other threads:[~2014-07-02 13:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 13:55 FSL Community BSP Meeting - 07/03/2014 - 18:00 GMT Otavio Salvador
2014-06-30 11:55 ` Otavio Salvador
2014-06-30 12:08   ` Otavio Salvador
2014-06-30 17:12     ` Otavio Salvador
2014-06-30 18:34       ` Daiane.Angolini
2014-07-01  3:54       ` Bob Cochran
2014-07-01 12:26         ` Daiane.Angolini
2014-07-01 21:20         ` Otavio Salvador
2014-07-01  5:59       ` zhenhua.luo
2014-07-01 21:21         ` Otavio Salvador
2014-06-30 18:33   ` Daiane.Angolini
2014-07-02 13:01 ` Bob Cochran
2014-07-02 13:06 ` Bob Cochran [this message]

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=53B403BD.3050604@mindchasers.com \
    --to=yocto@mindchasers.com \
    --cc=meta-freescale@yoctoproject.org \
    /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.