From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: Linux Kernel Maillist <linux-kernel@vger.kernel.org>
Subject: Re: HP server and atto driver from hell
Date: Wed, 30 Apr 2008 15:16:07 +0200 [thread overview]
Message-ID: <20080430131607.GX15819@charite.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0804291425260.23575@filesrv1.baby-dragons.com>
* Mr. James W. Laferriere <babydr@baby-dragons.com>:
> Hello Ralf , Fyi , the fusion/mpt driver supports some of the ATTO
> devices , if your lspci -v for the ATTO controllers looks simular to this
> one it may just work with the fusion drivers .
> Hth , JimL
>
> # lspci -v -s 0d:04.0
> 0d:04.0 SCSI storage controller: Atto Technology Ultra320 SCSI Host Adapter (rev 08)
> Subsystem: Atto Technology Unknown device 8027
> Flags: bus master, 66MHz, medium devsel, latency 128, IRQ 16
> I/O ports at 5000 [size=256]
> Memory at d8640000 (64-bit, non-prefetchable) [size=256K]
> Memory at d8600000 (64-bit, non-prefetchable) [size=256K]
> Capabilities: [50] Power Management version 2
> Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
> Capabilities: [68] PCI-X non-bridge device
Well, something seems to work:
[ 3.571216] Fusion MPT base driver 3.04.06
[ 3.571274] Copyright (c) 1999-2007 LSI Corporation
[ 3.577292] Fusion MPT SPI Host driver 3.04.06
[ 3.577389] ACPI: PCI Interrupt 0000:14:04.0[A] -> GSI 17 (level, low) -> IRQ 17
[ 3.577512] mptbase: ioc0: Initiating bringup
[ 3.836271] ioc0: LSI53C1030 C0: Capabilities={Initiator,Target}
[ 3.992277] scsi0 : ioc0: LSI53C1030 C0, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=17
[ 3.992277] ACPI: PCI Interrupt 0000:14:04.1[B] -> GSI 18 (level, low) -> IRQ 18
[ 3.992277] mptbase: ioc1: Initiating bringup
[ 4.244297] ioc1: LSI53C1030 C0: Capabilities={Initiator,Target}
[ 4.408304] scsi1 : ioc1: LSI53C1030 C0, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=18
# lspci -v -s 14:04.0
14:04.0 SCSI storage controller: Atto Technology Ultra320 SCSI Host Adapter (rev 08)
Subsystem: Atto Technology Unknown device 802f
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17
I/O ports at 5000 [size=256]
Memory at fdfc0000 (64-bit, non-prefetchable) [size=256K]
Memory at fdf80000 (64-bit, non-prefetchable) [size=256K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [68] PCI-X non-bridge device
Kernel driver in use: mptspi
Kernel modules: mptspi
--
Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt@charite.de
Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962
IT-Zentrum Standort CBF send no mail to snickebo@charite.de
next prev parent reply other threads:[~2008-04-30 13:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 20:17 HP server and atto driver from hell Ralf Hildebrandt
2008-04-29 21:43 ` Alan Cox
2008-04-30 8:26 ` Ralf Hildebrandt
2008-05-06 15:21 ` Ralf Hildebrandt
2008-04-29 22:29 ` Mr. James W. Laferriere
2008-04-30 8:27 ` Ralf Hildebrandt
2008-04-30 13:16 ` Ralf Hildebrandt [this message]
2008-04-30 13:42 ` Ralf Hildebrandt
2008-04-30 14:50 ` Moore, Eric
2008-04-30 16:16 ` Ralf Hildebrandt
2008-05-09 13:03 ` Sven Rudolph
2008-04-30 19:38 ` Alex Chiang
2008-05-06 16:59 ` Ralf Hildebrandt
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=20080430131607.GX15819@charite.de \
--to=ralf.hildebrandt@charite.de \
--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 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.