From: leigh@solinno.co.uk (Leigh Brown)
To: trini@kernel.crashing.org
Cc: paulus@samba.org, linuxppc-dev@lists.linuxppc.org, barbieri@gmail.com
Subject: [10/9] Support for old IBM PReP boxes
Date: Fri, 30 Jul 2004 18:06:18 +0100 [thread overview]
Message-ID: <20040730170618.GA9009@george.solinno.co.uk> (raw)
Will something like this do? It won't be that helpful for IBM PRePs,
but it should be an acceptable fallback for Motorolas. I put the test
after it's determined whether it's an IBM or Motorola PReP on the off
chance there is an IBM PReP that doesn't need any residual data to
function properly.
diff -urNX /home/leigh/.diffex linux-2.6.8-rc2-bk8.prev/arch/ppc/Kconfig linux-2.6.8-rc2-bk8/arch/ppc/Kconfig
--- linux-2.6.8-rc2-bk8.prev/arch/ppc/Kconfig 2004-07-29 20:38:27.000000000 +0100
+++ linux-2.6.8-rc2-bk8/arch/ppc/Kconfig 2004-07-30 17:55:42.000000000 +0100
@@ -853,10 +853,11 @@
Some PReP systems have residual data passed to the kernel by the
firmware. This allows detection of memory size, devices present and
other useful pieces of information. Sometimes this information is
- not present or incorrect.
+ not present or incorrect, in which case it could lead to the machine
+ behaving incorrectly. If this happens, either disable PREP_RESIDUAL
+ or pass the 'noresidual' option to the kernel.
- Unless you expect to boot on a PReP system, there is no need to
- select Y.
+ If you are running a PReP system, say Y here, otherwise say N.
config PROC_PREPRESIDUAL
bool "Support for reading of PReP Residual Data in /proc"
Binary files linux-2.6.8-rc2-bk8.prev/arch/ppc/platforms/.prep_setup.c.swp and linux-2.6.8-rc2-bk8/arch/ppc/platforms/.prep_setup.c.swp differ
diff -urNX /home/leigh/.diffex linux-2.6.8-rc2-bk8.prev/arch/ppc/platforms/prep_setup.c linux-2.6.8-rc2-bk8/arch/ppc/platforms/prep_setup.c
--- linux-2.6.8-rc2-bk8.prev/arch/ppc/platforms/prep_setup.c 2004-07-29 20:55:49.000000000 +0100
+++ linux-2.6.8-rc2-bk8/arch/ppc/platforms/prep_setup.c 2004-07-30 17:58:51.000000000 +0100
@@ -1134,6 +1134,10 @@
_prep_type = _PREP_Motorola;
}
+ /* Switch off all residual data processing if the user requests it */
+ if (strstr(cmd_line, "noresidual") != NULL)
+ res = NULL;
+
/* Initialise progress early to get maximum benefit */
prep_set_bat();
ibm_statusled_init();
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2004-07-30 17:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040730170618.GA9009@george.solinno.co.uk \
--to=leigh@solinno.co.uk \
--cc=barbieri@gmail.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).