[git pull] drm fixes
kjwinchester at gmail.com
Fri Mar 25 05:51:01 PDT 2011
On 25 March 2011 04:21, Dave Airlie <airlied at gmail.com> wrote:
> I'm also aware we never get enough testing coverage before stuff hits
> your tree, we'd need 1000s of testers to run drm-next and we just
> don't have that variation. So yes when new features hit -rc1 with the
> drm they nearly always cause regressions, its just not possible to
> test this stuff on every GPU/monitor/bios combination in existance
> before we give it to you, that just isn't happening. Like radeon
> pageflipping caused machines to completely hang and I didn't find out
> until -rc7 due to lack of testing coverage.
Not that I have much credibility to be talking here, but as a nouveau
user with a problem setup where I cannot seem to find anyone to help
, I wonder if getting support for the absolute latest GPUs into
mainline perhaps should not be the highest priority. Also, have you
considered the possibility that taking longer for code to hit Linus'
tree would have the effect of increasing your tester base for
drm-next? If I had a new video card that was giving me a blank
screen, I would certainly be ready to try a testing kernel tree if I
thought it would get me some level of functionality.
Luckily my problem is not a showstopper, and mainly prevents me from
using my second screen, but creating that bug and posting to the
nouveau mailing list did not get me much help in actually fixing the
problem. This is despite the fact that I was quite willing to try the
nouveau kernel tree, which unfortunately did not help.
More information about the dri-devel