diff options
| author | Ondrej Zary <linux@rainbow-software.org> | 2011-03-29 19:07:08 +0000 |
|---|---|---|
| committer | Paul Mundt <lethal@linux-sh.org> | 2011-03-31 13:48:58 +0900 |
| commit | 94e948e6e43cd34e0e2ca496d5e90e4ff0d884f9 (patch) | |
| tree | e67f3b5e4ed3166f2bb2fd16a5900df2ad65426a /drivers/video/efifb.c | |
| parent | 62e0ff1ef2d8ea0814487f73a7de431396a1e914 (diff) | |
| download | linux-94e948e6e43cd34e0e2ca496d5e90e4ff0d884f9.tar.gz linux-94e948e6e43cd34e0e2ca496d5e90e4ff0d884f9.tar.bz2 linux-94e948e6e43cd34e0e2ca496d5e90e4ff0d884f9.zip | |
s3fb: fix Virge/GX2
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@rainbow-software.org>
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
Diffstat (limited to 'drivers/video/efifb.c')
0 files changed, 0 insertions, 0 deletions