Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Mike Hibler <mike@fast.cs.utah.edu>
To: andrew@neep.com.au, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Value of an old K-class server?
Date: Thu, 2 Mar 2000 10:01:38 -0700 (MST)	[thread overview]
Message-ID: <200003021701.KAA19276@fast.cs.utah.edu> (raw)

> Date: Thu, 2 Mar 2000 21:02:12 +0800
> From: Andrew Shugg <andrew@neep.com.au>
> To: parisc-linux@thepuffingroup.com
> Subject: Re: [parisc-linux] Value of an old K-class server?
> 
> Okay.  =)  Is it clear at this point what is definitely going to be supported
> (even if it doesn't work now), and what will _never_ be supported?  (ie,
> basically, what has 1.0 and what has 1.1?)
> 

Your 715 and 735 should be fairly easy to support, even if they aren't one
of the current active development platforms.  They are 1.1 machines with
fairly "stock" off-the-shelf IO components very similar or identical to
some of the machines that are being worked on.

The "hard" machines will be 1.0 based machines (due to lack of architectural
features such as shadow registers and block TLBs that are probably assumed to
exist by the Linux code) and those with the different IO architectures
(CIO and NIO-based).  Note that the latter can be 1.1 (or 2.0?) based
machines, so you cannot just say that 1.1 machines will work.

Note that I speak not as an active developer of Linux, but as someone who
worked on Mach/BSD on these machines.  So believe the Puffin people more
than me!  They have a lot more resources available then we did, so things
might not be as hard for them.

             reply	other threads:[~2000-03-02 18:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-02 17:01 Mike Hibler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-02-29 23:55 [parisc-linux] Value of an old K-class server? Mike Hibler
2000-02-29 17:06 Andrew Shugg
2000-02-29 14:57 ` Robert Womack
2000-02-29 17:24 ` willy
2000-02-29 23:20   ` Grant Grundler
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-02-29 18:06 ` rob hoppe

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=200003021701.KAA19276@fast.cs.utah.edu \
    --to=mike@fast.cs.utah.edu \
    --cc=andrew@neep.com.au \
    --cc=parisc-linux@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