From: <gerg@snapgear.com>
To: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org
Cc: Greg Ungerer <gerg@uclinux.org>
Subject: [PATCH v2 2/3] m68k: use jbsr to call functions instead of bsrl
Date: Fri, 18 May 2012 14:22:50 +1000 [thread overview]
Message-ID: <1337314971-11087-3-git-send-email-gerg@snapgear.com> (raw)
In-Reply-To: <1337314971-11087-1-git-send-email-gerg@snapgear.com>
From: Greg Ungerer <gerg@uclinux.org>
There is a few places that the m68k entry code uses the bsrl instruction
to call other functions. That instruction is only supported on 68020 and
higher CPU types. If we use jbsr instead the code will be clean for all
68k and ColdFire CPU types.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
---
arch/m68k/kernel/entry_mm.S | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/m68k/kernel/entry_mm.S b/arch/m68k/kernel/entry_mm.S
index f3cd173..2385539 100644
--- a/arch/m68k/kernel/entry_mm.S
+++ b/arch/m68k/kernel/entry_mm.S
@@ -55,7 +55,7 @@ ENTRY(buserr)
SAVE_ALL_INT
GET_CURRENT(%d0)
movel %sp,%sp@- | stack frame pointer argument
- bsrl buserr_c
+ jbsr buserr_c
addql #4,%sp
jra ret_from_exception
@@ -63,7 +63,7 @@ ENTRY(trap)
SAVE_ALL_INT
GET_CURRENT(%d0)
movel %sp,%sp@- | stack frame pointer argument
- bsrl trap_c
+ jbsr trap_c
addql #4,%sp
jra ret_from_exception
--
1.7.0.4
next prev parent reply other threads:[~2012-05-18 4:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 4:22 [PATCH v2 00/03]: clean up and merge the MMU and non-MMU versions of entry.S gerg
2012-05-18 4:22 ` [PATCH v2 1/3] m68k: use some direct calls to ret_from_exception in entry code gerg
2012-05-20 9:19 ` Geert Uytterhoeven
2012-05-18 4:22 ` gerg [this message]
2012-05-20 9:15 ` [PATCH v2 2/3] m68k: use jbsr to call functions instead of bsrl Geert Uytterhoeven
2012-05-18 4:22 ` [PATCH v2 3/3] m68k: merge the MMU and non-MMU versions of the entry.S code gerg
2012-05-20 9:22 ` Geert Uytterhoeven
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=1337314971-11087-3-git-send-email-gerg@snapgear.com \
--to=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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