From: "Adam Radford" <aradford@amcc.com>
To: Ricky Beam <jfbeam@bluetronic.net>,
Christoph Hellwig <hch@infradead.org>
Cc: Linux SCSI List <linux-scsi@vger.kernel.org>
Subject: RE: [BK-PATCH] 3w-9xxx: proc interface
Date: Wed, 7 Jul 2004 11:27:55 -0700 [thread overview]
Message-ID: <I0HVAW03.QOA@hadar.amcc.com> (raw)
Rick,
There should be a beta version of 3dm2 & tw_cli that will work with the in-kernel
3w-9xxx driver on the 3ware website sometime this week.
I'd rather not re-add deprecated interfaces.
-Adam
-----Original Message-----
From: Ricky Beam [mailto:jfbeam@bluetronic.net]
Sent: Friday, July 02, 2004 11:42 AM
To: Christoph Hellwig
Cc: Adam Radford; Linux SCSI List
Subject: Re: [BK-PATCH] 3w-9xxx: proc interface
On Fri, 2 Jul 2004, Christoph Hellwig wrote:
>On Fri, Jul 02, 2004 at 12:08:23PM -0400, Ricky Beam wrote:
>> 3dm2 (the currently available one anyway) needs /proc/scsi/3w-9xxx to
>> discover any controllers. The current in-kernel driver doesn't contain any
>> /proc/scsi support. The attached patch restores the interface.
>
>I'd rather wait for a new 3dm2 release instead of adding deprecated interfaces.
>Adam, any schedule for a new release?
Well, I'm not the only one who cannot monitor/control their array with the
current in-kernel driver. I don't care if the proc interface makes it
back into the kernel; the systems I assemble with a 9500 will have the
proc interface restored until I have a 3dm2 in hand that doesn't need it.
Having a non-functioning 3dm2 is a major problem in my book. (technically,
not have a firmware update interface in the kernel's driver is also a
concern.)
Locking the door before you have a key to get back in is a bad idea.
--Ricky
next reply other threads:[~2004-07-07 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 18:27 Adam Radford [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-02 16:08 [BK-PATCH] 3w-9xxx: proc interface Ricky Beam
2004-07-02 18:35 ` Christoph Hellwig
2004-07-02 18:42 ` Ricky Beam
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=I0HVAW03.QOA@hadar.amcc.com \
--to=aradford@amcc.com \
--cc=hch@infradead.org \
--cc=jfbeam@bluetronic.net \
--cc=linux-scsi@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.