| 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: <4D7CFBC7.2060109@gmx.de> Date: Sun, 13 Mar 2011 18:15:51 +0100 From: Florian Tobias Schandinat <FlorianSchandinat@....de> To: Chris Ball <cjb@...top.org> CC: linux-fbdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/4] viafb: kill lcd_panel_id Hi Chris, Chris Ball schrieb: > Hi Florian, > > On Sat, Mar 12 2011, Florian Tobias Schandinat wrote: >> This patch removes all internal uses of another mostly artificial >> value. It does duplicate the information of the maximum resolution and >> it is not flexible as only a few resolutions exist. Hence it is better >> to remove it and clean the mess up. >> No runtime change expected. >> >> Signed-off-by: Florian Tobias Schandinat <FlorianSchandinat@....de> > > We're passing viafb_lcd_panel_id at boot-time on OLPC XO-1.5. > Won't this break boot for us, and anyone else who needs to use it? No need to worry. The external interface is kept for compatibility, only the internal uses are replace by panel hres/vres which contain the same information but are more generic. I have not yet tested it on OLPC as I did not have the time to compile a new kernel for it, but as it works on my VX900 laptop which also uses the viafb_lcd_panel_id setting it should be fine. Thanks, Florian Tobias Schandinat -- 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