[kdrive] KdScreenInfo::fb[KD_MAX_FB]

Mikhail Gusarov dottedmag at dottedmag.net
Fri Jan 1 23:59:37 PST 2010

Looks like all current kdrive servers use only KScreenInfo::fb[0], and
don't touch fb[1].

The only code which handles non-zero fb is command line parser and
KdScreenInit which setups overlay. As no servers fill in fb[1]
information, overlay setup will fail due to missing .frameBuffer,
.pixelStride, .depth and .bitsPerPixel.

Is fb[1] just an artifact which can be removed?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 834 bytes
Desc: not available
Url : http://lists.x.org/archives/xorg-devel/attachments/20100102/ec04645c/attachment.pgp 

More information about the xorg-devel mailing list