From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Benjamin Herrenschmidt <bh40@calva.net>,
Martin Costabel <costabel@wanadoo.fr>,
"linuxppc-dev" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.4 problems
Date: Fri, 01 Sep 2000 12:29:28 +0100 [thread overview]
Message-ID: <200009011129.MAA31853@hyperion.valhalla.net> (raw)
>>You mean when I type on the local "dead" keyboard? I couldn't test this
>>yet, because the machine from which I sshed in was 15 km away at work.
>>And after a while I had the bad idea to type "hwclock -r", upon which
>>the 6400 was really dead, so I could not test it any further. While I
>>observed it, the ADB interrupt did not increase.
>
> Ok, so it looks like Cuda gets dead.
>
> Iain Sandoe recently did work to improve the robustness of the Cuda state
> machine. I didn't yet have time to look at his code, but it may be
> interesting for you to test his patch.
It's not 2.4.0 (sorry)
- but, you can (a) either wait a few days - and I'll have a go or (b) take a
look at the 2.2.17 one and see (IMHO it shouldn't be difficult - the 2.4.0
via-cuda doesn't look much different from the 2.2.17 one).
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-09-01 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-01 11:29 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-31 16:10 Platform configuration (was: Re: CONFIG_PPC != Mac) Gabriel Paubert
2000-08-31 16:20 ` Michel Dänzer
2000-08-31 19:03 ` Joseph Garcia
2000-08-31 19:18 ` 2.4 problems Michel Dänzer
2000-08-31 19:25 ` Dan Malek
2000-08-31 20:36 ` Martin Costabel
2000-08-31 21:47 ` Benjamin Herrenschmidt
2000-09-01 1:12 ` Martin Costabel
2000-09-01 10:57 ` Benjamin Herrenschmidt
2000-08-31 21:30 ` Michel Lanners
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=200009011129.MAA31853@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=bh40@calva.net \
--cc=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 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).