From: Chris Caputo <ccaputo@alt.net>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: Peter Daum <gator@cs.tu-berlin.de>,
Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: 3ware driver (3w-xxxx) in 2.6.10: procfs entry
Date: Sun, 16 Jan 2005 19:52:37 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.44.0501161948350.22840-100000@nacho.alt.net> (raw)
In-Reply-To: <Pine.GSO.4.33.0501101212500.6604-100000@sweetums.bluetronic.net>
On Mon, 10 Jan 2005, Ricky Beam wrote:
> On Mon, 10 Jan 2005, Peter Daum wrote:
> >On Mon, 10 Jan 2005, Christoph Hellwig wrote:
> >> The change came from the driver maintainer at 3ware. Get the updated
> >> tools from their website.
> >
> >Which website do you mean? The programs in the download section of
> >"www.3ware.com" are just the ones that don't work anymore.
>
> Yeap. The "idiot" removed the proc interface from the driver before
> publishing the updated tools -- and I said so at the time. At the time
> the interface was removed, the new tools weren't available - period. They
> are still "beta" today (several months later.)
>
> Just put the procfs code back in the driver in your local tree and
> walk away. That's what I did -- but it doesn't look like I commited
> it to any BK tree :-( (and that box is *ahem* powered off)
Or just grab the latest (version 9.1.5.2) 3dm and tw_cli software from the
3ware web site. These may not be listed as being for your version of the
card, but they will work with the new driver.
Chris
next prev parent reply other threads:[~2005-01-17 3:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 13:03 3ware driver (3w-xxxx) in 2.6.10: procfs entry Peter Daum
2005-01-10 13:21 ` Christoph Hellwig
2005-01-10 13:56 ` Peter Daum
2005-01-10 16:45 ` Andrey Klochko
2005-01-10 17:21 ` Ricky Beam
2005-01-17 3:52 ` Chris Caputo [this message]
2005-01-19 11:09 ` Christoph Hellwig
2005-01-19 12:33 ` Peter Daum
2005-01-20 2:23 ` Jason L Tibbitts III
2005-01-20 4:38 ` Kyle Moffett
[not found] ` <ufais5s4sdk.fsf@epithumia.math.uh.edu>
2005-01-20 4:57 ` Kyle Moffett
2005-02-09 8:41 ` Peter Daum
2005-02-09 9:57 ` Peter Daum
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=Pine.LNX.4.44.0501161948350.22840-100000@nacho.alt.net \
--to=ccaputo@alt.net \
--cc=gator@cs.tu-berlin.de \
--cc=jfbeam@bluetronic.net \
--cc=linux-kernel@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 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).