linux-kernel - Re: [PATCH 1/2] radeon: fix radeon kms framebuffer device

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: <4A404049.1080707@mit.edu>
Date:	Mon, 22 Jun 2009 22:39:05 -0400
From:	Andy Lutomirski <luto@....edu>
To:	Jerome Glisse <jglisse@...hat.com>
CC:	airlied@...il.com, dri-devel@...ts.sf.net,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] radeon: fix radeon kms framebuffer device

Jerome Glisse wrote:
> smem.start is a physical address which kernel can remap to access
> video memory of the fb buffer. We now pin the fb buffer into vram
> by doing so we are loosing vram but fbdev need to be reworked to
> allow change in framebuffer address.

I tested this (and the corresponding 2/2 initialization order, but with 
radeon as a module), and plymouth seems to be fully functional 
(graphical boot, password prompt, etc).

(The driver set the wrong mode, but that's a different issue.)

Thanks!

Tested-by: Andy Lutomirski <luto@....edu>
--
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/