mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: narancs <narancs@narancs.tii.matav.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DEC KZPSA SCSI card - is there a linux driver?
Date: Mon, 11 Aug 2003 17:06:57 -0400	[thread overview]
Message-ID: <20030811170657.A30357@animx.eu.org> (raw)
In-Reply-To: <3F37A962.4030505@narancs.tii.matav.hu>; from narancs on Mon, Aug 11, 2003 at 04:34:10PM +0200

> I guess this mail should have gone to a mailing list like linux-scsi, 
> but I just couldn't find that list's address - sorry if this mail is not 
> to be here :)
> 
> so I have just got a DEC PCI SCSI card which has a sym53c720 chip and an 
> intel 930 chip and an LSI chip on board. it is a full-length 32bit PCI 
> scsi card. (it was working fine in an alpha axp system with true64 unix, 
> and now it is installed in a PC.)
> 
> with linux kernel 2.4.20 (suse8.2) trying all the modules, I just 
> couldn't get it working.
> I moved the card to other PCI slots and play with irqs, but no success.
> 
> please help that which driver should get it working if this card is 
> supported at all.

Are you sure it's not a raid controller?  Being a full length PCI card, it
may be.  DEC used Mylex DAC960 controller in some of their servers.  My
AS1000A came with 2 single channel DAC960PD cards.  Does it have a slot for
memory? (good indication of being raid)

> 00:0d.0 SCSI storage controller: Digital Equipment Corporation KZPSA [KZPSA]
>         Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- 
> ParErr+ Stepping- SERR+ FastB2B-
>         Status: Cap- 66Mhz- UDF+ FastB2B+ ParErr- DEVSEL=medium >TAbort- 
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 66 (2000ns min, 31750ns max), cache line size 08
>         Interrupt: pin A routed to IRQ 7
>         BIST result: 00
>         Region 0: Memory at fedfd000 (64-bit, non-prefetchable) [size=4K]
>         Region 2: I/O ports at d000 [size=4K]
>         Region 3: Memory at feb00000 (64-bit, non-prefetchable) [size=1M]
>         Expansion ROM at <unassigned> [disabled] [size=64K]

Doesn't seem like a raid controller here.  Is this an alpha machine?

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

      parent reply	other threads:[~2003-08-11 20:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-11 14:34 narancs
2003-08-11 15:54 ` Mr. James W. Laferriere
2003-08-12  7:26   ` narancs
2003-08-11 21:06 ` Wakko Warner [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=20030811170657.A30357@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=narancs@narancs.tii.matav.hu \
    /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

all inboxes | Powered by JetHome®