All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Hibler <mike@fast.cs.utah.edu>
To: chris@4mcnabb.net, parisc-linux@thepuffingroup.com
Subject: Re:  [parisc-linux] Got a machine, Got a Kernel Image, Got a Ramdisk Image, What's next?
Date: Tue, 16 Nov 1999 07:48:10 -0700 (MST)	[thread overview]
Message-ID: <199911161448.HAA18034@fast.cs.utah.edu> (raw)

> From: "Christopher L McNabb" <chris@4mcnabb.net>
> To: <parisc-linux@thepuffingroup.com>
> Date: Tue, 16 Nov 1999 09:23:07 -0500
> Subject: [parisc-linux] Got a machine, Got a Kernel Image, Got a Ramdisk Image, What's next?
> 
> I've been using Intel Linux since version 0.99.  My company recently retired
> an HP-9000 model 832, which is now sitting here in my house.  I would love
> to help out with the pa-risc port, but don't have the time or inclination to
> do actual development.  I can, however, do testing.
> 
> The box is an HP-9000 model 832, HP-UX 9.0, 32 Megs of RAM (yeah, I know
> that's rather low), and 3.5 gigs of hard drive space split between 6 HP-IB
> disk drives (4 internal, 2 external).  A SCSI interface is supposed to
> arrive fed-ex today, and I will be adding a CD-ROM and SCSI disks as cash
> becomes available.
> 
> What I really need to know, though, are two things:
> 1.  What is the process for getting the Linux kernel to boot?
> 2.  What can I do to help with the porting of Linux to the PA-RISC
> architecture?
> 

The current linux work is focusing on 1.1 and 2.0 architecture machines with
fairly traditional memory-mapped IO architectures.  The 832 is a PA 1.0
machine with a completely different "channel" based IO bus architecture
(NIO).

In a nutshell, it would be a long uphill battle to port anything to it
and for very little gain.  Scrap it!

             reply	other threads:[~1999-11-16 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-16 14:48 Mike Hibler [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-11-16 14:23 [parisc-linux] Got a machine, Got a Kernel Image, Got a Ramdisk Image, What's next? Christopher L McNabb
1999-11-16 19:14 ` Stan Sieler

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=199911161448.HAA18034@fast.cs.utah.edu \
    --to=mike@fast.cs.utah.edu \
    --cc=chris@4mcnabb.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.