linux-kernel - Re: [GIT PULL] fixes for tidspbridge 2.6.37-rc1

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTikoUiPe1o7OH07ZWzr+9dj-YZ5hEKiqcNun1wNZ@mail.gmail.com>
Date:	Wed, 10 Nov 2010 00:13:32 +0200
From:	Felipe Contreras <felipe.contreras@...il.com>
To:	Tony Lindgren <tony@...mide.com>
Cc:	"Guzman Lugo, Fernando" <fernando.lugo@...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 8:32 PM, Tony Lindgren <tony@...mide.com> wrote:
> * Guzman Lugo, Fernando <fernando.lugo@...com> [101109 09:43]:
>> 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
>
> Yeah this is stuff for Hiroshi to look at and queue for
> 2.6.28. No way we can merge these now.

Right, and he hasn't ack'ed them yet. So there's a chance they don't
get into 2.6.38 either.

>> and
>>   scatterlist: define SG chain for arm architecture
>
> And this we need to test carefully it's not something we
> can just merge.
>
> Has this been tested to work with omap MMC drivers?
>
> I'm not at all convinced the drivers can deal with
> chained SG lists.. This may not show up with light
> testing, the SG lists can be very small in most cases.
>
> So this would have to be tested to make sure the
> the chained SG list handled properly. The same goes
> for other omap drivers that may be using SG.

And the change doesn't affect OMAP only, it's for all ARM platforms.

The proposal from Russell was to do it only on OMAP, but I haven't
seen a patch that does that yet. Hopefully this would go into 2.6.38,
but again, it might not.

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