From: Alan <alan@lxorguk.ukuu.org.uk>
To: Tejun Heo <htejun@gmail.com>
Cc: Art Haas <ahaas@airmail.net>, linux-ide@vger.kernel.org
Subject: Re: CDROM drive not found when booting using new libata code
Date: Thu, 7 Dec 2006 10:55:25 +0000 [thread overview]
Message-ID: <20061207105525.4ebb4547@localhost.localdomain> (raw)
In-Reply-To: <45779852.1030909@gmail.com>
On Thu, 07 Dec 2006 13:28:02 +0900
Tejun Heo <htejun@gmail.com> wrote:
> Please test the attached patch.
That should be getting done automatically by the driver and used to work
with the old eh/probe code. It does rely on having done the initial PIO0
identify of both devices and the mode decision being made before mode
setting functions are called however, and that is/was documented as a
guarantee, and is relied upon all over.
Definitely worth testing Art, especially if it shows something up.
Tejun: pata_amd does the timing merges itself both for 8bit which is
shared and in the timing compute for the DMA cases. Also the other
pattern to these reports is ATAPI, although that might I guess be a
symptom of "slave".
The other problem is that mmio bus reset is broken, but the AMD always
uses PIO cycles so that shouldn't be involved.
Alan (still baffled by this one)
next prev parent reply other threads:[~2006-12-07 10:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 22:10 CDROM drive not found when booting using new libata code Art Haas
2006-11-21 9:26 ` Tejun Heo
2006-12-06 18:16 ` Art Haas
2006-12-07 4:28 ` Tejun Heo
2006-12-07 10:55 ` Alan [this message]
2006-12-07 12:37 ` Tejun Heo
2006-12-08 1:06 ` Art Haas
2006-12-27 13:29 ` Tejun Heo
2006-12-28 3:51 ` Tejun Heo
2007-01-02 21:07 ` Art Haas
2007-01-03 3:31 ` Tejun Heo
2007-01-03 18:08 ` Art Haas
2007-01-03 23:19 ` Dâniel Fraga
-- strict thread matches above, loose matches on Subject: below --
2007-03-14 19:33 YUP
2007-03-14 19:59 YUP
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=20061207105525.4ebb4547@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ahaas@airmail.net \
--cc=htejun@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).