From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 79DEBE006DB; Wed, 23 Jul 2014 07:19:07 -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 * (daiane.list[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.220.172 listed in list.dnswl.org] Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 37BB3E006B7 for ; Wed, 23 Jul 2014 07:19:03 -0700 (PDT) Received: by mail-vc0-f172.google.com with SMTP id im17so2299843vcb.17 for ; Wed, 23 Jul 2014 07:19:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=rju0m8CoZMDTkymaUr+yL+D+iKHBO0+3xpMtimsjdzM=; b=M/nZbCxIP6RohuokBlYAlvGWYmY4M8bym+Qm2oMGviq2Dn24eeYYN1uql6eCXXTeGc Dt7Aw/BGFu+idgWdJOb/Qs7piSUhzXxh4Y90jM1TuLXpWHut9q2jWaPQ50qdGw2RvZgg lmLFfJI2suEpdZXIAAZ4oU0fYNBe2Ax7XuAkrmzMw4MxHaXV/C89ZxTq8kCR6WTlhFsC YWT+DjNRZMzXVTvpjxrhQfyw3YMyRrCzgceXwLC+1cfEX1vRPGsGt3mYSYRB+k+SGPL6 19y1anYWbd9Aju5grTV737QwQGjqJ+DRgoaAyvUdj4eOLd3q8EOtfOcdK8GKx/Hjvzwr jofw== MIME-Version: 1.0 X-Received: by 10.52.0.177 with SMTP id 17mr2341805vdf.12.1406125142827; Wed, 23 Jul 2014 07:19:02 -0700 (PDT) Sender: angolini@gmail.com X-Google-Sender-Delegation: angolini@gmail.com Received: by 10.220.118.132 with HTTP; Wed, 23 Jul 2014 07:19:02 -0700 (PDT) In-Reply-To: References: Date: Wed, 23 Jul 2014 11:19:02 -0300 X-Google-Sender-Auth: z7RYba12sxgLQWdyDM84tNndHQM Message-ID: From: Daiane Angolini To: Jens Rehsack 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 14:19:07 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jul 22, 2014 at 2:24 AM, Jens Rehsack wrote: > Hi, > > 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). > > As firmware-imx we have 3.0.35_4.0.0 (tried 3.10.17, too - without > difference). 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. Long story long: > > 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?). I don=C2=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. So, I don=C2=B4t know if *any* combination works. > > 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. When dealing with GPU, is important that the kernel GPU driver and the GPU user-space package match. 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. 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=C2=B4s may be a huge difference, however I don=C2=B4t see it causing a crash) > > Though I don't have a concrete question beside "what library versions > are good for us?" - any hints, resources to study, ...? So, the question "what library version are good for us" should be answered by another question "do you need libraries?" Or, let=C2=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? Daiane