| 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
| ||
|
Message-Id: <200707181342.00647.a1426z@gawab.com> Date: Wed, 18 Jul 2007 13:42:00 +0300 From: Al Boldi <a1426z@...ab.com> To: linux-kernel@...r.kernel.org Subject: Re: VESAFB CUSTOM RESOLUTION Geert Uytterhoeven wrote: > On Wed, 18 Jul 2007, Sasa Ostrouska wrote: > > Daniel you seem to be right, as till now, no one of those solutions > > for me worked, I always end up or with a non recognised option or a > > small square 640x480 pixels where I see the console. I need to try > > still the vbetest thing what Mr. Daplas proposed. > > > > In any case this laptop has an screen of 16:10 aspect ratio and I > > belive would be good > > to have those modes in the vesafb driver. > > There are no modes in the vesafb driver. The vesafb driver uses the > video mode that was set by the BIOS before starting Linux. I have a similar problem with an onboard VIA-UniChrome chip, driven through an out-of-tree vendor-supplied driver just to get 85Hz refresh. Other than the pain of maintaining this driver out-of-tree, I have to contend with a 50% speed reduction compared to vesafb. vesafb is probably the most important display driver for compatibility reasons, and as such should support a large range of functionality. Is there any technical reason why vesafb shouldn't support non-BIOS modes? Thanks! -- Al - 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