[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimmd=jKk_x4DNao_NG9dEiQtQvOQ=TePn-Dgc_b@mail.gmail.com>
Date: Tue, 9 Nov 2010 23:26:04 +0200
From: Felipe Contreras <felipe.contreras@...il.com>
To: "Guzman Lugo, Fernando" <fernando.lugo@...com>
Cc: Tony Lindgren <tony@...mide.com>, Arnd Bergmann <arnd@...db.de>,
Greg KH <greg@...ah.com>, linux-omap@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Omar Ramirez Luna <omar.ramirez@...com>
Subject: Re: [GIT PULL] fixes for tidspbridge 2.6.37-rc1
On Tue, Nov 9, 2010 at 7:52 PM, Guzman Lugo, Fernando
<fernando.lugo@...com> wrote:
> On Tue, Nov 9, 2010 at 11:35 AM, Tony Lindgren <tony@...mide.com> wrote:
>> * Guzman Lugo, Fernando <fernando.lugo@...com> [101109 08:36]:
>>>
>>> tidspbridge iommu change are working fine all the patches and few fixes after
>>> that are alredy sent. what breaks tidspbridge, is the unmerged
>>> dependencies in linux omap tree, specifically the iommu module patches
>>> and the SG patch.
>>
>> Care to post a series of the missing patches listed above?
>
> Here are the missing patches:
>
> Fernando Guzman Lugo (4):
> iovmm: no gap checking for fixed address
> iovmm: add superpages support to fixed da address
> iovmm: replace __iounmap with omap_iounmap
> iommu: create new api to set valid da range
>
> and
> scatterlist: define SG chain for arm architecture
Those are not the only patches needed, you would also need:
omap: iommu: make iva2 iommu selectable
staging: tidspbridge: enable iva2 iommu
And the one that actually uses the new API for the da range which
hasn't even been submitted to the mailing list.
Personally, I haven't seen the new iommu code working correctly.
--
Felipe Contreras
--
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