From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <liml@rtr.ca>
Cc: James Courtier-Dutton <James@superbug.demon.co.uk>,
linux-ide@vger.kernel.org
Subject: Re: libata-passthrough problem.
Date: Sat, 12 Nov 2005 18:19:11 -0500 [thread overview]
Message-ID: <4376786F.2090503@pobox.com> (raw)
In-Reply-To: <43764853.5050306@rtr.ca>
Mark Lord wrote:
> Jeff Garzik wrote:
>
>>
>> Just download 2.6.15-rc1.
>>
>
> Okay, got it.
>
> Jeff: I cannot find anywhere in libata code,
> where the ATA unit number gets ORed into tf->device.
>
> If this is not done, then no PATA slave devices will
> be addressed correctly, even for regular I/O.
>
> Where is setting that bit done?
> I'm sure it must be in there, I just don't see it.
ata_tf_init() in include/linux/libata.h.
I admit with guilt that I had to search around a bit for it, too :)
Jeff
next prev parent reply other threads:[~2005-11-12 23:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 10:55 libata-passthrough problem James Courtier-Dutton
2005-11-12 15:18 ` Mark Lord
2005-11-12 17:57 ` Jeff Garzik
2005-11-12 19:53 ` Mark Lord
2005-11-12 19:56 ` Mark Lord
2005-11-12 23:19 ` Jeff Garzik
2005-11-12 23:54 ` [PATCH 2.6.15-rc1] libata: fix passthru for slave devices Mark Lord
2005-11-12 23:55 ` [PATCH 2.6.15-rc1] libata: fix comments on ata_tf_from_fis() Mark Lord
2005-11-13 0:15 ` [PATCH 2.6.15-rc1] libata: fix passthru for slave devices Jeff Garzik
2005-11-13 2:50 ` Mark Lord
2005-11-13 3:20 ` Jeff Garzik
2005-11-13 4:37 ` Mark Lord
2005-11-13 0:16 ` Jeff Garzik
2005-11-13 2:48 ` Mark Lord
2005-11-13 3:04 ` Mark Lord
2005-11-13 3:11 ` Mark Lord
2005-11-12 23:19 ` Jeff Garzik [this message]
2005-11-12 23:40 ` libata-passthrough problem Mark Lord
2005-11-13 15:13 ` James Courtier-Dutton
2005-11-13 17:01 ` Mark Lord
2005-11-13 17:03 ` Mark Lord
2005-11-13 20:17 ` James Courtier-Dutton
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=4376786F.2090503@pobox.com \
--to=jgarzik@pobox.com \
--cc=James@superbug.demon.co.uk \
--cc=liml@rtr.ca \
--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).