[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: m3mirror...

> > aty128fb: Rage Mobility M3 (AGP) [chip rev 0x0] 8M 128-bit SDR SGRAM (1:1)
> > Console: switching to colour frame buffer device 144x48
> > Registered "ati" backlight controller, level: 12/15
> > fb0: ATY Rage128 frame buffer device on PCI
> > no framebuffer address found for
> > /pci@f0000000/ATY,RageM3p12Parent@10/ATY,RageM3p12B
> I wonder what this is about anyway?  Why doesn't it find an address?
> 'B' doesn't have one, but 'A' does, so why is it using 'B'?

B and A are OF aliases for the same device I reckon, and which of the OF
nodes got supplied an address by Apple is beyond anyone's guess. Sometimes
even the parent node got the address...

Use the source, Luke. m3mirror is just a wrapper for the mirror ioctl, so
look at the ioctl code in the aty128fb driver. Make aty128fb spit out a
few messages indicating what it's doing. Make sure m3mirror was built with
kernel headers matching your kernel version, in case the or layout size of
the ioctl data has changed.

> the part that's interesting starts here:
> open("/dev/fb0", O_RDONLY)              = 4

So it did successfully open /dev/fb0. Now what?


Reply to: