From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 84BE9E006DB; Wed, 23 Jul 2014 10:31:20 -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.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (rehsack[at]gmail.com) * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 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 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [74.125.82.181 listed in list.dnswl.org] Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 16E84E006B7 for ; Wed, 23 Jul 2014 10:31:14 -0700 (PDT) Received: by mail-we0-f181.google.com with SMTP id k48so1583193wev.12 for ; Wed, 23 Jul 2014 10:31:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Udn6yBQPO6DLapGgsqAcmVtwTdrXHmgIHeXbTqiXTME=; b=zUUkSBm5cpDracKUbsci7j27Fr72uY0t1hByLFW4CfI3cON6WqeJLQe/m8xm2C4wyA yubl3uwIhOoVKjcmiPDy8AhN9iu4t764B8cw4JZx8WA7JWib764qD1xLo6TF5XIX+H3p MyMuHp9YVm35/YEkm6Pf7zhw2VnKNgLauerwqlhitnMZ5dr8kdN3/0bkr7GzETV1zY2B 34xuJ1Q225Ca8NTq9M8rMZL52AHzVIcVRuziiFSeEksoN4KGVG2GxoCBxzbrcwKGvof/ MX/oCpE660JwNXmhtOGwP6xkp2gTjnLjePR+DuuVa+rDzctSZKotqRKrWmsZHeq4A0sj 2WyA== X-Received: by 10.180.82.166 with SMTP id j6mr26629304wiy.71.1406136672709; Wed, 23 Jul 2014 10:31:12 -0700 (PDT) Received: from ernie.muppets.liwing.de (p578b540c.dip0.t-ipconnect.de. [87.139.84.12]) by mx.google.com with ESMTPSA id w5sm11861043wif.3.2014.07.23.10.31.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Jul 2014 10:31:11 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Jens Rehsack In-Reply-To: Date: Wed, 23 Jul 2014 19:31:12 +0200 Message-Id: References: To: Daiane Angolini X-Mailer: Apple Mail (2.1878.6) Cc: "meta-freescale@yoctoproject.org" Subject: Re: Right lib-imx/firmware-imx ... versions 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, 23 Jul 2014 17:31:20 -0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Am 23.07.2014 um 17:45 schrieb Daiane Angolini : > On Wed, Jul 23, 2014 at 11:51 AM, Jens Rehsack = wrote: >>=20 >> Am 23.07.2014 um 16:19 schrieb Daiane Angolini = : >>=20 >>> On Tue, Jul 22, 2014 at 2:24 AM, Jens Rehsack = wrote: >>>> Hi, >>>>=20 >>>> as mentioned in my very first post here, we're trying to get a = board >>>> running with yocto with a bsp for linux-imx-3.0.35_4.1.0 (bdde708). >>>>=20 >>>> As firmware-imx we have 3.0.35_4.0.0 (tried 3.10.17, too - without >>>> difference). >>>=20 >>> Long story short: Stick to one branch and use it, with the kernel >>> version and the imx-lib/gpu/imx-vpu/firmware version already there. = It >>> was what we tested someway. >>=20 >> But there is no Yocto support for imx-lib-3.0.35_4.1.0, neither that >> imx-vpu nor gpu-viv-lib-mxq version. Only 3.10.9 and 3.10.17 is = included >> (daisy has only 3.10.17). >=20 > I don=B4t remember exactly which version was used in each branch. = Sorry. > I can only say to you that using the branch as-is, was enough to my > uses. >=20 >=20 >>> Or, let=B4s be more practical. Have you tested your GPU integration? >>> What is the GPU driver version in your kernel, and your GPU = user-space >>> version? >>=20 >> Nope, how can I do that (fsl for dummies - I'm happy controlling = Yocto >> meanwhile). Just bitbake imx-test or something more? >=20 >=20 > For this kernel: > = http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/recipes-kernel= /linux/linux-imx_3.0.35.bb?h=3Ddora >=20 > Use this GPU user space > = http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/recipes-graphi= cs/gpu-viv-bin-mx6q?h=3Ddora >=20 > hfp or sfp.... >=20 > The Original 3.0.35-4.0.1 is not compatible with > gpu-viv-bin-mx6q_3.10.9-1.0.0, that=B4s why there is a patch to = upgrade > 3.0.35 to GPU driver p13 I didn't see that patch, digging for unless ... bsp porting isn't an = option. > However, it does not mean that this combination is free of bug. >=20 > And remember it=B4s only a hint. As you said at first, community does > not support linux-imx-3.0.35 any more. I took a look into differences between imx_3.10.17_1.0.0_ga and wandboard_imx_3.10.17_1.0.0_ga to get a picture what I have to hack to port the bsp from 3.0.35 to 3.10.17 - but I miss the place where previously platform initialization happened = (arch/arm/mach-mx6/board-mx6q_sabresd.*) Is there a suitable guide explaining bsp porting from imx_3.0.35_4.1.0 = to imx_3.10.17_1.0.0? Cheers --=20 Jens Rehsack rehsack@gmail.com