From: Andy Warner <andyw@pobox.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, Doug Ledford <dledford@redhat.com>
Subject: Re: libata & scsi rescan.
Date: Wed, 6 Oct 2004 22:49:29 -0500 [thread overview]
Message-ID: <20041006224929.B18793@florence.linkmargin.com> (raw)
In-Reply-To: <4164B548.7030700@pobox.com>; from jgarzik@pobox.com on Wed, Oct 06, 2004 at 11:17:28PM -0400
Jeff Garzik wrote:
>
> Well, the PDC2037x docs are under NDA, but the following information is
> obviously required to implement hotplug, and therefore will obviously be
> public once implemented:
>
> bits of Promise hotplug register, PDC_SATA_PLUG_CSR:
>
> 23:20 mask unplug irq (r/w)
> 19:16 mask plug irq (r/w)
> 11:8 SATAn is well connected (r/o)
> 7:4 SATAn is plugged again (rwc)
> 3:0 SATAn is disconnected (rwc)
There's a fine line between being terse and being cryptic,
as "man man" used to say .. :)
Is it also true that the standard SATA control, error and
status registers exist and function pretty much as the
spec says (at least for (1 << 16) in error and the
IPM & DET fields in Status) ?
--
andyw@pobox.com
Andy Warner Voice: (612) 801-8549 Fax: (208) 575-5634
next prev parent reply other threads:[~2004-10-07 3:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 17:39 libata & scsi rescan Andy Warner
2004-10-01 18:32 ` Jeff Garzik
2004-10-01 19:12 ` Andy Warner
2004-10-01 19:30 ` Jeff Garzik
2004-10-04 20:56 ` Andy Warner
2004-10-04 21:05 ` Jeff Garzik
2004-10-06 22:36 ` Andy Warner
2004-10-07 1:07 ` Jeff Garzik
2004-10-07 2:47 ` Andy Warner
2004-10-07 3:17 ` Jeff Garzik
2004-10-07 3:49 ` Andy Warner [this message]
2004-10-07 3:59 ` Jeff Garzik
2004-10-07 3:53 ` Jeff Garzik
2004-10-07 22:14 ` Andy Warner
2004-10-07 22:21 ` Jeff Garzik
2004-10-07 22:25 ` Jeff Garzik
2004-10-08 2:48 ` Andy Warner
2004-10-08 15:56 ` Andy Warner
2004-10-07 22:26 ` Jeff Garzik
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=20041006224929.B18793@florence.linkmargin.com \
--to=andyw@pobox.com \
--cc=dledford@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).