linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: "Wohlgemuth, Jason" <jason_wohlgemuth@gilbarco.com>
Cc: "'Peter Allworth'" <linsol@zeta.org.au>,
	"'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Low Memory / Software Emulation Exception / Performance
Date: Wed, 12 Apr 2000 09:27:54 -0400	[thread overview]
Message-ID: <38F479DA.A68E96BE@netx4.com> (raw)
In-Reply-To: 200004121138.HAA05150@hoover.gilbarco.com


Wohlgemuth, Jason wrote:


> Attached is the patch file you requested, this should bring the head.S
> distributed in mpc8xx-2.2.13 up-to-date with the dirty page fix.


It would be _really_ nice if I could get everyone to use the
MontaVista source distribution.  That has all of these patches
and then some.  This is the source I am using to bring 2.3.xx
up to date (along with patches for board specific updates).  I
believe you can start with ftp.mvista.com, then find the RPMs
in the CDK directory for the 8xx.

Through my own fault, there are too many kernel sources floating
around.  I would like to stop that.  I should finally have this
corrected in the 2.3.xx and subsequent source trees.

Thanks.


	-- Dan

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

  reply	other threads:[~2000-04-12 13:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-12 11:38 Low Memory / Software Emulation Exception / Performance Wohlgemuth, Jason
2000-04-12 13:27 ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-04-11 18:43 Wohlgemuth, Jason
2000-04-12  0:43 ` Peter Allworth
2000-04-11 17:20 Wohlgemuth, Jason
2000-04-11 13:50 Wohlgemuth, Jason
2000-04-11 16:40 ` Marcus Sundberg

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=38F479DA.A68E96BE@netx4.com \
    --to=dan@netx4.com \
    --cc=jason_wohlgemuth@gilbarco.com \
    --cc=linsol@zeta.org.au \
    --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).