Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: ralf@oss.sgi.com, linux-mips@oss.sgi.com
Subject: [PATCH] wrong EF_CP0_CAUSE offset
Date: Thu, 08 Nov 2001 15:37:00 -0800	[thread overview]
Message-ID: <3BEB171C.CF7949C2@mvista.com> (raw)

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


reg.h has the wrong offset EF_CP0_CAUSE and the wrong pt_regs size.

This seems to be a problem only for mips (32bit) tree.

Drow found this bug, BTW.

Jun

[-- Attachment #2: wrong-EF_CP0_CAUSE-offset.011108.011108.patch --]
[-- Type: text/plain, Size: 465 bytes --]

diff -Nru linux/include/asm-mips/reg.h.orig linux/include/asm-mips/reg.h
--- linux/include/asm-mips/reg.h.orig	Wed Aug 18 16:37:49 1999
+++ linux/include/asm-mips/reg.h	Thu Nov  8 15:23:32 2001
@@ -59,8 +59,8 @@
 #define EF_CP0_EPC		40
 #define EF_CP0_BADVADDR		41
 #define EF_CP0_STATUS		42
-#define EF_CP0_CAUSE		44
+#define EF_CP0_CAUSE		43
 
-#define EF_SIZE			180	/* size in bytes */
+#define EF_SIZE			176	/* size in bytes */
 
 #endif /* __ASM_MIPS_REG_H */

             reply	other threads:[~2001-11-08 23:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08 23:37 Jun Sun [this message]
2001-11-09  7:08 ` [PATCH] wrong EF_CP0_CAUSE offset Ralf Baechle

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=3BEB171C.CF7949C2@mvista.com \
    --to=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.com \
    /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