From: George Kibardin <george-kibardin@yandex.ru>
To: linux-ide@vger.kernel.org
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: 80 wire cable detection patch
Date: Sun, 06 Jan 2008 22:00:36 +0300 [thread overview]
Message-ID: <47812554.4060606@yandex.ru> (raw)
In-Reply-To: <200801051921.45084.bzolnier@gmail.com>
Signed-off-by: George Kibardin <george-kibardin@yandex.ru>
--- drivers/ide/ide-iops.c.orig 2008-01-03 18:35:23.000000000 +0300
+++ drivers/ide/ide-iops.c 2008-01-03 18:12:29.000000000 +0300
@@ -612,12 +612,12 @@
printk(KERN_DEBUG "%s: skipping word 93 validity check\n",
drive->name);
- if (hwif->cbl != ATA_CBL_PATA80 && !ivb)
- goto no_80w;
-
if (ide_dev_is_sata(id) && !ivb)
return 1;
+ if (hwif->cbl != ATA_CBL_PATA80 && !ivb)
+ goto no_80w;
+
/*
* FIXME:
* - change master/slave IDENTIFY order
Best,
George
> Hi,
>
> On Thursday 03 January 2008, George Kibardin wrote:
>
>> Hi Bartlomiej,
>>
>> I hope that you are the right person to look at my proposal.
>> I use 2.6.23-gentoo-r3 kernel on VIA Epia EX motherboard with WD SATA
>> HDD connected to it. (I don't understand exactly why, but kernel thinks
>> that this is not SATA HDD. It assigns name hda to it, there is no words
>> SATA in logs, loading via_sata modules doesn't change situation,
>> via82cxxx module detect this chipset correctly, there is no word SATA in
>> BIOS etc.). During boot I get:
>>
>
> There is probably PATA->SATA bridge on the motherboard.
>
>
>> host side 80-wire cable detection failed, limiting max speed to UDMA33
>>
>> (of course it is true - I don't have even 40 wires :-)
>> Digging the code I've figured out that for some reason checking that
>> there is 80 wire cable connected happens before checking that drive is
>> SATA. I've changed the order and this fixed my problem. Unfortunately, I
>> have not enough hardware to test this. The only thing I'm wondering - is
>> this bug or feature? Maybe you know the reason why sata check should go
>> almost last?
>>
>
> Your fix looks fine and is similar to how libata handles PATA->SATA bridges.
>
> Please add "Signed-off-by:" line,
>
>
>> --- drivers/ide/ide-iops.c.orig 2008-01-03 18:35:23.000000000 +0300
>> +++ drivers/ide/ide-iops.c 2008-01-03 18:12:29.000000000 +0300
>> @@ -612,12 +612,12 @@
>> printk(KERN_DEBUG "%s: skipping word 93 validity check\n",
>> drive->name);
>>
>> - if (hwif->cbl != ATA_CBL_PATA80 && !ivb)
>> - goto no_80w;
>> -
>> if (ide_dev_is_sata(id))
>> return 1;
>>
>
> change it to 'if (ide_dev_is_sata(id) && !ivb)' (some ATAPI devices needing
> IVB quirk like to identify themselves like SATA ones, but they aren't),
>
>
>> + if (hwif->cbl != ATA_CBL_PATA80 && !ivb)
>> + goto no_80w;
>> +
>> /*
>> * FIXME:
>> * - change master/slave IDENTIFY order
>>
>>
>
> and resubmit (cc:ing linux-ide@vger.kernel.org mailing list).
>
> Thanks,
> Bart
>
>
next parent reply other threads:[~2008-01-06 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <477D0BDF.6020801@yandex.ru>
[not found] ` <200801051921.45084.bzolnier@gmail.com>
2008-01-06 19:00 ` George Kibardin [this message]
2008-01-09 23:26 ` 80 wire cable detection patch Bartlomiej Zolnierkiewicz
2008-01-10 7:52 ` George Kibardin
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=47812554.4060606@yandex.ru \
--to=george-kibardin@yandex.ru \
--cc=bzolnier@gmail.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).