From: Cort Dougan <cort@ppc.kernel.org>
To: Andreas <a.tobler@schweiz.ch>
Cc: Linux -Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.3.25 builds
Date: Wed, 3 Nov 1999 13:42:12 -0700 [thread overview]
Message-ID: <19991103134212.A28448@chimaera.ppc.kernel.org> (raw)
In-Reply-To: <381F63A2.BE4A2AD7@schweiz.ch>; from Andreas on Tue, Nov 02, 1999 at 11:20:22PM +0100
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.
} Hi all,
} sitting here and try to build a 2.3.25 for PPC. No success. The same
} with 2.3.23/24. 2.3.23 worked except I had horrible amounts of Ram (2GB
} iso 80MB). Was to late to figure out the 2.3.24 the 2.3.25 was already
} out. So I tried this one.
} In the beginning not much luck, got some steps further when applying the
} fbmem patch mentioned on this list the earlier the day. (ramdisk support
} was disabled from beginning).
} Later I struggled about pieces in memory.c; pte is not member of.... Ok,
} I found some hints, but as a newbie I saw that there are too many things
} included. Diff showed me too many things changed. So, Paul, Cort, are
} you already aware of?
}
} Another major question I have, what is the 'deciding fact' for releasing
} a new dev kernel? Only one or two/three arch's working? I noticed that a
} few people had also problems building 2.3.25. ( Intel camp) Or, is it
} only the number count? (25 is better than 24?)
} Sorry, this is a bit cynic. But on the 2.2.x I see that there are up to
} at least xy pre's before a new Kernel is released.
}
} This mail is NOT meant as a blame, but I don't know how to treat such
} quick changes on the kernel side. Do I have to wait for a working kernel
} x steps behind the offical kernel?
} Yeah, I know I don't have to, I should contribute .... If I can....
} As said, what is the aim of releasing kernels in such short time stamps?
}
} Regards & thanks for Linux (I still prefer it to MacOS9)
}
} Andreas
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~1999-11-03 20:42 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 ` Cort Dougan [this message]
1999-11-03 22:13 ` 2.3.25 builds Andreas Tobler
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=19991103134212.A28448@chimaera.ppc.kernel.org \
--to=cort@ppc.kernel.org \
--cc=a.tobler@schweiz.ch \
--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).