From: mleopold@tiscali.dk
To: linux-mips@linux-mips.org
Cc: "Thiemo Seufer" <ica2_ts@csv.ica.uni-stuttgart.de>
Subject: Re: Linux on Indigo2 (IP28) - R10000
Date: Tue, 10 Jun 2003 20:38:19 +0200 [thread overview]
Message-ID: <3EDD28A400000BAC@cpfe4.be.tisc.dk> (raw)
In-Reply-To: <20030610181100.GB529@rembrandt.csv.ica.uni-stuttgart.de>
Hi Thiemo.
> The solution is to use a special kernel with compiled in cache barriers
> (needs a not-yet written compiler patch) and careful managing of page
> table accesses from userspace (needs rmap, and thus 2.5 Kernel).
I noticed this guy talking about O2 and having some patches and precompiled
kernels. Are these in anyway related to what you are talking about?
http://www.linux-mips.org/~glaurung/
> I'm working sowly on it, but I get constantly distracted by toolchain
> issues. :-)
I looked arround your website and saw "mips64-linux-ip28-2002-06-28.tar.gz"
whoo.. Sounds exiting =]
> > There was some talk in Febuary on a guy got Linux up and running on
an
> > Origin 200 - and some bootable cd's. That sounded prety interesting
=]
> The Origin is easier to suppot, it has coherent I/O.
And you are probably going to tell me that this is the same reson that the
O2 is working, right?
> > Btw: I also got my hands on an Octane (IP30) with an R10000 (195 Mhz)
-
> > I haven't tried to install on this one, but that might be interesting
too..
> This one is also I/O coherent, so chances are much better than for IP28.
Are you saying I might get this one working with the Debian boot-images
that I already tried, or?
--
Regards Martin Leopold.
Dept. of Computer Science, University of Copenhagen
next prev parent reply other threads:[~2003-06-10 18:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 17:52 Linux on Indigo2 (IP28) - R10000 mleopold
2003-06-10 18:11 ` Thiemo Seufer
2003-06-10 18:38 ` mleopold [this message]
2003-06-10 18:59 ` Thiemo Seufer
2003-06-10 19:14 ` Ralf Baechle
2003-06-11 20:35 ` Martin Leopold
2003-06-11 20:41 ` Thiemo Seufer
2003-06-12 11:06 ` Maciej W. Rozycki
2003-06-10 19:37 ` Erik J. Green
2003-06-10 18:56 ` ilya
2003-06-10 20:21 ` Keith M Wesolowski
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=3EDD28A400000BAC@cpfe4.be.tisc.dk \
--to=mleopold@tiscali.dk \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=linux-mips@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