| 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
| ||
|
Date: Sat, 27 Jun 2015 17:44:38 +0300 From: Nicolae Rosia <nicolae.rosia@...il.com> To: Vinod Koul <vinod.koul@...el.com> Cc: Appana Durga Kedareswara Rao <appana.durga.rao@...inx.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Srikanth Thokala <sthokal@...inx.com>, Michal Simek <michals@...inx.com>, Soren Brinkmann <sorenb@...inx.com>, Anirudha Sarangi <anirudh@...inx.com>, "dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>, Punnaiah Choudary Kalluri <punnaia@...inx.com>, "dan.j.williams@...el.com" <dan.j.williams@...el.com>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> Subject: Re: [PATCH v7] dma: Add Xilinx AXI Direct Memory Access Engine driver support On Sat, Jun 27, 2015 at 5:40 PM, Vinod Koul <vinod.koul@...el.com> wrote: [...] >> Please let me know if you are not clear. > No sorry am not... > > I asked how the device address in configured. For both MM2S S2MM you are > using sg for memory address, where are you getting device adress, are you > assuming/hardcoding or getting somehow, if so how? As the name says, one end is memory (MM) and the other end is an AXI4 Stream Bus (S) which has no concept of memory address. So yes, it is hardcoded at design time. -- 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