From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f51.google.com (mail-pb0-f51.google.com [209.85.160.51]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 36B1EE0044F for ; Sat, 25 Jan 2014 11:21:31 -0800 (PST) Received: by mail-pb0-f51.google.com with SMTP id un15so4424463pbc.24 for ; Sat, 25 Jan 2014 11:21:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=TcsnQwyQqo+eh0pTthTzlCnrEvtKoIkcbqNH+SNDlzg=; b=Bh3IsTIWOdWZ4Xf4Jm+FivquQ0uBbefO3PgiB+nyKPS3EwexJmrZZAt3DpxFnMi3Iz +qBfFFVGRUDS+6KRAwmbO6AYLAiU+GKKZOrbLzfg1UMiJ9MFcCUt+hmgUWLJZNfsvDkP ZU0PExX2V9vs0y2OED9JE3+ohN4MesuiVY0WLqLGgdKaN6Otte7yqGB6WonXMbkxH+jL HAe1x3HrrvyQgCz1VabJmWji6nCYHWju7+OzkPXOLgcihgIjbyPXrgpitvEm2eabsUEr WkN4wXgoYxRNyD6jvZLla0OWl9ftzr0xk0ZTolx4rscV1p+CQZY6DdXmP6pyAgE10RtC QYXQ== X-Gm-Message-State: ALoCoQnDDO8UV78BGA3N1L+PXRgMvpRumb7U/mNPhCc105+GgTvLl2Untx8mmfHg/WX7H+WX4leE X-Received: by 10.69.20.139 with SMTP id hc11mr21314629pbd.63.1390677691345; Sat, 25 Jan 2014 11:21:31 -0800 (PST) Received: from [192.168.0.53] ([63.226.49.26]) by mx.google.com with ESMTPSA id zc6sm40117042pab.18.2014.01.25.11.21.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 11:21:30 -0800 (PST) Message-ID: <52E40EB7.6060108@boundarydevices.com> Date: Sat, 25 Jan 2014 12:21:27 -0700 From: Eric Nelson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Otavio Salvador References: <1390528076-31527-1-git-send-email-otavio@ossystems.com.br> <52E2A048.9070005@boundarydevices.com> <20140124193747.31558.67847@domU-12-31-39-0A-A0-4F> <52E3294F.4090509@boundarydevices.com> In-Reply-To: Cc: meta-freescale Mailing List Subject: Re: [meta-fsl-arm][PATCH v3 00/11] Freescale 3.10.17-1.0.0-beta - part 1 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: Sat, 25 Jan 2014 19:21:34 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Thanks Otavio, On 01/25/2014 11:56 AM, Otavio Salvador wrote: > Hello Eric, > > On Sat, Jan 25, 2014 at 1:02 AM, Eric Nelson > wrote: >> On 01/24/2014 01:37 PM, Otavio Salvador wrote: >>> >>> Hello Eric, >>> >>> On Fri, Jan 24, 2014 at 3:18 PM, Eric Nelson >>> >> > wrote: >>> > On 01/23/2014 06:47 PM, Otavio Salvador wrote: >>> >> I did some small fixes that I found during test at O.S. Systems' >>> >> autobuilder and I dropped some fixes that were pushed to master (as >>> >> you've probably noticed from the e-mail to the mailing list). >>> >> >>> >> I am awaiting people's feedback for the patches as this upgrades >>> >> package versions and we should have a better test coverage. >>> >> >>> >> Please give a try in the 'master-next' branch and comment in anything >>> >> that could be improved in the patches. All comments are welcome... >>> >> >> >>> >> >> >>> >> >>> > >>> > I compile-tested the series against MACHINE="nitrogen6x" and >>> > MACHINE="nit6xlte" with target image "fsl-image-gui". >>> >>> Thank you. >>> >>> > The only compile-time issue was with clocks.sh and the imx_test recipe >>> > as noted separately. >>> >>> Please confirm you have the current patchset; you may have used the v2 >>> were this was indeed the case. The v3, >>> http://patchwork.openembedded.org/patch/65673/, should be fine. >>> >> >> Maybe. >> >> I'm having trouble piecing this together, but I'm running master-next >> directly. >> >> Unfortunately, the patch version gets dropped on the way into git >> and I'm not seeing a V2 in either the ML archive or patchwork. >> >> I'm also not finding a "--- changed in V3" comment anywhere. > > Yes; it is a little bit hard for me to keep track of the patchset (as > we usually do in U-Boot and like) as I've been using Gerrit to review > those patches internally before putting them in the mailing list and > patman requires also those extra header in the commit log. > Cool. So my testing was against the V3 patch set. > I will try to think how to improve it for future submissions ... > > I keep master-next updated with the very last revision. I just did it > again after pushing your patch. > >>> > Run-time testing showed that the GPU binaries still need to be >>> > updated from 1_3.10.9-1.0.0-hfp-r0, so X wouldn't start. >>> >>> Hum this is not expected as I didn't include GPU changes on this. Can >>> you send the Xorg.0.log? >>> >> I'll send this in the A.M.. I don't have access to it at the moment. >> >> This was expected though, right? >> >> We haven't been able to get even the frame-buffer versions of the >> libraries to operate against the 3.10.9 libraries and presumed an >> ABI break here. > > If you are running 3.10.17 this is expected as it uses p13 GPU > version. Otherwise it ought to work just fine. > Yep. I was building 3.10.17-beta in preparation for submitting patches for linux-boundary. Let me know when you have a GPU patch. I'll be happy to test. Regards, Eric