From: Markku Pesonen <tourula@gmail.com>
To: Darren Stevens <darren@stevens-zone.net>
Cc: Tejun Heo <tj@kernel.org>, linux-ide@vger.kernel.org
Subject: Re: pata_atiixp regression in 4.11-rc1
Date: Tue, 28 Mar 2017 12:57:42 +0300 [thread overview]
Message-ID: <d9c9cb23-e67f-779d-240d-e02f7d87e405@gmail.com> (raw)
In-Reply-To: <49cdecb0846.6a8a0888@auth.smtp.1and1.co.uk>
On 28.03.2017 11:24, Darren Stevens wrote:
> Hello Tejun
>
> On 27/03/2017, Tejun Heo wrote:
>> From a431ecd2d459da3c91a612061f09eb422ffe78e2 Mon Sep 17 00:00:00 2001
>> From: Tejun Heo <tj@kernel.org>
>> Date: Mon, 27 Mar 2017 13:52:00 -0400
>> Subject: [PATCH] Revert "pata_atiixp: Don't use unconnected secondary
>> port on SB600/SB700"
>>
>> This reverts commit 5946fdaee4ba449e8fbb5d403e1ed69437f916e8.
>>
>> The original commit's assumption that the secondary port is
>> unconnected turns out to be false.
>
> Not entirely. I based my patch on information in AMD's document
> 43366_sb7xx_bdg_pub_1.00.p
I found this in the AMD SB710 Databook, rev 1.60, p. 56:
"The integrated parallel ATA controller contains a single channel but
can be configured as primary or secondary channel."
The IDE connector on my Asrock 980DE3/U3S3 motherboard is configured as
the secondary channel. The primary channel is used by the optional
SATA-IDE emulation mode.
I don't know much about kernel programming, southbridges, or ata
controllers, but I hope this bit of information helps.
next prev parent reply other threads:[~2017-03-28 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 7:31 pata_atiixp regression in 4.11-rc1 Markku Pesonen
[not found] ` <CGME20170327092244epcas1p18acab65df487d4813421302740fa946b@epcas1p1.samsung.com>
2017-03-27 9:22 ` Bartlomiej Zolnierkiewicz
2017-03-27 17:49 ` Tejun Heo
2017-03-27 17:55 ` Tejun Heo
2017-03-28 8:24 ` Darren Stevens
2017-03-28 9:57 ` Markku Pesonen [this message]
2017-03-28 15:58 ` Tejun Heo
2017-03-28 15:56 ` Darren Stevens
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=d9c9cb23-e67f-779d-240d-e02f7d87e405@gmail.com \
--to=tourula@gmail.com \
--cc=darren@stevens-zone.net \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).