[haiku-commits] Re: r41411 - in haiku/trunk: build/jam headers/private/graphics/radeon_hd src/add-ons/accelerants/radeon_hd src/add-ons/kernel/drivers/graphics/radeon_hd

  • From: Stephan Aßmus <superstippi@xxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Tue, 10 May 2011 16:31:15 +0200

On 10.05.2011 16:25, Stephan Aßmus wrote:
On 10.05.2011 15:40, Axel Dörfler wrote:
Stephan Aßmus<superstippi@xxxxxx> wrote:
On 10.05.2011 09:20, Axel Dörfler wrote:
Alex von Gluck<kallisti5@xxxxxxxxxxx> wrote:
The Radeon HD cards seem to inject the preferred mode lines of
the active monitor into their VESA EDID (the vesa driver doesn't
pick it up because it compares the found monitor timings to the VESA
acceptable ones)
That's just how EDID works, and it's actually the monitor which
reports it
-- that's exactly what it was made for :-)
VESA doesn't support arbitrary mode lines which is why EDID doesn't
help in choosing the right correct resolution.
Hm, from your reply I don't know if you maybe misunderstand Alexander.
He is saying that the monitor's preferred mode ends up in the VESA mode
list, but it is still not picked by our VESA driver.

I'm not sure how you can know what Alex really intended to say (that
should probably be left to him ;-)), but that's not what he wrote:
EDID != mode list, EDID is what comes from the monitor, the mode list
is what comes from the card.

[...]  Alex says the reason is that the
VESA driver filters the list against "known" (built into the VESA
driver) modes, which I would find a bit strange, but I haven't read the

Sorry, should have re-read a bit further. What he says is more ambiguous. I don't know what exactly he means by "VESA acceptable ones". Either the card injects the mode into the VESA list, then it's acceptable as far as the card is concerned (and my interpretation of the problem makes sense), or it does not, in which case I have no idea what the card injects where... :-)

Alex, can you clarify? :-)

Best regards,

Other related posts: