Thanks for the update John!
Can you (one of the devs) explain a bit more about the VBIOS tables?
Can that be compared to something like the ACPI tables (eg. DSDT) or is it just the several states like "video watching" (GPU on xxx MHz, VRAM on xxx MHz) and "gaming" (with GPU on yyy MHz etc.)? Why do these tables lack information?
I personally always used Sapphire cards which afaik are close to AMD's reference design and they normally work nicely - also in terms of power consumption. Actually I have with profile=low (free driver stack) same or even 1-2 W better overall (power plug wall measured) wattage like I have in Windows XP with Catalyst. It's like 83 W (Linux free) idle vs. 85 W idle (W32). (Didn't try fglrx/Linux for a long time )
So I personally am really fine with power side of the free stack (just sad that dynpm does not use low profile!). But I see complaints from others sometimes.
So do some vendors provide clean implementation of VBIOS tables (like some mainbaord people provide good DSDTs) and some do not? How many quirks are allowed for a vendor that sells a Radeon GPU somewhere in a solution?
edit: And yes please for any kind of video accel (your E-350 Mini-ITX style boards would be perfect HTPCs then!) (low power, passively cooled and so on)
Stop TCPA, stupid software patents and corrupt politicians!