Bug#332548: Summary

To: Michel D?nzer <daenzer@debian.org>
Cc: 332548@bugs.debian.org, 345839@bugs.debian.org
Subject: Bug#332548: Summary
From: Paul Donohue <DebianBugs@TopQuark.net>
Date: Fri, 17 Feb 2006 10:18:11 -0500
Message-id: <[🔎] 20060217151811.GW29037@TopQuark.net>
Reply-to: Paul Donohue <DebianBugs@TopQuark.net>, 332548@bugs.debian.org
In-reply-to: <[🔎] 1140139142.27426.87.camel@localhost>
References: <[🔎] 20060215172210.GP29037@TopQuark.net> <[🔎] 1140139142.27426.87.camel@localhost>

> > It sounds like switching to MergedFB mode or the fglrx drivers fixes 
> > the problem for everyone - 
> BTW, dual head is known not to work correctly with fglrx when direct
> rendering is not enabled. That's not related to this bug.
When direct rendering is not enabled?  Hmmm...  I was under the impression direct rendering couldn't be enabled when dual head is enabled...

> > If I have time, I'll try some revisions in CVS between 6.8.2 and 6.9.0 
> > to see if I can find when the problem appeared, but this could take a 
> > while.
> I'm afraid there's no way around that...
I'm not particularly experienced with X development...  Will I need to build all of X using each CVS revision, or will it be possible to just build one or two copies of X, then build each copy of the driver from CVS and use it with the one copy of X?
...and...um...where is the CVS archive for the radeon driver?  I'm not seeing it at http://cvs.freedesktop.org/xorg/driver/

Reply to:

Follow-Ups:
- Bug#332548: Summary
  - From: Michel Dänzer <daenzer@debian.org>

References:
- Bug#332548: Summary
  - From: Paul Donohue <DebianBugs@TopQuark.net>
- Bug#332548: Summary
  - From: Michel Dänzer <daenzer@debian.org>

Prev by Date: Bug#345929: radeon memory map patch applied upstream
Next by Date: Bug#332548: Summary
Previous by thread: Bug#332548: Summary
Next by thread: Bug#332548: Summary
Index(es):
- Date
- Thread