public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com>
To: linux-m68k@vger.kernel.org
Subject: [coldfire] add byte reverse
Date: Thu, 29 Jan 2009 16:42:18 +0000	[thread overview]
Message-ID: <4981DC6A.1060507@codesourcery.com> (raw)

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

We've been using this patch for quite some time, because I thought
submission was being handled by someone else.

I see the swab_no.h header file already contains these bits, so it's
not needed there.

nathan
-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::         CodeSourcery


[-- Attachment #2: 0001-add-m68k-byterev.patch --]
[-- Type: text/x-patch, Size: 904 bytes --]


Signed-off-by: Nathan Sidwell <nathan@codesourcery.com>
---
 arch/m68k/include/asm/swab_mm.h |    9 +++++++++
 1 files changed, 9 insertions(+), 0 deletions(-)

diff --git a/arch/m68k/include/asm/swab_mm.h b/arch/m68k/include/asm/swab_mm.h
index 7221e30..a391274 100644
--- a/arch/m68k/include/asm/swab_mm.h
+++ b/arch/m68k/include/asm/swab_mm.h
@@ -6,11 +6,20 @@
 
 #define __SWAB_64_THRU_32__
 
+#if defined (__mcfisaaplus__) || defined (__mcfisac__)
+static inline __attribute_const__ __u32 __arch_swab32(__u32 val)
+{
+	__asm__ ("byterev %0" : "=d" (val) : "0" (val));
+	return val;
+}
+#define __arch_swab32 __arch_swab32
+#elif !defined (__mcoldfire__)
 static inline __attribute_const__ __u32 __arch_swab32(__u32 val)
 {
 	__asm__("rolw #8,%0; swap %0; rolw #8,%0" : "=d" (val) : "0" (val));
 	return val;
 }
 #define __arch_swab32 __arch_swab32
+#endif
 
 #endif /* _M68K_SWAB_H */
-- 
1.5.2.5


                 reply	other threads:[~2009-01-29 16:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4981DC6A.1060507@codesourcery.com \
    --to=nathan@codesourcery.com \
    --cc=linux-m68k@vger.kernel.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