From: "William J. Earl" <wje@cthulhu.engr.sgi.com>
To: eak@sgi.com
Cc: Vince Weaver <weave@eng.umd.edu>, linux@cthulhu.engr.sgi.com
Subject: Re: identifying sgi system type under Linux
Date: Thu, 13 Jan 2000 13:15:36 -0800 (PST) [thread overview]
Message-ID: <14462.16504.84215.298070@liveoak.engr.sgi.com> (raw)
In-Reply-To: <387E2510.43D52D70@detroit.sgi.com>
Eric Kimminau writes:
> Vince Weaver wrote:
> >
> > Hello again
> >
> > I was trying to see if I could get this Indigo2 to display that it is an
> > Indigo2 under /proc/cpuinfo [instead of current behavior, which assumes
> > all SGI's are indy's].
> >
> > Is it possible to figure out what system type it is from this info? Is
> > there another way to find out sgi system type? Or is this just not
> > possible?
...
> The problem is that IP22 could be an Indy or an Indigo/2. Even under
> IRIX if you run hinv it doesn't tell you that a system is an Indy or
> an Indigo/2. Your only clues come from knowing additional bits about
> what is or is not Indy or I2 hardware. For example you would never
> see Impact graphics on an Indy and you would never see an Indy 8-bit
> graphics board on an Indigo/2 (although there were 8 bit boards on an
> Indigo/2 - I have been looking aorund internally to see if I can find
> one to see what it actually reports at command monitor for graphics).
> Further confusion would be to try and identify an older Indigo with an
> R4000 upgrade from an Indy.
One key difference is that Indigo2 always has an EISA bus and
Indy never does.
Note that the Linux kernel (like the IRIX kernel) has a way of
detecting the difference, since it needs to know which box it is
running on, so you could just get the kernel to export the data via
/proc somewhere. The kernel variable "sgi_guiness" is 1 if the system
is an Indy ("Guinness") and 0 if the system is an Indigo2
("FullHouse"). Look at the file indy_hpc.c to see how this is detected.
next prev parent reply other threads:[~2000-01-13 21:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-12 16:27 cross-compile fails Vince Weaver
2000-01-12 20:04 ` Vince Weaver
2000-01-12 22:31 ` Vince Weaver
2000-01-13 18:09 ` identifying sgi system type Vince Weaver
2000-01-13 18:32 ` Status Indigo2 Beowulf project Avi Bercovich
2000-01-14 17:01 ` Andrew R. Baker
2000-01-13 19:18 ` identifying sgi system type under Linux Eric Kimminau
2000-01-13 20:31 ` Vince Weaver
2000-01-13 21:15 ` William J. Earl [this message]
2000-01-13 21:45 ` identifying sgi system type under Linux [patch] Vince Weaver
2000-01-14 12:25 ` Ralf Baechle
2000-01-13 23:19 ` identifying sgi system type William J. Earl
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=14462.16504.84215.298070@liveoak.engr.sgi.com \
--to=wje@cthulhu.engr.sgi.com \
--cc=eak@sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=weave@eng.umd.edu \
/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