From: Daiane Angolini <daiane.angolini@freescale.com>
To: David Hill <David.Hill@Oracle.com>,
Otavio Salvador <otavio@ossystems.com.br>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: fsl framebuffer image ?
Date: Mon, 3 Feb 2014 08:58:42 -0200 [thread overview]
Message-ID: <52EF7662.2030400@freescale.com> (raw)
In-Reply-To: <52EC19F2.30605@Oracle.com>
On 31-01-2014 19:47, David Hill wrote:
>
> Thanks Otavio,
> I see now that I picked the wrong machine type for the SDP in this
> build, which now make clear to me why I had a failure building u-boot.
> Unfortunately I don't need to do a lot of this so it is easy to stumble
> on which board is which.
>
> My need is for fsl-image-fb (or something close to it). Any recent
> kernel will do as long as I can get the accelerated framebuffer
> rendering stuff with a handful of other useful items like sshd.
You could copy only the fsl-image-fb image file, for your first tests.
But, the piece of code you need is:
DISTRO_FEATURES_remove = "x11 wayland"
x11 and wayland are the default DISTRO_FEATURES backend, if you remove
both, you have framebuffer.
Daiane
>
> We have several different boards in my group, Freescale and Boundry and
> maybe even a Wandboard, so I would really prefer not to use the
> meta-fsl-bsp-release if there is an easier, mainline way that I can
> understand. (And I guess follow directions).
>
> Any suggestions as to how I should proceed with to get accelerated fb
> support with fsl-community-bsp other than the earlier suggestion of
> qt4e-demo-image?
>
> I really wish that fsl-image-x11 just contained the two needed GL
> libraries with different postfixes like it used to. (libEGL-fb.so) I
> don't care about the image size because I am not distributing it.
>
> thanks,
> Dave
>
>
> On 1/31/14, Jan 31, 11:11 AM, Otavio Salvador wrote:
>> Hello David,
>>
>> On Thu, Jan 30, 2014 at 7:55 PM, David Hill <David.Hill@oracle.com>
>> wrote:
>>> On 1/14/14, Jan 14, 9:25 PM, Lauren Post wrote:
>>>> You can use the one in our meta-fsl-bsp-release layer. There is one
>>>> being
>>>> reviewed based on the one Freescale released in the
>>>> meta-fsl-bsp-release
>>>> layer. Our current 3.10.17-1.0.0 beta has support for all the
>>>> graphical
>>>> backends including the related image recipes for each backend.
>>>>
>>>> Get meta-fsl-release-layer from git.freescale.com.
>>>
>>>
>>> Hi Lauren,
>>> could I trouble you for a quick question ? I am getting a build
>>> failure
>>> and have not a clue how to proceed.
>>>
>>> meta-fsl-bsp-release & git checkout origin/dora_3.10.17-1.0.0_beta
>>>
>>> MACHINE=imx6qsabrelite
>>> bitbake fsl-iamge-fb
>> ...
>>
>> Personally I don't use the meta-fsl-bsp-release layer as it's not a
>> community layer, and we cannot contribute back patches and fixes to
>> it.
>>
>> The release layer is the official way Freescale is using to release
>> its new source code on top of meta-fsl-arm. The supported board list
>> is limited and is usually available in its release notes. But I don't
>> believe sabrelite is supported, as it's not a board from Freescale.
>>
>> I recommend you to use the fsl-community-bsp as is as sabrelite is
>> properly supported in there by Boundary Devices. You can see a blog
>> post[1] about how to build an image for Nitrogen6x (which works for
>> sabrelite board too). Just change "dylan" to "dora", the latest stable
>> release.
>>
>> If you need kernel 3.10.17 you can have an early snapshot on
>> master-next, although it's a work in progress, so far.
>>
>> 1.
>> http://www.ossystems.com.br/blog/2013/04/15/yocto-with-boundary-devices-nitrogen6x-5-steps-only.html
>>
>>
>> Regards,
>>
>
>
--
Daiane
next prev parent reply other threads:[~2014-02-03 11:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 20:22 fsl framebuffer image ? David Hill
2014-01-15 1:39 ` Otavio Salvador
2014-01-15 16:08 ` David Hill
2014-01-15 16:16 ` Gary Thomas
2014-02-03 20:19 ` David Hill
2014-02-03 20:22 ` Otavio Salvador
2014-02-03 20:25 ` Otavio Salvador
2014-02-03 20:43 ` David Hill
2014-02-04 1:32 ` Otavio Salvador
2014-02-04 22:47 ` David Hill
2014-02-04 23:17 ` Otavio Salvador
2014-02-05 5:37 ` Filip Piechocki
2014-02-06 22:48 ` David Hill
2014-02-07 18:54 ` David Hill
2014-02-07 18:56 ` Otavio Salvador
2014-02-07 20:07 ` Filip Piechocki
2014-02-10 12:01 ` Otavio Salvador
2014-02-03 20:38 ` David Hill
2014-01-15 2:25 ` Lauren Post
2014-01-30 21:55 ` David Hill
2014-01-31 16:11 ` Otavio Salvador
2014-01-31 21:47 ` David Hill
2014-02-03 10:58 ` Daiane Angolini [this message]
2014-02-03 14:16 ` Rogerio Nunes
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=52EF7662.2030400@freescale.com \
--to=daiane.angolini@freescale.com \
--cc=David.Hill@Oracle.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.