| To: | Tom Rini <trini@kernel.crashing.org> |
|---|---|
| Subject: | Re: [PATCH 2.6.9] KSEG/CKSEG fixes |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Fri, 22 Oct 2004 14:21:46 +0200 |
| Cc: | Ladislav Michl <ladis@linux-mips.org>, linux-mips@linux-mips.org |
| In-reply-to: | <20041021144815.GB25441@smtp.west.cox.net> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20041021001427.GA25441@smtp.west.cox.net> <20041021070921.GA2297@umax645sx> <20041021144815.GB25441@smtp.west.cox.net> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.1i |
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. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: kernel_thread creation bug?, Ralf Baechle |
|---|---|
| Next by Date: | Re: kernel_thread creation bug?, Atsushi Nemoto |
| Previous by Thread: | Re: [PATCH 2.6.9] KSEG/CKSEG fixes, Tom Rini |
| Next by Thread: | Re: [PATCH 2.6.9] KSEG/CKSEG fixes, Tom Rini |
| Indexes: | [Date] [Thread] [Top] [All Lists] |