All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-arm][PATCH] chromium: Update bbappend to version 38.0.2125.101
Date: Mon, 13 Oct 2014 14:41:55 +0200	[thread overview]
Message-ID: <543BC893.90705@pseudoterminal.org> (raw)
In-Reply-To: <543BC646.4050506@arantia.com>

[-- Attachment #1: Type: text/plain, Size: 6633 bytes --]

An update to chromium_38.0.2125.101.bb was just submitted to meta-browser.

On 2014-10-13 14:32, Ruben Morgade wrote:
> Hi,
>
> One question? This patch should work for a chromium_38.0.2125.101.bb 
> recipe right? Because the only one available is still the 
> chromium_37.0.2062.94.bb.
>
> Rgds
>
> El 13/10/14 a las #4, Carlos Rafael Giani escribió:
>> On 2014-10-13 14:01, Gary Thomas wrote:
>>> On 2014-10-13 05:35, Carlos Rafael Giani wrote:
>>>> In this update, the "component-build" packageconfig is no longer 
>>>> enabled
>>>> by default. Component builds do use much less RAM on build 
>>>> machines, but
>>>> according to Chromium developers, it is not recommended to use 
>>>> these for
>>>> anything other than developer builds.
>>>>
>>>> Note that you should still enable component mode if you don't have a
>>>> 64 bit build machine, or a machine with less than 8 GB RAM.
>>>>
>>>> Reference:
>>>> https://groups.google.com/a/chromium.org/d/topic/chromium-dev/yqIHEbquIBg/discussion 
>>>>
>>>>
>>>> Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
>>>> ---
>>>>   browser-layer/recipes-browser/chromium/chromium-imx.inc | 10 
>>>> ++++------
>>>>   ...m_37.0.2062.94.bbappend => chromium_38.0.2125.101.bbappend} |  
>>>> 4 +++-
>>>>   2 files changed, 7 insertions(+), 7 deletions(-)
>>>>   rename 
>>>> browser-layer/recipes-browser/chromium/{chromium_37.0.2062.94.bbappend 
>>>> => chromium_38.0.2125.101.bbappend} (67%)
>>>>
>>>> diff --git 
>>>> a/browser-layer/recipes-browser/chromium/chromium-imx.inc 
>>>> b/browser-layer/recipes-browser/chromium/chromium-imx.inc
>>>> index 02a027d..f955c80 100644
>>>> --- a/browser-layer/recipes-browser/chromium/chromium-imx.inc
>>>> +++ b/browser-layer/recipes-browser/chromium/chromium-imx.inc
>>>> @@ -4,9 +4,9 @@ DEPENDS_append = " libfslvpuwrap"
>>>>   # The code below fetches this repository, copies the extra source 
>>>> over to the main
>>>>   # chromium source directory, and applies the patches.
>>>>
>>>> -CHROMIUM_IMX_BRANCH = "master"
>>>> -CHROMIUM_IMX_SRCREV = "5c5cadd40ad04e66ec9b14a7a29370b76ed5c4f4"
>>>> -CHROMIUM_IMX_DESTSUFFIX = "chromium-imx-git"
>>>> +CHROMIUM_IMX_BRANCH ?= "master"
>>>> +CHROMIUM_IMX_SRCREV ?= "HEAD"
>>>> +CHROMIUM_IMX_DESTSUFFIX ?= "chromium-imx-git"
>>>>
>>>>   PATCH_BASE_DIR = "${WORKDIR}/${CHROMIUM_IMX_DESTSUFFIX}/patches"
>>>>
>>>> @@ -22,12 +22,10 @@ do_unpack[postfuncs] += "copy_chromium_imx_files"
>>>>   # patches to the OZONE_WAYLAND_EXTRA_PATCHES variable
>>>>   do_patch[prefuncs] =+ "add_chromium_imx_patches"
>>>>
>>>> -# * component build is on by default to reduce memory usage while 
>>>> compiling and to
>>>> -#   make it easier to patch binaries on the targets if necessary
>>>>   # * Lost context problems are not known to happen with Vivante GPUs,
>>>>   #   so it is safe to use ignore-lost-context
>>>>   # * EGL is on by default due to the GPU on the i.MX6
>>>> -PACKAGECONFIG_append = " component-build use-egl ignore-lost-context"
>>>> +PACKAGECONFIG_append = " use-egl ignore-lost-context"
>>>>
>>>>   copy_chromium_imx_files() {
>>>>       # sources in src/ are already organized in a manner
>>>> diff --git 
>>>> a/browser-layer/recipes-browser/chromium/chromium_37.0.2062.94.bbappend 
>>>> b/browser-layer/recipes-browser/chromium/chromium_38.0.2125.101.bbappend 
>>>>
>>>> similarity index 67%
>>>> rename from 
>>>> browser-layer/recipes-browser/chromium/chromium_37.0.2062.94.bbappend
>>>> rename to 
>>>> browser-layer/recipes-browser/chromium/chromium_38.0.2125.101.bbappend
>>>> index 1eb6490..f4c857b 100644
>>>> --- 
>>>> a/browser-layer/recipes-browser/chromium/chromium_37.0.2062.94.bbappend 
>>>>
>>>> +++ 
>>>> b/browser-layer/recipes-browser/chromium/chromium_38.0.2125.101.bbappend 
>>>>
>>>> @@ -1,5 +1,7 @@
>>>>   include chromium-imx.inc
>>>>
>>>> +CHROMIUM_IMX_BRANCH = "master"
>>>> +CHROMIUM_IMX_SRCREV = "aff6dd45041340190e3742118200219a6d7f3e87"
>>>>   CHROMIUM_IMX_COMMON_PATCHES += 
>>>> "file://${PATCH_BASE_DIR}/common/0001-Enable-share-group-workaround-for-Vivante-GPUs.patch 
>>>> \
>>>> - 
>>>> file://${PATCH_BASE_DIR}/common/0002-Add-VPU-video-decode-accelerator-to-Chromium-37-GPU-.patch"
>>>> + 
>>>> file://${PATCH_BASE_DIR}/common/0002-Add-VPU-video-decode-accelerator-to-Chromium-38-GPU-.patch"
>>>
>>> Did you mean to make this change or perhaps failed to send this last 
>>> patch file?
>>>
>>>>   CHROMIUM_IMX_WAYLAND_PATCHES += 
>>>> "file://${PATCH_BASE_DIR}/wayland/0001-Modify-eglwayland-versions-for-Vivante-GPUs.patch"
>>>>
>>
>> These are part of the chromium-imx repo , which is fetched in 
>> chromium-imx.inc .
>
> -- 
>
> Ruben Morgade
> STB product Manager
>
> *Arantia 2010, S.L.U.*
> Volta do Castro, s/n
> 15706 Santiago de Compostela (Spain)
> Tel: +34 902 209040
> Fax: +34 981 524428
> arantia@arantia.com <mailto:arantia@arantia.com>
> www.arantia.com <http://www.arantia.com/>
>
> *a Televes Corporation Company*
>
> Respeta el medio ambiente: imprime este correo, solo si lo consideras 
> necesario
>
> Nota de confidencialidad: Este mensaje se dirige exclusivamente a su 
> destinatario y puede contener información privilegiada o confidencial. 
> Si no es vd. el destinatario indicado, queda notificado de que la 
> lectura, utilización, divulgación y/o copia sin autorización está 
> prohibida en virtud de la legislación vigente. Si ha recibido este 
> mensaje por error, le rogamos que nos lo comunique inmediatamente por 
> esta misma vía y proceda a su destrucción. El correo electrónico vía 
> Internet no permite asegurar la confidencialidad de los mensajes que 
> se transmiten ni su integridad o correcta recepción. Arantia 2010 no 
> asume ninguna responsabilidad por estas circunstancias.
>
> Be environmentally responsible. Do not print this message unless 
> absolutely necessary
>
> This message is intended exclusively for its addressee and may contain 
> information that is CONFIDENTIAL and protected by a professional 
> privilege or whose disclosure is prohibited by law.If you are not the 
> intended recipient you are hereby notified that any read, 
> dissemination, copy or disclosure of this communication is strictly 
> prohibited by law. If this message has been received in error, please 
> immediately notify us via e-mail and delete it. Internet e-mail 
> neither guarantees the confidentiality nor the integrity or proper 
> receipt of the messages sent. Arantia 2010 does not assume any 
> liability for those circumstances.
>
>
>


[-- Attachment #2: Type: text/html, Size: 11295 bytes --]

      reply	other threads:[~2014-10-13 12:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13 11:35 [meta-fsl-arm][PATCH] chromium: Update bbappend to version 38.0.2125.101 Carlos Rafael Giani
2014-10-13 12:01 ` Gary Thomas
2014-10-13 12:13   ` Carlos Rafael Giani
2014-10-13 12:32     ` Ruben Morgade
2014-10-13 12:41       ` Carlos Rafael Giani [this message]

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=543BC893.90705@pseudoterminal.org \
    --to=dv@pseudoterminal.org \
    --cc=meta-freescale@yoctoproject.org \
    /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.