Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: olson@anchor.engr.sgi.com (Dave Olson)
To: adevries@engsoc.carleton.ca (Alex deVries)
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Parallel port support.
Date: Tue, 26 Jan 1999 10:32:38 -0800 (PST)	[thread overview]
Message-ID: <199901261832.KAA17419@anchor.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.3.96.990126121421.12068L-100000@lager.engsoc.carleton.ca> from Alex deVries at "Jan 26, 99 12:16:18 pm"

Alex deVries wrote: 
|  So the only things that actually hang off the pbus in the indy are:
|  - some of the SCSI control registers for the wd33c93

Yes, the "control" interface to the wd93.

|  - HAL2

Yep.

And as earlier discussed:
	RTC, prom, interrupt controller, serial ports.

Now, I do have an old spec that describes the parallel port
as a seperate chip, but I am nearly certain we folded it into
hpc3.  I may have to retract that though.  None of the specs
I have in my office are the final versions, and I don't have
an indigo2 lying around to look at the final chip layout.  If
you find a chip marked PI1, then I am remembering wrong, and we
did the parallel port as a seperate chip.

|  Where does ISDN fit in?

I don't remember, and I don't have the Indy specs handy, and I can't
find the online docs right now.  I think it went on the pbus, but
that's a vague memory.

|  What other machines have the HPC3, and what kind of devices do they have
|  on them?

Only the Indigo2 series (r4k, r8k, r10k) and Indy.


Dave Olson, Silicon Graphics
http://reality.sgi.com/olson   olson@sgi.com

WARNING: multiple messages have this Message-ID (diff)
From: olson@anchor.engr.sgi.com (Dave Olson)
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Parallel port support.
Date: Tue, 26 Jan 1999 10:32:38 -0800 (PST)	[thread overview]
Message-ID: <199901261832.KAA17419@anchor.engr.sgi.com> (raw)
Message-ID: <19990126183238.1xrOqvBSEv8RypRO3Aa-HHnPgQ8f5n5D8HU94FcQR2g@z> (raw)
In-Reply-To: <Pine.LNX.3.96.990126121421.12068L-100000@lager.engsoc.carleton.ca> from Alex deVries at "Jan 26, 99 12:16:18 pm"

Alex deVries wrote: 
|  So the only things that actually hang off the pbus in the indy are:
|  - some of the SCSI control registers for the wd33c93

Yes, the "control" interface to the wd93.

|  - HAL2

Yep.

And as earlier discussed:
	RTC, prom, interrupt controller, serial ports.

Now, I do have an old spec that describes the parallel port
as a seperate chip, but I am nearly certain we folded it into
hpc3.  I may have to retract that though.  None of the specs
I have in my office are the final versions, and I don't have
an indigo2 lying around to look at the final chip layout.  If
you find a chip marked PI1, then I am remembering wrong, and we
did the parallel port as a seperate chip.

|  Where does ISDN fit in?

I don't remember, and I don't have the Indy specs handy, and I can't
find the online docs right now.  I think it went on the pbus, but
that's a vague memory.

|  What other machines have the HPC3, and what kind of devices do they have
|  on them?

Only the Indigo2 series (r4k, r8k, r10k) and Indy.


Dave Olson, Silicon Graphics
http://reality.sgi.com/olson   olson@sgi.com

  parent reply	other threads:[~1999-01-26 18:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-26 17:03 Parallel port support Alex deVries
1999-01-26 17:09 ` Dave Olson
1999-01-26 17:09   ` Dave Olson
1999-01-26 17:16   ` Alex deVries
1999-01-26 17:26     ` Ulf Carlsson
1999-01-26 17:55       ` Dave Olson
1999-01-26 17:55         ` Dave Olson
1999-01-26 17:58         ` Ulf Carlsson
1999-01-26 18:33           ` Dave Olson
1999-01-26 18:33             ` Dave Olson
1999-01-26 18:12         ` Alex deVries
1999-01-26 18:34           ` Dave Olson
1999-01-26 18:34             ` Dave Olson
1999-01-26 18:32     ` Dave Olson [this message]
1999-01-26 18:32       ` Dave Olson
1999-01-26 17:21 ` Ulf Carlsson

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=199901261832.KAA17419@anchor.engr.sgi.com \
    --to=olson@anchor.engr.sgi.com \
    --cc=adevries@engsoc.carleton.ca \
    --cc=linux@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