From: Christian Kujau <evil@g-house.de>
To: Remco Post <r.post@sara.nl>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.6 PReP issues, still freezing
Date: Mon, 01 Dec 2003 15:23:22 +0100 [thread overview]
Message-ID: <3FCB4EDA.5000909@g-house.de> (raw)
In-Reply-To: <20031201121119.768fb4c1.r.post@sara.nl>
Remco Post wrote:
> I stopped complaining a while back (2.5.60 something) since I got absolutely
did you get any further?
i saw one of your posts:
http://www.cs.helsinki.fi/linux/linux-kernel/2002-38/0289.html
yes, the "not-compiling" issues during 2.5.3x. 2.5.38 is only compiling
a "vmlinux.gz", but no zImage.prep here. and this vmlinux.gz is
worthless. do you mind sending in your fix?
> no response. I'm one of the lucky (?) few who have a motorola powerstack
> (II) mobo.
root@sheep:~# cat /proc/cpuinfo
processor : 0
cpu : 604r
clock : ???
revision : 49.2 (pvr 0009 3102)
bogomips : 299.00
machine : PReP Utah (Powerstack II Pro4000)
l2 cache : 512KiB, parity disabled SRAM:synchronous, pipelined,
no parity
....from ebay :-)
Christian.
--
BOFH excuse #375:
Root name servers corrupted.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-01 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 13:21 2.6 PReP issues, still freezing Christian Kujau
2003-12-01 11:11 ` Remco Post
2003-12-01 14:23 ` Christian Kujau [this message]
2003-12-01 14:52 ` Remco Post
2003-12-01 19:16 ` Tom Rini
2003-12-01 21:05 ` Remco Post
2003-12-01 22:24 ` Remco Post
2003-12-01 22:47 ` Remco Post
2003-12-01 23:17 ` Christian Kujau
2003-12-02 0:26 ` Remco Post
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=3FCB4EDA.5000909@g-house.de \
--to=evil@g-house.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=r.post@sara.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.