On Thu, 26 Feb 2004 at 09:17:49 +1100, Benjamin Herrenschmidt wrote:
In the normal case, we really want all displays opened. This make
sure everything gets properly initialized by the firmware. The
fact that m3mirror hack doesn't work in this case is a side
effect ;) It could probably be
On Tue, 2004-02-24 at 13:18, Julien BLACHE wrote:
There was a patch for the 2.4 kernel, but it doesn't work on 2.6. On
2.4, you could also replace the prom_init.c file with the one from
2.4.20 and that would allow you to use m3mirror to enable the crt
output.
I have had a look at the
On Wed, 2004-02-25 at 06:18, Julien BLACHE wrote:
Maybe it's possible to reuse prom_init.c from 2.4.20 with a 2.6
kernel, I haven't tried (yet).
No but you can obtain the same result by commenting out one line :)
Just force check_display() to only open the first fisplay.
The proper solution
I am trying to get dual head, or even just CRT only use from the Rage
128 M3 on my TiBook without much luck.
The good news is, the problem is known; the bad news is, nobody is
working on it.
[...]
The proper solution would be to add dualhead support to
aty128fb.c. (or pester BenH until he
I got this from BenH, looks like he ment to CC the list but typoed :P.
--
David Stanaway [EMAIL PROTECTED]
---BeginMessage---
I could make it just open the first display if there were 2 and they
were both M3s, but is there are more general test to see if this is
necessary?
In the normal
I am trying to get dual head, or even just CRT only use from the Rage
128 M3 on my TiBook without much luck.
I just got a Studio 21 display and I am not having any luck using it in
linux yet.
I am using sid with X 4.3.0-2 and kernel 2.6.3 (I also build the drm
trunk from the source package in
6 matches
Mail list logo