All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [PATCH 08/24] linux-qoriq: unify recipe for QorIQ ARM and QorIQ PPC
Date: Tue, 15 Sep 2015 18:56:21 -0400	[thread overview]
Message-ID: <55F8A215.9080205@mindchasers.com> (raw)
In-Reply-To: <CAP9ODKq9bpumjCZ5m0Xd0qPVtMpZKPtHxd90rFZZ-j0rmORbpQ@mail.gmail.com>

On 09/15/2015 05:50 PM, Otavio Salvador wrote:
> Hello Bob,
>
> On Tue, Sep 15, 2015 at 6:36 PM, Bob Cochran <yocto@mindchasers.com> wrote:
>> On 09/15/2015 01:29 PM, Otavio Salvador wrote:
>>>
>>> On Tue, Sep 15, 2015 at 2:24 PM, Bob Cochran <yocto@mindchasers.com>
>>> wrote:
>>>>
>>>> On 08/12/2015 06:22 AM, Zhenhua Luo wrote:
>>>>>
>>>>>
>>>>> * update linux-qoriq recipe to support both QorIQ ARM and QorIQ PPC
>>>>> * update PREFERRED_PROVIDER_virtual/linux for ls1 target
>>>>> * remove linux-ls1 recipes
>>>>
>>>>
>>>>
>>>> Was this patch accepted, and if so, where did it go?
>>>>
>>>> Is this for the meta-freescale layer on git.freescale.com?  If so, can't
>>>> we
>>>> get the meta-freescale layer moved to git.yoctoproject.org and set up a
>>>> master branch?
>>>
>>>
>>> Yes, please check meta-freescale[1] for the ongoing effort.
>>>
>>> 1. https://github.com/Freescale/meta-freescale
>>>
>>
>> Thanks, but I'm still confused.
>>
>> Based on Lauren Post's email from 6/29 with the subject: "Freescale
>> meta-freescale announcement of new layer",  I thought  meta-freescale was
>> going to be hosted this year at
>>
>> http://git.freescale.com/git/cgit.cgi/yocto/meta-freescale.git/
>>
>> Is this still going to be used?  Someone please explain the purpose for
>> these two repos with the same name.
>
> Yes; this will host the releases done until upstreamed.
>
>> So we have 4 repos for QorIQ: i) meta-freescale on github; meta-freescale on
>> freescale.com;  iii) meta-fsl-ppc on yoctoproject.org; iv) meta-fsl-arm on
>> yoctoproject.org.
>>
>> What happens now to meta-fsl-arm and meta-fsl-ppc? Are these dead for new
>> QorIQ / Layerscape development?
>
> Once the transition is done for meta-freescale, community development
> will focus on meta-freescale but as this is still not clear when all
> merge will be complete and stable I've been keeping meta-fsl-arm
> update and is my main test platform.


Thanks for all the info Otavio.  I'm assuming your attention to 
meta-fsl-arm is primarily for i.MX. Please let me know if you are also 
testing LS1 (e.g., ls1021a-twr) now using meta-fsl-arm.

And I still need to figure out which repo(s) I should use to most 
effectively develop & test with the changes coming for Yocto 1.9.  I 
think I want to work with the github meta-freescale repo, especially 
since I need to build images for both ARM and Power.  Please let me know 
if you disagree and think I'm just asking for headaches due to a lack of 
stability.

Asking another way, are people testing against the github meta-freescale 
repo / layer?

