From: Markus Dahms <mad@automagically.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: 2.6 on IP22 (Indy)
Date: Tue, 28 Jun 2005 08:21:07 +0200 [thread overview]
Message-ID: <20050628062107.GA8665@gaspode.automagically.de> (raw)
In-Reply-To: <Pine.LNX.4.61L.0506271632380.23903@blysk.ds.pg.gda.pl>
Hello again,
>> For the R4000 there are two other things I could try: console on newport
>> instead of serial port and a 32-bit kernel, which I only tried on the
>> R4600.
> Well, I don't know what newport is, but if it's capable of providing
> output that early, it'll do.
Newport is the most common graphics option for the Indy and there exists
a console driver for it. Luckily it outputs some more stuff than the
serial console:
| CPU revision is: 00000430
| FPU revision is: 00000500
| ...
| Checking for the multiply/shift bug... yes, workaround... no.
| kernel panic - not syncing: Reliable operation impossible!
| Configure for R4000 to enable the workaround.
I configured the kernel for R4X00. There are a few references to
CONFIG_CPU_R4000 in the source which doesn't seem to be a config
option anymore, but I couldn't find a workaround somewhere...
>> I'll also try the said patch (you're referring to "blast_scache nop ...",
>> do you?).
> Precisely.
doesn't change anything, neither for R4000PC nor for R4600PC.
Markus
--
Reactor error - core dumped!
next prev parent reply other threads:[~2005-06-28 6:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 10:07 2.6 on IP22 (Indy) Markus Dahms
2005-06-27 13:17 ` Maciej W. Rozycki
2005-06-27 14:18 ` Markus Dahms
2005-06-27 20:54 ` Maciej W. Rozycki
2005-06-28 6:21 ` Markus Dahms [this message]
2005-06-28 9:05 ` Maciej W. Rozycki
2005-06-28 10:20 ` Markus Dahms
2005-06-28 11:25 ` Maciej W. Rozycki
2005-06-28 17:04 ` Markus Dahms
2005-06-29 16:54 ` Maciej W. Rozycki
2005-07-19 18:21 ` Markus Dahms
2005-07-20 1:45 ` Thiemo Seufer
2005-06-28 12:23 ` Stephen P. Becker
2005-06-28 12:44 ` Maciej W. Rozycki
2005-06-28 13:03 ` Stephen P. Becker
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=20050628062107.GA8665@gaspode.automagically.de \
--to=mad@automagically.de \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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