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: Fri, 8 Oct 2004 10:56:08 -0500 [thread overview]
Message-ID: <20041008105608.A24640@florence.linkmargin.com> (raw)
In-Reply-To: <4165C263.4080102@pobox.com>; from jgarzik@pobox.com on Thu, Oct 07, 2004 at 06:25:39PM -0400
Jeff Garzik wrote:
> [...]
> These args are wrong. Consider master/slave configurations.
Can I check that I've got these things right:
o *ap is a per sata-HBA-port structure ?
o each port can have 0, 1 or 2 drives attached ?
Though 0 & 1 are the only practical values
for current SATA hardware ?
Does this become 0 .. n when port expanders
enter into the picture ?
o struct scsi_device is a per drive structure ?
So *ap may need to support an aribrary list of devs,
just like struct Scsi_host does today ?
Since I bring up port expanders, will we still get hot-plug
notification from the hardware when a downstream drive changes
state ?
--
andyw@pobox.com
Andy Warner Voice: (612) 801-8549 Fax: (208) 575-5634
next prev parent reply other threads:[~2004-10-08 15:58 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
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 [this message]
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=20041008105608.A24640@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).