Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: willy@thepuffingroup.com
Cc: Andrew Shugg <andrew@neep.com.au>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Value of an old K-class server?
Date: Tue, 29 Feb 2000 15:20:05 -0800	[thread overview]
Message-ID: <200002292320.PAA08557@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Tue, 29 Feb 2000 12:24:39 PST." <20000229122439.F9944@thepuffingroup.com>

willy@thepuffingroup.com wrote:
> On Wed, Mar 01, 2000 at 01:06:47AM +0800, Andrew Shugg wrote:
> > The lowest-numbered K class machine I can find on HP's website is a K220.
> > I'm fairly sure the machine I've looked at is a K200, but if this model
> > never existed then it's probably a 220.  =)
> 
> I've just been going through The List of hardware, bashing the hw database
> into something more sane.  The K200 did exist, codenamed `Kittyhawk' with
> a 100MHz PA7200 CPU in it.  It has an NIO bus in it which is something
> we don't have documentation on yet (also known as HP-PB, I think).
> The K-class machines probably wont work very soon, but I suspect someone
> will eventually get them working.

Think of the K-class as a C-class (eg. C100) with HP-PB instead of EISA.
But forget the HP-PB.  Very few cards are made for it and most are HP
proprietary.  At least all the HP-PB SCSI boards are. The problem is not
getting the cards - getting a device driver will be difficult unless
someone in HP is a masochist and wants to write one. Not me.

Kittyhawks also have GSC "slots". The core I/O board has one "slot" and
the Harrier board has room for 4 more GSC cards.  IIRC, TPG has a dozen
or so gigabit ethernet cards which would fit nicely on a harrier.  I suspect
Andrew was refering to a Harrier board.

I have no clue what the actual value of a K200 is. One should be able to
upgrade the system to something faster than 100Mhz and add CPU's. I'm
just not sure it's worth it. Compare to a C3000 or B1000 before going
that route.

grant

Grant Grundler
Unix Development Lab
+1.408.447.7253

  reply	other threads:[~2000-03-01  0:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-29 17:06 [parisc-linux] Value of an old K-class server? Andrew Shugg
2000-02-29 14:57 ` Robert Womack
2000-02-29 17:24 ` willy
2000-02-29 23:20   ` Grant Grundler [this message]
2000-02-29 23:48   ` Andrew Shugg
2000-02-29 21:03     ` Robert Womack
2000-03-01  0:17     ` willy
2000-03-02 13:02       ` Andrew Shugg
2000-03-02 17:08         ` willy
2000-03-02 18:15           ` Stan Sieler
2000-03-01  4:35   ` Sandy Harris
     [not found]     ` <38BCA09A.9ABADBD0@cln.etc.bc.ca>
2000-03-05 23:01       ` Sandy Harris
2000-03-05 23:24         ` Barrie Spence
2000-03-06  2:22           ` [parisc-linux] Value of an old K-class server T. Martin
2000-03-06 11:47             ` Frank Benke
2000-03-07  0:00               ` Barrie Spence
2000-02-29 18:06 ` [parisc-linux] Value of an old K-class server? rob hoppe
  -- strict thread matches above, loose matches on Subject: below --
2000-02-29 23:55 Mike Hibler
2000-03-02 17:01 Mike Hibler

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=200002292320.PAA08557@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=andrew@neep.com.au \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=willy@thepuffingroup.com \
    /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