From: Matthew Wilcox <willy@debian.org>
To: "James P. Kinney III" <jkinney@localnetsolutions.com>
Cc: palinux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Firmware upgraded, STI console problem
Date: Wed, 12 Dec 2001 19:57:27 +0000 [thread overview]
Message-ID: <20011212195727.B22198@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1008185675.31094.49.camel@archimedes.localnetsolutions.com>; from jkinney@localnetsolutions.com on Wed, Dec 12, 2001 at 02:34:35PM -0500
On Wed, Dec 12, 2001 at 02:34:35PM -0500, James P. Kinney III wrote:
> Also, my processor is listed in firmware and docs as a PA8000. So why
> not 64-bit cpu. If I boot the 2.4.16-64 kernel, it hangs after the
> "branching" messege screen.
this must surely be a faq by now. the c160-era workstations shipped
with 32-bit firmware, so it's much more sensible to run a 32-bit kernel
on them. why do people think a 64-bit kernel is better? it's slower and
takes more ram than a 32-bit kernel. the only benefit it might offer
(being able to deal with >4gb of ram, or >4gb virtual address space)
aren't applicable -- you can't put that much ram in a c160, and we don't
support 64-bit user processes yet.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2001-12-12 19:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 19:34 [parisc-linux] Firmware upgraded, STI console problem James P. Kinney III
2001-12-12 19:57 ` Matthew Wilcox [this message]
2001-12-12 20:39 ` Grant Grundler
2001-12-12 20:50 ` Tom
2001-12-12 21:02 ` Matthew Wilcox
[not found] ` <1008218517.2031.1.camel@crudball>
2001-12-13 5:20 ` Matthew Wilcox
2001-12-13 14:21 ` Ryan Bradetich
2001-12-14 18:58 ` 735 and SCSI (was: Re: [parisc-linux] Firmware upgraded, STI console problem) Phil Anderson
2001-12-14 22:55 ` Richard Hirst
2001-12-17 5:43 ` Ryan Bradetich
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=20011212195727.B22198@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=jkinney@localnetsolutions.com \
--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