On Tue, Aug 05, 2003 at 09:46:19PM +0200, [EMAIL PROTECTED] wrote: > Ville Syrj�l� writes: > > <long explanation :) > > thanks a lot... now everything is clearer... -vo dfbmga is definitely the > way to go then :)
Of course ;) > >> matroxfb_proc: proc-interface driver? > > > > No idea. What kernel version is this? 2.4.20 doesn't seem to have this > > module. > kernel 2.4.21 has it, too iirc. 2.4.22-pre10 which I am using right now has > it. > when loaded, there is a lot of information in /proc/drivers/mga > with this tool it's more human readable... if matroxcard is not at /dev/fb0 > source needs to be patched to use /dev/fb1 ... > http://platan.vc.cvut.cz/ftp/pub/linux/matrox-latest/matrox_pins-0.1.tar.gz Ah ok. That's the info stored in the card BIOS. Max clocks, memory info etc. > ok... now back to directfb.... > I have been playing around with dfbinfo now: > ---- > Display Layers > > (00) FBDev Primary Layer (primary layer) > Type: graphics > Caps: brightness contrast saturation surface > > (01) Matrox Backend Scaler > Type: graphics picture video > Caps: brightness contrast deinterlacing dst_colorkey screen_location > surface > > (02) Matrox CRTC2 > Type: graphics picture video > Caps: brightness contrast flicker_filtering hue saturation surface > > (03) Matrox CRTC2 Sub-Picture > Type: graphics picture video > Caps: alphachannel opacity surface > ---- > (00) seems to be the layer of the vesa-frambuffer running on the nvidia > card. No it's matrox CRTC1. This looks fine. > in both cases dfbinfo still blacks the output on the nvidia card, I have to > switch consoles to get the picture back. Strange. > p.s. may i compile a webpage from this thread and especially your answers? Sure. I've thought about doing a matrox FAQ but never actually did. -- Ville Syrj�l� [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-users" as subject.
