linux-mips
[Top] [All Lists]

Re: [PATCH 2.6.9] KSEG/CKSEG fixes

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH 2.6.9] KSEG/CKSEG fixes
From: Tom Rini <trini@kernel.crashing.org>
Date: Fri, 22 Oct 2004 07:46:39 -0700
Cc: Ladislav Michl <ladis@linux-mips.org>, linux-mips@linux-mips.org
In-reply-to: <20041022122146.GB27961@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20041021001427.GA25441@smtp.west.cox.net> <20041021070921.GA2297@umax645sx> <20041021144815.GB25441@smtp.west.cox.net> <20041022122146.GB27961@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.6+20040907i
On Fri, Oct 22, 2004 at 02:21:46PM +0200, Ralf Baechle wrote:
> On Thu, Oct 21, 2004 at 07:48:15AM -0700, Tom Rini wrote:
> 
> > Would this include abstracting the notion of KSEG1/CKSEG1 into something
> > where one name would get the right var on 32 or 64 ?  If so, is this in
> > CVS now?  If not, wouldn't it make sense to put this in now and convert
> > it when the changes do go in?
> 
> The plan was to use K0BASE / K1BASE and define them as appropriate for
> a platform.  KSEG0 / KSEG1 / KSEG2 would always be 32-bit constants and
> CKSEG0/1/2 always 64-bit.  Somebody recently screwed the latter with a
> checkin.

Ah, that makes sense.  I'll wait for it to show up in HEAD.

-- 
Tom Rini
http://gate.crashing.org/~trini/

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