| 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
| ||
|
Date: Wed, 16 Feb 2011 19:41:40 +0200 (EET) From: Aaro Koskinen <aaro.koskinen@....fi> To: linux-fbdev@...r.kernel.org cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/6] sisfb: XGI Z9 POST Hi, On Mon, 14 Feb 2011, Aaro Koskinen wrote: > Here's some patches to get POST working with XGI Z9. I have tested them > with the following card: > > http://www.roboard.com/Files/RB-100/MiniPCI-VGA-Z9s_UM_v1r1A.pdf > > I'm using the card on an ARM board where the bootloader knows nothing > about VGA or VGA BIOS, so having POST support in the kernel driver > is mandatory. With these patches the memory size is correct detected, > R/W test passes and it's possible to use e.g. framebuffer console. > > Aaro Koskinen (6): > sisfb: POST should fail if R/W test fails > sisfb: move XGI POST RAM type detection into a subroutine > sisfb: add subroutine for detecting XGI Z9 > sisfb: add RAM type detection for XGI Z9 > sisfb: move XGI POST DDR2 bootup code into subroutines > sisfb: add support for XGI Z9 DDR2 POST Hmm, I think these patches can be ignored, at least for a while. I realized that xgifb driver is now in staging, and it has much wider support for XGI chips. So, we should work on getting that driver into an acceptable form. And after that, it should be even possible to drop XGI support from sisfb. A. -- 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