From: Martin Costabel <costabel@wanadoo.fr>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Re; 2.4.0-test9 on B&W G3
Date: Sat, 23 Sep 2000 07:19:17 +0200 [thread overview]
Message-ID: <39CC3D55.74CD42A2@wanadoo.fr> (raw)
In-Reply-To: 39CBAA3C.2CC16A34@wanadoo.fr
Martin Costabel wrote:
> Glad to hear that the linuxppc_2_3 bk tree is not dead. I was just going
> to ask about it, because since 2 weeks it has remained at -test8 which
> is feared for its terrible mailbox-eating habits.
>
> On the other hand, I am running a kernel obtained from this tree by
> applying just the "official" test9-pre1 patch, and I have now an uptime
> of 4 days, 22:02. This is the longest uptime I ever had with a 2.3/4
> kernel. No spontaneous freezes so far <knocking on wood>.
OK, I asked for it: As of right now, the bk linux_2_3 bk tree is at
2.4.0-test9-pre4. It is less dangerous than -test8 insofar as it doesn't
boot :-)
It compiles if one upgrades arch/ppc/kernel/time.c to, for example, the
one from Paul's linux-pmac-devel tree.
But it doesn't recognize my SCSI disk. I think it's a feature of
-test9-pre4 that SCSI is broken. This is patched in pre5 or pre6. So
I'll wait or use Paul's drivers/scsi directory...
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-23 5:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-22 16:47 Re; 2.4.0-test9 on B&W G3 Benjamin Herrenschmidt
2000-09-22 18:51 ` Martin Costabel
2000-09-23 5:19 ` Martin Costabel [this message]
2000-09-23 5:31 ` Tom Rini
2000-09-23 5:57 ` Martin Costabel
2000-09-23 14:08 ` MOL on 2.4/603 Samuel Rydh
2000-09-23 12:38 ` Re; 2.4.0-test9 on B&W G3 Geert Uytterhoeven
2000-09-22 20:37 ` Michel Lanners
2000-09-22 21:37 ` Benjamin Herrenschmidt
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=39CC3D55.74CD42A2@wanadoo.fr \
--to=costabel@wanadoo.fr \
--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 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.