linux-kernel - Re: [PATCH] Updating Documentation/fb/vesafb.txt

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] [day] [month] [year] [list]

Message-ID: <44D49384.9060701@gmail.com>
Date:	Sat, 05 Aug 2006 20:48:04 +0800
From:	"Antonino A. Daplas" <adaplas@...il.com>
To:	phreak@...too.org
CC:	Antonino Daplas <adaplas@....net>,
	linux-fbdev-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org, trivial@...nel.org
Subject: Re: [PATCH] Updating Documentation/fb/vesafb.txt

Christian Heim wrote:
> Hello Antonino,
> 
> +    | 640x480  800x600  1024x768 1280x1024 1600x1200
> +----+-----------------------------------------------
> +256 |  0x301    0x303    0x305    0x307     0x???   
> +32k |  0x310    0x313    0x316    0x319     0x373   
> +64k |  0x311    0x314    0x317    0x31A     0x374   
> +16M |  0x312    0x315    0x318    0x31B     0x375   
>  
>  To enable one of those modes you have to specify "vga=ask" in the
>  lilo.conf file and rerun LILO. Then you can type in the desired

This is not correct. VESA did not define 1600x1200 as part of
its DVT standard. And starting with VBE 2.0, VESA is not going to
define new mode ID's. Thus the mode ID that you get for 1600x1200 may
be unique only for your particular hardware/Video BIOS.

You may use X's 'vesa' driver to get a list of modes that your
BIOS supports. It will be written to /var/log/X*.0.log.

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/