From: "William J. Earl" <wje@cthulhu.engr.sgi.com>
To: Vince Weaver <weave@eng.umd.edu>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: identifying sgi system type
Date: Thu, 13 Jan 2000 15:19:22 -0800 (PST) [thread overview]
Message-ID: <14462.23930.613311.264388@liveoak.engr.sgi.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0001131258320.25401-100000@z.glue.umd.edu>
Vince Weaver writes:
> 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].
>
> I thought that maybe I could get the PROM to tell me this info, using code
> like this
>
> #include <asm/sgialib.h>
>
> struct linux_sysid *mree;
>
> mree=prom_getsysid();
> printk("Vendor: %s Prod: %s\n",mree->vend,mree->prod);
>
>
> the vendor is returned as SGI, but the "prod" just returns the serial
> number [which seems to be just the last few octets of the MAC address of
> the ethernet card].
>
> 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?
It is possible, but only with a database of serial numbers which
is not readily available. The simple way is to have the kernel export
the value of the "sgi_guiness" variable somehow, presumably via /proc.
prev parent reply other threads:[~2000-01-13 23:28 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
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 ` William J. Earl [this message]
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.23930.613311.264388@liveoak.engr.sgi.com \
--to=wje@cthulhu.engr.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