[hppa-linux] Document Priority?

[hppa-linux] Document Priority?

[Bill Katz]

Hello,
	I'm currently digging around, looking under rocks, and digging
up old documents that we eventually hope to clean up and release as
part of HPs support for this project.

	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.

	I just got source code for the PA7100LC processor ERS that I need
to go through and make suitable for release to the world.  It for
example has details on the hardware TLB miss handler.  Would this
be a priority given today's discussion of TLBs?

	Perhaps the biggest challenge is resurrecting appropriate versions
of TROFF and TeX to process these things.

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

	-Bill Katz

Re: [hppa-linux] Document Priority?

[Jason Eckhardt]

>
> 	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.

Re: [hppa-linux] Document Priority?

[Alan Cox]

The TLB miss stuff would be a good early one, that and the basic I/O.
The normal approach ports have taken is to get the basic kernel core
up and then the network card. That lets you use an NFS root - and means you
don't turn your disk to sillyputty while debugging the vm bugs 

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

I can still work nroff ;)

Re: [hppa-linux] Document Priority?

[Michael Shalayeff]

hi
looking at the released pdc/iodc docs i'm wondering what is in the missing
chapters? is it possible to release the whole contents table?
what are the plans for the rest of the book(s) ?
and, is there any plan for "pa-risc IO architecture" release any soon?

thanks,
-- 
    paranoic mickey       (my employers have changed but, the name has remained)

Re: [hppa-linux] Document Priority?

[Jason Eckhardt]

>
> hi
> looking at the released pdc/iodc docs i'm wondering what is in the missing
> chapters? is it possible to release the whole contents table?
> what are the plans for the rest of the book(s) ?
> and, is there any plan for "pa-risc IO architecture" release any soon?

  The PDC/IODC docs posted are actually a subset of the chapters of the
  PA-RISC I/O architecture doc. The first 8 or so chapters of the I/O
  doc contain specific information about the various "Module" types (such
  as processor modules, memory modules, I/O modules, bus converters, etc).
  The last 4-5 chapters and appendices are the same as the PDC/IODC docs we
  have.

  I'm not sure why we were given only the subset (which pertains only to
  the firmware) but I believe we can get a decent start with it. Eventually,
  we will need the other information if we intend to have working device
  drivers, etc. Of course, we can trudge through MkLinux code to figure some of
  it out, but I'd much prefer the doc.

  Jason.