> What I would suggest doing is changing the code to use a blacklist > instead of a whitelist, and make it optional with a CONFIG option that > is marked experimental, and then get it into the mainline for > additional testing. If we can get ATI to give us the right way to do > it, great, but if they aren't being responsive, maybe we should just > do it empirically.
I'm hesitant to switch a whitelist because of a couple of settings in there that are specific to the way the chip is wired on the mobo. Apparently, thinkpads are similar enough to Macs, but I wouldn't bet on this beeing "commmon"... Also, the code in there switches to D2, not D3 and is only for M6,M7 and M9 for now. I may be able to produce code for the M10 as well based on some dumps we did from the MacOS driver, paulus wrote something that we ended up not using because the chip is actually powered down on Macs with the M10. Then, there is the problem of machines where the chip is powered down during sleep... I can re-POST an rv280 (M9+) and an M10 but only in "graphics" mode, not the VGA side for which I know nothing about, with the same possible issue about video RAM mode register setting. Ben. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
