Messages in this thread | | | Date | Sun, 24 Mar 2002 20:40:27 -0600 | From | Steven Walter <> | Subject | Re: Screen corruption in 2.4.18 |
| |
On Mon, Mar 25, 2002 at 12:43:18PM +1100, Andre Pang wrote: > I've had a quick look at the pci-pc.c file which handles the PCI > fixups, but I can't see of a way to say "if this chip is detected > _and_ that chip is detected, modify this bit in the first chip." > It's possible, but not without some real ugly hackery. > > Assuming that _only_ the integrated KT133+KM133 chipset uses the > VT8365 PCI ID (0x8305), it'd be easy to make a special-case patch > for it. My only worry is that other chipsets (like the 'normal' > KT133 without the KM133) use the same PCI ID; we should avoid > modifying the fix for the other chipsets, if possible. > > Can somebody with a KT133/KT133A do a "lspci -n" and grep for > '8305'? If it doesn't appear, I'll send off my patch.
I fear this as well. In fact, I'm relatively certain that they /do/ both use the same PCI ID. Hence why lspci lists KT133/KM133. But I hope to big mistaken. If not, the only way I can see of detecting that it is a KM133 is by checking what device 01:00 is an S3 ProSavage. Yuck.
Hopefully I'll here back from VIA with a definitive answer about when to clear what bits, though. -- -Steven In a time of universal deceit, telling the truth is a revolutionary act. -- George Orwell He's alive. He's alive! Oh, that fellow at RadioShack said I was mad! Well, who's mad now? -- Montgomery C. Burns - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |