From: GertJan Spoelman <kl@gjs.cc>
To: Petr Baudis <pasky@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Updated Documentation/kernel-parameters.txt (resent, v3)
Date: Sat, 23 Nov 2002 16:17:08 +0100 [thread overview]
Message-ID: <200211231617.08772.kl@gjs.cc> (raw)
In-Reply-To: <20021123093600.GV25628@pasky.ji.cz>
Hello Petr,
Nice work.
Can you add/change the comments for the mem and mem=exactmap parameters.
The mem parameter doesn't behave in the same manner as it did before
2.4.19/20, I think it changed somewhere in the 2.4.19-pre series.
On an old Compaq 2500 with 320Mb memory the following line used to work :
append="mem=320M"
now I have to use:
append="mem=exactmap mem=640K@0 mem=319M@1M"
to get the kernel to see all the memory.
On later kernels if I use mem=320M it only sees 16Mb, this is also true for
2.5.44 (probably true for all the 2.5.x kernels) which I tried on that box.
I don't know if it's only something specific for that box and maybe not
necessarily true for other systems which have to use the mem parameter.
To me it looks like the mem parameter can now only be used to specify less
memory then the kernel actually recognizes.
Also can you add how to use the mem=exactmap parameter, it says now that such
lines can be constructed based on BIOS output or other requirements, that
doesn't tell me how such a line should look like, I only found out how to use
it by searching through posts on lkml, maybe you can add the above append
lines as an example.
Regards,
GertJan
On Saturday 23 November 2002 10:36, Petr Baudis wrote:
> Hello,
>
> this patch (against 2.5.49) updates Documentation/kernel-parameters.txt
> to the current state of kernel. It was somehow abadonded lately, so I did
> my best, but it's possible that I still missed some of the options - thus,
> if you will notice your favourite boot option missing there, please speak
> up. Note also that I will probably send up another update after few further
> kernel releases..
>
> Also, I attempted to introduce some uniform format to the entries, I
> added the format description where I was able to find it out and decypher
> it, and I also added gross amount of external links to the headers of the
> source files or to the README-like files, where the options are described
> into more degree. This way, hopefully this file has a chance to be actually
> usable for the users ;-).
>
> There are almost certainly some entries which I missed, it was really a
> huge number and the main reason is that some of the boot options don't use
> the __setup macro, which I grep'd for.
>
> I hope the patch is ok, there should be no problems with it. Please
> apply.
>
> Documentation/kernel-parameters.txt | 811
> +++++++++++++++++++++++++++--------- 1 files changed, 627 insertions(+),
> 184 deletions(-)
>
> Note that this is the fourth submission of the patch - I took the
> opportunity and updated the patch from 2.5.48 to 2.5.49. AFAIK mutt
> shouldn't mangle the patch in any way, so it should apply cleanly to your
> tree, Linus.
>
> Kind regards,
> Petr Baudis
next prev parent reply other threads:[~2002-11-23 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 9:36 [PATCH] Updated Documentation/kernel-parameters.txt (resent, v3) Petr Baudis
2002-11-23 15:17 ` GertJan Spoelman [this message]
2002-11-24 15:48 ` Petr Baudis
2002-11-27 12:04 ` GertJan Spoelman
-- strict thread matches above, loose matches on Subject: below --
2002-11-23 16:11 J.E.J. Bottomley
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=200211231617.08772.kl@gjs.cc \
--to=kl@gjs.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=pasky@ucw.cz \
/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