Attached is a patch which describes the kernel upgrade procedure for 
mips and mipsel.

Gruesse,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/
Index: release-notes.ent
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/release-notes.ent,v
retrieving revision 1.7
diff -u -r1.7 release-notes.ent
--- release-notes.ent   18 May 2005 23:48:21 -0000      1.7
+++ release-notes.ent   21 May 2005 19:08:40 -0000
@@ -157,6 +157,10 @@
 <![ %i386    [ <!entity % glibcneedsnewkernel "INCLUDE"> ]]>
 <![ %hppa    [ <!entity % glibcneedsnewkernel "INCLUDE"> ]]>
 <![ %hppa    [ <!entity % upgradekernel "INCLUDE"> ]]>
+<![ %mips    [ <!entity % glibcneedsnewkernel "INCLUDE"> ]]>
+<![ %mips    [ <!entity % upgradekernel "INCLUDE"> ]]>
+<![ %mipsel  [ <!entity % glibcneedsnewkernel "INCLUDE"> ]]>
+<![ %mipsel  [ <!entity % upgradekernel "INCLUDE"> ]]>
 <![ %sparc   [ <!entity % glibcneedsnewkernel "INCLUDE"> ]]>
 <![ %sparc   [ <!entity % upgradekernel "INCLUDE"> ]]>
                <!entity % glibcneedsnewkernel "IGNORE">
Index: en/release-notes.en.sgml
===================================================================
RCS file: 
/cvs/debian-doc/ddp/manuals.sgml/release-notes/en/release-notes.en.sgml,v
retrieving revision 1.33
diff -u -r1.33 release-notes.en.sgml
--- en/release-notes.en.sgml    18 May 2005 23:48:21 -0000      1.33
+++ en/release-notes.en.sgml    21 May 2005 19:08:43 -0000
@@ -360,6 +360,21 @@
           CPUs or above.</p>
 ]]>
 
