From: "Georg C. F. Greve" <greve@gnu.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, rick@linuxmafia.com
Subject: Re: Problem with Promise SATA-II 150 TX4 Controller (rev 2) [105a:3d18]
Date: Tue, 28 Dec 2004 19:53:38 +0100 [thread overview]
Message-ID: <m3pt0u45l9.fsf@reason.gnu-hamburg> (raw)
In-Reply-To: <m3zmzy492i.fsf@reason.gnu-hamburg> (Georg C. F. Greve's message of "Tue, 28 Dec 2004 18:38:29 +0100")
[-- Attachment #1.1: Type: text/plain, Size: 286 bytes --]
[update]
After some more investigation, I stumbled upon the thread that dealt
with the Promise 579 in October 2004, which contained a similar
situation and error message with the proposed fix at
http://marc.theaimsgroup.com/?l=linux-ide&m=109814647928388&w=2
so I made the changes
[-- Attachment #1.2: patch --]
[-- Type: text/plain, Size: 818 bytes --]
--- linux-2.6.10/drivers/scsi/sata_promise.c 2004-12-24 22:35:23.000000000 +0100
+++ linux-2.6.10-lirc/drivers/scsi/sata_promise.c 2004-12-28 19:03:31.000000000 +0100
@@ -160,10 +160,11 @@ static struct pci_device_id pdc_ata_pci_
board_20319 },
{ PCI_VENDOR_ID_PROMISE, 0x3319, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
board_20319 },
+ { PCI_VENDOR_ID_PROMISE, 0x3d18, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
+ board_20319 },
{ } /* terminate list */
};
-
static struct pci_driver pdc_ata_pci_driver = {
.name = DRV_NAME,
.id_table = pdc_ata_pci_tbl,
@@ -408,6 +409,8 @@ static irqreturn_t pdc_interrupt (int ir
spin_lock(&host_set->lock);
+ writel(mask, mmio_base + PDC_INT_SEQMASK);
+
for (i = 0; i < host_set->n_ports; i++) {
VPRINTK("port %u\n", i);
ap = host_set->ports[i];
[-- Attachment #1.3: Type: text/plain, Size: 61 bytes --]
and recompiled.
When rebooting, this was the dmesg output
[-- Attachment #1.4: Type: text/plain, Size: 1137 bytes --]
sata_promise version 1.01
ACPI: PCI interrupt 0000:02:0c.0[A] -> GSI 20 (level, low) -> IRQ 20
ata3: SATA max UDMA/133 cmd 0xF881A200 ctl 0xF881A238 bmdma 0x0 irq 20
ata4: SATA max UDMA/133 cmd 0xF881A280 ctl 0xF881A2B8 bmdma 0x0 irq 20
ata5: SATA max UDMA/133 cmd 0xF881A300 ctl 0xF881A338 bmdma 0x0 irq 20
ata6: SATA max UDMA/133 cmd 0xF881A380 ctl 0xF881A3B8 bmdma 0x0 irq 20
ata3: no device found (phy stat 00000000)
scsi4 : sata_promise
ata4: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:407f
ata4: dev 0 ATA, max UDMA/133, 390721968 sectors: lba48
ata4: dev 0 configured for UDMA/133
scsi5 : sata_promise
ata5: no device found (phy stat 00000000)
scsi6 : sata_promise
ata6: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:407f
ata6: dev 0 ATA, max UDMA/133, 390721968 sectors: lba48
ata6: dev 0 configured for UDMA/133
scsi7 : sata_promise
Vendor: ATA Model: ST3200822AS Rev: 3.01
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: ST3200822AS Rev: 3.01
Type: Direct-Access ANSI SCSI revision: 05
[-- Attachment #1.5: Type: text/plain, Size: 467 bytes --]
which does not yet look perfect, but it seems to work.
The disks are present in the system and can be partitioned. Will let
you know in case I run into problems.
Any chance to have the adapter supported in the next release? :)
Regards,
Georg
--
Georg C. F. Greve <greve@gnu.org>
Free Software Foundation Europe (http://fsfeurope.org)
Brave GNU World (http://brave-gnu-world.org)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-12-28 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 17:38 Problem with Promise SATA-II 150 TX4 Controller (rev 2) [105a:3d18] Georg C. F. Greve
2004-12-28 18:53 ` Georg C. F. Greve [this message]
2005-01-03 12:43 ` sata_promise support for pci id 0x3d18 {Re: Problem with Promise SATA-II 150 TX4 Controller (rev 2) [105a:3d18]} Christian Vogel
2005-02-06 4:51 ` Problem with Promise SATA-II 150 TX4 Controller (rev 2) [105a:3d18] Jeff Garzik
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=m3pt0u45l9.fsf@reason.gnu-hamburg \
--to=greve@gnu.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=rick@linuxmafia.com \
/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).