From: Daiane Angolini <daiane.list@gmail.com>
To: Jens Rehsack <rehsack@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Right lib-imx/firmware-imx ... versions
Date: Wed, 23 Jul 2014 12:45:32 -0300 [thread overview]
Message-ID: <CA+jg_OXMYsjndztfva2Ed3zigNkhNpt4w4JOuHuNecwjxeimqw@mail.gmail.com> (raw)
In-Reply-To: <DF533160-2978-4351-90C3-C5D78B138012@gmail.com>
On Wed, Jul 23, 2014 at 11:51 AM, Jens Rehsack <rehsack@gmail.com> wrote:
>
> 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,
>>>
>>> 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.
>
> 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).
I don´t 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.
>> Or, let´s 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?
For this kernel:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/recipes-kernel/linux/linux-imx_3.0.35.bb?h=dora
Use this GPU user space
http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/recipes-graphics/gpu-viv-bin-mx6q?h=dora
hfp or sfp....
The Original 3.0.35-4.0.1 is not compatible with
gpu-viv-bin-mx6q_3.10.9-1.0.0, that´s why there is a patch to upgrade
3.0.35 to GPU driver p13
However, it does not mean that this combination is free of bug.
And remember it´s only a hint. As you said at first, community does
not support linux-imx-3.0.35 any more.
Daiane
next prev parent reply other threads:[~2014-07-23 15:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 5:24 Right lib-imx/firmware-imx ... versions Jens Rehsack
2014-07-23 3:57 ` Jens Rehsack
2014-07-23 14:19 ` Daiane Angolini
2014-07-23 14:51 ` Jens Rehsack
2014-07-23 15:14 ` xxiao8
2014-07-23 15:46 ` Daiane Angolini
2014-07-23 15:45 ` Daiane Angolini [this message]
2014-07-23 17:31 ` Jens Rehsack
2014-08-02 14:59 ` Jens Rehsack
2014-08-04 15:41 ` John Weber
2014-08-04 19:04 ` Jens Rehsack
2014-08-04 19:48 ` John Weber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+jg_OXMYsjndztfva2Ed3zigNkhNpt4w4JOuHuNecwjxeimqw@mail.gmail.com \
--to=daiane.list@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=rehsack@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.