linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc dev list <linuxppc-dev@lists.linuxppc.org>,
	Cort Dougan <cort@ladron.cs.nmt.edu>
Subject: [PATCH] l2cr fix for BootX
Date: Wed, 23 Dec 1998 05:03:55 +0100	[thread overview]
Message-ID: <19981223050355.013934@mail.mipsys.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]

Enclosed is a patch to pmac_setup.c and setup.c that

 - removes the relics of the old l2cr=xxxx kernel arg. in setup.c
 - adds code for getting the "l2cr-value" property, currently at the root
of "cpus" node (that's where bootx puts it but this could eventually be
changed since no one uses it yet).

I did put the code in pmad_setup.c to avoid breaking anything on other
arch, you may want to move it to ppc common code since you know it better
than me and you may want to remove the global (i was not sure, I did put
them to allow other processors to read the value too but I don't think
there is any MP G3 available anyway).

With this fix and the latest bootx, G3 upgrade card vendors will be able
to set a preference in BootX prefs file with the L2CR value from their
proprietary MacOS software (PowerLogix is expected to do it soon).
There'll be soon a generic tool for "capturing" the l2cr value under
MacOS and set the appropriate resource in BootX too.

-- 
           E-Mail: <mailto:bh40@calva.net>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>



[-- Attachment #2: l2cr.patch.tgz --]
[-- Type: application/octet-stream, Size: 1094 bytes --]

                 reply	other threads:[~1998-12-23  4:03 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=19981223050355.013934@mail.mipsys.com \
    --to=bh40@calva.net \
    --cc=cort@ladron.cs.nmt.edu \
    --cc=linuxppc-dev@lists.linuxppc.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).