All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: L3.10.17_1.0.2 Release ABI changes
Date: Fri, 31 Oct 2014 08:56:15 -0700	[thread overview]
Message-ID: <5453B11F.2040400@boundarydevices.com> (raw)

Hi all,

I just downloaded the release notes for the L3.10.17_1.0.2
kernel release:
	https://community.freescale.com/docs/DOC-102677

The kernel patches are easy to identify, and rebasing our
3.10.17_1.0.1_ga branch on top of them was pretty trivial.

The documentation (file i.MX_6_Yocto_Project_Patch_Release.pdf)
refers to updates to updates though:

	• Graphics: gpu-viv-bin-mx6q, 3.10.17_1.0.2
	• Graphics: gpu-viv-g2d, 3.10.17_1.0.2
	• Graphics: Xorg-driver, 3.10.17_1.0.2

A quick scan of the kernel patches doesn't show any
obvious ABI changes, but since some bits are only
accessible through the closed-source libraries, it's
hard to tell.

In particular, it's not clear whether the changes (additions) to
enum _gcePATCH_ID require a simultaneous kernel/library update.

If so, then I'm not sure how/when to push an update to
meta-fsl-arm-extra for our kernel, since it will need to
be coordinated with meta-fsl-arm/recipes-graphics (and
probably other vendor kernels).

Please advise,


Eric


             reply	other threads:[~2014-10-31 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 15:56 Eric Nelson [this message]
2014-10-31 19:10 ` L3.10.17_1.0.2 Release ABI changes Lauren Post
2014-10-31 22:45   ` Eric Nelson

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=5453B11F.2040400@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --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.