From: Thomas Marteau <marteaut@esiee.fr>
To: Grant Grundler <grundler@puffin.external.hp.com>
Cc: Matthew Wilcox <willy@debian.org>,
"parisc-linux@parisc-linux.org" <parisc-linux@parisc-linux.org>
Subject: Re: [parisc-linux] Second Draft of the help for the kernel options
Date: Mon, 08 Oct 2001 16:44:05 +0200 [thread overview]
Message-ID: <3BC1BBB5.F1ACA@esiee.fr> (raw)
In-Reply-To: 200110080348.VAA24289@puffin.external.hp.com
Hi all,
I have put the Matthew Wilcox's CPU and 64bit section. For the PDC
narrow, a section was already written. So, I do not the change unless
you tell that:
"
32-bit PDC
CONFIG_PDC_NARROW
Turning this option on enables support for 32-bit firmware when
running
a 64-bit kernel. You should select this option if you have a
workstation
from the C160-J2240 era.
"
is better than:
"
32-bit PDC
CONFIG_PDC_NARROW
Saying Y here will allow developers with a C180, C200, C240, C360,
J200, J210, and/or a J2240 to test 64-bit kernels by providing
a wrapper for the 32-bit PDC calls. Since the machines which
which require this option do not support over 4G of RAM, this
option is targeted for developers of these machines wishing to
test changes on both 32-bit and 64-bit configurations.
If unsure, say N.
"
Anyway, thanks for your comment and if you have any idea, please mail
me, Thomas.
ESIEE Team
next prev parent reply other threads:[~2001-10-08 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 23:16 [parisc-linux] Second Draft of the help for the kernel options Thomas Marteau
2001-10-02 15:23 ` Bjorn Helgaas
2001-10-02 17:32 ` Grant Grundler
2001-10-03 8:57 ` Thomas Marteau
2001-10-07 23:31 ` Matthew Wilcox
2001-10-08 3:48 ` Grant Grundler
2001-10-08 14:44 ` Thomas Marteau [this message]
2001-10-08 14:58 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2001-10-02 6:12 Jurriaan Kalkman
2001-10-02 8:44 Jurij Smakov
2001-10-02 9:38 ` Richard Allen
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=3BC1BBB5.F1ACA@esiee.fr \
--to=marteaut@esiee.fr \
--cc=grundler@puffin.external.hp.com \
--cc=parisc-linux@parisc-linux.org \
--cc=willy@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.