From: "Robert E. Cochran" <yocto@mindchasers.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Lauren Post <Lauren.Post@freescale.com>
Subject: Re: Freescale meta-freescale announcement of new layer
Date: Thu, 10 Mar 2016 22:57:53 -0500 [thread overview]
Message-ID: <56E24241.1040807@mindchasers.com> (raw)
In-Reply-To: <CAP9ODKosbeJWQsL70MpefYBCBk8m2wCMx1poCd9MLwq-4q67gw@mail.gmail.com>
On 03/10/2016 11:27 AM, Otavio Salvador wrote:
> Hello Robert,
>
> On Thu, Mar 10, 2016 at 12:00 PM, Robert E. Cochran
> <yocto@mindchasers.com> wrote:
> ...
>> Thank you for the reply. Where will the meta-freescale layer / repo be
>> located? I would like to see one created on yoctoproject.org with a master
>> branch. Currently the meta-freescale layer on freescale.com doesn't have a
>> master branch.
>>
>> I ask that either you or someone else inside NXP sends out an announcement
>> when this switch officially takes place.
> For now, it is available on Github with a master branch. Patches for
> it are handled using meta-freescale as usual.
Thank you for the reply Otavio. I had been using the GitHub
meta-freescale, but I think it has fallen behind.
As an example, meta-fsl-ppc has commit 2e9b383ccaf4 that patches
qoriq_build_64bit_kernel.bbclass and u-boot-qoriq_2015.01.bb. However,
neither this commit nor the patched-up files can be found in Github's
meta-freescale. Therefore, I went back to using meta-fsl-ppc for
building Power QorIQ images.
Please let me know if you'll be updating meta-freescale to bring it up
to date for ppc QorIQ, or let me know if I'm mistaken about this.
Thanks again,
Bob
>
> In not so distant future we intend to move include the repository on
> Yocto Project git server however it is not yet ready for it.
>
next prev parent reply other threads:[~2016-03-11 3:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 18:38 Freescale meta-freescale announcement of new layer Lauren Post
2015-06-30 1:58 ` Bob Cochran
2015-06-30 2:25 ` Luo Zhenhua
2015-06-30 4:36 ` Weng White
2015-07-08 22:15 ` Bob Cochran
2016-03-09 15:38 ` Robert E. Cochran
2016-03-10 9:54 ` Zhenhua Luo
2016-03-10 15:00 ` Robert E. Cochran
2016-03-10 16:27 ` Otavio Salvador
2016-03-11 3:57 ` Robert E. Cochran [this message]
2016-03-11 4:37 ` Zhenhua Luo
2016-03-11 10:29 ` Otavio Salvador
2016-04-07 7:49 ` Ahsan, Noor
2016-04-07 10:31 ` Otavio Salvador
2016-04-07 13:43 ` Ahsan, Noor
2016-03-16 18:10 ` Robert E. Cochran
2016-03-16 19:56 ` Otavio Salvador
2016-03-17 10:44 ` Zhenhua Luo
2016-03-17 11:43 ` Otavio Salvador
2016-03-18 2:53 ` Zhenhua Luo
2016-03-18 6:34 ` Ting Liu
2016-03-18 12:56 ` Otavio Salvador
2016-03-19 3:00 ` Robert E. 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=56E24241.1040807@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=Lauren.Post@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
/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.