| 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: <BANLkTin7vsfjF+86UrGb7ph0B8TpiXiF0A@mail.gmail.com> Date: Tue, 3 May 2011 15:48:07 -0500 From: "Ramirez Luna, Omar" <omar.ramirez@...com> To: Arnd Bergmann <arnd@...db.de> Cc: lkml <linux-kernel@...r.kernel.org>, devel <devel@...verdev.osuosl.org> Subject: Re: [PATCH v4 0/6] staging tidspbridge: iommu migration Hi Arnd, On Tue, May 3, 2011 at 3:18 PM, Arnd Bergmann <arnd@...db.de> wrote: > On Thursday 28 April 2011 17:31:46 Omar Ramirez Luna wrote: >> Rework and rebase of the previous set of patches for iommu migration[1]. >> >> Reorganized the patches to avoid several iterations to change the same code. >> >> Patches were tested with an OMAP3630 board, with both, basic samples and >> gst-dsp; these are dependant on patch: >> "OMAP: iovmm: fix SW flags passed by user"[2]. > > The code removal in this series looks good, but the move from > one proprietary iommu API to another proprietary iommu API > seems pointless. > > It would be much more helpful if you could convert the tidspbridge > code to the dma-mapping API, or to the generic iommu API > and provide these interfaces from the omap code. Yes, I thought removing a bunch of lines from staging might be good. I'll check what can be done to use generic iommu or dma-mapping. Thanks, Omar -- 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