Thread (59 messages) 59 messages, 7 authors, 2017-11-15

n900 in next-20170901

From: tony@atomide.com (Tony Lindgren)
Date: 2017-11-10 15:37:41
Also in: linux-omap, lkml

* Joonsoo Kim [off-list ref] [171110 06:43]:
On Thu, Nov 09, 2017 at 10:23:40PM -0800, Tony Lindgren wrote:
quoted
* Tony Lindgren [off-list ref] [171109 22:19]:
quoted
* Tony Lindgren [off-list ref] [171110 03:28]:
quoted
Then I'll follow up on cleaning up save_secure_ram_context later.
Here's a better version, the static mapping did not get used.. It
just moved the area so it happened to work. It needs to be set
up as MT_MEMORY_RWX_NONCACHED instead.
I see a better version now. Hmm... I guess that it also has the
problem that I mentioned on first version.
quoted
And FYI, here's what I currently have for the follow-up patch,
but that can wait a bit.
Okay. So, this patch should be applied on the top of above better version?
Yeah, but we may actually want to combine both patches into a
single patch to avoid the save_secure_ram_context 0xffff translation
limit, see my comments in the first version.

Regards,

Tony
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help