From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rehsack@gmail.com>
Received: by yocto-www.yoctoproject.org (Postfix, from userid 118)
	id BFCD0E006DB; Wed, 23 Jul 2014 07:51:59 -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
	*      [209.85.212.174 listed in list.dnswl.org]
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com
	[209.85.212.174])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 50ECEE006B7
	for <meta-freescale@yoctoproject.org>;
	Wed, 23 Jul 2014 07:51:55 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id d1so7937503wiv.13
	for <meta-freescale@yoctoproject.org>;
	Wed, 23 Jul 2014 07:51:54 -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=r0WfyXz7sq2upKCqVdVCxXX3pQkN6a5nqTWyXUvBNqc=;
	b=lnAp9uqO2zIYPpTOJ1iBbGdEnjIxnEV7kpYwz7jgpSR+Wiw2b6yz3yZX5RhY7bTJSr
	rztaGFMlOjDYsXnfEwXY9YDTytOqNgsZF0oEekKq4CL10yzYjpQ/bj0yHO7IrSlDt47E
	PgWV+zci/QY/piqC0v5ZpEdph4Faa5g9pYmOOzMuetOGq/2NCFfrf8WWGZuVuPzXmQZM
	NcPLKYRpef2XcN6hr6OcfkJFSbUXEfJWlJlasg3qOz7mvwBKGITPjswERvHytxnWwHip
	iMOnYeNu9bbx9NSRvlVQ3N94ht7oy4YeXMIqBeMI5km4zxprkmkUOTXd8OxMoDIz8iFS
	5xcg==
X-Received: by 10.180.14.162 with SMTP id q2mr25678241wic.29.1406127114569;
	Wed, 23 Jul 2014 07:51:54 -0700 (PDT)
Received: from jenss-mbp.rdm.local (pd956d8ef.dip0.t-ipconnect.de.
	[217.86.216.239])
	by mx.google.com with ESMTPSA id sa4sm6826027wjb.45.2014.07.23.07.51.52
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 23 Jul 2014 07:51:53 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Jens Rehsack <rehsack@gmail.com>
In-Reply-To: <CA+jg_OVRMTN4cVVWvkQyWc2x+F9eBQDff9YxwTmiDqf1EPg0_w@mail.gmail.com>
Date: Wed, 23 Jul 2014 16:51:51 +0200
Message-Id: <DF533160-2978-4351-90C3-C5D78B138012@gmail.com>
References: <C95EE08A-73E9-4B95-AA68-C27A8F22A1D4@gmail.com>
	<CA+jg_OVRMTN4cVVWvkQyWc2x+F9eBQDff9YxwTmiDqf1EPg0_w@mail.gmail.com>
To: Daiane Angolini <daiane.list@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Cc: "meta-freescale@yoctoproject.org" <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
	<meta-freescale.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/meta-freescale>,
	<mailto:meta-freescale-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/meta-freescale>
List-Post: <mailto:meta-freescale@yoctoproject.org>
List-Help: <mailto:meta-freescale-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/meta-freescale>,
	<mailto:meta-freescale-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jul 2014 14:51:59 -0000
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


Am 23.07.2014 um 16:19 schrieb Daiane Angolini <daiane.list@gmail.com>:

> On Tue, Jul 22, 2014 at 2:24 AM, Jens Rehsack <rehsack@gmail.com> =
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.

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).

> Long story long:
>=20
>> When we run xmbc with lib-imx, gpu-viv-ib-mx6q, lib-vpu in daisy
>> versions (3.10.17), xbmc immediately crashes with a segfault in
>> gpu-viv-ib-mx6q (does someone wants the trace?). Using Dora versions
>> (3.10.9) we can at least start xbmc and can start one movie. When
>> we play a second movie, the system crashes with "dma physical memory
>> allocation error" (trace/console output wanted?).
>=20
> I don=B4t have previous success cases in running xbmc. I mean, I have
> never (myself) tried it, but in other hand, I have never heard about
> someone that had succeeded.

http://stephan-rafin.net/blog/ or more concrete: =
http://stephan-rafin.net/blog/2014/01/29/yet-another-yocto-image/

But as far as I see from his recipes, he's using mx6d.

> So, I don=B4t know if *any* combination works.
>=20
>> The board manufacturer recommends we try the freescale libs =
(firmware,
>> lib-imx, gpu...) in precisely matching version (3.0.35_4.1.0), but =
none
>> of them seems to exist in meta-fsl-arm(-extra). That confuses me in =
the
>> way that I expect, the distributed versions are stable.
>=20
> When dealing with GPU, is important that the kernel GPU driver and the
> GPU user-space package match.

As said, I have linux-imx-3.0.35_4.1.0 at revision bdde708 with patches
=
https://github.com/rehsack/meta-jens/tree/master/recipes-kernel/linux/linu=
x-curie-3.0.35

Doesn't look to me as if any modifies GPU kernel driver ...

> When working with IPU for imx6. It does not matter what imx-lib you is
> working with. ipu-lib is not used for imx6 since 3.0.15, or something
> like that. So, for IPU, no user-space package needed.

k

> When working with VPU, imx-vpu is needed, and imx-firmware is needed.
> However, any should work, and what you miss from one to another is
> only bugfixes. (of course, it=B4s may be a huge difference, however I
> don=B4t see it causing a crash)

The crash I see with xbmc and 3.10.9 drivers (firmware-imx-3.0.35_4.0.0+
imx-lib-, imx-vpu- & gpu-viv-lib-mx6q-3.10.9_1.0.0) is nearly =
byte-identical
to https://community.freescale.com/thread/304414 ...

However, with gpu-viv-lib-mx6q (other versions doesn't seem to matter in
any way), it immediately crashes=20

#0  0x2be582b0 in gcoHAL_QueryChipCount (Hal=3DHal@entry=3D0x0,
   Count=3DCount@entry=3D0x1c3b65c) at gc_hal_user_query.c:1726
#1  0x2b275244 in veglGetThreadData () at gc_egl.c:137
#2  0x2b26e210 in eglfGetDisplay (display_id=3D0x1c2b568) at =
gc_egl_init.c:464
#3  eglGetDisplay (DisplayID=3D0x1c2b568) at gc_egl_init.c:565
#4  0x00880fac in CEGLWrapper::InitDisplay (this=3D0x1c16c40,
   display=3Ddisplay@entry=3D0x1a64e50) at EGLWrapper.cpp:206

which points to gpu-viv-lib-mx6q ...

>> Though I don't have a concrete question beside "what library versions
>> are good for us?" - any hints, resources to study, ...?
>=20
> So, the question "what library version are good for us" should be
> answered by another question "do you need libraries?"

=46rom available xbmc recipes I think so - but maybe the imx port isn't
the right way. OTOH, looks as if wolfgar did a good job there, at least
for wandboard, uitite & co.

> 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?

Nope, how can I do that (fsl for dummies - I'm happy controlling Yocto
meanwhile). Just bitbake imx-test or something more?

Thanks in advance.

Best regards
--=20
Jens Rehsack
rehsack@gmail.com