public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: "Martin K. Petersen" <mkp@mkp.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Booting from or using a Compaq RA4100 Array
Date: Tue, 3 Jan 2006 08:51:30 +0100	[thread overview]
Message-ID: <200601030851.30624@bilbo.math.uni-mannheim.de> (raw)
In-Reply-To: <yq1oe2u2z6i.fsf@wilson.lab.mkp.net>

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]

Am Montag, 2. Januar 2006 20:43 schrieben Sie:
>>>>>> "Mark" == Mark Schaefer <mark@markschaefer.org> writes:
>
>Mark> 	Also, any info on the Tachyon chips would be helpful.  I have
>Mark> a TS and a HPFC-5000C (32-bit old chip).
>
>HPFC-5000 is the original HP Tachyon design which my driver won't
>support.  It doesn't have FCP support in hardware or anything.  My
>driver only does TachLite.
>
>My aim is to support the following boards:
>
>HP A5156A	HPFC-5100 /2.0	(TL)
>HP A5157A	HPFC-5100B/2.2	(TL) dual port
>HP A5158A	HPFC-5100C/2.3	(TL)
>HP A5158A	HPFC-5100D/3.0	(TL)
>HP A6795A	HPFC-5200C/2.2	(XL2)
>Compaq FC HBA   HPFC-5166A/1.2  (TS)
>
>The Compaq FC HBA is the one that the RA-4x00 people have.  I don't
>have this controller yet but there should be one waiting for me at the
>post office once the world goes out of suspend mode tomorrow...

Ok, can you collect such a list of the "other" cards that your driver does not 
support? And a list of PCI ids that match both lists?

These are the devices supported by the original cpqfc driver:

#define PCI_DEVICE_ID_COMPAQ_TACHYON    0xa0fc
#define PCI_DEVICE_ID_HP_TACHYON        0x1028
#define PCI_DEVICE_ID_HP_TACHLITE       0x1029

I now own a Agilent HHBA-5121. What's that for a thing?

Eike

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-01-03  7:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-28 20:29 Booting from or using a Compaq RA4100 Array Mark Schaefer
2005-12-29  7:45 ` Rolf Eike Beer
2005-12-29 21:51   ` mark
2005-12-29 22:02     ` Rolf Eike Beer
2005-12-30 14:39       ` mark
2005-12-30 22:18       ` Martin K. Petersen
2006-01-02  2:22         ` Mark Schaefer
2006-01-02 16:18           ` Christoph Hellwig
2006-01-02 19:43           ` Martin K. Petersen
2006-01-03  7:51             ` Rolf Eike Beer [this message]
2006-01-03 12:34               ` Matthew Wilcox
2006-01-03 16:28                 ` Rolf Eike Beer
2006-01-03 19:20               ` Martin K. Petersen
  -- strict thread matches above, loose matches on Subject: below --
2005-12-30 14:40 mark
2006-02-06 17:46 cpqfc gone - all compay RA4X00 Array now useless in linux? Ingo Flaschberger
2006-02-06 18:23 ` Rolf Eike Beer
2006-02-06 18:38   ` Ingo Flaschberger
2006-02-07  7:55     ` Rolf Eike Beer
2006-02-07 10:05       ` Booting from or using a Compaq RA4100 Array Ingo Flaschberger

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=200601030851.30624@bilbo.math.uni-mannheim.de \
    --to=eike-kernel@sf-tec.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mkp@mkp.net \
    /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