linux-kernel - Re: [PATCHv3 01/11] staging: tidspbridge: replace iommu custom for opensource implementation

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:	Mon, 18 Oct 2010 15:06:29 +0300
From:	Ionut Nicu <ionut.nicu@...dbit.ro>
To:	Felipe Contreras <felipe.contreras@...il.com>
Cc:	Fernando Guzman Lugo <x0095840@...com>, gregkh@...e.de,
	felipe.contreras@...ia.com, ameya.palande@...ia.com, nm@...com,
	Hiroshi.DOYU@...ia.com, ohad@...ery.com,
	linux-kernel@...r.kernel.org, andy.shevchenko@...il.com,
	linux-omap@...r.kernel.org
Subject: Re: [PATCHv3 01/11] staging: tidspbridge: replace iommu custom for
 opensource implementation

Hi,

On Mon, 2010-10-18 at 01:36 +0300, Felipe Contreras wrote: 
> On Tue, Oct 5, 2010 at 11:35 PM, Fernando Guzman Lugo <x0095840@...com> wrote:
> > Now the tidspbridge uses the API's from
> > iovmm module.
> >
> > Signed-off-by: Fernando Guzman Lugo <x0095840@...com>
> 
> NAK. This patch doesn't work... I guess it's supposed to.
> 
> So far I've found these errors, but it still doesn't work, maybe we
> should start thinking of reverting the whole iommu stuff:
> 

I also tested it with the userspace-dspbridge tools and it doesn't work
for me either.

Maybe it's better to revert this patch series for now and re-submit it
when all necessary patches get merged and it actually works on top of
the staging-next tree?

Regards,
Ionut.

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