| To: | Ralf Baechle <ralf@linux-mips.org> |
|---|---|
| Subject: | Re: Memory Management HAndling |
| From: | Manish Lachwani <mlachwani@mvista.com> |
| Date: | Fri, 11 Mar 2005 09:06:42 -0800 |
| Cc: | Alan Cox <alan@lxorguk.ukuu.org.uk>, Rishabh@soc-soft.com, linux-mips@linux-mips.org |
| In-reply-to: | <20050311155924.GD5958@linux-mips.org> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <4BF47D56A0DD2346A1B8D622C5C5902C61E22B@soc-mail.soc-soft.com> <1110548190.15943.46.camel@localhost.localdomain> <20050311155924.GD5958@linux-mips.org> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040308 |
Ralf Baechle wrote: Right, I had the 2.4.21 HIGHMEM working on PMC-Sierra Yosemite. Also, at that time, Sibyte supported HIGHMEM.On Fri, Mar 11, 2005 at 01:36:31PM +0000, Alan Cox wrote:On Gwe, 2005-03-11 at 05:25, Rishabh@soc-soft.com wrote:These macros can handle memory pages in KSEG0. Any suggestions on how can they be changed for addressing memory present in HIGHMEM. Since VA will not be in linear relation with mem_map.Take a look at how kmap() works on x86 and how the mappings are used.Highmem is supported for MIPS since ~ 2.4.18 or so. Ralf Thanks Manish Lachwani |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Memory Management HAndling, Ralf Baechle |
|---|---|
| Next by Date: | Re: Memory Management HAndling, Ralf Baechle |
| Previous by Thread: | Re: Memory Management HAndling, Ralf Baechle |
| Next by Thread: | Re: Memory Management HAndling, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |