From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id DA447E00A6C; Thu, 18 Jun 2015 09:47:35 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [157.56.110.107 listed in list.dnswl.org] * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bn0107.outbound.protection.outlook.com [157.56.110.107]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 29709E00A31 for ; Thu, 18 Jun 2015 09:47:30 -0700 (PDT) Received: from BN3PR0301CA0018.namprd03.prod.outlook.com (10.160.180.156) by CH1PR03MB611.namprd03.prod.outlook.com (10.255.156.167) with Microsoft SMTP Server (TLS) id 15.1.195.15; Thu, 18 Jun 2015 16:47:28 +0000 Received: from BN1AFFO11FD008.protection.gbl (2a01:111:f400:7c10::113) by BN3PR0301CA0018.outlook.office365.com (2a01:111:e400:4000::28) with Microsoft SMTP Server (TLS) id 15.1.195.15 via Frontend Transport; Thu, 18 Jun 2015 16:47:28 +0000 Authentication-Results: spf=fail (sender IP is 192.88.158.2) smtp.mailfrom=freescale.com; yoctoproject.org; dkim=none (message not signed) header.d=none; Received-SPF: Fail (protection.outlook.com: domain of freescale.com does not designate 192.88.158.2 as permitted sender) receiver=protection.outlook.com; client-ip=192.88.158.2; helo=az84smr01.freescale.net; Received: from az84smr01.freescale.net (192.88.158.2) by BN1AFFO11FD008.mail.protection.outlook.com (10.58.52.68) with Microsoft SMTP Server (TLS) id 15.1.190.9 via Frontend Transport; Thu, 18 Jun 2015 16:47:27 +0000 Received: from [127.0.0.1] (RA43240-03.am.freescale.net [10.81.17.26]) by az84smr01.freescale.net (8.14.3/8.14.0) with ESMTP id t5IGlP7n029660 for ; Thu, 18 Jun 2015 09:47:25 -0700 Message-ID: <5582F61D.2040808@freescale.com> Date: Thu, 18 Jun 2015 11:47:25 -0500 From: Ann Thornton User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: References: <1434564146-11377-1-git-send-email-otavio@ossystems.com.br> <1434564146-11377-3-git-send-email-otavio@ossystems.com.br> <5581BC50.5020504@mail.bg> <5581BE95.9060009@mail.bg> <5581C98C.8060802@mail.bg> <5582E4A1.5070108@mail.bg> In-Reply-To: <5582E4A1.5070108@mail.bg> X-EOPAttributedMessage: 0 X-Microsoft-Exchange-Diagnostics: 1; BN1AFFO11FD008; 1:hRTVdJsQOgoNvl1ynINtX2kCUPWKE8mDFhRBBT9NcYD8bS5bhvhkKSV0S5b3DFtpwL/E7JFT8ioUuAHtalozkMHYIyXucNtTdFg16gUGoWHWPIsA9fDXtgrnFG7pSQc7khdGM8vFTJV9JfUV9gNtYfhdqj9y/eu/vDHQ9b/oy+VhKnJ15tgAhFI3EJi4tanXDfZHMAk/NhC6EFf5cLpt5XDkdhdoAt7BVUcfHDvcsXC2WE+CjVNf4RBVkzEJ2FyISKbMgRRNLzQEPfCJ1RX83/RimSXW0sZ0ovhnj+D2N/k= X-Forefront-Antispam-Report: CIP:192.88.158.2; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(2980300002)(339900001)(189002)(199003)(479174004)(24454002)(252514010)(52604005)(51704005)(377454003)(51914003)(5001960100002)(110136002)(107886002)(4001350100001)(65816999)(33656002)(46102003)(65956001)(19580395003)(80316001)(19580405001)(86362001)(36756003)(512944002)(6806004)(65806001)(189998001)(54356999)(76176999)(50986999)(87266999)(87936001)(64126003)(104016003)(450100001)(77156002)(62966003)(2351001)(556974002)(77096005)(106466001)(93886004)(92566002)(85426001)(105606002)(84326002)(230783001)(120886001)(59896002)(83506001)(2950100001)(572464001); DIR:OUT; SFP:1102; SCL:1; SRVR:CH1PR03MB611; H:az84smr01.freescale.net; FPR:; SPF:Fail; MLV:ovrnspm; MX:1; A:1; PTR:InfoDomainNonexistent; LANG:en; X-Microsoft-Exchange-Diagnostics: 1; CH1PR03MB611; 2:ZtM30ImAAdzFp6bedGOu++bbSYfZm1zPSrZ9cMzs07d41lzOW2b0L4ghzJN/ILh8; 3:Nb383t4/hQKdTL/k8rrEXdIY46M2b6b/CgBLHh3lFZtjxNWB/o3oVOpkFQME+XfGzHRtPtyOy/BY6ikz3x1onl5w2qWhmSaAUCisQGkY0DIVU13RTCHjsuZ0FOpx1b/W/Hby6d8d46oCihhdQCViXGwuBQCjC59vBqXg0JFlgVUQ2B/+Hc7n7NZzZNHg3mic8RLNh7hcMNrM5ukvl/15lcRf/m3BB7eLxhB/0yFBM4s=; 20:RSzUmKqbwoguDcCJ/hn/OkY+n6B88fwOgBcNUhPZKjPPh+HyreMq9m3Top+BXwuE+B4hZFkndZiCyO4lCYHNXsOzLXxxE39zvO4yNgFbmYnR6sqcLyqw7n3OkQXVywZX/WfetKMYYKXtjNAQb/iXUHPiFuubQZ8cH/ZDoVUX+XIYHyFzX5uP1fC/2X8M//MJtuFc2o51yd1gVh5WwqyFqCjDbnP4H6a8w0o5UOOnVjy8QNkKv+gxcHw0pUhP9LjUkpQAQDW/AWz7pyKVSujBHEdkXtLl1VOSfk65KzR8g7mJxcs203M2qWEdOzHZlHkPiJw7JG7gK6iKhkGZWYYrkOqA2RRKTYeUWZs8F5Iq74w=; 4:LYBCHnboIrslFBHwdUSjWh7dJNSFB2XNQ1jAIZF41nu27H9L2aa1e88yAb0z9Nx0WB7v5985HRxHC2VUQyzDZeWYVDfEoNIyAot0jQsjs869YTFbqqZQHG4k0OE0BeK7szfdcPmozDyCIUcMMQwM/kCddrf4A2CL7bfyakMsbbpLq6s6GC/8wH/sxYYKRySQRp/ANOiW99+Cp+LK3jbLUF3S12ZsL5YdM/xEVym56mBdB9GNEuup9BRMH4KWYy7EYIY+lTWt4NB37OlfnGwcl49x9l/xIbmFkR+JiqO6zqA= X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CH1PR03MB611; X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:CH1PR03MB611; BCL:0; PCL:0; RULEID:; SRVR:CH1PR03MB611; X-Forefront-PRVS: 0611A21987 X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; CH1PR03MB611; 23:Bjjfls7CfZOO7P8DprBeaWgR2kYvlSjKK4GNQ3ezLd?= =?us-ascii?Q?8j7oQJuof7DkAMwMih5o4wEcvnvHp5fCqpzHyOEt8ARIaX3r1Yuur+7x7Xt+?= =?us-ascii?Q?UlvCG2copbe7TG8KgzGVbfm2iW+Bv2SEKP0lzFoXv+BWOO81b64itZ0eVXS+?= =?us-ascii?Q?f4mYmU9iUEonZ1EL22mv1PfAPqcKNNZPz9Adtd65smVmVttyff/P/16eu4kb?= =?us-ascii?Q?WrEoH+qym1BqwO4lOjSGYFxrsB9XS25oXNCTG5hAln2ZlqFqB1vMroQ21qsR?= =?us-ascii?Q?xYV0/YMrIqpy/5iba77E719lt2XpOd/HzO8CsosprFyERpjil3dgDX6LFaBK?= =?us-ascii?Q?mt6k/1UdKEi2xQQ7kBmL1Ccb2VSeRVAW6hRx7NOL4v7mec5rGj8vb8rBTvAO?= =?us-ascii?Q?Wsc+sDzsr6Z7Q+t/C9l6MA26EJTqyFAiuEPI8bVe60k2Qt12uAKhRz935HBk?= =?us-ascii?Q?uhhibkv37SyiFjaNacrNELul/eBCZb+NrtjX6GiKMzbA5R41yz7r+VGeigdS?= =?us-ascii?Q?7d56L3maMxHpYflXdHoqESvZWvM5enGeX7LEJ12So5REOMVtHUkzwfk+HUx5?= =?us-ascii?Q?zG+LmJRtcHy9UxtRp00gxHZYA6ziyJWvQUjzrfMwy51SU/nNVCS1iu6/B32w?= =?us-ascii?Q?y1AO0/IS7aupVeHbehbbLhfgTbi3wep1rOFAM+PGbcKQf9nu7LVE9CO6mr6E?= =?us-ascii?Q?UIKWDsuCW+uyKuLwvbJbC1vVBYfTKt+TmbnTsCagFfyHFIouuVhAdp6UHRIE?= =?us-ascii?Q?VyURZrvu4QKrx6KcIMx2itw8BlSHc+o/iMC+N0QisfdzvVOgkHd9bEsM/ZfY?= =?us-ascii?Q?oZLswVoMgBtPByGBKqnMDqDPpSXnjULQvmfl+V5l97ytL0sJ3eDqhUS1ZGqg?= =?us-ascii?Q?JGUPsS6xVdTARC4E8znD7VCPbUHsuoZ1h6AWxLEZKGssRN0+QKsB6uDeO6K+?= =?us-ascii?Q?idU+ClYsmw6kqSU6U1nwLDJFgM/dFenloVcla4l0VazHx8HpxZAzIIJX/hPx?= =?us-ascii?Q?O26yB4MUv0aOsK3b/HwWF5e5Asr4Uj1aJEykFW6mbnKBgHBOqtRZToT44RHr?= =?us-ascii?Q?I2bnX5R7pS7QQUDrnqJEoVbu6qY8naf0RsYzi4Ry0QqHhwPOYuVwklMtGJ2Y?= =?us-ascii?Q?okUJBy14zpDJxqbKKbB9KwMrX2wgW0NqRFjQVnm1Msek38kcmTaaxGZqbL5K?= =?us-ascii?Q?d4yOnehiN3jC3tpiacd+J7JaqKivA8Uwc2IlNbhxrIB0yzfHxfuZSAaKB88m?= =?us-ascii?Q?p1QAPSAoYDJxwaM9ptkiZX/O0+qj0NUzfQxwHNxuhid/v95okvE0BV5gKyWE?= =?us-ascii?Q?rU2mHeaCToqbRmMt+BXZK68JAWIRy+2MnddZY4OIgN?= X-Microsoft-Exchange-Diagnostics: 1; CH1PR03MB611; 5:7PsCfW3PPkfJzZzQYVNK0pAzBdenYvVEmbNcjuXLoMR345wHb4d/eo02n3KXZBN5Zw23SUotvgK+EmPvXLnqM/gEB0bJuK58ITNkcUBgq/uNB1jojH7p4L9u77DLEaaZN3GA8h3bs3xxpi8Os/9ocA==; 24:iJnftd/gQKNwMdZWVgtB1yFFEU5gYH4Ji0HbpOeei87sYtMfL45Q9UfLY/T9P5JhARQ6RfEluYgoHHIVl4FfcrFLmVBorEHC5Mdif67GjWI=; 20:M+ZpxPLB2PvRJV+m/dw+I5bjyr0NYwn5X6JnnumIy4zr0EKHHXOCeVpZ6mvMhN4B9/KXXpOBb+bfbwQ9loaOcw== X-OriginatorOrg: freescale.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 18 Jun 2015 16:47:27.0760 (UTC) X-MS-Exchange-CrossTenant-Id: 710a03f5-10f6-4d38-9ff4-a80b81da590d X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=710a03f5-10f6-4d38-9ff4-a80b81da590d; Ip=[192.88.158.2]; Helo=[az84smr01.freescale.net] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH1PR03MB611 Subject: Re: [meta-fsl-arm][PATCH 3/4] linux-fslc-mx6 (3.14-1.0.x): Add recipe X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jun 2015 16:47:35 -0000 Content-Type: multipart/alternative; boundary="------------070803010305090607040101" --------------070803010305090607040101 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Thanks for the kind words, Nikolay. We are trying to respond more quickly. Ann Thornton On 6/18/2015 10:32 AM, Nikolay Dimitrov wrote: > Hi Daiane, Otavio, > > On 06/18/2015 04:58 PM, Otavio Salvador wrote: >> On Thu, Jun 18, 2015 at 10:40 AM, Daiane Angolini >> wrote: >>> On Wed, Jun 17, 2015 at 4:45 PM, Otavio Salvador >>> wrote: >>>> On Wed, Jun 17, 2015 at 4:25 PM, Nikolay Dimitrov >>>> wrote: >>>>> So, in terms of functionality this kernel sits somewhere >>>>> between mainline and FSL releases, is that correct? >>>> >>>> Yes; it is FSL release + stable releases + vendor/community >>>> fixes >>> >>> I've been thinking about this issue. And this provider (for imx6 >>> only) may make sense to have "fslc" sufix, exactly because it has >>> freescale + community patches >>> >>> However, the other (currently linux-fslc) does not make sense. >>> Maybe linux-cmt makes more sense today. >>> >>> I remember one of the arguments to not use only "linux" and use a >>> prefix was that it's not a pure mainline provider (it clones from >>> github) and because it leave the "linux" only for internal kernels >>> >>> Any other suggestion? >> >> I think we need to consider some things here: >> >> linux-fslc is a kernel tree we maintain u-boot-fslc is a u-boot tree >> we maintain >> >> both have same goals and the idea is to provide a place to share >> patches and backports. >> >> The motivation to make the 3.14 is because FSL is not taking the >> fixes and security updates from stable, so a place to merge those >> seems to be beneficial. I don't want a plethora of names as it makes >> harder for people to contribute and share work so I propose two >> solutions: >> >> linux-fslc_4.0.bb linux-fslc-mx6_3.14-1.0.x.bb >> >> or >> >> linux-fslc_4.0.bb linux-fslc_3.14-1.0.x-mx6.bb >> >> Both works. > > Thanks for sharing your ideas, this helps me to understand somewhat > better the motivation behind creating these linux kernel providers. > > So, my comments are not to oppose any changes/improvements at all, but > just to add a more global perspective on where the Yocto kernel > providers fit in the long chain between mainline and the OEM: > > 1. linux-mainline > ----------------- > Good generic imx6 support, no support for ASRC, VPU. Regarding the GPU - > Jon Nettleton is working on the etnaviv code, so probably some day we'll > have a fully open GPU support there. Until then - no GPU support in > mainline, only basic FB on hdmi/lvds (parallel lcd probably also works, > but I haven't tested it). Supported by the kernel developers. > > 2. linux-fslc > ------------- > Almost mainline. Here we collect patches that either will take very long > to be applied in mainline, or are inappropriate for mainline (but still > useful for Yocto users). As stability and features should be as good > mainline, if not slightly better due to custom fixes for Yocto. > Supported by Yocto community. > > 3. linux-as-proposed-by-otavio > ------------------------------ > Man-in-the middle. Forward-ported FSL code, back-ported important > patches from mainline. Probably something like "linux-imx-next". Who > will support this code? > > 4. linux-imx > ------------ > THE FSL kernel. Freescale's team is doing a great job, and there are > more or less regular releases with good overall quality. It's quite > normal/expected that this kernel version will always lag behind > mainline. One thing which bothers me is that there's no way for the > community to interact with the FSL BSP team, which means no transparent > way to submit/track/resolve issues. This same role is currently being > played by the Yocto community due to several individuals who have > internal access to the FSL BSP team and can help pushing through issues. > Supported by Yocto community (including FSL engineers). > > > So, even if I like the idea that #3 will have newer code than #4, the > main question is who will support it (support means both development and > validation)? > > Regards, > Nikolay -- Ann Thornton /Microcontrollers Software and Applications Freescale Semiconductors email: Ann.Thornton@freescale.com/ --------------070803010305090607040101 Content-Type: text/html; charset="windows-1252" Content-Transfer-Encoding: 8bit

