From: Bob Cochran <yocto@mindchasers.com>
To: "zhenhua.luo@freescale.com" <zhenhua.luo@freescale.com>,
Daiane Angolini <daiane.list@gmail.com>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: Minutes of FSL Community BSP Meeting in 2014-07-03
Date: Mon, 07 Jul 2014 20:08:35 -0400 [thread overview]
Message-ID: <53BB3683.7000508@mindchasers.com> (raw)
In-Reply-To: <0d4b8b8ccca34b40b3e6030343c7ae79@DM2PR03MB399.namprd03.prod.outlook.com>
On 07/06/2014 11:51 PM, zhenhua.luo@freescale.com wrote:
> The document integration in http://freescale.github.io will be in my proposal of ppc layer roadmap, hopefully I can send out the proposal this week.
Thank you Zhenhua,
In addition to the issues that have already been raised, can you also
please include the following in your road map:
i) Whether there will be an SDK1.7 beta trial for community participation
ii) Will SDK1.6 patches be posted to meta-fsl-ppc (perhaps just to
update the SRCREV, so community members can know the code on the FSL
Public GIT has been updated with SDK1.6 patches)
iii) Will both SDK and community releases be supported going forward or
will SDK (eventually) go away?
I had previously volunteered to provide some high-level documentation
for QorIQ developers on the community site. I'll wait until after you
post the road map to see if it's something the community wants or needs
in addition to your road map.
>
> Regarding the testing, currently the full build/function/performance testing are done for SDK, and the build test is conducted for community layer.
>
> I want to give some clarification of the toolchain version, the SDK uses FSL toolchian(e.g. SDK 1.6 uses gcc-4.8.1), the ppc layer in upstream uses toochain(master uses gcc-4.9.x) provided by Yocto, so ther might be some fixes of toolchain in uupstram ppc layer, which is not needed by SDK.
>
>
> Best Regards,
>
> Zhenhua
>
>> -----Original Message-----
>> From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-
>> bounces@yoctoproject.org] On Behalf Of Daiane Angolini
>> Sent: Saturday, July 05, 2014 2:15 AM
>> To: Bob Cochran
>> Cc: meta-freescale@yoctoproject.org; Otavio Salvador
>> Subject: Re: [meta-freescale] Minutes of FSL Community BSP Meeting in
>> 2014-07-03
>>
>> On Fri, Jul 4, 2014 at 2:52 PM, Bob Cochran <yocto@mindchasers.com> wrote:
>>> On 07/04/2014 01:35 PM, Daiane Angolini wrote:
>>>>
>>>> I agree with all your email and have no useful comment, however I
>>>> want to focus on one thing:
>>>>
>>>>
>>>>>
>>>>> There appears to be two landing pages for Freescale community bsp
>>>>> work
>>>>> product:
>>>>>
>>>>> 1) "Freescale Yocto Project main page":
>>>>> https://community.freescale.com/docs/DOC-1616
>>>>>
>>>>> 2) "FSL Community BSP": http://freescale.github.io
>>>>>
>>>>>
>>>>
>>>>
>>>> The github.io is the FSL Community BSP landing page. And today there
>>>> is no ppc reference because we are working on integration (targeting
>>>> 1.7). It means that, today, meta-fsl-pcc are not part of FSL
>>>> Community BSP
>>>>
>>>> (and I really think that makes complete sense to include it, we only
>>>> need to be careful)
>>>>
>>>> However, the DOC-1616 is a document from imx.community. And I would
>>>> like to understand why you pointed to this doc.
>>>
>>>
>>>
>>> I did so because I was confused, and I haven't been carefully reading
>>> the community emails because I'm developing with QorIQ and didn't
>>> think the work applied to me (until recently).
>>>
>>> I assume others will share in my confusion because search engines will
>>> lead them to the same page, which is titled "Freescale Yocto Project
>> main page"
>>> and has a banner above it that states Freescale Community.
>>
>> hummmm!!!
>> I got it now!
>>
>> ;-) thanks
>>
>> Daiane
>>>
>>> Thank you for the clarification.
>>>
>>>
>>>
>>>
>>>
>>>>
>>>> As you have pointed it, I understand that, being part of
>>>> imx.community, or any other sub-community does not make any
>>>> difference.
>>>>
>>>> I made most of the imx.community doc refers to yocto, and I´m feeling
>>>> that it´s time to review all those docs. Maybe, I need to use this
>>>> DOC-1616 as a real landing page to FSL Community BSP for any
>>>> Freescale chip.
>>>>
>>>>
>>>> Daiane
>>>>
>>>
>> --
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
next prev parent reply other threads:[~2014-07-08 0:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 16:38 Minutes of FSL Community BSP Meeting in 2014-07-03 Otavio Salvador
2014-07-03 16:49 ` Trevor Woerner
2014-07-04 13:01 ` Daiane Angolini
2014-07-04 15:18 ` Bob Cochran
2014-07-04 16:17 ` Otavio Salvador
2014-07-04 17:21 ` Bob Cochran
2014-07-04 17:35 ` Daiane Angolini
2014-07-04 17:52 ` Bob Cochran
2014-07-04 18:15 ` Daiane Angolini
2014-07-07 3:51 ` zhenhua.luo
2014-07-08 0:08 ` Bob Cochran [this message]
2014-07-04 16:13 ` Otavio Salvador
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=53BB3683.7000508@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=daiane.list@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
--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.