linux-kernel - Re: [2.6 patch] select ATA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <480DE6F5.8060403@gmail.com>
Date:	Tue, 22 Apr 2008 22:24:05 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Sergei Shtylyov <sshtylyov@...mvista.com>
CC:	Jeff Garzik <jeff@...zik.org>, Adrian Bunk <bunk@...nel.org>,
	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: [2.6 patch] select ATA_SFF

Hi,

Sergei Shtylyov wrote:
>    ADMA is not SFF-8038i compilant, it's the IDE DMA spec of its own. 
> And I'm seeing references to libata-sff.c... confusing.

In libata, SFF is used for controllers which have TF interface and BMDMA 
is used for the BMDMA part of SFF-8038i.  I think this is the source of 
confusion here.

>    Looks like there's no clean separation within libata-sff.c itself 
> between SFF-8038i (BMDMA spec) and IDE registers itself -- that confused 
> me: at first I thought there's a big issue with a patch. :-/
> 
>    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?

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/