Re: radeonfb problem on Mac mini

[Michael Lorenz <macallan%NetBSD.org@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Jul 20, 2008, at 18:24, Krister Walfridsson wrote:

> On Sun, 20 Jul 2008, Michael Lorenz wrote:
>
> > Then EDID data aren't the cause of your problem. Is there anything  
> > interesting in your dmesg output?
Here we go:
> radeonfb0: using static EDID

So using OF-provided EDID data works.

> max_dotclock according to supported modes: 108000
> radeonfb0: using static EDID
> max_dotclock according to supported modes: 108000
> radeonfb0: 64 MB aperture at 0x98000000, 64 KB registers at 0x90000000
> radeonfb0: display 0: initial virtual resolution 640x350 at 32 bpp
> radeonfb0: port 0: physical 640x350 70Hz
> radeonfb0: port 1: physical 640x350 70Hz
... which leaves the question why on earth it picks this resolution.  
I trust you don't have an ancient monitor from the previous ice age  
connected.

Anyway, let me have a look if the EDID parser has debug options,  
there must be a reason why it picked this mode instead of something  
sane.

have fun
Michael

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBSIQTvspnzkX8Yg2nAQJ58AgAtYlrlkyofTP82q8g6v10YtdjBZyooA2A
s8gOYS/A6M29D7xoe6iQVSYg9/qgyumc8QXgVwCm41jY/tVpNDmt9bfqS5A4lJJG
ux1Boa6z62wOBASWDdIe3XUNMyDondOHBac/BYgEPPC/Iwq+WhqOImNSKMgfBp0P
ZrGp4dJj3e2LJSF/7MeMMpu+lOByAoCVboc5JbtNBNHiouQHaoC2TtUAobum6LVI
yYfCQmqIQnrK0/SDW7KbBmZAT6AbxLG+kbWXU+9ggs26s2phQ2UicGwPNkI1Mo8a
i/GVRfKSz7W/nMXr/ZskOLp/lJIrFtDmzty3+74tAPbFlKQ9wUjJ/w==
=6m7c
-----END PGP SIGNATURE-----