From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 6765EE009D7; Thu, 9 Jul 2015 07:05:38 -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=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.213.181 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-ig0-f181.google.com (mail-ig0-f181.google.com [209.85.213.181]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 3C513E009A7 for ; Thu, 9 Jul 2015 07:05:34 -0700 (PDT) Received: by iggp10 with SMTP id p10so14585927igg.0 for ; Thu, 09 Jul 2015 07:05:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=tfhE4bKgkj93wpWQgy/vu3S0wUzmf+U2LSyMzNVaHcM=; b=mEJ5HyiGqE+LcTe8kPddUB/23T/vbbMVUfUpLLo4OwYjTOlM2z2m2wth2z1plxDYHU mDnI5Kdv4nOflgFx5FHC8vgACPEa08/b9fw8g8KuAmIg5ab45DZANpL/rxQDhePiGEFq dNanDSpD1EzZ6yBgxKAXlOEOu4XZ+kXW+GL9QPzEgPwqlppLp6jUEGqn2Ehq7LkAbav9 g/rCXcLWbaJjzg8TndG9Oxgc5ILAUt4i7HQgtndNuP/5U1zisznfcDnI5vnwE4u+7Tdd q3RWnGyy+/IZg0S/DYmSrMWf2uWOoOWfBrhjuTvU/MPdfxDYvw5L+oYop3u7Y8+9kkN5 PNmg== MIME-Version: 1.0 X-Received: by 10.107.135.200 with SMTP id r69mr27704668ioi.54.1436450734338; Thu, 09 Jul 2015 07:05:34 -0700 (PDT) Sender: otavio.salvador@gmail.com Received: by 10.36.218.7 with HTTP; Thu, 9 Jul 2015 07:05:34 -0700 (PDT) In-Reply-To: References: Date: Thu, 9 Jul 2015 11:05:34 -0300 X-Google-Sender-Auth: iZ6MwKaFNwmzUkB-PZ7nsgzSvV0 Message-ID: From: Otavio Salvador To: Daiane Angolini Cc: "meta-freescale@yoctoproject.org" Subject: Re: SOC_FAMILY Rework 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, 09 Jul 2015 14:05:38 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello Daiane, First, thank you for preparing this e-mail. On Wed, Jul 8, 2015 at 4:42 PM, Daiane Angolini wro= te: > We have today the following SOC_FAMILY tree (for meta-fsl-arm) > > i.MX -> mx3 -> mx31; > i.MX -> mx3 -> mx35; > i.MX -> mx5 -> mx51; > i.MX -> mx5 -> mx53; > i.MX -> mx6 -> mx6dl; > i.MX -> mx6 -> mx6q; > i.MX -> mx6 -> mx6sl; > i.MX -> mx6 -> mx6sx; > i.MX -> mxs -> mx23; > i.MX -> mxs -> mx28; Those are fine, as far as I can see. > Layerscape -> ls102xa; I think this should be: qoriq -> qoriq-arm -> ls102xa > Vybrid -> vf -> vf50; > Vybrid -> vf -> vf60; I would change this for: vybrid > vf50; vybrid > vf60; ... > Some of the points I think is important to consider when choosing a > OVERRIDE tree is the SoC divergence and convergence. In i.MX case, we > have some obvious examples such as GPU type, existence of VPU, and > machine features such as CAN (although imx6 generally supports CAN, > there are some board with connector, and other without it). > > In CAN case, CAN is a SoC feature enabled by the board or not. In WIFI > case, it=E2=80=99s only a board feature. > > So, the points to rule the OVERRIDE is SoC features and board features. Not really. The SoC override is to offer a way to modify the source for ALL boards and also to offer the possibility to cluster binary compatible binaries. This ends affecting the MACHINE_SOCARCH and the SoC subarch we designed to avoid too much rebuilds. Features as CAN or WIFI are machine features and shouldn't be mapped for SoC overrides. > Another important thing to keep in mind is the deepness. How deep > should be the OVERRIDE tree? Two or tree levels? Not a big deal; it depends if it makes usage sense or not. Current set seems good for me. > OVERRIDE should be used to cluster BSP packages and configurations > accordingly with SoC and machine features. Today the meta-fsl-arm BSP > packages can be seen in the table [1]. Most of packages are the same > for all i.MX boards (including kernel and u-boot not included in the > table), but some are very specific to a group of SoCs only (i.e. > fsl-alsa-plugins), and there is the case where a package is for only > one SoC Family, but has big inner segmentation (Vivante) > > [1] https://github.com/Freescale/Documentation/blob/master/release-notes/= source/soc-pkg-optimization.inc Agreed. > The classic example of a crazy OVERRIDE is =E2=80=98mxs=E2=80=99. It was = included in > the past to cluster imx23 and imx28 because they are the only 2 board > using imx-bootlets. Does =E2=80=98mxs=E2=80=99 make sense nowaday? Would = imx6UL be > more related with imx28 than with imx6Q? Would imx6SX be clustered > with vf60? I think UL will end being a mx6ul and it will demand the check of all mx6 uses to see if it is compatible or not. See Lauren's patch regarding the GPU presence in Weston for an example. > Maybe, we can concentrate the OVERRIDE only around GPU and VPU. We > have an extensive segmentation of OVERRIDE for imx6, and a cluster for > all the SoCs without GPU (vf,layerscape?,imx2,imx3,imx6UL, imx7) It does not work. The point of OVERRIDE is to make changes in a set of SoCs and we cannot contaminate other BSP (Intel, TI, Samsung, Qualcomm...) > I only thing this is the right timing to review and rework SOC_FAMILY. > I'm i.MX biased, so I can only say about i.MX, would be glad to hear > feedback from Vybrid and QoirQ. As I said before, the QorIQ should have common and arch specific overrides (I see the former going to be most used) and i.MX global override will be rarely used. --=20 Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750