Thanks for the kind words, Nikolay.  We are trying to respond more quickly.

Ann Thornton

On 6/18/2015 10:32 AM, Nikolay Dimitrov wrote:
Hi Daiane, Otavio,

On 06/18/2015 04:58 PM, Otavio Salvador wrote:
On Thu, Jun 18, 2015 at 10:40 AM, Daiane Angolini
<daiane.list@gmail.com> wrote:
On Wed, Jun 17, 2015 at 4:45 PM, Otavio Salvador
<otavio@ossystems.com.br> wrote:
On Wed, Jun 17, 2015 at 4:25 PM, Nikolay Dimitrov
<picmaster@mail.bg> wrote:
So, in terms of functionality this kernel sits somewhere
between mainline and FSL releases, is that correct?

Yes; it is FSL release + stable releases + vendor/community
fixes

I've been thinking about this issue. And this provider (for imx6
only) may make sense to have "fslc" sufix, exactly because it has
freescale + community patches

However, the other (currently linux-fslc) does not make sense.
Maybe linux-cmt makes more sense today.

I remember one of the arguments to not use only "linux" and use a
prefix was that it's not a pure mainline provider (it clones from
github) and because it leave the "linux" only for internal kernels

Any other suggestion?

I think we need to consider some things here:

linux-fslc is a kernel tree we maintain u-boot-fslc is a u-boot tree
we maintain

both have same goals and the idea is to provide a place to share
patches and backports.

The motivation to make the 3.14 is because FSL is not taking the
fixes and security updates from stable, so a place to merge those
seems to be beneficial. I don't want a plethora of names as it makes
harder for people to contribute and share work so I propose two
solutions:

linux-fslc_4.0.bb linux-fslc-mx6_3.14-1.0.x.bb

or

linux-fslc_4.0.bb linux-fslc_3.14-1.0.x-mx6.bb

Both works.

Thanks for sharing your ideas, this helps me to understand somewhat
better the motivation behind creating these linux kernel providers.

So, my comments are not to oppose any changes/improvements at all, but
just to add a more global perspective on where the Yocto kernel
providers fit in the long chain between mainline and the OEM:

1. linux-mainline
-----------------
Good generic imx6 support, no support for ASRC, VPU. Regarding the GPU -
Jon Nettleton is working on the etnaviv code, so probably some day we'll
have a fully open GPU support there. Until then - no GPU support in
mainline, only basic FB on hdmi/lvds (parallel lcd probably also works,
but I haven't tested it). Supported by the kernel developers.

2. linux-fslc
-------------
Almost mainline. Here we collect patches that either will take very long
to be applied in mainline, or are inappropriate for mainline (but still
useful for Yocto users). As stability and features should be as good
mainline, if not slightly better due to custom fixes for Yocto.
Supported by Yocto community.

3. linux-as-proposed-by-otavio
------------------------------
Man-in-the middle. Forward-ported FSL code, back-ported important
patches from mainline. Probably something like "linux-imx-next". Who
will support this code?

4. linux-imx
------------
THE FSL kernel. Freescale's team is doing a great job, and there are
more or less regular releases with good overall quality. It's quite
normal/expected that this kernel version will always lag behind
mainline. One thing which bothers me is that there's no way for the
community to interact with the FSL BSP team, which means no transparent
way to submit/track/resolve issues. This same role is currently being
played by the Yocto community due to several individuals who have
internal access to the FSL BSP team and can help pushing through issues.
Supported by Yocto community (including FSL engineers).


So, even if I like the idea that #3 will have newer code than #4, the
main question is who will support it (support means both development and
validation)?

Regards,
Nikolay


--
Ann Thornton

Microcontrollers Software and Applications
Freescale Semiconductors
email: Ann.Thornton@freescale.com
--------------070803010305090607040101--