From: Meelis Roos <mroos@linux.ee>
To: Don Brace <don.brace@microsemi.com>
Cc: Hannes Reinecke <hare@suse.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>,
James Bottomley <james.bottomley@hansenpartnership.com>,
Jens Axboe <axboe@kernel.dk>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Hannes Reinecke <hare@suse.com>
Subject: RE: [PATCH] hpsa: add support for legacy boards
Date: Tue, 11 Jul 2017 18:58:36 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1707111853330.9598@math.ut.ee> (raw)
In-Reply-To: <4993A297653ECB4581FA5C3C31323D19533CE9D1@avsrvexchmbx2.microsemi.net>
> The 5i controller is probably too old for the hpsa driver to support.
> The hpsa driver is looking for information to determine if the drive is online/offline and
> this information is not available.
>
> What was the original issue you were having with the cciss driver?
Christoph Hellwig updated block layer with "block: Make most
scsi_req_init() calls implicit" and at first try, cciss was left without
the needed initialization. This caused OOPS in udev probing but the
system worked. The issue was fixed by Christoph quickly.
But he suggested it might be worth trying hpsa driver instead of cciss,
with a longer term goal to to move users of cciss over to hpsa if
possible. Now that I have tested it, it seems not all older cards are
supported in hpsa - it's more than ID-s and interrupt masks.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2017-07-11 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 6:49 [PATCH] hpsa: add support for legacy boards Hannes Reinecke
2017-07-11 14:25 ` Meelis Roos
2017-07-11 15:38 ` Don Brace
2017-07-11 15:58 ` Meelis Roos [this message]
2017-07-12 7:11 ` Christoph Hellwig
2017-07-12 7:12 ` Hannes Reinecke
2017-08-02 15:05 ` 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=alpine.LRH.2.20.1707111853330.9598@math.ut.ee \
--to=mroos@linux.ee \
--cc=axboe@kernel.dk \
--cc=don.brace@microsemi.com \
--cc=hare@suse.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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