From: David VomLehn <dvomlehn@cisco.com>
To: linux-mips@linux-mips.org
Subject: Does HIGHMEM work on 32-bit MIPS ports?
Date: Tue, 19 Feb 2008 20:09:45 -0800 [thread overview]
Message-ID: <47BBA809.3050505@cisco.com> (raw)
As we continue to investigate using high memory on MIPS, we keep coming
up with odd results. The basic mapping of high memory seems to be
working correctly, and if we use an INITRAMFS root filesystem, things
seem to work. Things also seem to work with an NFS root filesystem if we
disable preemption, though we get someone squirrelly behavior in some
minor ways. Has anyone else successfully been able to use high memory on
a 32-bit MIPS Linux port?
Any feedback would be helpful.
--
David VomLehn, dvomlehn@cisco.com
The opinions expressed herein are likely mine, but might not be my employer's...
next reply other threads:[~2008-02-20 4:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 4:09 David VomLehn [this message]
2008-02-20 16:18 ` Does HIGHMEM work on 32-bit MIPS ports? Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2008-02-20 19:20 David VomLehn
2008-02-21 10:55 ` Maciej W. Rozycki
2008-02-26 21:06 David VomLehn
2008-03-05 22:55 David VomLehn
2008-03-06 15:44 ` Ralf Baechle
2008-03-07 5:02 David VomLehn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47BBA809.3050505@cisco.com \
--to=dvomlehn@cisco.com \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox