From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Prabhu S <prabhusundar@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH] chromium: Update bbappend to version 40.0.2214.91
Date: Tue, 27 Jan 2015 00:26:35 +0100 [thread overview]
Message-ID: <54C6CD2B.5010409@pseudoterminal.org> (raw)
In-Reply-To: <CAGQpYzZw=PkY6JrYpKwMMF7c4jz3mbszoT7wbYXFC0XwpitOMg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]
This is a little confusing, yes. The reason is that it applies for both
38 and 40. Perhaps renaming it to 40 in chromium-imx' chromium-40 branch
makes more sense.
On 2015-01-27 00:24, Prabhu S wrote:
> 0002-Add-VPU-video-decode-accelerator-to-Chromium-38-GPU-.patch - do
> you still need 38 name in it?
>
> On Mon, Jan 26, 2015 at 5:21 PM, Carlos Rafael Giani
> <dv@pseudoterminal.org <mailto:dv@pseudoterminal.org>> wrote:
>
> Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org
> <mailto:dv@pseudoterminal.org>>
> ---
> .../recipes-browser/chromium/chromium_40.0.2214.91.bbappend | 12
> ++++++++++++
> 1 file changed, 12 insertions(+)
> create mode 100644
> browser-layer/recipes-browser/chromium/chromium_40.0.2214.91.bbappend
>
> diff --git
> a/browser-layer/recipes-browser/chromium/chromium_40.0.2214.91.bbappend
> b/browser-layer/recipes-browser/chromium/chromium_40.0.2214.91.bbappend
> new file mode 100644
> index 0000000..20d7ceb
> --- /dev/null
> +++
> b/browser-layer/recipes-browser/chromium/chromium_40.0.2214.91.bbappend
> @@ -0,0 +1,12 @@
> +include chromium-imx.inc
> +
> +CHROMIUM_IMX_BRANCH = "chromium-40"
> +CHROMIUM_IMX_SRCREV = "4a799509fa9a9c6281268856d20ff531927e39a3"
> +CHROMIUM_IMX_COMMON_PATCHES +=
> "file://${PATCH_BASE_DIR}/common/0001-Enable-share-group-workaround-for-Vivante-GPUs.patch"
> +
> +VPU_PATCHES =
> "file://${PATCH_BASE_DIR}/common/0002-Add-VPU-video-decode-accelerator-to-Chromium-38-GPU-.patch"
> +
> +CHROMIUM_IMX_VPU_PATCHES_mx6q += "${VPU_PATCHES}"
> +CHROMIUM_IMX_VPU_PATCHES_mx6dl += "${VPU_PATCHES}"
> +
> +CHROMIUM_IMX_WAYLAND_PATCHES +=
> "file://${PATCH_BASE_DIR}/wayland/0001-Modify-eglwayland-versions-for-Vivante-GPUs.patch"
> --
> 1.9.1
>
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> <mailto:meta-freescale@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
>
[-- Attachment #2: Type: text/html, Size: 4037 bytes --]
next prev parent reply other threads:[~2015-01-26 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 23:21 [meta-fsl-arm][PATCH] chromium: Update bbappend to version 40.0.2214.91 Carlos Rafael Giani
2015-01-26 23:24 ` Prabhu S
2015-01-26 23:26 ` Carlos Rafael Giani [this message]
2015-01-26 23:28 ` Otavio Salvador
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=54C6CD2B.5010409@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=meta-freescale@yoctoproject.org \
--cc=prabhusundar@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.