linux-kernel - Re: kexec and framebuffer

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: <44C011B3.3060900@gmail.com>
Date:	Fri, 21 Jul 2006 07:28:51 +0800
From:	"Antonino A. Daplas" <adaplas@...il.com>
To:	Kalev Lember <kalev@...rtlink.ee>
CC:	Gerd Hoffmann <kraxel@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: kexec and framebuffer

Kalev Lember wrote:
> Gerd Hoffmann wrote:
>>> I am wondering what would be the preferred method to extract screen_info
>>> from running kernel. Should this be made available from sysfs or maybe a
>>> new system call be created?
>>>     
>> Simply ask /dev/fb0?
>> Patch for kexec tools attached.
>>   
> Thank you, this was really helpful.
>> +	if (0 != strcmp(fix.id, "vesafb"))
>> +		goto out;
> I think this check should be removed so that other framebuffer drivers
> besides vesafb would also work.

I think having the check is correct, only vesafb relies totally on
screen_info. If you remove the check, you can get the wrong information
from other framebuffer drivers.

> +	/* fixme: better get size from /proc/iomem */
> +	real_mode->lfb_size       = (fix.smem_len + 65535) / 65536;
> +	real_mode->pages          = (fix.smem_len + 4095) / 4096;

Note that fix.smem_len is the size of the remapped memory which can be
smaller than the actual framebuffer length. But there's a fixme comment
there so you probably know about this.

> Additionally the fix.id is "VESA VGA",
> not "vesafb".

Yes.

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