From: Ian Chilton <mailinglist@ichilton.co.uk>
To: linux-mips@oss.sgi.com
Subject: 2.4.16 success on Indy (was Re: 2.4.16 success on Decstation 5000/150)
Date: Mon, 3 Dec 2001 00:00:36 +0000 [thread overview]
Message-ID: <20011203000036.A10356@buzz.ichilton.local> (raw)
In-Reply-To: <20011203000338.A30090@paradigm.rfc822.org>
Hello,
> the current cvs (as of a couple hours ago) works without additional
> patches on my Decstation 5000/150 like a charm:
It also worked for me earlier on an Indy R4600 - 1st kernel I have had
properly boot since 2.4-test9 IIRC.
/proc/cpuinfo output:
processor : 0
cpu model : R4600 V2.0 FPU V2.0
BogoMIPS : 100.23
wait instruction : yes
microsecond timers : yes
extra interrupt vector : no
hardware watchpoint : no
VCED exceptions : not available
VCEI exceptions : not available
Bye for Now,
Ian
next prev parent reply other threads:[~2001-12-03 1:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 23:03 2.4.16 success on Decstation 5000/150 Florian Lohoff
2001-12-03 0:00 ` Ian Chilton [this message]
2001-12-03 13:37 ` 2.4.16 success on Indy (was Re: 2.4.16 success on Decstation 5000/150) Florian Lohoff
2001-12-03 16:19 ` Ian Chilton
2001-12-03 16:34 ` Ladislav Michl
2001-12-03 18:25 ` Florian Lohoff
2001-12-03 22:44 ` Ian Chilton
2001-12-07 2:31 ` Ralf Baechle
2001-12-08 16:35 ` Ladislav Michl
2001-12-10 17:17 ` [PATCH] timer fix (was: Re: 2.4.16 success on Indy...) Ladislav Michl
2001-12-04 7:41 ` 2.4.16 success on Indy (was Re: 2.4.16 success on Decstation 5000/150) Ladislav Michl
2001-12-04 8:59 ` Florian Lohoff
2001-12-04 9:11 ` Geert Uytterhoeven
2001-12-04 9:18 ` Ladislav Michl
2001-12-05 1:10 ` Florian Lohoff
2001-12-04 9:26 ` 2.4.16 success on Decstation 5000/150 Houten K.H.C. van (Karel)
2001-12-04 11:44 ` Maciej W. Rozycki
2001-12-04 12:04 ` Martin Schulze
2001-12-04 12:20 ` Maciej W. Rozycki
2001-12-04 23:31 ` Klaus Naumann
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=20011203000036.A10356@buzz.ichilton.local \
--to=mailinglist@ichilton.co.uk \
--cc=ian@ichilton.co.uk \
--cc=linux-mips@oss.sgi.com \
/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