Linux PARISC architecture development
 help / color / mirror / Atom feed
From: joel.soete@freebel.net
To: Matthew Wilcox <willy@debian.org>
Cc: joel.soete@freebel.net, Matthew Wilcox <willy@debian.org>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] hppa64-linux-gcc not in gcc dpkg?
Date: Wed, 19 Jun 2002 18:07:21 +0200 (CEST)	[thread overview]
Message-ID: <1024502841.3d10ac39dc7dd@webmail.tiscalinet.be> (raw)
In-Reply-To: <20020619151755.L9435@parcelfarce.linux.theplanet.co.uk>

Quoting Matthew Wilcox <willy@debian.org>:

> On Wed, Jun 19, 2002 at 04:07:03PM +0200, joel.soete@freebel.net wrote:
> > May I am wrong (I thought that the PDC of the b2000 was not a 64bits
> one; I will
> > check )
> 
> ah, you relied on memory rather than reading the help text then?
> 
> 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 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.
> 
> b2000 and similar machines have firmware which supports both 32 and 64
> bit PDC calls.
> 
Nice (for sure next time I will read help)
Thanks a lot,
    Joel



-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)

      reply	other threads:[~2002-06-19 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19 13:28 [parisc-linux] hppa64-linux-gcc not in gcc dpkg? joel.soete
2002-06-19 13:36 ` Matthew Wilcox
2002-06-19 14:07   ` joel.soete
2002-06-19 14:17     ` Matthew Wilcox
2002-06-19 16:07       ` joel.soete [this message]

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=1024502841.3d10ac39dc7dd@webmail.tiscalinet.be \
    --to=joel.soete@freebel.net \
    --cc=parisc-linux@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox