[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Release Notes patch for Sparc issues not applied



On Sunday 15 May 2005 13:15, Frans Pop wrote:
> In [1] I submitted 2 patches for the Release Notes. It looks like only
> one of those was applied.

Oops. I now see that the patch _was_ applied, but ended up in the wrong 
location. It was intended to go in the chapter on new installations.

I still think that is more logical. The attached patch will move the text 
to its intended place. (The patch in my previous mail can be ignored.)

Cheers,
FJP

--- release-notes.en.sgml.orig	2005-05-15 14:52:32.181765767 +0200
+++ release-notes.en.sgml	2005-05-15 14:53:29.295509170 +0200
@@ -184,6 +184,37 @@
         <prgn>boot-floppies</prgn> has been replaced by a new componentized and
         more powerful installation system called <prgn>debian-installer</prgn>.</p>
 
+<![ %sparc [ 
+      <sect id="sparc_kbd"><heading>Issues with keyboards on &arch-title;</heading>
+
+        <p>There are several issues with keyboard selection during installation.</p>
+
+        <p>The first issue is with USB keyboards by Sun as used on for example
+        SunBlade systems. When installing using the default 2.4 kernel, these are
+        incorrectly "recognized" by the installer as regular Sun keyboards.
+        A workaround is documented in the Installation Guide (see link above,
+        chapter "Using the Debian Installer").</p>
+
+        <p>The second issue is kernel related. Kernels in the 2.6 series use
+        a different input layer that makes all keyboards look like "normal"
+        PC keyboards. This means that if you boot the installer with a 2.4
+        kernel and configure it for a Sun or USB keyboard and later (in expert
+        mode) select a 2.6 kernel for the new system, you will very likely end
+        up with a non-working keyboard after reboot.</p>
+
+      </sect>
+
+      <sect id="sparc_fb"><heading>Issues with framebuffer on &arch-title;</heading>
+
+        <p>Because of display problems on some systems, framebuffer support is
+        disabled by default for &arch-title;. This can result in ugly display on
+        systems that do properly support the framebuffer, like those with ATI
+        graphical cards. If you see display problems in the installer, you can try
+        booting the installer with parameter "debian-installer/framebuffer=true".</p>
+
+      </sect>
+]]>
+
       </chapt>
 
 
@@ -701,36 +732,6 @@
 ]]>
         </sect>
 ]]>
-<![ %sparc [ 
-      <sect id="sparc_kbd"><heading>Issues with keyboards on &arch-title;</heading>
-
-        <p>There are several issues with keyboard selection during installation.</p>
-
-        <p>The first issue is with USB keyboards by Sun as used on for example
-        SunBlade systems. These are incorrectly "recognized" by the installer
-        as regular Sun keyboards. A workaround is documented in the Installation
-        Guide (see link above, chapter "Using the Debian Installer").</p>
-
-        <p>The second issue is kernel related. Kernels in the 2.6 series use
-        a different input layer that makes all keyboards look like "normal"
-        PC keyboards. This means that if you boot the installer with a 2.4
-        kernel and configure it for a Sun or USB keyboard and later (in expert
-        mode) select a 2.6 kernel for the new system, you will very likely end
-        up with a non-working keyboard after reboot.</p>
-
-      </sect>
-
-      <sect id="sparc_fb"><heading>Issues with framebuffer on &arch-title;</heading>
-
-        <p>Because of display problems on some systems, framebuffer support is
-        disabled by default for &arch-title;. This can result in ugly display on
-        systems that do properly support the framebuffer, like those with ATI
-        graphical cards. If you see display problems in the installer, you can try
-        booting the installer with parameter "debian-installer/framebuffer=true".</p>
-
-      </sect>
-]]>
-
 
         </chapt>
 

Attachment: pgpPHTcqxgTia.pgp
Description: PGP signature


Reply to: