Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Christoph Plattner <christoph.plattner@dot.at>
To: Grant Grundler <grundler@cup.hp.com>
Cc: plaven@ozemail.com.au, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] 800/G30, G50, E55 Support?
Date: Wed, 31 Jan 2001 20:11:39 +0100	[thread overview]
Message-ID: <3A78636B.18A9195B@dot.at> (raw)
In-Reply-To: 200101311830.KAA29281@milano.cup.hp.com

He, that's interesting:

See link:
	http://www.mkg.sfc.keio.ac.jp/support/FAQ/README

Here a copy and paste out of it:

2.2 MIPS

RT-Mach and 4.4BSD Lite server for MIPS-based Sony NEWS workstation
currently support the following devices.

        CPU:    R4400 (and compatibles).
        Devices:Built-in Serial (Zilog 85230 ESCC)
                Built-in SCSI (HP SPIFI)
                Built-in Ethernet (Sony SONIC)
                Video Board (NWB-1102)
                Keyboard
                Mouse

It seem as they support the SPIFI of HP !
I have not downloaded yet. I have to register and I want to read around
that stuff.
I also does not know, if this is a source snapshot.
But perhaps it can help .....

Cheers
	Christoph


Grant Grundler wrote:
> 
> Christoph Plattner wrote:
> > But there are some people who are interested in writing drivers
> > for these machines and I want to use my E55 (9000/856). I only
> > need the input (doucmentation, HP-UX sources, etc) to do such
> > work (especially for the 8-port serial multiplexer).
> ...
> > Where can I get the INFOS to do that ????
> 
> I've sent some HP internal URLs to someone in HP who expressed interested
> in getting SPIFI (NIO SCSI) docs published. I haven't heard back from him
> in a while.
> 
> Someone from HP who shares your interest can do either (or both)
> of the following two things:
> o write and publish an initial version of the code you need and provide
>   technical support when needed. This is what I did for ccio code.
>   (which is trivial compared to writing SPIFI chip support)
> o Enable someone else to write the code by: review the relevant
>   unpublished docs, fix references to IP not owned by HP, delete
>   people/project names, get an HP attorney to review and bless the result.
> 
> Any other takers inside HP?
> If so reply to me privately and I'll try to help locate the documents.
> 
> grant
> 
> Grant Grundler
> parisc-linux {PCI|IOMMU|SMP} hacker
> +1.408.447.7253
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux

-- 
-------------------------------------------------------------------------
private:	christoph.plattner@dot.at
company:	christoph.plattner@alcatel.at

      parent reply	other threads:[~2001-01-31 19:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-27  4:38 [parisc-linux] HP9000 800/G30 and G50 Support? Pete
2001-01-30  7:01 ` Pete
2001-01-30 13:49   ` Matthew Wilcox
2001-01-31  7:03     ` Pete
2001-01-31 18:14       ` [parisc-linux] 800/G30, G50, E55 Support? Christoph Plattner
2001-01-31 18:30         ` Grant Grundler
2001-01-31 18:54           ` Christoph Plattner
2001-01-31 19:11           ` Christoph Plattner [this message]

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=3A78636B.18A9195B@dot.at \
    --to=christoph.plattner@dot.at \
    --cc=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=plaven@ozemail.com.au \
    /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