linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: [PATCH] Add VPD support to aacraid
Date: Thu, 25 Jan 2007 10:07:02 +0100	[thread overview]
Message-ID: <45B87336.5070707@suse.de> (raw)

Hi Mark,

I found to my surprise that the aacraid driver does not support VPD
pages at all. I'm somewhat used to modern SCSI HBAs export SCSI-2 disks,
but not supporting VPD pages at all is really a bit .. hmm .. SCSI-1-ish.
And it makes it really impossible to assign a persistent device ID to
those drives.

And it really made my eyes hurt. Now that I have the latest, top-of-the
range SAS drives with a real HW RAID controller and the disks are
exported as

SCSI-2.

Just as I thought we'd been finally past those days. Sigh.

Anyway, I don't think that it should be too hard to add proper VPD page
support (ie page 0x83), but for that one would have some documentation
how to ask the controller for it. I'll leave that to you :-)
You can use the page 0x80 support as a template.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke			hare@suse.de
SuSE Linux Products GmbH		S390 & zSeries
Maxfeldstraße 5				+49 911 74053 688
90409 Nürnberg				http://www.suse.de
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2007-01-25  9:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25  9:07 Hannes Reinecke [this message]
2007-01-25  9:47 ` [PATCH] Add VPD support to aacraid Hannes Reinecke
2007-01-25 18:19   ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2007-01-25 18:37 Salyzyn, Mark
2007-01-26  8:04 ` Hannes Reinecke

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=45B87336.5070707@suse.de \
    --to=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    /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;
as well as URLs for NNTP newsgroup(s).