From: Mark Lord <liml@rtr.ca>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Tejun Heo <htejun@gmail.com>,
Jeff Garzik <jeff@garzik.org>, Adrian Bunk <bunk@kernel.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [2.6 patch] select ATA_SFF
Date: Thu, 24 Apr 2008 08:50:16 -0400 [thread overview]
Message-ID: <48108208.8060302@rtr.ca> (raw)
In-Reply-To: <481080EA.7010107@ru.mvista.com>
Sergei Shtylyov wrote:
> Alan Cox wrote:
>
>>> Sergei Shtylyov wrote:
>
>>>>>> Jeff, Tejun, what "sff" in the file name actually means? Isn't
>>>>>> it strange that the drivers lacking DMA support or not really
>>>>>> compliant with SFF-8038i have to link with this file?
>
>>>>> Maybe it should be libata-tf and libata-bmdma, but sff (sans bmdma)
>>>>> and bmdma is acceptable, hopefully, right?
>
>>>> What's sff sans bmdma?
>
>>> Supposed to be TF interface. IIRC, the SFF term was first from Alan
>>> although it's entirely possible that I misunderstood it and used it
>>> in the wrong way. Alan, can you please clear up the confusion?
>
>> The SFF/Intel spec is for PCI IDE (BMDMA or otherwise), so it covers and
>> defines all the common bits of the IDE interface on PCI (and in defining
>> the legacy interface conveniently documents the extended ST-412 interface
>> used by ATA and "pre-ATA" IDE/EIDE controllers).
>
> If you mean SFF-8038i (which can indeed be named "SFF/Intel"), it
> documents *only* BMDMA. If you mean something else, please be more
> precise.
..
The "Intel PCI IDE Controller Specification Revision 1.0 3/4/94" doesn't mention
bmdma at all, but does document the taskfile register addresses.
It defers to ATA-1 for actual taskfile descriptions/functionality, though.
There's nothing particularly bad about the current naming we use, though.
Cheers
next prev parent reply other threads:[~2008-04-24 12:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 21:31 [2.6 patch] select ATA_SFF Adrian Bunk
2008-04-22 11:39 ` Jens Axboe
2008-04-22 13:10 ` Sergei Shtylyov
2008-04-22 13:24 ` Tejun Heo
2008-04-22 13:36 ` Sergei Shtylyov
2008-04-22 13:41 ` Tejun Heo
2008-04-22 14:35 ` Mark Lord
2008-04-22 14:38 ` Tejun Heo
2008-04-22 14:44 ` Mark Lord
2008-04-22 15:00 ` Tejun Heo
2008-04-22 15:04 ` Sergei Shtylyov
2008-04-22 18:54 ` Sergei Shtylyov
2008-04-23 2:16 ` Tejun Heo
2008-04-23 4:21 ` Jeff Garzik
2008-04-23 11:16 ` Sergei Shtylyov
2008-04-23 13:30 ` Mark Lord
2008-04-22 14:43 ` Sergei Shtylyov
2008-04-22 14:51 ` Mark Lord
2008-04-24 11:35 ` Alan Cox
2008-04-24 12:45 ` Sergei Shtylyov
2008-04-24 12:50 ` Mark Lord [this message]
2008-04-24 13:00 ` Sergei Shtylyov
2008-04-24 14:27 ` Alan Cox
2008-04-24 15:30 ` Sergei Shtylyov
2008-04-24 15:15 ` Alan Cox
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=48108208.8060302@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@kernel.org \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.