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] [day] [month] [year] [list]
Date:	Tue, 06 Feb 2007 15:57:31 +0100
From:	Bernardo Innocenti <bernie@...eler.com>
To:	Bernardo Innocenti <bernie@...eler.com>
CC:	Geert Uytterhoeven <Geert.Uytterhoeven@...ycom.com>,
	Linux Frame Buffer Device Development 
	<linux-fbdev-devel@...ts.sourceforge.net>,
	lkml <linux-kernel@...r.kernel.org>, aleph <aleph@...eler.com>
Subject: Re: [Linux-fbdev-devel] How to mmap a shadow framebuffer in virtual
 memory

Bernardo Innocenti wrote:

> I still couldn't solve my problem, but thanks for helping.
> 
> The way you map memory in ps3fb_mmap() is basically the same.
> In my case, memory is allocated with __get_free_pages() instead
> of being at an absolute physical address, but I can't see how
> it could make any difference.

A few weeks ago I found the solution, which I report here to help
people who are googling for the same problem.

consistent_alloc() performed all the required magic to allocate
a contiguous buffer in phisical memory:

 -       if (!(fb_info.shadow = (void *)__get_free_pages(GFP_KERNEL, OLED_MEMORDER))
 +       if (!(fb_info.shadow = consistent_alloc(GFP_KERNEL, PAGE_ALIGN(OLED_MEMSIZE),
 +                       &fb_info.shadow_phys, PTE_BUFFERABLE))


The complete patch set is here, just in case:

   http://www.develer.com/patches/linux/pending/

-- 
   // Bernardo Innocenti - Develer S.r.l., R&D dept.
 \X/  http://www.develer.com/

-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