From: Wakko Warner <wakko@animx.eu.org>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Richard Scobie <richard@sauce.co.nz>,
linux-scsi@vger.kernel.org
Subject: Re: mptsas problem
Date: Tue, 15 Apr 2008 18:49:49 -0400 [thread overview]
Message-ID: <20080415224949.GA9155@animx.eu.org> (raw)
In-Reply-To: <0631C836DBF79F42B5A60C8C8D4E8229FBE557@NAMAIL2.ad.lsil.com>
Moore, Eric wrote:
>
> > Does "chip rev" mean software/firmware or an actual chip? Is
> > there anyway
> > the driver can see this and set the queue_depth to 1?
>
> When I mean chip, I'm refering to hardware. The revision of your
> chip(1064/1068/1078) is located at offset 8 in pci config space. This
> also known as PCI_CLASS_REVISION. You can get this by using the tool
> called lspci.
04:02.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068 PCI-X
Fusion-MPT SAS (rev 01)
00: 00 10 54 00 56 01 30 02 01 00 00 01 08 48 00 00
10: 01 50 00 00 04 00 41 d8 00 00 00 00 04 00 40 d8
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 10 30 30
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 40 0a
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 01 98 02 06 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 07 b0 60 10 10 04 43 13
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 05 68 80 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 11 00 00 00 01 20 00 00 01 30 00 00 00 00 00 00
I'm not that familiar with the pci config space. Are you saying that I need
a new chip for the new firmware? If so, considering everything is soldered
on the board, I'd have a hard time replacing it! =)
--
Lab tests show that use of micro$oft causes cancer in lab animals
Got Gas???
next prev parent reply other threads:[~2008-04-15 22:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 23:40 mptsas problem Richard Scobie
2008-04-07 1:04 ` Wakko Warner
2008-04-13 13:00 ` Douglas Gilbert
2008-04-13 14:39 ` James Bottomley
2008-04-13 14:31 ` James Bottomley
2008-04-13 16:48 ` Wakko Warner
2008-04-13 16:58 ` James Bottomley
2008-04-13 17:06 ` Wakko Warner
2008-04-13 17:37 ` James Bottomley
2008-04-13 20:49 ` Wakko Warner
2008-04-14 18:16 ` Moore, Eric
2008-04-14 21:34 ` Wakko Warner
2008-04-15 17:26 ` Moore, Eric
2008-04-15 22:49 ` Wakko Warner [this message]
2008-04-13 22:22 ` Douglas Gilbert
2008-04-13 23:51 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2008-04-06 19:56 Wakko Warner
[not found] ` <0631C836DBF79F42B5A60C8C8D4E8229F64FC1@NAMAIL2.ad.lsil.com>
2008-04-07 1:07 ` Wakko Warner
2008-04-07 11:36 ` Bernd Schubert
2008-04-07 15:16 ` Moore, Eric
2008-04-07 16:54 ` Wakko Warner
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=20080415224949.GA9155@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=richard@sauce.co.nz \
/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