[meta-freescale] 3.10.17-1.0.0_beta meta-fsl-bsp-release layer

Alok Kumar alokkat at gmail.com
Fri Jan 24 08:41:05 PST 2014


Great,  I have chromium working on nitrogen6x. Thanks to everyone for
guiding me.
Could someone please advise if HW accelerated chromium beta is available
for testing (somehow ?).

Thanks
Alok


On Thu, Jan 23, 2014 at 11:49 AM, Alok Kumar <alokkat at gmail.com> wrote:

> Oh I think I was building core-image-base. Will check this out.
>
>
> On Thu, Jan 23, 2014 at 11:06 AM, Gary Thomas <gary at mlbassoc.com> wrote:
>
>> On 2014-01-23 08:20, Alok Kumar wrote:
>>
>>> I have include meta-gnome in bblayer.conf, but I dont see any X server
>>> running.
>>>
>>> what should I include  in local.conf to get X running?
>>>
>>
>> What image did you build?  Something like core-image-sato or
>> fsl-image-gui will
>> get you an X server running on your hardware.
>>
>> n.b. please keep replies on the mailing list so that everyone can benefit.
>>
>>  On Thu, Jan 23, 2014 at 10:14 AM, Gary Thomas <gary at mlbassoc.com<mailto:
>>> gary at mlbassoc.com>> wrote:
>>>
>>>     On 2014-01-23 08:08, Alok Kumar wrote:
>>>
>>>         Eric,
>>>
>>>         After building chromium, when I tried to launch it
>>>
>>>         find / -name "chrome*"
>>>         /usr/bin/chrome
>>>         /usr/bin/chrome/chrome_100___percent.pak
>>>
>>>         /usr/bin/chrome/chrome
>>>         /usr/bin/chrome/chrome.pak
>>>
>>>         I get following error.
>>>         /usr/bin/chrome/chrome
>>>
>>>         (chrome:2068): Gtk-WARNING **: cannot open display:
>>>
>>>         Any thoughts, what I am missing here.
>>>
>>>
>>>     Do you have X running?
>>>
>>>     If you tried to run this from outside the X desktop, you'll need to
>>> do something like
>>>        DISPLAY=:0.0 /usr/bin/chrome/chrome
>>>
>>>
>>>         On Mon, Jan 20, 2014 at 10:14 PM, Eric Nelson
>>> <eric.nelson at boundarydevices.__com <mailto:eric.nelson@
>>> boundarydevices.com> <mailto:eric.nelson at __boundarydevices.com
>>>
>>>         <mailto:eric.nelson at boundarydevices.com>>> wrote:
>>>
>>>              Hi Alok,
>>>
>>>
>>>              On 01/20/2014 09:44 AM, Alok Kumar wrote:
>>>
>>>                  Hi Eric,
>>>
>>>                  I am not sure if I understand it. my apology.
>>>
>>>
>>>              No sweat. Over a year in and I'm still figuring things
>>> out...
>>>
>>>
>>>                  I am following this
>>>         http://wiki.wandboard.org/____index.php/Getting_started_____
>>> with_Yocto_on_Wandboard <http://wiki.wandboard.org/__
>>> index.php/Getting_started___with_Yocto_on_Wandboard>
>>>
>>>         <http://wiki.wandboard.org/__index.php/Getting_started___
>>> with_Yocto_on_Wandboard <http://wiki.wandboard.org/
>>> index.php/Getting_started_with_Yocto_on_Wandboard>>
>>>
>>>
>>>                  and took stable dora branch.
>>>
>>>
>>>              I'd start with Daiane's docs on i.MX Community:
>>>         http://layers.openembedded.____org/layerindex/branch/master/____layer/meta-gnome/
>>> <http://layers.openembedded.__org/layerindex/branch/master/_
>>> _layer/meta-gnome/
>>>
>>>         <http://layers.openembedded.org/layerindex/branch/master/
>>> layer/meta-gnome/>>
>>>
>>>
>>>              And O.S.Systems that describes how to specifically build for
>>>              Nitrogen6x:
>>>         http://www.ossystems.com.br/____blog/2013/04/15/yocto-with-_
>>> ___boundary-devices-nitrogen6x-5-____steps-only.html
>>>         <http://www.ossystems.com.br/__blog/2013/04/15/yocto-with-__
>>> boundary-devices-nitrogen6x-5-__steps-only.html>
>>>
>>>
>>>              <http://www.ossystems.com.br/_
>>> _blog/2013/04/15/yocto-with-__boundary-devices-nitrogen6x-5-
>>> __steps-only.html
>>>         <http://www.ossystems.com.br/blog/2013/04/15/yocto-with-
>>> boundary-devices-nitrogen6x-5-steps-only.html>>
>>>
>>>              Make sure you use the "dora" branch instead of "dylan"
>>> though.
>>>
>>>
>>>                  Now if I want to try chromium" beta,
>>>                  a) should I got to development branch first and get
>>> everything from below.
>>>
>>>                          repo init -u
>>>         https://github.com/Freescale/____fsl-community-bsp-platform <
>>> https://github.com/Freescale/__fsl-community-bsp-platform>
>>>
>>>         <https://github.com/Freescale/__fsl-community-bsp-platform <
>>> https://github.com/Freescale/fsl-community-bsp-platform>> -b master
>>>
>>>
>>>
>>>              Again, you should stick with "Dora" unless you need
>>> something
>>>              specific in "master".
>>>
>>>
>>>                  b) apply chromium recipe on this build and build the
>>> image.
>>>
>>>
>>>              After the repo sync, you'll need to pull in the meta-browser
>>>              layer:
>>>                       ~/yocto/sources$ git clone git://
>>> github.com/OSSystems/____meta-browser.git <http://github.com/OSSystems/_
>>> _meta-browser.git>
>>>         <http://github.com/OSSystems/__meta-browser.git <
>>> http://github.com/OSSystems/meta-browser.git>>
>>>
>>>
>>>
>>>              And you'll need to add meta-browser and meta-gnome to your
>>>              conf/bblayers.conf file:
>>>
>>>              BBLAYERS = " \
>>>                 ...
>>>                 ${BSPDIR}/sources/meta-____openembedded/meta-gnome \
>>>
>>>
>>>                 ${BSPDIR}/sources/meta-browser \
>>>                 ...
>>>              "
>>>
>>>              And finally, you'll need to pull it into your build.
>>>              The easy way is to add this to your local.conf file:
>>>
>>>              IMAGE_INSTALL += " \
>>>                       chromium \
>>>              "
>>>
>>>              I'm not sure why, but when I went through these steps,
>>>              I got complaints about the license for libav and
>>>              was prompted to add this to local.conf:
>>>
>>>                       LICENSE_FLAGS_WHITELIST = "commercial"
>>>
>>>              I think there's something screwy with that, though.
>>>              The recipes in poky/meta/recipes-multimedia/____libav/
>>>
>>>
>>>              appear to have a combination of GPL and LGPL
>>>              licenses.
>>>
>>>
>>>                  c) where should I test this on Sabrelite or nitorgen6x ?
>>>
>>>
>>>              We recommend the use of "nitrogen6x" for the MACHINE type.
>>>              The resulting image will run on either the SABRE Lite
>>>              or Nitrogen6X boards.
>>>
>>>              Regards,
>>>
>>>
>>>              Eric
>>>
>>>
>>>
>>>
>>>         --
>>>         Regards
>>>         Alok Kumar
>>>
>>>
>>>         _________________________________________________
>>>         meta-freescale mailing list
>>>         meta-freescale at yoctoproject.__org <mailto:meta-freescale@
>>> yoctoproject.org>
>>>         https://lists.yoctoproject.__org/listinfo/meta-freescale <
>>> https://lists.yoctoproject.org/listinfo/meta-freescale>
>>>
>>>
>>>     --
>>>     ------------------------------__------------------------------
>>>
>>>     Gary Thomas                 |  Consulting for the
>>>     MLB Associates              |    Embedded world
>>>     ------------------------------__------------------------------
>>>
>>>     _________________________________________________
>>>     meta-freescale mailing list
>>>     meta-freescale at yoctoproject.__org <mailto:meta-freescale@
>>> yoctoproject.org>
>>>     https://lists.yoctoproject.__org/listinfo/meta-freescale <
>>> https://lists.yoctoproject.org/listinfo/meta-freescale>
>>>
>>>
>>>
>>>
>>> --
>>> Regards
>>> Alok Kumar
>>>
>>
>> --
>> ------------------------------------------------------------
>> Gary Thomas                 |  Consulting for the
>> MLB Associates              |    Embedded world
>> ------------------------------------------------------------
>>
>
>
>
> --
> Regards
> Alok Kumar
>



-- 
Regards
Alok Kumar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20140124/2d1c05e7/attachment-0001.html>


More information about the meta-freescale mailing list