Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: ralf@uni-koblenz.de
Cc: William Ellis <bellis@cerf.net>,
	Linux porting team <linux@cthulhu.engr.sgi.com>
Subject: Re: boot problem
Date: Wed, 14 Jan 1998 16:56:38 -0800	[thread overview]
Message-ID: <199801150056.QAA17975@fir.engr.sgi.com> (raw)
In-Reply-To: <19980115012622.51359@uni-koblenz.de>

ralf@uni-koblenz.de writes:
...
 > No, the FDDI card is just being ignored by Linux.  The problem is
 > indeed the fact that the newport GFX card isn't installed.  I'll
 > take a look at it when I have time for more than one breath
 > per minute ...
 > 
 > Thinking about it, the kernel should only try to touch the gfx hardware
 > at all, if the ARC environment variable ``console'' is unset.  If you
 > want to run from a serial console, then the variable's value should be
 > either ``d1'' or ``d2'' for the first rsp. second serial interface.
 > I suppose IRIX just defaults to serial console because it knows that
 > a Challenge S is headless or after a failed probe for gfx hardware.

     IRIX probes for the graphics card.  If the probe fails, it
assumes this is not one.  If there is no graphics, or if console != g,
it sets the system console to the serial port.  Note, however, that
IRIX normally puts up an X login on the graphics head even if
console=d and thus the console is on the serial port.  This seems
like a reasonable approach for linux as well.

 > William, what is the recommended way to recognice whethere a machine
 > is a Indy or Challenge S?  Probing for a GFX card or checking via
 > ARC firmware?

       I would probe for the graphics card.  If you try to fetch
from the configuration register and get a bus error, or if the
returned value is wrong, assume no graphics. 

       You can check that you can read from the first register
location (0x1f0f0000); if there is a bus error, there is no graphics.
Then check that the GFXBUSY bit (0x8) in the status register at 
0x1f0f1338 turns off within about 300 ms.  The IRIX driver also
does this to check that the card is alive:

	/*
	 * Write an int into the 16-bit xstarti register.
	 * Read it back from the fixed-point xstartf register.
	 * The format is 16 bits of integer, 4 bits of fraction,
	 * all << 7.  In this case, the fraction is 0, so we expect
	 * to read (0x12348765 & 0xffff) << 11.
	 */

	rex3->set.xstarti = 0x12348765;
	if ( rex3->set._xstart.word == ((0x12348765 & 0xffff) << 11) ) {
		ng1_probed[index] = NG1_FOUND;
		return 1;
	}

set.xstarti is 0x1f0f0148 and set._xstart.word is 0x1f0f0100.

  reply	other threads:[~1998-01-15  0:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-14 23:50 boot problem William Ellis
1998-01-14 23:55 ` Ariel Faigon
1998-01-14 23:55   ` Ariel Faigon
1998-01-14 23:58 ` Shrijeet Mukherjee
1998-01-15  0:00 ` Charles Marker
1998-01-15  0:00   ` Charles Marker
1998-01-15  0:11 ` Eric Kimminau
1998-01-15  0:26 ` ralf
1998-01-15  0:56   ` William J. Earl [this message]
1998-01-15  5:15     ` ralf
1998-01-15  6:10       ` William J. Earl
1998-01-15  0:34 ` Alan Cox
1998-01-15  0:34   ` Alan Cox

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=199801150056.QAA17975@fir.engr.sgi.com \
    --to=wje@fir.engr.sgi.com \
    --cc=bellis@cerf.net \
    --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