All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@puffin.external.hp.com>
To: Matthew Wilcox <willy@debian.org>
Cc: Thomas Marteau <marteaut@esiee.fr>,
	"parisc-linux@parisc-linux.org" <parisc-linux@parisc-linux.org>
Subject: Re: [parisc-linux] Second Draft of the help for the kernel options
Date: Sun, 07 Oct 2001 21:48:47 -0600	[thread overview]
Message-ID: <200110080348.VAA24289@puffin.external.hp.com> (raw)
In-Reply-To: Message from Matthew Wilcox <willy@debian.org> of "Mon, 08 Oct 2001 00:31:47 BST." <20011008003147.A6105@parcelfarce.linux.theplanet.co.uk>

Matthew Wilcox wrote:
> 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 machine
>   from the C160-J2240 era.

s/machine/workstation/
I'm pretty sure all 64-bit capable servers properly handle
PDC calls in wide mode. PAT PDC supports a few calls in
narrow mode (for boot loader) but the rest must be in wide mode.

Note that IODC generally requires narrow mode.
(Superdome IODC is different - but I don't recall exactly how).

BTW, I prefer Matthew's rewrite over the Thomas' proposal.
No offense intended thomas - thanks for submitting the original.

grant

  reply	other threads:[~2001-10-08  3:52 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 [this message]
2001-10-08 14:44     ` Thomas Marteau
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=200110080348.VAA24289@puffin.external.hp.com \
    --to=grundler@puffin.external.hp.com \
    --cc=marteaut@esiee.fr \
    --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.