linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Tobler <a.tobler@schweiz.ch>
To: Cort Dougan <cort@ppc.kernel.org>, Ani Joshi <ajoshi@shell.unixbox.com>
Cc: Linux -Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.3.25 builds
Date: Wed, 03 Nov 1999 23:13:24 +0100	[thread overview]
Message-ID: <3820B383.E7B64A69@schweiz.ch> (raw)
In-Reply-To: 19991103134212.A28448@chimaera.ppc.kernel.org


Hi Cort and others,

right now I'm in the situation that 2.3.25 seems to compile and to boot
on a 7200. Booting is going on....
Ok up. 

I included the patches from Ani except the fbmem and all others which
refused to patch with: patch -p1 -F 3 -l --verbose <patch.file
The important for me were the pgtable.h and the fbmem.c. I use the
pmac_config as default conf with ramdisk support off. And only the
platinumfb, the scsi is Mac like & with Adaptec aic78xx. Which is my
used Disk-Controller.

Now it is up with the horrible message that I have 2GB of Mem..... (only
80MB are real) ((top report))
The fbmem.patch I took from  <kernel@kvack.org> as on the list (kernel)
this day. The latest at 14:19 EST

Thanks and sorry for the moody question the day before.

Finally I return for work to 2.2.14pre3 for daily work. Wallstreet
reports will follow as soon I can get some spare time not coding for Win :-(


Cort Dougan wrote:
> 
> The next release should build for PPC.  There were some swap changes that
> had to be cleaned up.  The Linus 2.3.x trees are now nearly up-to-date with
> my tree so it shouldn't be released with ppc broken as often now.
>


Andreas

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

      reply	other threads:[~1999-11-03 22:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <381F63A2.BE4A2AD7@schweiz.ch>
1999-11-03 20:42 ` 2.3.25 builds Cort Dougan
1999-11-03 22:13   ` Andreas Tobler [this message]

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=3820B383.E7B64A69@schweiz.ch \
    --to=a.tobler@schweiz.ch \
    --cc=ajoshi@shell.unixbox.com \
    --cc=cort@ppc.kernel.org \
    --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).