linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Skov <jskov@redhat.com>
To: Peter Allworth <linsol@zeta.org.au>
Cc: Jesper Skov <jskov@redhat.com>,
	duncanp@research.canon.com.au,
	linuxppc-embedded@lists.linuxppc.org,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: Low memory problems in 8xx Linux
Date: Wed, 9 Feb 2000 09:43:49 +0100 (CET)	[thread overview]
Message-ID: <14497.10437.498606.647038@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <38A0AE0D.2EB99353@zeta.org.au>


>>>>> "Peter" == Peter Allworth <linsol@zeta.org.au> writes:

Peter> Jesper Skov wrote:
>>  >>>>> "Peter" == Peter Allworth <linsol@zeta.org.au> writes:

Peter> <snip>

Peter> If you need the MMU patches straight-away, I've put them on
>>
Peter> http://www.zeta.org.au/~linsol
>>
Peter> They only work against cllf-2.2.13 for now. Marcus Sundberg has
Peter> sent me a revised patch which should work for other 2.2 kernels
Peter> (caveat emptor).  I'll try to add that asap.
>>  Peter and Duncan,
>>
>> The 2.2.13 patch you posted was slightly (but critically) wrong, if
>> I'm not mistaken. The value updated in memory was not reloaded into
>> r21 which is where the code below this snipped expects to find the
>> value.
>>
>> This patch should do the trick. At least my kernel seems to work.

Peter> Jesper,

Peter> Which kernel are you using and which patch file?  (Please
Peter> double-check the readme.txt file.)

I was assuming one of the patches was for
ftp://linuxppc.cs.nmt.edu/pub/linuxppc/embedded/mpc8xx-2.2.13.tgz, but
I don't think either matches very well.

Peter> My http://www.zeta.org.au/~linsol directory contains two
Peter> versions of the patch to head.S. If you are using cllf-2.2.13
Peter> which includes the use of r21 as you've described, then use
Peter> "head.S-patch".

Peter> Marcus Sundberg provided the other file "head.S.non-cllf" which
Peter> is for older kernels that used r20 for the pte and didn't do
Peter> the update of the GUARDED bit. (I need to change the names in
Peter> the diff headers to make this clearer.)

I read the patch and think I understand what's going on, but I don't
see where the GUARDED bits comes in. Maybe I'm missing some subtlety
from other patches (cllf?) and should not use the code at all. I'd
better back it out.

Jesper

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-02-09  8:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-31 15:02 Low memory problems in 8xx Linux Marcus Sundberg
2000-02-01  2:51 ` Peter Allworth
2000-02-01 18:08   ` Marcus Sundberg
2000-02-01 19:47     ` Dan Malek
2000-02-01 23:30       ` Peter Allworth
2000-02-01 23:59         ` Dan Malek
2000-02-01 23:54       ` duncanp
2000-02-02  0:25         ` Peter Allworth
2000-02-08 10:01           ` Jesper Skov
2000-02-09  0:00             ` Peter Allworth
2000-02-09  8:43               ` Jesper Skov [this message]
2000-02-09 23:26                 ` Peter Allworth
2000-02-09  1:11             ` more " Peter Allworth
2000-02-09  5:52               ` Dan Malek
2000-02-09  8:40               ` Jesper Skov
2000-03-22 15:43   ` Residual data Claude Robitaille
2000-03-23 10:36     ` Gabriel Paubert

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=14497.10437.498606.647038@thinktwice.zoftcorp.dk \
    --to=jskov@redhat.com \
    --cc=duncanp@research.canon.com.au \
    --cc=linsol@zeta.org.au \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-embedded@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).