Skip to contentSkip to conversation

XFree86-4.0 Status?

DISCUSSION David L. Thompson 3 participants 3 messages Jun 3, 2000 – Jun 6, 2000 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

I was wondering if anybody could comment on the status of XFree86-4.0. I tried installing this on a PowerBook G3/250 and have had no luck. I've seen just a few posts in regards to "support isn't there yet" so I was wondering if anybody could comment.

Thanks,
David
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[email protected] 5515 Skyway Drive, Missoula, MT 59804

                                    Phone : (406)257-8530

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#2 lore raw
Quoted 5 lines · David L. Thompson

I was wondering if anybody could comment on the status of XFree86-4.0. I tried installing this on a PowerBook G3/250 and have had no luck. I've seen just a few posts in regards to "support isn't there yet" so I was wondering if anybody could comment.

I suppose that's Mach64 hardware, so you have to use the fbdev driver _and_ a patched kernel to correct broken OF PCI memory mappings.

Ask Michael Schmitz :)

Michel

--
I believe the technical term is "Oops!"
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#3 lore raw
Quoted 10 lines
Quoted 5 lines

I was wondering if anybody could comment on the status of XFree86-4.0. I tried installing this on a PowerBook G3/250 and have had no luck. I've seen just a few posts in regards to "support isn't there yet" so I was wondering if anybody could comment.

I suppose that's Mach64 hardware, so you have to use the fbdev driver _and_ a patched kernel to correct broken OF PCI memory mappings.

Ask Michael Schmitz :)

I haven't tried it on that machine but if it's a Mach64 chipset there will likely be a PCI resource collision between VRAM and MMIO space. I had to patch both 2.3.99pre7 and 2.2.15 to make it work. For 2.3.x, Geert's old PCI resource patch did fine, reassignment for 2.2.15 is a bad hack likely to break on other machines (I just guessed a free PCI address range instead of walking the resource tree).

Michael

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/