linux-mips
[Top] [All Lists]

(no subject)

To: ralf@linux-mips.org
Subject: (no subject)
From: Brian Murphy <brm@murphy.dk>
Date: Tue, 06 Apr 2004 21:56:36 +0200
Cc: brian@murphy.dk, linux-mips@linux-mips.org
Original-recipient: rfc822;linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org
Hi Ralf,
        the arbitrary change of lasat machine numbers in revision 1.70 
of bootinfo.h means the lasat machines don't get very far in the boot
process. I use this number as an index into several arrays to dynamically
set up the minor hardware differences between the two machines, 
it being off by one causes a horrible crash the first time one of the 
values is used.

Was there a good reason for the change or can you apply the following patch
to allow these systems to boot...?

/Brian

Index: include/asm-mips/bootinfo.h
===================================================================
RCS file: /cvs/linux/include/asm-mips/bootinfo.h,v
retrieving revision 1.73
diff -u -r1.73 bootinfo.h
--- include/asm-mips/bootinfo.h 15 Mar 2004 07:55:26 -0000      1.73
+++ include/asm-mips/bootinfo.h 6 Apr 2004 19:46:13 -0000
@@ -200,8 +200,8 @@
  * Valid machtype for group LASAT
  */
 #define MACH_GROUP_LASAT       21
-#define  MACH_LASAT_100                1       /* Masquerade 
II/SP100/SP50/SP25 */
-#define  MACH_LASAT_200                2       /* Masquerade PRO/SP200 */
+#define  MACH_LASAT_100                0       /* Masquerade 
II/SP100/SP50/SP25 */
+#define  MACH_LASAT_200                1       /* Masquerade PRO/SP200 */
 
 /*
  * Valid machtype for group TITAN

<Prev in Thread] Current Thread [Next in Thread>
  • (no subject), Brian Murphy <=