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: HAL2 support.
Date: Sun, 24 Jan 1999 20:06:09 -0800 (PST)	[thread overview]
Message-ID: <199901250406.UAA07213@anchor.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.3.96.990124153515.17852A-100000@lager.engsoc.carleton.ca> from Alex deVries at "Jan 24, 99 04:01:19 pm"

Alex deVries wrote: 
|  Also, am I right in saying that there's no devices written for HPC3 that
|  use the pbus?  Looks like the first step to writing a HAL driver is to be
|  able to write to the pbus.

The pbus interface itself is a pretty simple interface.

|  What else is actually on the pbus on the Indy?  From this HPC
|  documentation, looks
|  like:
|  - fdc (I thought Indy floppies were SCSI though)

There was talk of doing floppy this way, but it never was actually done.

|  - rtc
|  - prom
|  - scsi (although not the 33c93)

scsi is off the hpc3, but it's only the control path (pio to registers)
that uses the pbus interface.  The datapath is a different bus.

|  - int2 (what's this?)

interrupt control.

|  - hal2
|  - pi1 (what's this?)

parallel port.

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: HAL2 support.
Date: Sun, 24 Jan 1999 20:06:09 -0800 (PST)	[thread overview]
Message-ID: <199901250406.UAA07213@anchor.engr.sgi.com> (raw)
Message-ID: <19990125040609.3zLT1kqmybrg5a_4JzoCjjrySiWSki7rxlOZpJfsXzw@z> (raw)
In-Reply-To: <Pine.LNX.3.96.990124153515.17852A-100000@lager.engsoc.carleton.ca> from Alex deVries at "Jan 24, 99 04:01:19 pm"

Alex deVries wrote: 
|  Also, am I right in saying that there's no devices written for HPC3 that
|  use the pbus?  Looks like the first step to writing a HAL driver is to be
|  able to write to the pbus.

The pbus interface itself is a pretty simple interface.

|  What else is actually on the pbus on the Indy?  From this HPC
|  documentation, looks
|  like:
|  - fdc (I thought Indy floppies were SCSI though)

There was talk of doing floppy this way, but it never was actually done.

|  - rtc
|  - prom
|  - scsi (although not the 33c93)

scsi is off the hpc3, but it's only the control path (pio to registers)
that uses the pbus interface.  The datapath is a different bus.

|  - int2 (what's this?)

interrupt control.

|  - hal2
|  - pi1 (what's this?)

parallel port.

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

  reply	other threads:[~1999-01-25  4:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-24 21:01 HAL2 support Alex deVries
1999-01-25  4:06 ` Dave Olson [this message]
1999-01-25  4:06   ` Dave Olson
     [not found] <19990128004527.A1266@bun.falkenberg.se>
     [not found] ` <Pine.LNX.3.96.990125122018.21345K-100000@lager.engsoc.carleton.ca>
1999-01-28 18:50   ` Ulf Carlsson
1999-01-25 19:27     ` Alex deVries
1999-01-28 20:32       ` 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=199901250406.UAA07213@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