Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Hudson <mhudson@home.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] The Kxx0 machines and other questions.
Date: Sun, 30 Jul 2000 19:08:18 -0500	[thread overview]
Message-ID: <3984C372.254E875@home.com> (raw)
In-Reply-To: 20000724144024.B25594@vodka.thepuffingroup.com


> On Mon, Jul 24, 2000 at 11:53:06AM -0500, Matthew Hudson wrote:
> > Now on subject. K200 working in Linux and if so
> > is there SMP support yet?
> 
> we're not really interested in supporting the k class right now.
> it's pretty similar to early C/J class (C100, C110, J200, J210), but it
> has some `interesting' devices in it that may be hard to support (the
> SCSI adapter looks slightly strange).  we don't have any SMP support yet
> and this machine won't be high on the priority list when we do start
> working on SMP.  i guess you're going to have to join in and do some
> hacking yourself :-)

Like I have the time for this, but... (famous last words)

Since I haven't had the time (yet) to attempt booting into Linux
with this monster what is its status? Non-functional or?
Where can I get some documentation for the various hardware in
this machine.

What is the status of the J210XC and will I be able to create
a functional Linux environment for it(the J210) if I wanted to
start coding? (currently running 10.20)

-Matt

  reply	other threads:[~2000-07-31  0:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-24 16:53 [parisc-linux] HP/UX 10.20 800 series media? Matthew Hudson
2000-07-24 18:40 ` Matthew Wilcox
2000-07-31  0:08   ` Matthew Hudson [this message]
2000-07-31  5:55     ` [parisc-linux] The Kxx0 machines and other questions Grant Grundler
2000-07-31 14:58       ` Matthew Hudson
2000-07-24 20:06 ` [parisc-linux] HIL hardware Qs Brian S. Julin

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=3984C372.254E875@home.com \
    --to=mhudson@home.com \
    --cc=matthew@wil.cx \
    --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