Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Vince Weaver <weave@eng.umd.edu>
Cc: "William J. Earl" <wje@cthulhu.engr.sgi.com>,
	eak@sgi.com, linux@cthulhu.engr.sgi.com
Subject: Re: identifying sgi system type under Linux [patch]
Date: Fri, 14 Jan 2000 13:25:25 +0100	[thread overview]
Message-ID: <20000114132525.E4278@uni-koblenz.de> (raw)
In-Reply-To: <Pine.GSO.4.21.0001131637260.12920-200000@z.glue.umd.edu>

On Thu, Jan 13, 2000 at 04:45:41PM -0500, Vince Weaver wrote:

> >       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.
> 
> thanks, this is what I needed!  It works (at least for me!)
> 
> Here is the patch, I'd like someone with and Indy to try and be sure it
> works all around....

It's ``obviously correct''.  However I'd prefer if somebody would rewrite
the bootinfo.h and /proc stuff in a cleaner, more easy to maintain way.
We've got various modules that want to output information via cpuinfo
like the CPU-info, the second level cache handler and about the board
itself.  So what I want is something where various subsystems that want
to contribute to the /proc/cpuinfo content can register their own routines
when then will be called via get_cpuinfo().

  Ralf

  reply	other threads:[~2000-01-15  1:05 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 [this message]
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=20000114132525.E4278@uni-koblenz.de \
    --to=ralf@oss.sgi.com \
    --cc=eak@sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=weave@eng.umd.edu \
    --cc=wje@cthulhu.engr.sgi.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