+<![ %mips [
+        <p>On MIPS machines you will need to upgrade to a newer kernel
+        version first before upgrading the system. This is because of a
+        inconsistent definition of the inter process communication of
+        the new libc and the kernel so you need an updated kernel first
+        that provides the correct definition.</p>
+]]>
+<![ %mipsel [
+        <p>On MIPSEL machines you will need to upgrade to a newer kernel
+        version first before upgrading the system. This is because of a
+        inconsistent definition of the inter process communication of
+        the new libc and the kernel so you need an updated kernel first
+        that provides the correct definition.</p>
+]]>
+
 <![ %upgradekernel [
           <sect2 id="kernel-upgrade"><heading>Upgrading the kernel</heading>
 
@@ -992,6 +1007,8 @@
 
     <appendix id="kernel-upgrade-howto"><heading>Upgrading the kernel</heading>
 
+<![ %not-mips [
+<![ %not-mipsel [
           <p><strong>The information in this appendix is relevant only for
           if, for a successful upgrade of the system, you need to upgrade the
           kernel <em/before/ upgrading the system. Please read
@@ -1000,10 +1017,22 @@
 
           <p>The following instructions explain step by step how to use the
           available backported tools to install the newer kernel.</p>
+]]>
+]]>
+<![ %mips [
+          <p>The following instructions explain step by step how to
+          install a newer kernel prior to the upgrade.</p>
+]]>
+<![ %mipsel [
+          <p>The following instructions explain step by step how to
+          install a newer kernel prior to the upgrade.</p>
+]]>
 
           <p><taglist>
                <tag>Download and install the needed packages</tag>
 
+<![ %not-mips [
+<![ %not-mipsel [
                <item><p><em>with apt</em>: to install the packages with
                <prgn>apt</prgn> or one of its frontends, add the following line
                in your <file>/etc/apt/sources.list</file>:
@@ -1014,6 +1043,61 @@
 # deb-src &url-kernel-upgrade;
                </example>
 
+]]>
+]]>
+
+<![ %mips [
+               <item><p>If you have an <em>SGI IP22</em> you should
+               first prepare it to boot with <package>arcboot</package>,
+               and not to boot the kernel directly. <package>arcboot</package>
+               is available in woody so you can install it in the usual
+               ways.</p>
+
+               <p>Fetch the current kernel package from sarge from
+               the Debian mirror of your choice. The available
+               packages are</p>
+
+               <p><list>
+               <item><url 
id="http://ftp.debian.org/debian/pool/main/k/kernel-patch-2.4.27-mips/kernel-image-2.4.27-r4k-ip22_2.4.27-8.040815-1_mips.deb";>
 for R4XX0 processors and the SGI IP22 subarchitecture like the Indy and 
Indigo2.</item>
+               <item><url 
id="http://ftp.debian.org/debian/pool/main/k/kernel-patch-2.4.27-mips/kernel-image-2.4.27-r5k-ip22_2.4.27-8.040815-1_mips.deb";>
 for R5000 processors and the SGI IP22 subarchitecture like the Indy and 
Indigo2.</item>
+               <item><url 
id="http://ftp.debian.org/debian/pool/main/k/kernel-patch-2.4.27-mips/kernel-image-2.4.27-sb1-swarm-bn_2.4.27-8.040815-1_mips.deb";>
 for the Broadcom BCM91250A (aka SWARM) pass 2.2.</item>
+
+               </list></p>
+
+               <p>Then install the package with <tt>dpkg -i</tt>. It will
+               complain about module mismatches (from modutils) and
+               ask if the installation should continue, with a default
+               of <tt>NO</tt>. Say <tt>YES</tt> here, the modules are
+               not used for basic system operation needed for an upgrade.
+               </p>
+]]>
+
+<![ %mipsel [
+               <item><p>Fetch the current kernel package from sarge from
+               the Debian mirror of your choice. The available
+               packages are</p>
+
+               <p><list>
+               <item><url 
id="http://ftp.debian.org/debian/pool/main/k/kernel-patch-2.4.27-mips/kernel-image-2.4.27-r3k-kn02_2.4.27-8.040815-1_mipsel.deb";>
 for R3000 based DECstations with KN02 (or compatible) mainboard, such as the 
DECstation 5000/1xx series with xx=20,25,33 and the DECstation 5000/240.</item>
+               <item><url 
id="http://ftp.debian.org/debian/pool/main/k/kernel-patch-2.4.27-mips/kernel-image-2.4.27-r4k-kn04_2.4.27-8.040815-1_mipsel.deb";>
 for R4X00 based DECstations with KN04 (or compatible) mainboard, such as the 
DECstation 5000/150, the Personal DECstation 5000/50 and the DECstation 
5000/260.</item>
+               <item><url 
id="http://ftp.debian.org/debian/pool/main/k/kernel-patch-2.4.27-mips/kernel-image-2.4.27-r5k-cobalt_2.4.27-8.040815-1_mipsel.deb";>
 for MIPS based Cobalt machines (such as the Qube, RaQ, Qube2 and RaQ2).</item>
+               <item><url 
id="http://ftp.debian.org/debian/pool/main/k/kernel-patch-2.4.27-mips/kernel-image-2.4.27-r5k-lasat_2.4.27-8.040815-1_mipsel.deb";>
 for R5000 processors on the Lasat Masquerade Pro.</item>
+               <item><url 
id="http://ftp.debian.org/debian/pool/main/k/kernel-patch-2.4.27-mips/kernel-image-2.4.27-sb1-swarm-bn_2.4.27-8.040815-1_mipsel.deb";>
 for the Broadcom BCM91250A (aka SWARM) pass 2.2.</item>
+               <item><url 
id="http://ftp.debian.org/debian/pool/main/k/kernel-patch-2.4.27-mips/kernel-image-2.4.27-xxs1500_2.4.27-8.040815-1_mipsel.deb";>
 for  the Au1500 based XXS1500 board.</item>
+
+               </list></p>
+
+               <p>Then install the package with <tt>dpkg -i</tt>. It will
+               complain about module mismatches (from modutils) and
+               ask if the installation should continue, with a default
+               of <tt>NO</tt>. Say <tt>YES</tt> here, the modules are
+               not used for basic system operation needed for an upgrade.
+               </p>
+]]>
+
+
+<![ %not-mips [
+<![ %not-mipsel [
 <![ %sparc [
                Then install the packages
                <package>kernel-image-2.4.27-2-sparc32</package>,
@@ -1056,6 +1140,8 @@
                <package>initrd-tools</package> depends on 
<package>cramfsprogs</package>.
                All other dependencies can be satisfied with packages from
                &oldreleasename; in the usual way.</p>
+]]>
+]]>
 ]]>
                </item>
 

Reply via email to