Lines Matching +full:8 +full:xxx

17 /* XXX This device has a 'dev-comm' property which apparently is
18  * XXX a pointer into the openfirmware's address space which is
19  * XXX a shared area the kernel driver can use to keep OBP
20  * XXX informed about the current resolution setting.  The idea
21  * XXX is that the kernel can change resolutions, and as long
22  * XXX as the values in the 'dev-comm' area are accurate then
23  * XXX OBP can still render text properly to the console.
24  * XXX
25  * XXX I'm still working out the layout of this and whether there
26  * XXX are any signatures we need to look for etc.
60 	ep->depth = of_getintprop_default(ep->of_node, "depth", 8);  in e3d_get_props()
89 #define RAMDAC_VID_8FB_0	0x00000080UL /* PCI base 8bpp FB buffer 0 */
90 #define RAMDAC_VID_8FB_1	0x00000084UL /* PCI base 8bpp FB buffer 1 */
91 #define RAMDAC_VID_XXXFB	0x00000088UL /* PCI base of XXX FB */
124 	red_8 = red >> 8;  in e3d_setcolreg()
125 	green_8 = green >> 8;  in e3d_setcolreg()
126 	blue_8 = blue >> 8;  in e3d_setcolreg()
128 	value = (blue_8 << 24) | (green_8 << 16) | (red_8 << 8);  in e3d_setcolreg()
144 /* XXX This is a bit of a hack.  I can't figure out exactly how the
145  * XXX two 8bpp areas of the framebuffer work.  I imagine there is
146  * XXX a WID attribute somewhere else in the framebuffer which tells
147  * XXX the ramdac which of the two 8bpp framebuffer regions to take
148  * XXX the pixel from.  So, for now, render into both regions to make
149  * XXX sure the pixel shows up.
227 	var->red.offset = 8;  in e3d_set_fbinfo()
228 	var->red.length = 8;  in e3d_set_fbinfo()
230 	var->green.length = 8;  in e3d_set_fbinfo()
232 	var->blue.length = 8;  in e3d_set_fbinfo()
338 	case 8:  in e3d_pci_register()