From: "Darrick J. Wong" <djwong@us.ibm.com>
To: John Scarpa <john@tlchosting.com>
Cc: dougg@torque.net, linux-scsi@vger.kernel.org,
Alexis Bruemmer <alexisb@us.ibm.com>
Subject: Re: Please help if u can.
Date: Wed, 21 Feb 2007 12:55:26 -0800 [thread overview]
Message-ID: <45DCB1BE.403@us.ibm.com> (raw)
In-Reply-To: <45DC9053.10908@tlchosting.com>
John Scarpa wrote:
> First a very big thanks to all of u! I have been suffering a serious
> lack of sleep problem lately.. i should have noticed that by whom has
> been submitting the past 500 fixes and updates!
>
> Quick question, is the driver still consider experimental??
Very much so. The SAS bits are fairly stable nowadays, but the rest is
still YMWV. :)
> the guys i
> work with say it doesn't support sata drives and it's still experimental
SATA support is under development. Patches exist in the git tree here:
http://www.kernel.org/git/?p=linux/kernel/git/jejb/aic94xx-sas-2.6.git;a=summary
> so don't use it. And i can't find anything on the state of this driver.
>
> PS. I should have said i dropped that aic94xx-seq.fw in
> /lib,/lib/firmware,/lib64,/lib64/firmware (still have yet to get this
> sucker to work)
Yes, you need a udev that's new enough to know how to handle the
firmware loading interface. Typically, udev will load firmware from
/lib/firmware, though I suppose that depends on the distribution. Not
sure if RH/Fedora support fw loading, newer Ubuntu-E and SuSE do...
--D
next prev parent reply other threads:[~2007-02-21 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 1:16 Please help if u can John Scarpa
2007-02-21 5:21 ` Douglas Gilbert
2007-02-21 6:20 ` Darrick J. Wong
2007-02-21 18:32 ` John Scarpa
2007-02-21 20:55 ` Darrick J. Wong [this message]
2007-02-21 22:56 ` Aravind Parchuri
2007-02-26 22:13 ` Luben Tuikov
2007-02-26 21:56 ` Luben Tuikov
2007-02-26 23:20 ` Luben Tuikov
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=45DCB1BE.403@us.ibm.com \
--to=djwong@us.ibm.com \
--cc=alexisb@us.ibm.com \
--cc=dougg@torque.net \
--cc=john@tlchosting.com \
--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.