modesetting feature status

[Joshua C.]

2008/9/17 Adam Jackson <ajax at redhat.com>:
> On Wed, 2008-09-17 at 20:36 +0200, Joshua C. wrote:
>
>> Dave can you make the radeon driver fall back to vesa in case of a
>> problem? my display disappears after modprobe radeon modeset=1 and if
>> the driver unloads itself, then maybe i can see any error messages on
>> the display.
>
> Not really.  There's no way to ask the display "hey, that mode I'm
> sending you, does it work?" so it's sort of hard to programmatically
> know when it doesn't work.
>
> - ajax

modprobe radeon modeset=0 works fine and modeset=1 crashes the
display. this means that modeset=1 should either (1) pass some
(already available information) to the driver or (2) make it execute a
spesific routine.
case 1 - there should be a way to look into this info before it's
passed to the driver.
case 2 - then my problem is in the routine and only debugging can help.

I tried to look into the drm-modeset-radeon patch in kernel -0.317 and
-0.321 but it is 1,7 MB and I don't know where to start from. Any idea
what i should look at?