From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe001.messaging.microsoft.com [216.32.180.184]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 75986E015F8 for ; Wed, 2 Oct 2013 07:43:05 -0700 (PDT) Received: from mail20-co1-R.bigfish.com (10.243.78.227) by CO1EHSOBE034.bigfish.com (10.243.66.99) with Microsoft SMTP Server id 14.1.225.22; Wed, 2 Oct 2013 14:43:04 +0000 Received: from mail20-co1 (localhost [127.0.0.1]) by mail20-co1-R.bigfish.com (Postfix) with ESMTP id 29347401AC; Wed, 2 Oct 2013 14:43:04 +0000 (UTC) X-Forefront-Antispam-Report: CIP:70.37.183.190; KIP:(null); UIP:(null); IPV:NLI; H:mail.freescale.net; RD:none; EFVD:NLI X-SpamScore: -14 X-BigFish: VS-14(zzbb2dI98dI9371I1432I1451L444fM1521Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de097h186068h8275dhz2dh2a8h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19b4h19c3h1ad9h1b0ah1b2fh1fb3h1d0ch1d2eh1d3fh1dfeh1dffh1f5fh1fe8h1ff5h209eh1155h) Received: from mail20-co1 (localhost.localdomain [127.0.0.1]) by mail20-co1 (MessageSwitch) id 138072498290666_1102; Wed, 2 Oct 2013 14:43:02 +0000 (UTC) Received: from CO1EHSMHS012.bigfish.com (unknown [10.243.78.254]) by mail20-co1.bigfish.com (Postfix) with ESMTP id 091928C006D; Wed, 2 Oct 2013 14:43:02 +0000 (UTC) Received: from mail.freescale.net (70.37.183.190) by CO1EHSMHS012.bigfish.com (10.243.66.22) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 2 Oct 2013 14:43:01 +0000 Received: from tx30smr01.am.freescale.net (10.81.153.31) by 039-SN1MMR1-004.039d.mgd.msft.net (10.84.1.14) with Microsoft SMTP Server (TLS) id 14.3.158.2; Wed, 2 Oct 2013 14:43:00 +0000 Received: from [10.29.244.63] ([10.29.244.63]) by tx30smr01.am.freescale.net (8.14.3/8.14.0) with ESMTP id r92EgxCY005350; Wed, 2 Oct 2013 07:43:00 -0700 Message-ID: <524C2FDA.4080908@freescale.com> Date: Wed, 2 Oct 2013 11:38:18 -0300 From: Daiane Angolini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Alex J Lennon References: <524C1BDA.8000507@dynamicdevices.co.uk> <524C218D.7020101@freescale.com> <524C2793.4020107@dynamicdevices.co.uk> In-Reply-To: <524C2793.4020107@dynamicdevices.co.uk> X-OriginatorOrg: freescale.com X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: meta-freescale@yoctoproject.org Subject: Re: Issues using meta-freescale i.MX6 vs LTIB ? 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: Wed, 02 Oct 2013 14:43:06 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 10/02/2013 11:02 AM, Alex J Lennon wrote: > > On 02/10/2013 14:37, Daiane Angolini wrote: >> On 10/02/2013 10:12 AM, Alex J Lennon wrote: >>> Hi, >>> >>> I'm trying to qualify a decision to use Yocto / meta-freescale for an >>> upcoming >>> i.MX6 board variant (based on the Sabre reference) instead of using the >>> officially supported release based on LTIB. >>> >>> My preference is strongly for the Yocto/OpenEmbedded build environment, >>> for various reasons, but I understand that the Freescale i.MX6 BSP is >>> not >>> officially supported at this time. >>> >>> Knowing the experience and activity levels of the people working via >>> these >>> lists, I suspect that meta-freescale is by now significantly ahead of >>> the current >>> release of LTIB. >>> >>> That said I wonder if there are any known issues with using >>> meta-freescale >>> which might give me pause, and cause me to use LTIB at this time? >> >> You can see all current known issues here >> https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=meta-fsl-arm&list_id=105732 >> >> >> As you may know, the last LTIB release from Freescale was 3.0.35_4.1.0. >> > > Thanks Daiane, > > I guess what I'm really asking is, what are the drawbacks and > limitations (just just bugs per-se) > with using the current under-development i.MX6 OpenEmbedded BSP vs the > released LTIB BSP > > Maybe to put it another way, functionally is there a roadmap for where > the i.MX6 BSP is at > and what isn't yet working or supported. Presumably there are things > that are not working > or supported or FSL would be offically supporting at this time...? I don't like to leave non replied questions along my way. Although, this is the most difficult kind of question to answer. I, personally, cannot promise you what Freescale will or will not officially support. I can say what I'm supposed to support. And, officially, I'm only supposed to support imx-community. Although, I've been working a lot with meta-fsl-arm, and everything I can do internally to improve meta-fsl-arm technical support I've been doing. I've been using only yocto since 2 years ago. Last time I installed a new Ubuntu on my machine I even tried to install LTIB. I don't have any LTIB installed on my machine any more \o/ And, every time I need to reproduce a customer's issue, I use yocto to generate whatever I need. (but for Android) The things that are not working and I would love to see working is; * all user-space package independent on kernel headers * MM support for linux mainline * Wayland accelerated for imx6 (all other board by SW only) * I know there are details on GPU support that is not perfect enough, but you must judge if it's needed or not for you. For official support and roadmap, please contact you local Freescale representative. For kernel feature list (linux-imx), please, consult linux reference manual from the proper release version. Again, I cannot say "official" things to you. I'm not the official Freescale voice. > >> And, as already said in ML, next release 3.10.9_1.0.0 will be Yocto >> > > Apparently so :) I just wasn't sure whether I could mention that yet, > but as you already have... ;) I saw this already public on imx-community And I'm sorry not being able to make you feel more comfortable. -- Daiane