linux-mips
[Top] [All Lists]

Re: Building 64 bit kernel on Cobalt

To: "Atsushi Nemoto" <anemo@mba.ocn.ne.jp>
Subject: Re: Building 64 bit kernel on Cobalt
From: "Franck Bui-Huu" <vagabon.xyz@gmail.com>
Date: Mon, 19 Mar 2007 11:17:48 +0100
Cc: maillist@jg555.com, linux-mips@linux-mips.org, ralf@linux-mips.org
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=D3iMSjsPvoIZ9EnVQEF6Oy0u1qmwWRwHVYUKwoeAHq/qkaIF/uDdSZPUoakMnyd0P/qjXkxxaJ0cv2RJZsPPC4lLcfIYauTRXmVlXY8quPOKkr4HT/d1F9EQr/hIN9M3tQt8IG/kYu0eBnaC30aX7r2M326t4WEznd8455QvLQE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KcMHhnDDaIk5YfM0EVSWt1ZD65jPuUg3/a3THSCBxtWwjXVDpzzqFvHAaXVBQ9XbwhbTFTeRz77xzoTk69AoHiAEOx74Zga+Mng0ULDGgxnVW29aTCJCV/M5nAJn/p0pC4S6TaGz7A9J1q66BqkQbxGv16Ll0k28a6vwpw2g2GA=
In-reply-to: <cda58cb80703190308k4e57e194u56dca25b063646b6@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <45FDB498.1040504@jg555.com> <20070319.101209.79013781.nemoto@toshiba-tops.co.jp> <45FE1D95.8050204@jg555.com> <20070319.150705.100740532.nemoto@toshiba-tops.co.jp> <cda58cb80703190308k4e57e194u56dca25b063646b6@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
On 3/19/07, Franck Bui-Huu <vagabon.xyz@gmail.com> wrote:
On 3/19/07, Atsushi Nemoto <anemo@mba.ocn.ne.jp> wrote:
> On Sun, 18 Mar 2007 22:20:21 -0700, Jim Gifford <maillist@jg555.com> wrote:
> > Here's the config file I'm using http://ftp.jg555.com/cobalt.config
> > Now if I revert all changes that have occurred to setup.c from 2.6.19 to
> > 2.6.20, everything works perfectly.
> >
> > Without that patch, this is as far as it gets.
>
> You are using CONFIG_BUILD_ELF64=y and CKSEG0 load address.
> This combination does not work.  Please refer these threads:
>

Thanks Atsushi for sorting this out. It's a bit sad to get these type
of information after so many email echanges...


BTW, how this config has ever worked for a 2.6.19 kernel ? I don't see
why using __pa() instead of CPHYSADDR() breaks this config...
--
              Franck

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