| 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: <20110331045234.GA15486@linux-sh.org> Date: Thu, 31 Mar 2011 13:52:46 +0900 From: Paul Mundt <lethal@...ux-sh.org> To: Ondrej Zary <linux@...nbow-software.org> Cc: Ondrej Zajicek <santiago@...reenet.org>, linux-fbdev@...r.kernel.org, Kernel development list <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] s3fb: fix Virge/GX2 On Tue, Mar 29, 2011 at 09:07:08PM +0200, Ondrej Zary wrote: > Fix Virge/GX2 support in s3fb: > - fix IDs: 86C357 is GX2, 86C359 is GX2+, 86C356 probably does not exist > - add memory size detection > - drive it the same way as Trio3D/2X > > The original IDs most likely came from S3 website which claims that: > - 356 is Virge/GX2 with ID=8A10, driver included in Windows 2K, XP > - 357 is Virge/GX2+ with ID=8A11, driver included in Windows ME > - 359 is Virge/GX2+ with ID=8A12, driver included in Windows ME > but: > - google search for 86C356 only reveals references to Trio3D (probably > because of a typo - Trio3D is 86C365) > - my card is clearly marked as 86C357, Virge/GX2 and has ID=8A10 > - there is no driver for IDs 8A11 and 8A12 in Windows ME > - there is a driver for ID 8A10 in Windows ME that says it's GX2 (357) > > Tested with #9 Reality 334 (86C357 Virge/GX2, ID=0x8A10). > > Signed-off-by: Ondrej Zary <linux@...nbow-software.org> > Applied, thanks. -- 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