From: Mark Lord <liml@rtr.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alan Cox <alan@redhat.com>,
"Richardson, Charlotte" <Charlotte.Richardson@stratus.com>,
jgarzik@pobox.com, "Petrakis, Peter" <Peter.Petrakis@stratus.com>,
"Duval, Dan" <Dan.Duval@stratus.com>,
"Dailey, Nate" <Nate.Dailey@stratus.com>,
linux-ide@vger.kernel.org
Subject: Re: ata-piix.c (and libata.ko) in RHEL5.1 (build 78 currently) - this kernel is 2.6.18 baqsed
Date: Fri, 22 Feb 2008 12:37:28 -0500 [thread overview]
Message-ID: <47BF0858.9050400@rtr.ca> (raw)
In-Reply-To: <20080222170312.4c849c0d@core>
Alan Cox wrote:
>> 3) It is critical to ensure that the ATA "ctl" register is never
>> written to when no drive is attached. This means bracketing the SRST
>> sequence to first do a PCS detection before permitting the SRST.
>> If "ctl" is accessed with no drive attached, the machine locks up hard.
>
> At least for PATA you probably need to disable IORDY handshaking before
> the reset and probe.
..
Perhaps, but this was for SATA.
I don't even own any PATA disks nowadays.. other than a couple
that are buried inside USB/Firewire enclosures. My last bare PATA
drive died this morning, while testing a SATA bridge on it.
That drive was one of the infamous IBM DeathStar series from early
in the decade. R.I.P. Or pieces, actually. The platters make
great unbreakable "camping mirrors". :)
Cheers
prev parent reply other threads:[~2008-02-22 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6853F62BE9A693419863D51D4554A9E3012BE92B@EXNA.corp.stratus.com>
2008-02-22 15:10 ` ata-piix.c (and libata.ko) in RHEL5.1 (build 78 currently) - this kernel is 2.6.18 baqsed Alan Cox
2008-02-22 16:40 ` Mark Lord
2008-02-22 17:03 ` Alan Cox
2008-02-22 17:37 ` Mark Lord [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=47BF0858.9050400@rtr.ca \
--to=liml@rtr.ca \
--cc=Charlotte.Richardson@stratus.com \
--cc=Dan.Duval@stratus.com \
--cc=Nate.Dailey@stratus.com \
--cc=Peter.Petrakis@stratus.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=jgarzik@pobox.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).