From: Michel Lanners <mlan@cpu.lu>
To: paulus@linuxcare.com.au
Cc: linuxppc-dev@lists.linuxppc.org
Subject: PATCH: final version of l2cr cmd line
Date: Sun, 3 Sep 2000 15:15:45 +0200 (CEST) [thread overview]
Message-ID: <200009031315.PAA00925@piglet.grunz.lu> (raw)
[-- Attachment #1: Type: TEXT/plain, Size: 797 bytes --]
Hi Paul,
Since BenH fixed the _set_L2CR() function, I have been able to shorten
the l2cr command line code. Attached is the patch vs. your current 2.4
rsync tree. I've not been able for a long time to boot a 2.4 kernel, but
it never crashed in this part ;-)
Anyway, all the patch does is to actually enable the processing of l2cr=
command lines.
Thanks for including this if you have no objection.
Cheers
Michel
PS Patch also posted to sourceforge.
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
[-- Attachment #2: l2cr.diff --]
[-- Type: TEXT/plain, Size: 575 bytes --]
diff -uNr linux-2.4.paul/arch/ppc/kernel/setup.c linux/arch/ppc/kernel/setup.c
--- linux-2.4.paul/arch/ppc/kernel/setup.c Tue Aug 8 07:46:33 2000
+++ linux/arch/ppc/kernel/setup.c Sat Sep 2 11:26:13 2000
@@ -661,11 +661,13 @@
{
unsigned long val = simple_strtoul(str, NULL, 0);
printk(KERN_INFO "l2cr set to %lx\n", val);
- _set_L2CR(0);
- _set_L2CR(val);
+ _set_L2CR(0); /* force invalidate by disable cache */
+ _set_L2CR(val); /* and enable it */
}
}
+__setup("l2cr=", ppc_setup_l2cr);
+
void __init ppc_init(void)
{
/* clear the progress line */
next reply other threads:[~2000-09-03 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-03 13:15 Michel Lanners [this message]
2000-09-03 13:45 ` PATCH: final version of l2cr cmd line Benjamin Herrenschmidt
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=200009031315.PAA00925@piglet.grunz.lu \
--to=mlan@cpu.lu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com.au \
/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).