linux-kernel - Re: [PATCH v4 0/6] staging tidspbridge: iommu migration

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]

Date:	Tue, 3 May 2011 22:18:29 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Omar Ramirez Luna <omar.ramirez@...com>
Cc:	"Greg Kroah-Hartman" <gregkh@...e.de>,
	Felipe Contreras <felipe.contreras@...il.com>,
	Fernando Guzman Lugo <x0095840@...com>,
	"Ohad Ben-Cohen" <ohad@...ery.com>, Nishanth Menon <nm@...com>,
	lkml <linux-kernel@...r.kernel.org>,
	devel <devel@...verdev.osuosl.org>
Subject: Re: [PATCH v4 0/6] staging tidspbridge: iommu migration

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.

	Arnd
--
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/