From: Peter Allworth <linsol@zeta.org.au>
To: duncanp@research.canon.com.au
Cc: linuxppc-embedded@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: Low memory problems in 8xx Linux
Date: Wed, 02 Feb 2000 11:25:04 +1100 [thread overview]
Message-ID: <38977960.40E014A1@zeta.org.au> (raw)
In-Reply-To: 20000201235813.4F5611B51A@elph.research.canon.com.au
duncanp@research.canon.com.au wrote:
>
> Dan,
>
> On 1 Feb, Dan Malek wrote:
> > I have already incorporated most of these into 2.3.xx
> > kernel, and a 2.2.13 version that I will update as a tar file
> > on a server.
>
> would you mind posting a diff against the current 2.2.13 kernel on the
> ftp server when you do this as well? we've got a kernel in CVS here (i
> imagine plently of others are doing this too), and it would be easier
> for us if we can patch it.
>
> Dunk.
Dunk,
If you need the MMU patches straight-away, I've put them on
http://www.zeta.org.au/~linsol
They only work against cllf-2.2.13 for now. Marcus Sundberg has sent
me a revised patch which should work for other 2.2 kernels (caveat emptor).
I'll try to add that asap.
Cheers,
PeterA.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-02 0:25 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 [this message]
2000-02-08 10:01 ` Jesper Skov
2000-02-09 0:00 ` Peter Allworth
2000-02-09 8:43 ` Jesper Skov
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=38977960.40E014A1@zeta.org.au \
--to=linsol@zeta.org.au \
--cc=duncanp@research.canon.com.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).