Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Elvis Dowson <elvis.dowson@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Elvis Dowson <elvis.dowson@gmail.com>
Subject: [meta-xilinx] xilinx-kernel: Change string comparision checks to use strict POSIX compliance.
Date: Fri,  8 Jun 2012 16:32:21 +0200	[thread overview]
Message-ID: <1339165942-53107-1-git-send-email-elvis.dowson@gmail.com> (raw)

This commit fixes an issue with string comparision checks failing because
of not using strict POSIX compliance, therby failing to copy the device
tree from the hardware model to the linux kernel device tree.

Signed-off-by: Elvis Dowson <elvis.dowson@gmail.com>
---
 classes/xilinx-kernel.bbclass |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/classes/xilinx-kernel.bbclass b/classes/xilinx-kernel.bbclass
index c0e11fe..14f4c7d 100644
--- a/classes/xilinx-kernel.bbclass
+++ b/classes/xilinx-kernel.bbclass
@@ -42,10 +42,12 @@ if [ -n "${XILINX_BSP_PATH}" ]; then
 	if [ "${XILINX_BOARD}" != "unknown" ]; then
 		dts=`find "${XILINX_BSP_PATH}" -name *.dts -print`
 		if [ -e "$dts" ]; then
-			bbnote "Replacing device tree to match hardware model"
-			if [ "${TARGET_ARCH}" == "powerpc" ]; then
+			bbnote "Xilinx BSP device tree located in: ${dts}"
+			if [ "${TARGET_ARCH}" = "powerpc" ]; then
+				bbnote "Replacing linux kernel powerpc device tree to match located hardware model"
 				cp -pP ${dts} ${S}/arch/powerpc/boot/dts/virtex${KERNEL_TARGET}.dts
 			else
+				bbnote "Replacing linux kernel microblaze device tree to match located hardware model"
 				cp -pP ${dts} ${S}/arch/microblaze/platform/generic/${KERNEL_TARGET}.dts
 			fi
 		else
-- 
1.7.9.5




             reply	other threads:[~2012-06-08 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 14:32 Elvis Dowson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-08 14:54 [meta-xilinx] xilinx-kernel: Change string comparision checks to use strict POSIX compliance Elvis Dowson

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=1339165942-53107-1-git-send-email-elvis.dowson@gmail.com \
    --to=elvis.dowson@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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