From: Bjorn Helgaas <bjorn_helgaas@hp.com>
To: 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: Tue, 2 Oct 2001 09:23:20 -0600 [thread overview]
Message-ID: <20011002152055.DE860403B@ldl.fc.hp.com> (raw)
In-Reply-To: <3BB8F957.C9811C25@esiee.fr>
> Finally, PA8x00 is the good choice for all new stuff like A500, B1000,
> B2000, B2600, C200+, C240+, C3000, C3600, J282, J2240, J5000, J6000,
> J6700, J7000, K250, K260, K270, K370, K450, K460, K470, K570, L1000,
> L2000, L3000, N4000, V2200, V2250, V2500.
I think it is unlikely that V2200, V2250, and V2500 will ever be supported.
I'm not very familiar with PDC on most of these machines, but at least on
Halfdome, you can get a pretty good clue as to what processor to target by
doing "in fru" at the PDC BCH menu:
Main Menu: Enter command or menu > in fru
CELL 0 CPU FRU INFORMATION:
Cab/
Slot/ Part Serial Date Art Scan FRU
Specific
CPU FRU Name Number Number Code Rev Rev
Information
----- ---------------- ----------- ------------ ---- --- ----
----------------
0/0/0 Processor A6445-70001 00000000001P 0000 PA8700
Rev 2.2
Maybe a pointer to similar functionality in other firmware would be useful
and reduce the dependence on the lists of machines.
next prev parent reply other threads:[~2001-10-02 15:20 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 [this message]
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
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=20011002152055.DE860403B@ldl.fc.hp.com \
--to=bjorn_helgaas@hp.com \
--cc=marteaut@esiee.fr \
--cc=parisc-linux@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