| 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
| ||
|
Message-ID: <20110221115839.2048e8fe@lxorguk.ukuu.org.uk> Date: Mon, 21 Feb 2011 11:58:39 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Sergei Shtylyov <sshtylyov@...sta.com> Cc: Bartlomiej Zolnierkiewicz <bzolnier@...il.com>, linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 02/20] ata_piix: unify code for programming PIO and MWDMA timings On Mon, 21 Feb 2011 14:38:37 +0300 Sergei Shtylyov <sshtylyov@...sta.com> wrote: > Hello. > > On 21-02-2011 0:07, Alan Cox wrote: > > >> PIO mode is setup by different code, and it takes care of the IORDY > >> setting according to the PIO rules (and it gets called). DMA mode setup should > >> just ignore the IORDY setting as in all other sane drivers. > > > Well it can't ignore it - but if you mean just keep the bit as is then > > Yes, I mean this. > > > that sounds sensible, have to see what the docs say happens if you ever > > set MWDMA without IORDY. > > Don't think they say anything on this matter but I can't imagine that > IORDY matters for DMA. Sure - but it does matter for an ATAPI transaction with then has a DMA phase because those timings will be used for the command transfer which is PIO. Alan -- 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/
Powered by blists - more mailing lists