From: Ralf Baechle <ralf@oss.sgi.com>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
"Gleb O. Raiko" <raiko@niisi.msk.ru>, Jun Sun <jsun@mvista.com>,
Alexandr Andreev <andreev@niisi.msk.ru>,
linux-mips@oss.sgi.com
Subject: Re: 3 questions about linux-2.4.18 and R3000
Date: Mon, 3 Jun 2002 16:15:18 -0700 [thread overview]
Message-ID: <20020603161518.B28859@dea.linux-mips.net> (raw)
In-Reply-To: <20020603231118.GI23411@rembrandt.csv.ica.uni-stuttgart.de>; from ica2_ts@csv.ica.uni-stuttgart.de on Tue, Jun 04, 2002 at 01:11:18AM +0200
On Tue, Jun 04, 2002 at 01:11:18AM +0200, Thiemo Seufer wrote:
> > Wonderful. Due to the hackish way we're using to build 64-bit kernels
> > for the currently supported targets we don't run into this problems,
> > there are no R_MIPS_HIGHEST relocs ever.
>
> Well, for my I2 Impact I do. :-) I hope to get it running again with
> the current kernel (plus my patches) in the next days.
Interesting. So you don't place the kernel into any of the 32-bit
compatibility address spaces on that machine?
Ralf
next prev parent reply other threads:[~2002-06-03 23:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 22:16 3 questions about linux-2.4.18 and R3000 Alexandr Andreev
2002-05-24 21:10 ` Jun Sun
2002-05-27 21:13 ` Alexandr Andreev
2002-05-28 17:15 ` Jun Sun
2002-05-30 0:18 ` Alexandr Andreev
2002-05-31 9:43 ` Gleb O. Raiko
2002-06-03 8:55 ` Ralf Baechle
2002-06-03 18:30 ` Maciej W. Rozycki
2002-06-03 22:40 ` Ralf Baechle
2002-06-03 23:01 ` Thiemo Seufer
2002-06-03 23:04 ` Ralf Baechle
2002-06-03 23:11 ` Thiemo Seufer
2002-06-03 23:15 ` Ralf Baechle [this message]
2002-06-03 23:53 ` Thiemo Seufer
2002-06-04 17:41 ` nick
2002-06-05 22:37 ` Thiemo Seufer
2002-06-05 23:50 ` Ilya Volynets
2002-06-06 23:54 ` Thiemo Seufer
2002-06-04 14:39 ` Maciej W. Rozycki
2002-06-04 14:37 ` Maciej W. Rozycki
2002-06-05 22:38 ` Thiemo Seufer
2002-06-04 14:34 ` Maciej W. Rozycki
2002-06-04 11:31 ` Gleb O. Raiko
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=20020603161518.B28859@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=andreev@niisi.msk.ru \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=raiko@niisi.msk.ru \
/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.