Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Christoph Plattner <christoph.plattner@gmx.at>
To: "M. Grabert" <xam@cs.ucc.ie>
Cc: "parisc-linux@lists.parisc-linux.org"
	<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] SCSI driver for E-class servers - SPIFI ?
Date: Thu, 13 Jun 2002 22:26:49 +0200	[thread overview]
Message-ID: <3D090009.CB2EF7B7@gmx.at> (raw)
In-Reply-To: Pine.LNX.4.44.0206122318230.3448-100000@sal.ucc.ie

Thanks, for the answers.

I never thought, the SE stands here for the single ended, I know the 
difference between SE and differential.

BTW: It's me, who wrote the MUX console support, and this is already
checked in into the Linux tree (for half an year now). 
But I am interested in having a full device support....

Christoph P.



"M. Grabert" wrote:
> 
> On Wed, 12 Jun 2002, Christoph Plattner wrote:
> 
> > Sorry, that I am not so "deep" in the HP device knowledge, can you give
> > me sime hints !
> >
> > HP-BP is this a HP bus system ?
> 
> Yes, it's the HP Precision Bus (aka NIO). AFAIK it's mainly used in the
> (very) old servers, like F10. I don't know what the current status of
> support
> is, but it used to be unsupported (no docu ?).
> 
> (hint: www.parisc-linux.org ->glossary, mailing list archive)
> 
> > Is this used in the E55 (or similar) ?
> 
> Yes. Although (regarding to www.openpa.net) something like a modified
> version.
> 
> (hint: www.openpa.net, www.google.com, www.parisc-linux.org ->hardware
> database)
> 
> > Is the "SE" SCSI that one in the E55 (what stands "SE" for) ?
> 
> SE stands for SingleEnded and reffers to how the SCSI device is connected
> (signalling etc.). It's the "normal" SCSI (unlike LVD,
> LowVoltageDifferential), used in SCSI-I and SCSI-II (narrow)
> 
> > What is SDTR ?
> 
> It's the signal send on the scsi bus to negotiate syncronous data
> transfer (or asynchronous sent with a REQ/ACK) if they support it.
> 
> > Sorry, but I am interested in that stuff, and I know, I can help after
> > initial steps. Some weeks ago, I rewrote an ethernet driver of an
> > not-well known chip on an VAX termianl for VAX Linux. So after some
> > hacking days (or better nights), there will be real progress.
> >
> > So I am interested in helping here.
> 
> nice :)
> 
> > Sorry for this question again:
> > What is the status of the MUX. As far I can remember, you started to
> > write on this driver. Is this correct ?
> 
> Perhaps s.o. can answer this question. AFAIK somebody is indeed writing
> on it and has succeded to use the console port on the MUX.
> 
> geretings max

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

  reply	other threads:[~2002-06-13 20:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-10 20:04 [parisc-linux] SCSI driver for E-class servers - SPIFI ? Christoph Plattner
2002-06-10 21:53 ` Grant Grundler
2002-06-10 23:16   ` Christoph Plattner
2002-06-11 21:39     ` Grant Grundler
2002-06-12 21:21       ` Christoph Plattner
2002-06-12 22:36         ` M. Grabert
2002-06-13 20:26           ` Christoph Plattner [this message]
2002-06-12 23:06         ` Grant Grundler
2002-06-12 23:08         ` Grant Grundler
2002-06-13 20:30           ` Christoph Plattner
2002-06-13 21:11             ` Grant Grundler
2002-06-13 21:18               ` Christoph Plattner

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=3D090009.CB2EF7B7@gmx.at \
    --to=christoph.plattner@gmx.at \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=xam@cs.ucc.ie \
    /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