Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Jason Eckhardt <jason@equator.com>
To: hppa-linux@thepuffingroup.com
Subject: Re: [hppa-linux] Document Priority?
Date: Mon, 22 Mar 1999 11:52:16 -0800 (PST)	[thread overview]
Message-ID: <199903221952.LAA23806@gatekeeper.equator.com> (raw)


>
> 	Does anyone have particular machines/chips/subassemblies that
> they are desperate for documentation on?  I've been working on "LASI"
> which is the I/O subsystem for the 712 (and pretty much all 7100LC, 
> 7300LC, 7200, 8000, 8200 based computers).  I'm currently digging for
> I/O docs for the earlier machines like the 720/730 adn early 715s.
>

  Not sure about everyone else, but I'd be intersted in these to get C
  class machines up and running. Its likely that these at least overlap
  the other systems:

   1. Onyx ERS (PCXU).
   2. CORE I/O on Raven or similar systems. Not sure if this is the same
      as LASI on 712.
   3. Graphics subsystems. For my machine in particular, builtin 
      Visualize-EG (goat).
   4. Any bug reports that MUST be worked around by the OS. In particular,
      I believe the S-chip had problems that could not be ignored by the OS.


   I'm sure I'll think of more.

> 	What output format should I generate? PostScript? PDF? PCL?
>

  1st PDF or 2nd PS.
  Forget PCL.

  Jason.

             reply	other threads:[~1999-03-22 19:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-22 19:52 Jason Eckhardt [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-03-25 19:56 [hppa-linux] Document Priority? Jason Eckhardt
1999-03-22 18:56 Bill Katz
1999-03-22 19:59 ` Alan Cox
1999-03-25 16:49 ` Michael Shalayeff

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=199903221952.LAA23806@gatekeeper.equator.com \
    --to=jason@equator.com \
    --cc=hppa-linux@thepuffingroup.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