linux-mips
[Top] [All Lists]

Re: 3 questions about linux-2.4.18 and R3000

To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Subject: Re: 3 questions about linux-2.4.18 and R3000
From: Ralf Baechle <ralf@oss.sgi.com>
Date: Mon, 3 Jun 2002 16:04:25 -0700
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
In-reply-to: <20020603230107.GH23411@rembrandt.csv.ica.uni-stuttgart.de>; from ica2_ts@csv.ica.uni-stuttgart.de on Tue, Jun 04, 2002 at 01:01:07AM +0200
References: <20020603015536.B2832@dea.linux-mips.net> <Pine.GSO.3.96.1020603202021.14451K-100000@delta.ds2.pg.gda.pl> <20020603154011.A11393@dea.linux-mips.net> <20020603230107.GH23411@rembrandt.csv.ica.uni-stuttgart.de>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.2.5.1i
On Tue, Jun 04, 2002 at 01:01:07AM +0200, Thiemo Seufer wrote:

> > >  For MIPS64 they definitely do not work, OTOH, including the N32 ABI.
> > 
> > Are they good enough to build 64-bit kernels?
> 
> One simple patch [1] is missing from the release. R_MIPS_HIGHEST relocs
> are zeroed out in a few cases where the assembler resolves them itself.
> The rest works for me quite nice.

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.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>