Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Cory Jon Hollingsworth <cory@real-time.com>
To: Ralf Baechle <ralf@uni-koblenz.de>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Hard Hat and Tandem.
Date: Thu, 19 Aug 1999 17:52:04 -0500	[thread overview]
Message-ID: <37BC8A94.289936FF@real-time.com> (raw)
In-Reply-To: 19990818133932.A8965@uni-koblenz.de

Ralf Baechle wrote:

> On Sun, Aug 15, 1999 at 01:54:24PM -0500, Cory Jon Hollingsworth wrote:
>
> >     I have a Tandem model number CMN B006S that I'm trying to get Hard
> > Hat up and running on.  This is a machine build for Tandem by SGI and,
> > based on the descriptions I have read, I believe it is a close cousin to
> > the Challenge S.
>
> >     For instance an hinv returns:
> > Syestem: IP22
> > Processor: 150 Mhz R4400, with FPU
> > Primary I-cache size: 16 Kbytes
> > Primary D-cache size: 16 Kbytes
> > Secondary cache size: 1024 Kbytes
> > Memory size: 256 Mbytes
> > SCSI Disk: scsi(0)disk(1)
>
> Could you send me a the full hinv output, just to verify that this
> system is really an IP22 with no Tandem specific specials?
>

    Well the above is all that comes from a straight hinv.  I do get more if
I do an 'hinv -t' or 'hinv -t -p' though.  Half of the 'hinv -t -p' scrolls
off the screen and the information seems to be redundant anyway (4 lines to
describe serial port 1 for instance).

    Here is the output of an 'hinv -t'.

system ARC SGI-IP22 key 0
   processor CPU MIPS-R4400 key 0
    processor FPU MIPS-R4400FPC key 0
    cache primary icache 16 Kbytes (block 1 lines, line 16 bytes)
    cache primary dcache 16 Kbytes (block 1 lines, line 16 bytes)
    cache secondary cache 1024 Kbytes (block 1 lines, line 128 bytes)
    memory main 256 Mbytes
  controller network ec0 key 0
    peripheral network key 0
  adapter SCSI WD33C93B key 0
    controller disk SGI SEAGATE ST31230N key 1
      peripheral disk unit 0
  controller serial IP22 tty key 0
    peripheral line key 0
  controller serial IP22 tty key 1
    peripheral line key 0
  controller keyboard pc kbd key 0
  controller pointer pcms key 0
    peripheral pointer key 0

    Now I don't know what it means by keyboard and pointer.  The machine has
no keyboard or mouse port.  It does have two serial ports that look like PS/2
mouse ports though.  I'm running the dumb terminal off one right now.

> Further, what is the product name under which this Tandem was marketed?
> Is it CMN B006S?  I'd like to document the fact that this machine is
> (un?)supported in the Linux/MIPS docs.
>

    I don't know to both questions.  The only identification the outside of
the box is the above model name/number affixed to the bottom panel.  The box
is jet black  and says TANDEM in the lower right corner.  I've opened it up
and it has a copyright 1993 Silicon Graphics on one of the circuit boards,
but the machine is absent of any obvious identification.

<snip, snip>

> >     My question is: Can I get a precompiled vmlinux replacement for the
> > Hard Hat distribution which will allow me to continue with the
> > installation?   Or, since Tandem is not officially supported,  do I
> > spend the next couple of months hand assembling a root partition on the
> > machine from the bits I currently have working via NFS?
>
> There are several kernels in exactly the directory you got the initrd
> image from.
>

    Cool.  Any idea which one I should use?  Or should I try them all until I
find one that works?

>
> I have never heared about these Tandem machine but I assume that it it
> identical to the Indy rsp. Challenge S.
>

    Well I could give you a bastardized history lesson.  Bastardized in the
sense that I think I know the story, but could be wrong since I'm repeating
info that has been passed to me through multiple sources.

    Tandem was a company situated in Texas that was in the business of
selling business servers.  At the time this box was purchased, Tandem was
repackaging SGI hardware and selling them as Tandem servers.  Since then
Tandem has been bought by Compaq, which I believe where more or less bought
Tandem in order to acquire the brand name.  Currently I believe Compaq sells
industrial computers under the Tandem name.  I do not think those machines
have a MIPS chip set though.

    Keep in mind everything or anything I said in the above paragraph may be
wrong. 8-)  I'm just repeating hear say.

    I actually have a second Tandem box which is still a mystery box since it
requires a 220 outlet and the power grid in my apartment needs to be
customized to support it. 8-)  Once I get that monster up and running I'll
have to run an hinv to see what it has for guts.

    Thanks.

    Cory

  reply	other threads:[~1999-08-19 23:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-15 18:54 Hard Hat and Tandem Cory Jon Hollingsworth
1999-08-18 11:39 ` Ralf Baechle
1999-08-19 22:52   ` Cory Jon Hollingsworth [this message]
1999-08-20  1:23     ` Ralf Baechle
1999-08-21  0:45       ` Cory Jon Hollingsworth
1999-08-21  1:18         ` William J. Earl
1999-08-21  1:55         ` Joan Eslinger
1999-08-21  2:04           ` William J. Earl
1999-08-21 10:20           ` Cory Jon Hollingsworth

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=37BC8A94.289936FF@real-time.com \
    --to=cory@real-time.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@uni-koblenz.de \
    /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