From: Reinhold Jordan <r.jordan@asc.de>
To: linux-kernel@vger.kernel.org
Subject: option memmap
Date: Wed, 11 Jan 2006 15:48:29 +0100 [thread overview]
Message-ID: <43C51ABD.4050204@asc.de> (raw)
Hello,
is there any documentation for this option better than this in
linux/Documentation/kernel-parameters.txt ?
I have a laptop with a defect memory soldered on the main-board.
128KB of 128MB are defect started at 7936KB
As I read from kernel-parameters.txt the option
memmap=128K$7936K
reserve this area. But this seems to be simply ignored. Even, if I
fade out 64MB, Knoppix still create a RAM disk, which is larger
as the remaining memory...
Does someone know advice?
Thanks, regards, Reinhold
--
Reinhold Jordan
WWW: http://reinhold.bachrain.de Mail: reinhold@bachrain.de
qmail-spam-protection with intelligent-greylisting, reverse-smtp....
qmail.spamfilter.051215.076.tar.bz2 actual rejects 99.995% of spam!!
next reply other threads:[~2006-01-11 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 14:48 Reinhold Jordan [this message]
2006-01-12 9:57 ` option memmap Reinhold Jordan
2006-01-12 14:52 ` Ram Gupta
2006-01-17 8:08 ` Reinhold Jordan
2006-01-15 23:53 ` Randy.Dunlap
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=43C51ABD.4050204@asc.de \
--to=r.jordan@asc.de \
--cc=linux-kernel@vger.kernel.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