linux-kernel - Re: Problems with framebuffer in 2.6.22-git17

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]

Message-Id: <1185572600.26603.10.camel@daplas>
Date:	Sat, 28 Jul 2007 05:43:20 +0800
From:	"Antonino A. Daplas" <adaplas@...il.com>
To:	Adrian McMenamin <adrianmcmenamin@...il.com>
Cc:	Adrian McMenamin <lkmladrian@...il.com>,
	linux-kernel@...r.kernel.org, lethal@...rs.sourceforge.net
Subject: Re: Problems with framebuffer in 2.6.22-git17

On Fri, 2007-07-27 at 20:47 +0100, Adrian McMenamin wrote:
> On 26/07/07, Antonino A. Daplas <adaplas@...il.com> wrote:
> 
> >
> > I'm also confused. Can you change the color depth to 32 bpp ('fbset
> > -depth 32')?  I'm thinking of a possible pseudo_palette overrun.
> >
> 
> The code behaves in exactly the same way with the bit depth set to 32
> and without the patch reversion (ie forces a reboot).
> 
> With the parch reverted there is a flicker of output on the screen
> before a reboot is forced (it will boot with 16bpp though the colour
> is a bit iffy)
> 
> With the patch reverted and 24bpp, it oopses before freezing (with two
> odd looking boot logos on the screen):

Can you try the attached patch? It's just a clean-up patch: uses
framebuffer_alloc/release instead of kmalloc. 

Tony

View attachment "pvr2_cleanup.diff" of type "text/x-patch" (1639 bytes)