From: Matthew Wilcox <willy@debian.org>
To: Stefan Pfetzing <dreamind@dreamind.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Cdrecord and parisc64 kernel
Date: Fri, 19 Jul 2002 13:03:04 +0100 [thread overview]
Message-ID: <20020719130304.T13352@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20020719114920.GA4928@dreamind.de>; from dreamind@dreamind.de on Fri, Jul 19, 2002 at 01:49:20PM +0200
On Fri, Jul 19, 2002 at 01:49:20PM +0200, Stefan Pfetzing wrote:
> I just installed Debian/hppa on my HP Visualize C200.
> After I've compiled a kernel for 64bit and tried to use cdrecord it crashed
from the FAQ:
14. Can I run a 64-bit kernel on my machine ?
The answer to this is generally determined by the firmware your machine
runs. Workstations up to and including the J2240 and C360 only have 32-bit
firmware. The normal 64-bit kernel will not run on these systems. The
A500 and L2000 server only have 64-bit firmware, and these machines must
run a 64-bit kernel. The C3000 and similar workstations have both 32-bit
and 64-bit firmware and can therefore run either kernel.
A more important question is : why do you want to run a 64-bit kernel ?
Since we do not yet support 64-bit userspace, there is no advantage
to be gained running a 64-bit kernel on a machine with less than 3.5GB
of memory.
For those who do want to test 64-bit kernels on older machines, there is a
special configuration option `32-bit PDC' which will allow a 64-bit kernel
to work with 32-bit firmware. We cannot enable this option by default
as the resulting kernel will not work on machines with 64-bit firmware.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-07-19 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 11:49 [parisc-linux] Cdrecord and parisc64 kernel Stefan Pfetzing
2002-07-19 12:03 ` Matthew Wilcox [this message]
2002-07-19 23:19 ` Stefan Pfetzing
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=20020719130304.T13352@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=dreamind@dreamind.de \
--cc=parisc-linux@lists.parisc-linux.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