From: Jeff Garzik <jgarzik@pobox.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Matt Domsch <Matt_Domsch@dell.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: ata_piix: port disabled. ignoring.
Date: Thu, 20 May 2004 01:00:57 -0400 [thread overview]
Message-ID: <40AC3B89.9060900@pobox.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0405171545490.19405@waterleaf.sonytel.be>
Geert Uytterhoeven wrote:
> If I try to work around the problem by applying this patch:
>
> --- linux-2.6.6-bk4/drivers/scsi/ata_piix.c.orig 2004-05-17 20:02:25.000000000 +0200
> +++ linux-2.6.6-bk4/drivers/scsi/ata_piix.c 2004-05-17 20:59:15.000000000 +0200
> @@ -330,8 +330,8 @@
> if (!pci_test_config_bits(ap->host_set->pdev,
> &piix_enable_bits[ap->port_no])) {
> ata_port_disable(ap);
> - printk(KERN_INFO "ata%u: port disabled. ignoring.\n", ap->id);
> - return;
> + //printk(KERN_INFO "ata%u: port disabled. ignoring.\n", ap->id);
> + printk(KERN_INFO "ata%u: port disabled. NOT IGNORING!\n", ap->id);
> }
>
> if (!piix_sata_probe(ap)) {
>
> everything works fine, even if I disable the second SATA port in the BIOS:
I think this check is vaguely incorrect, because it sounds like you are
in combined mode. That would imply that ap->port_no is incorrect, for
this one special case. (details: in combined aka legacy mode, port
number is always zero because it is initialized as two separate hosts,
not one host with two ata_ports)
However, since this is SATA, and PIIX does at least give us a "no
device" indication, we could probably just delete the 'if' and the code
you are commenting out as well.
Ponder, ponder...
Another thing I am pondering is detecting combined mode in
drivers/pci/quirks.c, and reconfiguring the motherboard such that is it
no longer in combined mode.
Jeff
prev parent reply other threads:[~2004-05-20 5:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 13:11 ata_piix: port disabled. ignoring Geert Uytterhoeven
2004-05-14 15:09 ` Matt Domsch
2004-05-14 15:38 ` Geert Uytterhoeven
2004-05-14 16:02 ` Jeff Garzik
2004-05-17 11:10 ` Geert Uytterhoeven
2004-05-17 14:19 ` Geert Uytterhoeven
2004-05-18 13:20 ` Bartlomiej Zolnierkiewicz
2004-05-19 7:48 ` Geert Uytterhoeven
2004-05-19 13:10 ` Bartlomiej Zolnierkiewicz
2004-05-24 9:51 ` Geert Uytterhoeven
2004-05-24 10:55 ` Bartlomiej Zolnierkiewicz
2004-05-20 5:00 ` Jeff Garzik [this message]
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=40AC3B89.9060900@pobox.com \
--to=jgarzik@pobox.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=Matt_Domsch@dell.com \
--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