>
>> And is there a mailing list to see when patches get applied to the
>> meta-freescale repo on gitub.com/Freescale, or are you just expecting us to
>> watch it via github?  You have always done such a great job letting us know
>> when patches are applied to meta-fsl-arm.
>
> I have not been sending meta-freescale merges here to avoid flooding
> it. It is still not ready for production use and then I assumed people
> wishing to participate would follow the repository. I can start
> sending it though...
>
>> BTW, the linux-qoriq kernel built with ls1021a_defconfig also failed to
>> build in the same way as it did when being built with the linux-ls1 recipe
>> in meta-fsl-arm.  At this point, I'm guessing there is a tools issue, since
>> I can build the same commit with the SDK1.8 (stable) toolchain and config.
>> I'll dig a little deeper, but please let me know if this is a known issue.
>>
>> |
>> /build/yocto/ls1020/tmp/work-shared/ls1021atwr/kernel-source/arch/arm/kernel/return_address.c:66:7:
>> error: redefinition of 'return_address'
>> |  void *return_address(unsigned int level)
>> |        ^
>
> GCC 5.2 gift! ;-)
>



  reply	other threads:[~2015-09-15 22:56 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 10:22 [PATCH 01/24] ipc: optimize the ipc recipes directories Zhenhua Luo
2015-08-12 10:22 ` [PATCH 02/24] merge-files: define S to fix build warning Zhenhua Luo
2015-08-12 10:22 ` [PATCH 03/24] skmm-ep: move COMPATIBLE_MACHINE to botton line Zhenhua Luo
2015-08-12 10:22 ` [PATCH 04/24] web-sysmon: add RDEPENDS and COMPATIBLE_MACHINE Zhenhua Luo
2015-08-12 10:22 ` [PATCH 05/24] asf: move RDEPENDS and add COMPATIBLE_MACHINE Zhenhua Luo
2015-08-12 10:22 ` [PATCH 06/24] ar: " Zhenhua Luo
2015-08-12 10:22 ` [PATCH 07/24] ceetm: add COMPATIBLE_MACHINE and remove unnecessary DEPENDS Zhenhua Luo
2015-08-12 10:22 ` [PATCH 08/24] linux-qoriq: unify recipe for QorIQ ARM and QorIQ PPC Zhenhua Luo
2015-09-15 17:24   ` Bob Cochran
2015-09-15 17:29     ` Otavio Salvador
2015-09-15 21:36       ` Bob Cochran
2015-09-15 21:50         ` Otavio Salvador
2015-09-15 22:56           ` Bob Cochran [this message]
2015-09-15 23:12             ` Otavio Salvador
2015-08-12 10:22 ` [PATCH 09/24] ls-debug: add recipe Zhenhua Luo
2015-08-12 10:22 ` [PATCH 10/24] lttng-modules: always do 64b build for e6500 targets Zhenhua Luo
2015-08-12 10:22 ` [PATCH 11/24] pkc-host: add COMPATIBLE_MACHINE Zhenhua Luo
2015-08-12 10:22 ` [PATCH 12/24] qoriq-perf: add recipe Zhenhua Luo
2015-08-12 10:22 ` [PATCH 13/24] catter-gather: " Zhenhua Luo
2015-08-12 10:22 ` [PATCH 14/24] skmm-host: add COMPATIBLE_MACHINE Zhenhua Luo
2015-08-12 10:22 ` [PATCH 15/24] o-seville: update COMPATIBLE_MACHINE Zhenhua Luo
2015-08-12 10:22 ` [PATCH 16/24] fsl-tlu: add recipe Zhenhua Luo
2015-08-12 10:22 ` [PATCH 17/24] u-boot-qoriq: remove redundant code Zhenhua Luo
2015-08-12 10:22 ` [PATCH 18/24] reorg the qoriq include files Zhenhua Luo
2015-09-25 22:49   ` Bob Cochran
2015-09-28 11:40     ` Otavio Salvador
2015-08-12 10:22 ` [PATCH 19/24] replace qoriq-base.inc with qoriq-ppc.inc in qoriq tune files Zhenhua Luo
2015-08-12 10:22 ` [PATCH 20/24] update machine conf of e500v2 targets Zhenhua Luo
2015-08-12 10:22 ` [PATCH 21/24] update machine conf of e500mc targets Zhenhua Luo
2015-08-12 10:22 ` [PATCH 22/24] update machine conf of e5500 targets Zhenhua Luo
2015-08-12 10:22 ` [PATCH 23/24] update machine conf of e6500 targets Zhenhua Luo
2015-08-12 10:22 ` [PATCH 24/24] update ls1021atwr machine conf Zhenhua Luo

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=55F8A215.9080205@mindchasers.com \
    --to=yocto@mindchasers.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.