From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ptmx.org (ptmx.org [178.63.28.110]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 0C8C5E0087A for ; Mon, 20 Jan 2014 09:40:14 -0800 (PST) Received: from [10.1.14.248] (83-64-248-68.inzersdorf.xdsl-line.inode.at [83.64.248.68]) by ptmx.org (Postfix) with ESMTPSA id EB49F22600; Mon, 20 Jan 2014 18:40:12 +0100 (CET) Message-ID: <52DD5F7C.2020109@pseudoterminal.org> Date: Mon, 20 Jan 2014 18:40:12 +0100 From: Carlos Rafael Giani User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Daiane Angolini , "meta-freescale@yoctoproject.org" References: <52DCF67C.6030503@pseudoterminal.org> <52DD2EB0.5030208@freescale.com> <52DD3586.8090103@pseudoterminal.org> <52DD39FD.9090406@freescale.com> In-Reply-To: <52DD39FD.9090406@freescale.com> Subject: Re: About customizing the image_types_fsl class 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: Mon, 20 Jan 2014 17:40:16 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 2014-01-20 16:00, Daiane Angolini wrote: > > As I know it's supposed to be released today/tomorrow > Just had a discussion with developers working on Cubox-I support. They tried to push MXC SPL support for the CuBox-i upstream, didn't work out so far. Otavio suggested to use mainline without SPL for now, but I am skeptical about it. SPL is a very nice feature, it allows me to use the exact same installation for several Cubox-i machines. The way I see it, there are two options for me: 1) Use the u-boot fork with MXC SPL support for now, until mainline supports MXC SPL. Then immediately switch to mainline by applying a patch to meta-fsl-arm-extra. 2) Use mainline without SPL, and live with the fact that I need a build for every single CuBox-i machine. I personally favor (1), especially since it is already fully working for me. I could send the patches to the mailing list after a little cleanup. You seem to favor (2), since mainline is usually a better choice than some odd fork (I agree on this in principle, but in this case, I favor the fork).