From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 6/7] linux-yocto/3.19: CONFIG_ATA_BMDMA and gcc5 ARM64
Date: Thu, 21 May 2015 15:08:56 -0400 [thread overview]
Message-ID: <b36c8a68c82eb1454e0c842ab2a390fc772a159e.1432235097.git.bruce.ashfield@windriver.com> (raw)
In-Reply-To: <cover.1432235097.git.bruce.ashfield@windriver.com>
Integrating the following commit to remove a ATA configuration warning:
common-pc-drivers: Enable CONFIG_ATA_BMDMA
Enabling the ATA_BMDMA re-enables ATA_PIIX which was getting
disabled
Signed-off-by: Saul Wold <sgw@linux.intel.com>
And the following to fix the ARM64 gcc5 boot:
arm64: psci: move psci firmware calls out of line
An arm64 allmodconfig fails to build with GCC 5 due to __asmeq
assertions in the PSCI firmware calling code firing due to mcount
preambles breaking our assumptions about register allocation of
function
arguments:
/tmp/ccDqJsJ6.s: Assembler messages:
/tmp/ccDqJsJ6.s:60: Error: .err encountered
/tmp/ccDqJsJ6.s:61: Error: .err encountered
/tmp/ccDqJsJ6.s:62: Error: .err encountered
/tmp/ccDqJsJ6.s:99: Error: .err encountered
/tmp/ccDqJsJ6.s:100: Error: .err encountered
/tmp/ccDqJsJ6.s:101: Error: .err encountered
This patch fixes the issue by moving the PSCI calls out-of-line into
their own assembly files, which are safe from the compiler's
meddling
fingers.
Reported-by: Andy Whitcroft <apw@canonical.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Armin Kuter <akuster@mvista.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb | 4 ++--
meta/recipes-kernel/linux/linux-yocto_3.19.bb | 18 +++++++++---------
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb
index e55a75a74e4e..bb567d67a3fd 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.19.bb
@@ -9,8 +9,8 @@ LINUX_VERSION ?= "3.19.5"
KMETA = "meta"
KCONF_BSP_AUDIT_LEVEL = "2"
-SRCREV_machine ?= "374b5d0e09ea016975f3d5ab5544968f31054f52"
-SRCREV_meta ?= "7215fe431391a322c7e39f410e7b8f2a2b507892"
+SRCREV_machine ?= "a3f6f39fc369dba2816908bc1b324e0170aaa27d"
+SRCREV_meta ?= "44879ee54dce8e11695dcb476d1b178a48a71f6a"
PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_3.19.bb b/meta/recipes-kernel/linux/linux-yocto_3.19.bb
index 72fe25ac867f..8d8a8c5901d1 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.19.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.19.bb
@@ -11,15 +11,15 @@ KBRANCH_qemux86 ?= "standard/common-pc"
KBRANCH_qemux86-64 ?= "standard/common-pc-64/base"
KBRANCH_qemumips64 ?= "standard/mti-malta64"
-SRCREV_machine_qemuarm ?= "00d625a9e909ff5cbf138cb20dc54e10f30638b3"
-SRCREV_machine_qemuarm64 ?= "374b5d0e09ea016975f3d5ab5544968f31054f52"
-SRCREV_machine_qemumips ?= "76bf3763b224e6d15c060206015f787e8968a4d7"
-SRCREV_machine_qemuppc ?= "6188d8bb5f774f0f760225f34371e94fcf8615d4"
-SRCREV_machine_qemux86 ?= "374b5d0e09ea016975f3d5ab5544968f31054f52"
-SRCREV_machine_qemux86-64 ?= "374b5d0e09ea016975f3d5ab5544968f31054f52"
-SRCREV_machine_qemumips64 ?= "623f6699ea6c4148579c8ede54ccfe0f3784b531"
-SRCREV_machine ?= "374b5d0e09ea016975f3d5ab5544968f31054f52"
-SRCREV_meta ?= "7215fe431391a322c7e39f410e7b8f2a2b507892"
+SRCREV_machine_qemuarm ?= "97428dbb2231f8a715de9db66f3c2358e4927716"
+SRCREV_machine_qemuarm64 ?= "a3f6f39fc369dba2816908bc1b324e0170aaa27d"
+SRCREV_machine_qemumips ?= "a4573b23f8fa35a6e93131fac2f1c0f1d5115fea"
+SRCREV_machine_qemuppc ?= "8bbd8a1369c773dbe8bed27b613aa4b7dd175670"
+SRCREV_machine_qemux86 ?= "a3f6f39fc369dba2816908bc1b324e0170aaa27d"
+SRCREV_machine_qemux86-64 ?= "a3f6f39fc369dba2816908bc1b324e0170aaa27d"
+SRCREV_machine_qemumips64 ?= "62681c2cfa32bee03aee368b704228bc91c2483f"
+SRCREV_machine ?= "a3f6f39fc369dba2816908bc1b324e0170aaa27d"
+SRCREV_meta ?= "44879ee54dce8e11695dcb476d1b178a48a71f6a"
SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.19.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta"
--
2.1.0
next prev parent reply other threads:[~2015-05-21 19:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 19:08 [PATCH 0/7] linux-yocto: consolidated pull request Bruce Ashfield
2015-05-21 19:08 ` [PATCH 1/7] linux-yocto/3.14: cavium and configuration changes Bruce Ashfield
2015-05-21 19:08 ` [PATCH 2/7] linux-yocto/3.19: braswell DRM/i915 Graphics fixes Bruce Ashfield
2015-05-21 19:08 ` [PATCH 3/7] linux-yocto-custom: clarify bbappend versus copy in comments Bruce Ashfield
2015-05-21 21:55 ` Andre McCurdy
2015-05-22 0:59 ` Bruce Ashfield
2015-05-22 1:19 ` Andre McCurdy
2015-05-22 1:31 ` Bruce Ashfield
2015-05-21 19:08 ` [PATCH 4/7] linux-yocto: drop suggestion of devshell for patch failures Bruce Ashfield
2015-05-21 19:08 ` [PATCH 5/7] linux-yocto/3.19: Braswell DRM fixes Bruce Ashfield
2015-05-21 19:08 ` Bruce Ashfield [this message]
2015-05-21 19:08 ` [PATCH 7/7] linux-yocto/3.19: NFC config, Braswell fixes and axxia support Bruce Ashfield
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=b36c8a68c82eb1454e0c842ab2a390fc772a159e.1432235097.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox