5 menu "Graphics support"
14 source "drivers/char/agp/Kconfig"
16 source "drivers/gpu/vga/Kconfig"
18 source "drivers/gpu/drm/Kconfig"
20 source "drivers/gpu/stub/Kconfig"
26 config VIDEO_OUTPUT_CONTROL
27 tristate "Lowlevel video output switch controls"
29 This framework adds support for low-level control of the video
33 tristate "Support for frame buffer devices"
35 The frame buffer device provides an abstraction for the graphics
36 hardware. It represents the frame buffer of some video hardware and
37 allows application software to access the graphics hardware through
38 a well-defined interface, so the software doesn't need to know
39 anything about the low-level (hardware register) stuff.
41 Frame buffer devices work identically across the different
42 architectures supported by Linux and make the implementation of
43 application programs easier and more portable; at this point, an X
44 server exists which uses the frame buffer device exclusively.
45 On several non-X86 architectures, the frame buffer device is the
46 only way to use the graphics hardware.
48 The device is accessed through special device nodes, usually located
49 in the /dev directory, i.e. /dev/fb*.
51 You need an utility program called fbset to make full use of frame
52 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
53 and the Framebuffer-HOWTO at
54 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
57 Say Y here and to the driver for your graphics board below if you
58 are compiling a kernel for a non-x86 architecture.
60 If you are compiling for the x86 architecture, you can say Y if you
61 want to play with it, but it is not essential. Please note that
62 running graphical applications that directly touch the hardware
63 (e.g. an accelerated X server) and that are not frame buffer
64 device-aware may cause unexpected results. If unsure, say N.
67 bool "Enable firmware EDID"
71 This enables access to the EDID transferred from the firmware.
72 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
73 transfers do not work for your driver and if you are using
74 nvidiafb, i810fb or savagefb.
76 In general, choosing Y for this option is safe. If you
77 experience extremely long delays while booting before you get
78 something on your display, try setting this to N. Matrox cards in
79 combination with certain motherboards and monitors are known to
80 suffer from this problem.
89 config FB_BOOT_VESA_SUPPORT
94 If true, at least one selected framebuffer driver can take advantage
95 of VESA video modes set at an early boot stage via the vga= parameter.
97 config FB_CFB_FILLRECT
102 Include the cfb_fillrect function for generic software rectangle
103 filling. This is used by drivers that don't provide their own
104 (accelerated) version.
106 config FB_CFB_COPYAREA
111 Include the cfb_copyarea function for generic software area copying.
112 This is used by drivers that don't provide their own (accelerated)
115 config FB_CFB_IMAGEBLIT
120 Include the cfb_imageblit function for generic software image
121 blitting. This is used by drivers that don't provide their own
122 (accelerated) version.
124 config FB_CFB_REV_PIXELS_IN_BYTE
129 Allow generic frame-buffer functions to work on displays with 1, 2
130 and 4 bits per pixel depths which has opposite order of pixels in
131 byte order to bytes in long order.
133 config FB_SYS_FILLRECT
138 Include the sys_fillrect function for generic software rectangle
139 filling. This is used by drivers that don't provide their own
140 (accelerated) version and the framebuffer is in system RAM.
142 config FB_SYS_COPYAREA
147 Include the sys_copyarea function for generic software area copying.
148 This is used by drivers that don't provide their own (accelerated)
149 version and the framebuffer is in system RAM.
151 config FB_SYS_IMAGEBLIT
156 Include the sys_imageblit function for generic software image
157 blitting. This is used by drivers that don't provide their own
158 (accelerated) version and the framebuffer is in system RAM.
160 menuconfig FB_FOREIGN_ENDIAN
161 bool "Framebuffer foreign endianness support"
164 This menu will let you enable support for the framebuffers with
165 non-native endianness (e.g. Little-Endian framebuffer on a
166 Big-Endian machine). Most probably you don't have such hardware,
167 so it's safe to say "n" here.
170 prompt "Choice endianness support"
171 depends on FB_FOREIGN_ENDIAN
173 config FB_BOTH_ENDIAN
174 bool "Support for Big- and Little-Endian framebuffers"
177 bool "Support for Big-Endian framebuffers only"
179 config FB_LITTLE_ENDIAN
180 bool "Support for Little-Endian framebuffers only"
189 config FB_DEFERRED_IO
196 depends on FB_DEFERRED_IO
203 Common utility functions useful to fbdev drivers of VGA-based
214 select BACKLIGHT_LCD_SUPPORT
215 select BACKLIGHT_CLASS_DEVICE
218 config FB_MODE_HELPERS
219 bool "Enable Video Mode Handling Helpers"
223 This enables functions for handling video modes using the
224 Generalized Timing Formula and the EDID parser. A few drivers rely
225 on this feature such as the radeonfb, rivafb, and the i810fb. If
226 your driver does not take advantage of this feature, choosing Y will
227 just increase the kernel size by about 5K.
229 config FB_TILEBLITTING
230 bool "Enable Tile Blitting Support"
234 This enables tile blitting. Tile blitting is a drawing technique
235 where the screen is divided into rectangular sections (tiles), whereas
236 the standard blitting divides the screen into pixels. Because the
237 default drawing element is a tile, drawing functions will be passed
238 parameters in terms of number of tiles instead of number of pixels.
239 For example, to draw a single character, instead of using bitmaps,
240 an index to an array of bitmaps will be used. To clear or move a
241 rectangular section of a screen, the rectangle will be described in
242 terms of number of tiles in the x- and y-axis.
244 This is particularly important to one driver, matroxfb. If
247 comment "Frame buffer hardware drivers"
251 tristate "Cirrus Logic support"
252 depends on FB && (ZORRO || PCI)
253 select FB_CFB_FILLRECT
254 select FB_CFB_COPYAREA
255 select FB_CFB_IMAGEBLIT
257 This enables support for Cirrus Logic GD542x/543x based boards on
258 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
260 If you have a PCI-based system, this enables support for these
261 chips: GD-543x, GD-544x, GD-5480.
263 Please read the file <file:Documentation/fb/cirrusfb.txt>.
265 Say N unless you have such a graphics board or plan to get one
266 before you next recompile the kernel.
269 tristate "Permedia2 support"
270 depends on FB && ((AMIGA && BROKEN) || PCI)
271 select FB_CFB_FILLRECT
272 select FB_CFB_COPYAREA
273 select FB_CFB_IMAGEBLIT
275 This is the frame buffer device driver for cards based on
276 the 3D Labs Permedia, Permedia 2 and Permedia 2V chips.
277 The driver was tested on the following cards:
278 Diamond FireGL 1000 PRO AGP
279 ELSA Gloria Synergy PCI
280 Appian Jeronimo PRO (both heads) PCI
281 3DLabs Oxygen ACX aka EONtronics Picasso P2 PCI
282 Techsource Raptor GFX-8P (aka Sun PGX-32) on SPARC
283 ASK Graphic Blaster Exxtreme AGP
285 To compile this driver as a module, choose M here: the
286 module will be called pm2fb.
288 config FB_PM2_FIFO_DISCONNECT
289 bool "enable FIFO disconnect feature"
290 depends on FB_PM2 && PCI
292 Support the Permedia2 FIFO disconnect feature.
295 tristate "ARM PrimeCell PL110 support"
296 depends on FB && ARM && ARM_AMBA
297 select FB_CFB_FILLRECT
298 select FB_CFB_COPYAREA
299 select FB_CFB_IMAGEBLIT
301 This framebuffer device driver is for the ARM PrimeCell PL110
302 Colour LCD controller. ARM PrimeCells provide the building
303 blocks for System on a Chip devices.
305 If you want to compile this as a module (=code which can be
306 inserted into and removed from the running kernel), say M
307 here and read <file:Documentation/kbuild/modules.txt>. The module
308 will be called amba-clcd.
312 depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
314 default FB_ARMCLCD_SHARP_LQ035Q7DB02
316 config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
317 bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
319 This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
320 color QVGA, HRTFT panel. The LogicPD device includes
321 an integrated HRTFT controller IC.
322 The native resolution is 240x320.
324 config FB_ARMCLCD_SHARP_LQ057Q3DC02
325 bool "LogicPD LCD 5.7\" QVGA"
327 This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
328 color QVGA, TFT panel. The LogicPD device includes an
329 The native resolution is 320x240.
331 config FB_ARMCLCD_SHARP_LQ64D343
332 bool "LogicPD LCD 6.4\" VGA"
334 This is an implementation of the Sharp LQ64D343, a 6.4"
335 color VGA, TFT panel. The LogicPD device includes an
336 The native resolution is 640x480.
338 config FB_ARMCLCD_SHARP_LQ10D368
339 bool "LogicPD LCD 10.4\" VGA"
341 This is an implementation of the Sharp LQ10D368, a 10.4"
342 color VGA, TFT panel. The LogicPD device includes an
343 The native resolution is 640x480.
346 config FB_ARMCLCD_SHARP_LQ121S1DG41
347 bool "LogicPD LCD 12.1\" SVGA"
349 This is an implementation of the Sharp LQ121S1DG41, a 12.1"
350 color SVGA, TFT panel. The LogicPD device includes an
351 The native resolution is 800x600.
353 This panel requires a clock rate may be an integer fraction
354 of the base LCDCLK frequency. The driver will select the
355 highest frequency available that is lower than the maximum
356 allowed. The panel may flicker if the clock rate is
357 slower than the recommended minimum.
359 config FB_ARMCLCD_AUO_A070VW01_WIDE
360 bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
362 This is an implementation of the AU Optronics, a 7.0"
363 WIDE Color. The native resolution is 234x480.
365 config FB_ARMCLCD_HITACHI
366 bool "Hitachi Wide Screen 800x480"
368 This is an implementation of the Hitachi 800x480.
374 bool "Acorn VIDC support"
375 depends on (FB = y) && ARM && ARCH_ACORN
376 select FB_CFB_FILLRECT
377 select FB_CFB_COPYAREA
378 select FB_CFB_IMAGEBLIT
380 This is the frame buffer device driver for the Acorn VIDC graphics
381 hardware found in Acorn RISC PCs and other ARM-based machines. If
385 bool "CLPS711X LCD support"
386 depends on (FB = y) && ARM && ARCH_CLPS711X
387 select FB_CFB_FILLRECT
388 select FB_CFB_COPYAREA
389 select FB_CFB_IMAGEBLIT
391 Say Y to enable the Framebuffer driver for the CLPS7111 and
395 bool "SA-1100 LCD support"
396 depends on (FB = y) && ARM && ARCH_SA1100
397 select FB_CFB_FILLRECT
398 select FB_CFB_COPYAREA
399 select FB_CFB_IMAGEBLIT
401 This is a framebuffer device for the SA-1100 LCD Controller.
402 See <http://www.linux-fbdev.org/> for information on framebuffer
405 If you plan to use the LCD display with your SA-1100 system, say
409 tristate "Motorola i.MX LCD support"
410 depends on FB && (HAVE_FB_IMX || ARCH_MX1 || ARCH_MX2)
411 select FB_CFB_FILLRECT
412 select FB_CFB_COPYAREA
413 select FB_CFB_IMAGEBLIT
416 tristate "CyberPro 2000/2010/5000 support"
417 depends on FB && PCI && (BROKEN || !SPARC64)
418 select FB_CFB_FILLRECT
419 select FB_CFB_COPYAREA
420 select FB_CFB_IMAGEBLIT
422 This enables support for the Integraphics CyberPro 20x0 and 5000
423 VGA chips used in the Rebel.com Netwinder and other machines.
424 Say Y if you have a NetWinder or a graphics card containing this
425 device, otherwise say N.
429 depends on (FB = y) && APOLLO
431 select FB_CFB_FILLRECT
432 select FB_CFB_IMAGEBLIT
436 depends on (FB = y) && Q40
438 select FB_CFB_FILLRECT
439 select FB_CFB_COPYAREA
440 select FB_CFB_IMAGEBLIT
443 tristate "Amiga native chipset support"
444 depends on FB && AMIGA
446 This is the frame buffer device driver for the builtin graphics
447 chipset found in Amigas.
449 To compile this driver as a module, choose M here: the
450 module will be called amifb.
453 bool "Amiga OCS chipset support"
456 This enables support for the original Agnus and Denise video chips,
457 found in the Amiga 1000 and most A500's and A2000's. If you intend
458 to run Linux on any of these systems, say Y; otherwise say N.
461 bool "Amiga ECS chipset support"
464 This enables support for the Enhanced Chip Set, found in later
465 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
466 you intend to run Linux on any of these systems, say Y; otherwise
470 bool "Amiga AGA chipset support"
473 This enables support for the Advanced Graphics Architecture (also
474 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
475 and CD32. If you intend to run Linux on any of these systems, say Y;
479 bool "Amiga FrameMaster II/Rainbow II support"
480 depends on (FB = y) && ZORRO
481 select FB_CFB_FILLRECT
482 select FB_CFB_COPYAREA
483 select FB_CFB_IMAGEBLIT
485 This is the frame buffer device driver for the Amiga FrameMaster
486 card from BSC (exhibited 1992 but not shipped as a CBM product).
489 tristate "Arc Monochrome LCD board support"
491 select FB_SYS_FILLRECT
492 select FB_SYS_COPYAREA
493 select FB_SYS_IMAGEBLIT
496 This enables support for the Arc Monochrome LCD board. The board
497 is based on the KS-108 lcd controller and is typically a matrix
498 of 2*n chips. This driver was tested with a 128x64 panel. This
499 driver supports it for use with x86 SBCs through a 16 bit GPIO
500 interface (8 bit data, 8 bit control). If you anticipate using
501 this driver, say Y or M; otherwise say N. You must specify the
502 GPIO IO address to be used for setting control and data.
505 bool "Atari native chipset support"
506 depends on (FB = y) && ATARI
507 select FB_CFB_FILLRECT
508 select FB_CFB_COPYAREA
509 select FB_CFB_IMAGEBLIT
511 This is the frame buffer device driver for the builtin graphics
512 chipset found in Ataris.
515 bool "Open Firmware frame buffer device support"
516 depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
517 select FB_CFB_FILLRECT
518 select FB_CFB_COPYAREA
519 select FB_CFB_IMAGEBLIT
522 Say Y if you want support with Open Firmware for your graphics
526 bool "Apple \"control\" display support"
527 depends on (FB = y) && PPC_PMAC && PPC32
528 select FB_CFB_FILLRECT
529 select FB_CFB_COPYAREA
530 select FB_CFB_IMAGEBLIT
533 This driver supports a frame buffer for the graphics adapter in the
534 Power Macintosh 7300 and others.
537 bool "Apple \"platinum\" display support"
538 depends on (FB = y) && PPC_PMAC && PPC32
539 select FB_CFB_FILLRECT
540 select FB_CFB_COPYAREA
541 select FB_CFB_IMAGEBLIT
544 This driver supports a frame buffer for the "platinum" graphics
545 adapter in some Power Macintoshes.
548 bool "Apple \"valkyrie\" display support"
549 depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
550 select FB_CFB_FILLRECT
551 select FB_CFB_COPYAREA
552 select FB_CFB_IMAGEBLIT
555 This driver supports a frame buffer for the "valkyrie" graphics
556 adapter in some Power Macintoshes.
559 bool "Chips 65550 display support"
560 depends on (FB = y) && PPC32 && PCI
561 select FB_CFB_FILLRECT
562 select FB_CFB_COPYAREA
563 select FB_CFB_IMAGEBLIT
565 This is the frame buffer device driver for the Chips & Technologies
566 65550 graphics chip in PowerBooks.
569 bool "Asiliant (Chips) 69000 display support"
570 depends on (FB = y) && PCI
571 select FB_CFB_FILLRECT
572 select FB_CFB_COPYAREA
573 select FB_CFB_IMAGEBLIT
575 This is the frame buffer device driver for the Asiliant 69030 chipset
578 bool "IMS Twin Turbo display support"
579 depends on (FB = y) && PCI
580 select FB_CFB_IMAGEBLIT
581 select FB_MACMODES if PPC
583 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
584 many Macintosh and compatible computers.
587 tristate "VGA 16-color graphics support"
588 depends on FB && (X86 || PPC)
589 select FB_CFB_FILLRECT
590 select FB_CFB_COPYAREA
591 select FB_CFB_IMAGEBLIT
593 select FONT_8x16 if FRAMEBUFFER_CONSOLE
595 This is the frame buffer device driver for VGA 16 color graphic
596 cards. Say Y if you have such a card.
598 To compile this driver as a module, choose M here: the
599 module will be called vga16fb.
601 config FB_BF54X_LQ043
602 tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
603 depends on FB && (BF54x) && !BF542
604 select FB_CFB_FILLRECT
605 select FB_CFB_COPYAREA
606 select FB_CFB_IMAGEBLIT
608 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
610 config FB_BFIN_T350MCQB
611 tristate "Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT)"
612 depends on FB && BLACKFIN
614 select FB_CFB_FILLRECT
615 select FB_CFB_COPYAREA
616 select FB_CFB_IMAGEBLIT
618 This is the framebuffer device driver for a Varitronix VL-PS-COG-T350MCQB-01 display TFT LCD
619 This display is a QVGA 320x240 24-bit RGB display interfaced by an 8-bit wide PPI
620 It uses PPI[0..7] PPI_FS1, PPI_FS2 and PPI_CLK.
622 config FB_BFIN_LQ035Q1
623 tristate "SHARP LQ035Q1DH02 TFT LCD"
624 depends on FB && BLACKFIN && SPI
625 select FB_CFB_FILLRECT
626 select FB_CFB_COPYAREA
627 select FB_CFB_IMAGEBLIT
630 This is the framebuffer device driver for a SHARP LQ035Q1DH02 TFT display found on
631 the Blackfin Landscape LCD EZ-Extender Card.
632 This display is a QVGA 320x240 18-bit RGB display interfaced by an 16-bit wide PPI
633 It uses PPI[0..15] PPI_FS1, PPI_FS2 and PPI_CLK.
635 To compile this driver as a module, choose M here: the
636 module will be called bfin-lq035q1-fb.
639 tristate "HP STI frame buffer device support"
640 depends on FB && PARISC
641 select FB_CFB_FILLRECT
642 select FB_CFB_COPYAREA
643 select FB_CFB_IMAGEBLIT
648 STI refers to the HP "Standard Text Interface" which is a set of
649 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
650 Enabling this option will implement the linux framebuffer device
651 using calls to the STI BIOS routines for initialisation.
653 If you enable this option, you will get a planar framebuffer device
654 /dev/fb which will work on the most common HP graphic cards of the
655 NGLE family, including the artist chips (in the 7xx and Bxxx series),
656 HCRX, HCRX24, CRX, CRX24 and VisEG series.
658 It is safe to enable this option, so you should probably say "Y".
661 bool "Generic Macintosh display support"
662 depends on (FB = y) && MAC
663 select FB_CFB_FILLRECT
664 select FB_CFB_COPYAREA
665 select FB_CFB_IMAGEBLIT
670 depends on (FB = y) && DIO
671 select FB_CFB_IMAGEBLIT
675 tristate "TGA/SFB+ framebuffer support"
676 depends on FB && (ALPHA || TC)
677 select FB_CFB_FILLRECT
678 select FB_CFB_COPYAREA
679 select FB_CFB_IMAGEBLIT
682 This is the frame buffer device driver for generic TGA and SFB+
683 graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards,
684 also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3
685 TURBOchannel cards, also known as PMAGD-A, -B and -C.
687 Due to hardware limitations ZLX-E2 and E3 cards are not supported
688 for DECstation 5000/200 systems. Additionally due to firmware
689 limitations these cards may cause troubles with booting DECstation
690 5000/240 and /260 systems, but are fully supported under Linux if
691 you manage to get it going. ;-)
693 Say Y if you have one of those.
696 tristate "Userspace VESA VGA graphics support"
697 depends on FB && CONNECTOR
698 select FB_CFB_FILLRECT
699 select FB_CFB_COPYAREA
700 select FB_CFB_IMAGEBLIT
701 select FB_MODE_HELPERS
703 This is the frame buffer driver for generic VBE 2.0 compliant
704 graphic cards. It can also take advantage of VBE 3.0 features,
705 such as refresh rate adjustment.
707 This driver generally provides more features than vesafb but
708 requires a userspace helper application called 'v86d'. See
709 <file:Documentation/fb/uvesafb.txt> for more information.
714 bool "VESA VGA graphics support"
715 depends on (FB = y) && X86
716 select FB_CFB_FILLRECT
717 select FB_CFB_COPYAREA
718 select FB_CFB_IMAGEBLIT
719 select FB_BOOT_VESA_SUPPORT
721 This is the frame buffer device driver for generic VESA 2.0
722 compliant graphic cards. The older VESA 1.2 cards are not supported.
723 You will get a boot time penguin logo at no additional cost. Please
724 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
727 bool "EFI-based Framebuffer Support"
728 depends on (FB = y) && X86 && EFI
729 select FB_CFB_FILLRECT
730 select FB_CFB_COPYAREA
731 select FB_CFB_IMAGEBLIT
733 This is the EFI frame buffer device driver. If the firmware on
734 your platform is EFI 1.10 or UEFI 2.0, select Y to add support for
735 using the EFI framebuffer as your console.
738 tristate "N411 Apollo/Hecuba devkit support"
739 depends on FB && X86 && MMU
740 select FB_SYS_FILLRECT
741 select FB_SYS_COPYAREA
742 select FB_SYS_IMAGEBLIT
744 select FB_DEFERRED_IO
747 This enables support for the Apollo display controller in its
748 Hecuba form using the n411 devkit.
751 tristate "Hercules mono graphics support"
753 select FB_CFB_FILLRECT
754 select FB_CFB_COPYAREA
755 select FB_CFB_IMAGEBLIT
757 Say Y here if you have a Hercules mono graphics card.
759 To compile this driver as a module, choose M here: the
760 module will be called hgafb.
762 As this card technology is 15 years old, most people will answer N
766 bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
767 depends on FB_HGA && EXPERIMENTAL
769 This will compile the Hercules mono graphics with
770 acceleration functions.
773 tristate "SGI Visual Workstation framebuffer support"
774 depends on FB && X86_VISWS
775 select FB_CFB_FILLRECT
776 select FB_CFB_COPYAREA
777 select FB_CFB_IMAGEBLIT
779 SGI Visual Workstation support for framebuffer graphics.
782 bool "SGI Graphics Backend frame buffer support"
783 depends on (FB = y) && (SGI_IP32 || X86_VISWS)
784 select FB_CFB_FILLRECT
785 select FB_CFB_COPYAREA
786 select FB_CFB_IMAGEBLIT
788 This is the frame buffer device driver for SGI Graphics Backend.
789 This chip is used in SGI O2 and Visual Workstation 320/540.
792 int "Video memory size in MB"
796 This is the amount of memory reserved for the framebuffer,
797 which can be any value between 1MB and 8MB.
800 bool "SBUS and UPA framebuffers"
801 depends on (FB = y) && SPARC
803 Say Y if you want support for SBUS or UPA based frame buffer device.
807 depends on (FB = y) && (SPARC && FB_SBUS)
808 select FB_CFB_FILLRECT
809 select FB_CFB_COPYAREA
810 select FB_CFB_IMAGEBLIT
812 This is the frame buffer device driver for the BWtwo frame buffer.
815 bool "CGthree support"
816 depends on (FB = y) && (SPARC && FB_SBUS)
817 select FB_CFB_FILLRECT
818 select FB_CFB_COPYAREA
819 select FB_CFB_IMAGEBLIT
821 This is the frame buffer device driver for the CGthree frame buffer.
824 bool "CGsix (GX,TurboGX) support"
825 depends on (FB = y) && (SPARC && FB_SBUS)
826 select FB_CFB_COPYAREA
827 select FB_CFB_IMAGEBLIT
829 This is the frame buffer device driver for the CGsix (GX, TurboGX)
833 bool "Creator/Creator3D/Elite3D support"
834 depends on FB_SBUS && SPARC64
835 select FB_CFB_COPYAREA
836 select FB_CFB_IMAGEBLIT
838 This is the frame buffer device driver for the Creator, Creator3D,
839 and Elite3D graphics boards.
842 bool "TCX (SS4/SS5 only) support"
844 select FB_CFB_FILLRECT
845 select FB_CFB_COPYAREA
846 select FB_CFB_IMAGEBLIT
848 This is the frame buffer device driver for the TCX 24/8bit frame
852 bool "CGfourteen (SX) support"
854 select FB_CFB_FILLRECT
855 select FB_CFB_COPYAREA
856 select FB_CFB_IMAGEBLIT
858 This is the frame buffer device driver for the CGfourteen frame
859 buffer on Desktop SPARCsystems with the SX graphics option.
862 bool "P9100 (Sparcbook 3 only) support"
864 select FB_CFB_FILLRECT
865 select FB_CFB_COPYAREA
866 select FB_CFB_IMAGEBLIT
868 This is the frame buffer device driver for the P9100 card
869 supported on Sparcbook 3 machines.
872 bool "Leo (ZX) support"
874 select FB_CFB_FILLRECT
875 select FB_CFB_COPYAREA
876 select FB_CFB_IMAGEBLIT
878 This is the frame buffer device driver for the SBUS-based Sun ZX
879 (leo) frame buffer cards.
882 bool "IGA 168x display support"
883 depends on (FB = y) && SPARC32
884 select FB_CFB_FILLRECT
885 select FB_CFB_COPYAREA
886 select FB_CFB_IMAGEBLIT
888 This is the framebuffer device for the INTERGRAPHICS 1680 and
889 successor frame buffer cards.
892 bool "Sun XVR-500 3DLABS Wildcat support"
893 depends on (FB = y) && PCI && SPARC64
894 select FB_CFB_FILLRECT
895 select FB_CFB_COPYAREA
896 select FB_CFB_IMAGEBLIT
898 This is the framebuffer device for the Sun XVR-500 and similar
899 graphics cards based upon the 3DLABS Wildcat chipset. The driver
900 only works on sparc64 systems where the system firmware has
901 mostly initialized the card already. It is treated as a
902 completely dumb framebuffer device.
905 bool "Sun XVR-2500 3DLABS Wildcat support"
906 depends on (FB = y) && PCI && SPARC64
907 select FB_CFB_FILLRECT
908 select FB_CFB_COPYAREA
909 select FB_CFB_IMAGEBLIT
911 This is the framebuffer device for the Sun XVR-2500 and similar
912 graphics cards based upon the 3DLABS Wildcat chipset. The driver
913 only works on sparc64 systems where the system firmware has
914 mostly initialized the card already. It is treated as a
915 completely dumb framebuffer device.
918 bool "Sun XVR-1000 support"
919 depends on (FB = y) && SPARC64
920 select FB_CFB_FILLRECT
921 select FB_CFB_COPYAREA
922 select FB_CFB_IMAGEBLIT
924 This is the framebuffer device for the Sun XVR-1000 and similar
925 graphics cards. The driver only works on sparc64 systems where
926 the system firmware has mostly initialized the card already. It
927 is treated as a completely dumb framebuffer device.
930 tristate "NEC PowerVR 2 display support"
931 depends on FB && SH_DREAMCAST
932 select FB_CFB_FILLRECT
933 select FB_CFB_COPYAREA
934 select FB_CFB_IMAGEBLIT
936 Say Y here if you have a PowerVR 2 card in your box. If you plan to
937 run linux on your Dreamcast, you will have to say Y here.
938 This driver may or may not work on other PowerVR 2 cards, but is
939 totally untested. Use at your own risk. If unsure, say N.
941 To compile this driver as a module, choose M here: the
942 module will be called pvr2fb.
944 You can pass several parameters to the driver at boot time or at
945 module load time. The parameters look like "video=pvr2:XXX", where
946 the meaning of XXX can be found at the end of the main source file
947 (<file:drivers/video/pvr2fb.c>). Please see the file
948 <file:Documentation/fb/pvr2fb.txt>.
951 bool "Epson 1355 framebuffer support"
952 depends on (FB = y) && ARCH_CEIVA
953 select FB_CFB_FILLRECT
954 select FB_CFB_COPYAREA
955 select FB_CFB_IMAGEBLIT
957 Build in support for the SED1355 Epson Research Embedded RAMDAC
958 LCD/CRT Controller (since redesignated as the S1D13505) as a
959 framebuffer. Product specs at
960 <http://vdc.epson.com/>.
963 tristate "Epson S1D13XXX framebuffer support"
965 select FB_CFB_FILLRECT
966 select FB_CFB_COPYAREA
967 select FB_CFB_IMAGEBLIT
969 Support for S1D13XXX framebuffer device family (currently only
970 working with S1D13806). Product specs at
971 <http://vdc.epson.com/>
974 tristate "AT91/AT32 LCD Controller support"
975 depends on FB && HAVE_FB_ATMEL
976 select FB_CFB_FILLRECT
977 select FB_CFB_COPYAREA
978 select FB_CFB_IMAGEBLIT
980 This enables support for the AT91/AT32 LCD Controller.
983 bool "Frame Buffer in internal SRAM"
984 depends on FB_ATMEL && ARCH_AT91SAM9261
986 Say Y if you want to map Frame Buffer in internal SRAM. Say N if you want
987 to let frame buffer in external SDRAM.
990 bool "Use a STN display with AT91/AT32 LCD Controller"
991 depends on FB_ATMEL && (MACH_AT91SAM9261EK || MACH_AT91SAM9G10EK)
994 Say Y if you want to connect a STN LCD display to the AT91/AT32 LCD
995 Controller. Say N if you want to connect a TFT.
1000 tristate "nVidia Framebuffer Support"
1001 depends on FB && PCI
1002 select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
1003 select FB_MODE_HELPERS
1004 select FB_CFB_FILLRECT
1005 select FB_CFB_COPYAREA
1006 select FB_CFB_IMAGEBLIT
1010 This driver supports graphics boards with the nVidia chips, TNT
1011 and newer. For very old chipsets, such as the RIVA128, then use
1013 Say Y if you have such a graphics board.
1015 To compile this driver as a module, choose M here: the
1016 module will be called nvidiafb.
1018 config FB_NVIDIA_I2C
1019 bool "Enable DDC Support"
1020 depends on FB_NVIDIA
1023 This enables I2C support for nVidia Chipsets. This is used
1024 only for getting EDID information from the attached display
1025 allowing for robust video mode handling and switching.
1027 Because fbdev-2.6 requires that drivers must be able to
1028 independently validate video mode parameters, you should say Y
1031 config FB_NVIDIA_DEBUG
1032 bool "Lots of debug output"
1033 depends on FB_NVIDIA
1036 Say Y here if you want the nVidia driver to output all sorts
1037 of debugging information to provide to the maintainer when
1038 something goes wrong.
1040 config FB_NVIDIA_BACKLIGHT
1041 bool "Support for backlight control"
1042 depends on FB_NVIDIA
1045 Say Y here if you want to control the backlight of your display.
1048 tristate "nVidia Riva support"
1049 depends on FB && PCI
1050 select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
1051 select FB_MODE_HELPERS
1052 select FB_CFB_FILLRECT
1053 select FB_CFB_COPYAREA
1054 select FB_CFB_IMAGEBLIT
1058 This driver supports graphics boards with the nVidia Riva/Geforce
1060 Say Y if you have such a graphics board.
1062 To compile this driver as a module, choose M here: the
1063 module will be called rivafb.
1066 bool "Enable DDC Support"
1070 This enables I2C support for nVidia Chipsets. This is used
1071 only for getting EDID information from the attached display
1072 allowing for robust video mode handling and switching.
1074 Because fbdev-2.6 requires that drivers must be able to
1075 independently validate video mode parameters, you should say Y
1078 config FB_RIVA_DEBUG
1079 bool "Lots of debug output"
1083 Say Y here if you want the Riva driver to output all sorts
1084 of debugging information to provide to the maintainer when
1085 something goes wrong.
1087 config FB_RIVA_BACKLIGHT
1088 bool "Support for backlight control"
1092 Say Y here if you want to control the backlight of your display.
1095 tristate "Intel 810/815 support (EXPERIMENTAL)"
1096 depends on EXPERIMENTAL && FB && PCI && X86_32 && AGP_INTEL
1097 select FB_MODE_HELPERS
1098 select FB_CFB_FILLRECT
1099 select FB_CFB_COPYAREA
1100 select FB_CFB_IMAGEBLIT
1103 This driver supports the on-board graphics built in to the Intel 810
1104 and 815 chipsets. Say Y if you have and plan to use such a board.
1106 To compile this driver as a module, choose M here: the
1107 module will be called i810fb.
1109 For more information, please read
1110 <file:Documentation/fb/intel810.txt>
1113 bool "use VESA Generalized Timing Formula"
1116 If you say Y, then the VESA standard, Generalized Timing Formula
1117 or GTF, will be used to calculate the required video timing values
1118 per video mode. Since the GTF allows nondiscrete timings
1119 (nondiscrete being a range of values as opposed to discrete being a
1120 set of values), you'll be able to use any combination of horizontal
1121 and vertical resolutions, and vertical refresh rates without having
1122 to specify your own timing parameters. This is especially useful
1123 to maximize the performance of an aging display, or if you just
1124 have a display with nonstandard dimensions. A VESA compliant
1125 monitor is recommended, but can still work with non-compliant ones.
1126 If you need or want this, then select this option. The timings may
1127 not be compliant with Intel's recommended values. Use at your own
1130 If you say N, the driver will revert to discrete video timings
1131 using a set recommended by Intel in their documentation.
1136 bool "Enable DDC Support"
1137 depends on FB_I810 && FB_I810_GTF
1142 tristate "Intel LE80578 (Vermilion) support"
1143 depends on FB && PCI && X86
1144 select FB_MODE_HELPERS
1145 select FB_CFB_FILLRECT
1146 select FB_CFB_COPYAREA
1147 select FB_CFB_IMAGEBLIT
1149 This driver supports the LE80578 (Vermilion Range) chipset
1151 config FB_CARILLO_RANCH
1152 tristate "Intel Carillo Ranch support"
1153 depends on FB_LE80578 && FB && PCI && X86
1155 This driver supports the LE80578 (Carillo Ranch) board
1158 tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EXPERIMENTAL)"
1159 depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL && EMBEDDED
1160 select FB_MODE_HELPERS
1161 select FB_CFB_FILLRECT
1162 select FB_CFB_COPYAREA
1163 select FB_CFB_IMAGEBLIT
1164 select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
1165 depends on !DRM_I915
1167 This driver supports the on-board graphics built in to the Intel
1168 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM chipsets.
1169 Say Y if you have and plan to use such a board.
1171 To make FB_INTELFB=Y work you need to say AGP_INTEL=y too.
1173 To compile this driver as a module, choose M here: the
1174 module will be called intelfb.
1176 For more information, please read <file:Documentation/fb/intelfb.txt>
1178 config FB_INTEL_DEBUG
1179 bool "Intel driver Debug Messages"
1182 Say Y here if you want the Intel driver to output all sorts
1183 of debugging information to provide to the maintainer when
1184 something goes wrong.
1187 bool "DDC/I2C for Intel framebuffer support"
1192 Say Y here if you want DDC/I2C support for your on-board Intel graphics.
1195 tristate "Matrox acceleration"
1196 depends on FB && PCI
1197 select FB_CFB_FILLRECT
1198 select FB_CFB_COPYAREA
1199 select FB_CFB_IMAGEBLIT
1200 select FB_TILEBLITTING
1201 select FB_MACMODES if PPC_PMAC
1203 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
1204 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
1205 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
1206 Matrox G400, G450 or G550 card in your box.
1208 To compile this driver as a module, choose M here: the
1209 module will be called matroxfb.
1211 You can pass several parameters to the driver at boot time or at
1212 module load time. The parameters look like "video=matrox:XXX", and
1213 are described in <file:Documentation/fb/matroxfb.txt>.
1215 config FB_MATROX_MILLENIUM
1216 bool "Millennium I/II support"
1217 depends on FB_MATROX
1219 Say Y here if you have a Matrox Millennium or Matrox Millennium II
1220 video card. If you select "Advanced lowlevel driver options" below,
1221 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
1222 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
1223 also use font widths different from 8.
1225 config FB_MATROX_MYSTIQUE
1226 bool "Mystique support"
1227 depends on FB_MATROX
1229 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
1230 video card. If you select "Advanced lowlevel driver options" below,
1231 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
1232 packed pixel and 32 bpp packed pixel. You can also use font widths
1236 bool "G100/G200/G400/G450/G550 support"
1237 depends on FB_MATROX
1239 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
1240 video card. If you select "Advanced lowlevel driver options", you
1241 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
1242 pixel and 32 bpp packed pixel. You can also use font widths
1245 If you need support for G400 secondary head, you must say Y to
1246 "Matrox I2C support" and "G400 second head support" right below.
1247 G450/G550 secondary head and digital output are supported without
1250 The driver starts in monitor mode. You must use the matroxset tool
1251 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
1252 swap primary and secondary head outputs, or to change output mode.
1253 Secondary head driver always start in 640x480 resolution and you
1254 must use fbset to change it.
1256 Do not forget that second head supports only 16 and 32 bpp
1257 packed pixels, so it is a good idea to compile them into the kernel
1258 too. You can use only some font widths, as the driver uses generic
1259 painting procedures (the secondary head does not use acceleration
1262 G450/G550 hardware can display TV picture only from secondary CRTC,
1263 and it performs no scaling, so picture must have 525 or 625 lines.
1265 config FB_MATROX_I2C
1266 tristate "Matrox I2C support"
1267 depends on FB_MATROX
1270 This drivers creates I2C buses which are needed for accessing the
1271 DDC (I2C) bus present on all Matroxes, an I2C bus which
1272 interconnects Matrox optional devices, like MGA-TVO on G200 and
1273 G400, and the secondary head DDC bus, present on G400 only.
1275 You can say Y or M here if you want to experiment with monitor
1276 detection code. You must say Y or M here if you want to use either
1277 second head of G400 or MGA-TVO on G200 or G400.
1279 If you compile it as module, it will create a module named
1282 config FB_MATROX_MAVEN
1283 tristate "G400 second head support"
1284 depends on FB_MATROX_G && FB_MATROX_I2C
1286 WARNING !!! This support does not work with G450 !!!
1288 Say Y or M here if you want to use a secondary head (meaning two
1289 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
1290 head is not compatible with accelerated XFree 3.3.x SVGA servers -
1291 secondary head output is blanked while you are in X. With XFree
1292 3.9.17 preview you can use both heads if you use SVGA over fbdev or
1293 the fbdev driver on first head and the fbdev driver on second head.
1295 If you compile it as module, two modules are created,
1296 matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
1297 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
1298 also load i2c-matroxfb to get it to run.
1300 The driver starts in monitor mode and you must use the matroxset
1302 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
1303 PAL or NTSC or to swap primary and secondary head outputs.
1304 Secondary head driver also always start in 640x480 resolution, you
1305 must use fbset to change it.
1307 Also do not forget that second head supports only 16 and 32 bpp
1308 packed pixels, so it is a good idea to compile them into the kernel
1309 too. You can use only some font widths, as the driver uses generic
1310 painting procedures (the secondary head does not use acceleration
1314 tristate "ATI Radeon display support"
1315 depends on FB && PCI
1316 select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
1317 select FB_MODE_HELPERS
1318 select FB_CFB_FILLRECT
1319 select FB_CFB_COPYAREA
1320 select FB_CFB_IMAGEBLIT
1321 select FB_MACMODES if PPC_OF
1323 Choose this option if you want to use an ATI Radeon graphics card as
1324 a framebuffer device. There are both PCI and AGP versions. You
1325 don't need to choose this to run the Radeon in plain VGA mode.
1327 There is a product page at
1328 http://products.amd.com/en-us/GraphicCardResult.aspx
1330 config FB_RADEON_I2C
1331 bool "DDC/I2C for ATI Radeon support"
1332 depends on FB_RADEON
1336 Say Y here if you want DDC/I2C support for your Radeon board.
1338 config FB_RADEON_BACKLIGHT
1339 bool "Support for backlight control"
1340 depends on FB_RADEON
1343 Say Y here if you want to control the backlight of your display.
1345 config FB_RADEON_DEBUG
1346 bool "Lots of debug output from Radeon driver"
1347 depends on FB_RADEON
1350 Say Y here if you want the Radeon driver to output all sorts
1351 of debugging information to provide to the maintainer when
1352 something goes wrong.
1355 tristate "ATI Rage128 display support"
1356 depends on FB && PCI
1357 select FB_CFB_FILLRECT
1358 select FB_CFB_COPYAREA
1359 select FB_CFB_IMAGEBLIT
1360 select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
1361 select FB_MACMODES if PPC_PMAC
1363 This driver supports graphics boards with the ATI Rage128 chips.
1364 Say Y if you have such a graphics board and read
1365 <file:Documentation/fb/aty128fb.txt>.
1367 To compile this driver as a module, choose M here: the
1368 module will be called aty128fb.
1370 config FB_ATY128_BACKLIGHT
1371 bool "Support for backlight control"
1372 depends on FB_ATY128
1375 Say Y here if you want to control the backlight of your display.
1378 tristate "ATI Mach64 display support" if PCI || ATARI
1379 depends on FB && !SPARC32
1380 select FB_CFB_FILLRECT
1381 select FB_CFB_COPYAREA
1382 select FB_CFB_IMAGEBLIT
1383 select FB_BACKLIGHT if FB_ATY_BACKLIGHT
1384 select FB_MACMODES if PPC
1386 This driver supports graphics boards with the ATI Mach64 chips.
1387 Say Y if you have such a graphics board.
1389 To compile this driver as a module, choose M here: the
1390 module will be called atyfb.
1393 bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
1394 depends on PCI && FB_ATY
1395 default y if SPARC64 && PCI
1397 Say Y here to support use of ATI's 64-bit Rage boards (or other
1398 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
1399 framebuffer device. The ATI product support page for these boards
1400 is at <http://support.ati.com/products/pc/mach64/mach64.html>.
1402 config FB_ATY_GENERIC_LCD
1403 bool "Mach64 generic LCD support (EXPERIMENTAL)"
1404 depends on FB_ATY_CT
1406 Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
1407 Rage XC, or Rage XL chipset.
1410 bool "Mach64 GX support" if PCI
1414 Say Y here to support use of the ATI Mach64 Graphics Expression
1415 board (or other boards based on the Mach64 GX chipset) as a
1416 framebuffer device. The ATI product support page for these boards
1418 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
1420 config FB_ATY_BACKLIGHT
1421 bool "Support for backlight control"
1425 Say Y here if you want to control the backlight of your display.
1428 tristate "S3 Trio/Virge support"
1429 depends on FB && PCI
1430 select FB_CFB_FILLRECT
1431 select FB_CFB_COPYAREA
1432 select FB_CFB_IMAGEBLIT
1433 select FB_TILEBLITTING
1436 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1438 Driver for graphics boards with S3 Trio / S3 Virge chip.
1441 tristate "S3 Savage support"
1442 depends on FB && PCI && EXPERIMENTAL
1443 select FB_MODE_HELPERS
1444 select FB_CFB_FILLRECT
1445 select FB_CFB_COPYAREA
1446 select FB_CFB_IMAGEBLIT
1449 This driver supports notebooks and computers with S3 Savage PCI/AGP
1452 Say Y if you have such a graphics card.
1454 To compile this driver as a module, choose M here; the module
1455 will be called savagefb.
1457 config FB_SAVAGE_I2C
1458 bool "Enable DDC2 Support"
1459 depends on FB_SAVAGE
1462 This enables I2C support for S3 Savage Chipsets. This is used
1463 only for getting EDID information from the attached display
1464 allowing for robust video mode handling and switching.
1466 Because fbdev-2.6 requires that drivers must be able to
1467 independently validate video mode parameters, you should say Y
1470 config FB_SAVAGE_ACCEL
1471 bool "Enable Console Acceleration"
1472 depends on FB_SAVAGE
1475 This option will compile in console acceleration support. If
1476 the resulting framebuffer console has bothersome glitches, then
1480 tristate "SiS/XGI display support"
1481 depends on FB && PCI
1482 select FB_CFB_FILLRECT
1483 select FB_CFB_COPYAREA
1484 select FB_CFB_IMAGEBLIT
1485 select FB_BOOT_VESA_SUPPORT if FB_SIS = y
1487 This is the frame buffer device driver for the SiS 300, 315, 330
1488 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1489 Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
1491 To compile this driver as a module, choose M here; the module
1492 will be called sisfb.
1495 bool "SiS 300 series support"
1498 Say Y here to support use of the SiS 300/305, 540, 630 and 730.
1501 bool "SiS 315/330/340 series and XGI support"
1504 Say Y here to support use of the SiS 315, 330 and 340 series
1505 (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
1506 as XGI V3XT, V5, V8 and Z7.
1509 tristate "VIA UniChrome (Pro) and Chrome9 display support"
1510 depends on FB && PCI && X86
1511 select FB_CFB_FILLRECT
1512 select FB_CFB_COPYAREA
1513 select FB_CFB_IMAGEBLIT
1518 This is the frame buffer device driver for Graphics chips of VIA
1519 UniChrome (Pro) Family (CLE266,PM800/CN400,P4M800CE/P4M800Pro/
1520 CN700/VN800,CX700/VX700,P4M890) and Chrome9 Family (K8M890,CN896
1522 Say Y if you have a VIA UniChrome graphics board.
1524 To compile this driver as a module, choose M here: the
1525 module will be called viafb.
1529 config FB_VIA_DIRECT_PROCFS
1530 bool "direct hardware access via procfs (DEPRECATED)(DANGEROUS)"
1534 Allow direct hardware access to some output registers via procfs.
1535 This is dangerous but may provide the only chance to get the
1536 correct output device configuration.
1537 Its use is strongly discouraged.
1542 tristate "NeoMagic display support"
1543 depends on FB && PCI
1544 select FB_MODE_HELPERS
1545 select FB_CFB_FILLRECT
1546 select FB_CFB_COPYAREA
1547 select FB_CFB_IMAGEBLIT
1550 This driver supports notebooks with NeoMagic PCI chips.
1551 Say Y if you have such a graphics card.
1553 To compile this driver as a module, choose M here: the
1554 module will be called neofb.
1557 tristate "IMG Kyro support"
1558 depends on FB && PCI
1559 select FB_CFB_FILLRECT
1560 select FB_CFB_COPYAREA
1561 select FB_CFB_IMAGEBLIT
1563 Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
1566 To compile this driver as a module, choose M here: the
1567 module will be called kyrofb.
1570 tristate "3Dfx Banshee/Voodoo3/Voodoo5 display support"
1571 depends on FB && PCI
1572 select FB_CFB_IMAGEBLIT
1573 select FB_CFB_FILLRECT
1574 select FB_CFB_COPYAREA
1575 select FB_MODE_HELPERS
1577 This driver supports graphics boards with the 3Dfx Banshee,
1578 Voodoo3 or VSA-100 (aka Voodoo4/5) chips. Say Y if you have
1579 such a graphics board.
1581 To compile this driver as a module, choose M here: the
1582 module will be called tdfxfb.
1584 config FB_3DFX_ACCEL
1585 bool "3Dfx Acceleration functions (EXPERIMENTAL)"
1586 depends on FB_3DFX && EXPERIMENTAL
1588 This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer
1589 device driver with acceleration functions.
1592 bool "Enable DDC/I2C support"
1593 depends on FB_3DFX && EXPERIMENTAL
1597 Say Y here if you want DDC/I2C support for your 3dfx Voodoo3.
1600 tristate "3Dfx Voodoo Graphics (sst1) support"
1601 depends on FB && PCI
1602 select FB_CFB_FILLRECT
1603 select FB_CFB_COPYAREA
1604 select FB_CFB_IMAGEBLIT
1606 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
1607 Voodoo2 (cvg) based graphics card.
1609 To compile this driver as a module, choose M here: the
1610 module will be called sstfb.
1612 WARNING: Do not use any application that uses the 3D engine
1613 (namely glide) while using this driver.
1614 Please read the <file:Documentation/fb/sstfb.txt> for supported
1615 options and other important info support.
1618 tristate "VIA VT8623 support"
1619 depends on FB && PCI
1620 select FB_CFB_FILLRECT
1621 select FB_CFB_COPYAREA
1622 select FB_CFB_IMAGEBLIT
1623 select FB_TILEBLITTING
1626 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1628 Driver for CastleRock integrated graphics core in the
1629 VIA VT8623 [Apollo CLE266] chipset.
1632 tristate "Trident/CyberXXX/CyberBlade support"
1633 depends on FB && PCI
1634 select FB_CFB_FILLRECT
1635 select FB_CFB_COPYAREA
1636 select FB_CFB_IMAGEBLIT
1638 This is the frame buffer device driver for Trident PCI/AGP chipsets.
1639 Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D
1641 There are also integrated versions of these chips called CyberXXXX,
1642 CyberImage or CyberBlade. These chips are mostly found in laptops
1643 but also on some motherboards including early VIA EPIA motherboards.
1644 For more information, read <file:Documentation/fb/tridentfb.txt>
1646 Say Y if you have such a graphics board.
1648 To compile this driver as a module, choose M here: the
1649 module will be called tridentfb.
1652 tristate "ARK 2000PV support"
1653 depends on FB && PCI
1654 select FB_CFB_FILLRECT
1655 select FB_CFB_COPYAREA
1656 select FB_CFB_IMAGEBLIT
1657 select FB_TILEBLITTING
1660 select FONT_8x16 if FRAMEBUFFER_CONSOLE
1662 Driver for PCI graphics boards with ARK 2000PV chip
1663 and ICS 5342 RAMDAC.
1666 tristate "Permedia3 support (EXPERIMENTAL)"
1667 depends on FB && PCI && EXPERIMENTAL
1668 select FB_CFB_FILLRECT
1669 select FB_CFB_COPYAREA
1670 select FB_CFB_IMAGEBLIT
1672 This is the frame buffer device driver for the 3DLabs Permedia3
1673 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
1674 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
1675 and maybe other boards.
1678 tristate "Fujitsu carmine frame buffer support"
1679 depends on FB && PCI
1680 select FB_CFB_FILLRECT
1681 select FB_CFB_COPYAREA
1682 select FB_CFB_IMAGEBLIT
1684 This is the frame buffer device driver for the Fujitsu Carmine chip.
1685 The driver provides two independent frame buffer devices.
1688 depends on FB_CARMINE
1689 prompt "DRAM timing"
1690 default FB_CARMINE_DRAM_EVAL
1692 config FB_CARMINE_DRAM_EVAL
1693 bool "Eval board timings"
1695 Use timings which work on the eval card.
1697 config CARMINE_DRAM_CUSTOM
1698 bool "Custom board timings"
1700 Use custom board timings.
1704 bool "Au1100 LCD Driver"
1705 depends on (FB = y) && MIPS && SOC_AU1100
1706 select FB_CFB_FILLRECT
1707 select FB_CFB_COPYAREA
1708 select FB_CFB_IMAGEBLIT
1710 This is the framebuffer driver for the AMD Au1100 SOC. It can drive
1711 various panels and CRTs by passing in kernel cmd line option
1712 au1100fb:panel=<name>.
1715 bool "Au1200 LCD Driver"
1716 depends on (FB = y) && MIPS && SOC_AU1200
1717 select FB_CFB_FILLRECT
1718 select FB_CFB_COPYAREA
1719 select FB_CFB_IMAGEBLIT
1721 This is the framebuffer driver for the AMD Au1200 SOC. It can drive
1722 various panels and CRTs by passing in kernel cmd line option
1723 au1200fb:panel=<name>.
1725 source "drivers/video/geode/Kconfig"
1728 tristate "HD64461 Frame Buffer support"
1729 depends on FB && HD64461
1730 select FB_CFB_FILLRECT
1731 select FB_CFB_COPYAREA
1732 select FB_CFB_IMAGEBLIT
1734 This is the frame buffer device driver for the Hitachi HD64461 LCD
1738 bool "PMAG-AA TURBOchannel framebuffer support"
1739 depends on (FB = y) && TC
1740 select FB_CFB_FILLRECT
1741 select FB_CFB_COPYAREA
1742 select FB_CFB_IMAGEBLIT
1744 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
1745 used mainly in the MIPS-based DECstation series.
1748 tristate "PMAG-BA TURBOchannel framebuffer support"
1750 select FB_CFB_FILLRECT
1751 select FB_CFB_COPYAREA
1752 select FB_CFB_IMAGEBLIT
1754 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
1755 used mainly in the MIPS-based DECstation series.
1758 tristate "PMAGB-B TURBOchannel framebuffer support"
1760 select FB_CFB_FILLRECT
1761 select FB_CFB_COPYAREA
1762 select FB_CFB_IMAGEBLIT
1764 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
1765 in the MIPS-based DECstation series. The card is currently only
1766 supported in 1280x1024x8 mode.
1769 bool "Maxine (Personal DECstation) onboard framebuffer support"
1770 depends on (FB = y) && MACH_DECSTATION
1771 select FB_CFB_FILLRECT
1772 select FB_CFB_COPYAREA
1773 select FB_CFB_IMAGEBLIT
1775 Support for the onboard framebuffer (1024x768x8) in the Personal
1776 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
1780 bool "G364 frame buffer support"
1781 depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
1782 select FB_CFB_FILLRECT
1783 select FB_CFB_COPYAREA
1784 select FB_CFB_IMAGEBLIT
1786 The G364 driver is the framebuffer used in MIPS Magnum 4000 and
1787 Olivetti M700-10 systems.
1790 bool "Motorola 68328 native frame buffer support"
1791 depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
1792 select FB_CFB_FILLRECT
1793 select FB_CFB_COPYAREA
1794 select FB_CFB_IMAGEBLIT
1796 Say Y here if you want to support the built-in frame buffer of
1797 the Motorola 68328 CPU family.
1800 tristate "PXA168/910 LCD framebuffer support"
1801 depends on FB && (CPU_PXA168 || CPU_PXA910)
1802 select FB_CFB_FILLRECT
1803 select FB_CFB_COPYAREA
1804 select FB_CFB_IMAGEBLIT
1806 Frame buffer driver for the built-in LCD controller in the Marvell
1810 tristate "PXA LCD framebuffer support"
1811 depends on FB && ARCH_PXA
1812 select FB_CFB_FILLRECT
1813 select FB_CFB_COPYAREA
1814 select FB_CFB_IMAGEBLIT
1816 Frame buffer driver for the built-in LCD controller in the Intel
1819 This driver is also available as a module ( = code which can be
1820 inserted and removed from the running kernel whenever you want). The
1821 module will be called pxafb. If you want to compile it as a module,
1822 say M here and read <file:Documentation/kbuild/modules.txt>.
1826 config FB_PXA_OVERLAY
1827 bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
1829 depends on FB_PXA && (PXA27x || PXA3xx)
1831 config FB_PXA_SMARTPANEL
1832 bool "PXA Smartpanel LCD support"
1836 config FB_PXA_PARAMETERS
1837 bool "PXA LCD command line parameters"
1841 Enable the use of kernel command line or module parameters
1842 to configure the physical properties of the LCD panel when
1843 using the PXA LCD driver.
1845 This option allows you to override the panel parameters
1846 supplied by the platform in order to support multiple
1847 different models of flatpanel. If you will only be using a
1848 single model of flatpanel then you can safely leave this
1851 <file:Documentation/fb/pxafb.txt> describes the available parameters.
1854 tristate "2700G LCD framebuffer support"
1855 depends on FB && ARCH_PXA
1856 select FB_CFB_FILLRECT
1857 select FB_CFB_COPYAREA
1858 select FB_CFB_IMAGEBLIT
1860 Framebuffer driver for the Intel 2700G (Marathon) Graphics
1864 bool "Enable debugging info via debugfs"
1865 depends on FB_MBX && DEBUG_FS
1868 Enable this if you want debugging information using the debug
1869 filesystem (debugfs)
1874 tristate "Freescale DIU framebuffer support"
1875 depends on FB && FSL_SOC
1876 select FB_MODE_HELPERS
1877 select FB_CFB_FILLRECT
1878 select FB_CFB_COPYAREA
1879 select FB_CFB_IMAGEBLIT
1880 select PPC_LIB_RHEAP
1882 Framebuffer driver for the Freescale SoC DIU
1885 tristate "W100 frame buffer support"
1886 depends on FB && ARCH_PXA
1887 select FB_CFB_FILLRECT
1888 select FB_CFB_COPYAREA
1889 select FB_CFB_IMAGEBLIT
1891 Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
1892 It can also drive the w3220 chip found on iPAQ hx4700.
1894 This driver is also available as a module ( = code which can be
1895 inserted and removed from the running kernel whenever you want). The
1896 module will be called w100fb. If you want to compile it as a module,
1897 say M here and read <file:Documentation/kbuild/modules.txt>.
1903 depends on (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1905 config SH_LCD_MIPI_DSI
1908 config FB_SH_MOBILE_LCDC
1909 tristate "SuperH Mobile LCDC framebuffer support"
1910 depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK
1911 select FB_SYS_FILLRECT
1912 select FB_SYS_COPYAREA
1913 select FB_SYS_IMAGEBLIT
1915 select FB_DEFERRED_IO
1916 select SH_MIPI_DSI if SH_LCD_MIPI_DSI
1918 Frame buffer driver for the on-chip SH-Mobile LCD controller.
1920 config FB_SH_MOBILE_HDMI
1921 tristate "SuperH Mobile HDMI controller support"
1922 depends on FB_SH_MOBILE_LCDC
1923 select FB_MODE_HELPERS
1928 Driver for the on-chip SH-Mobile HDMI controller.
1931 tristate "Toshiba Mobile IO FrameBuffer support"
1932 depends on FB && MFD_CORE
1933 select FB_CFB_FILLRECT
1934 select FB_CFB_COPYAREA
1935 select FB_CFB_IMAGEBLIT
1937 Frame buffer driver for the Toshiba Mobile IO integrated as found
1938 on the Sharp SL-6000 series
1940 This driver is also available as a module ( = code which can be
1941 inserted and removed from the running kernel whenever you want). The
1942 module will be called tmiofb. If you want to compile it as a module,
1943 say M here and read <file:Documentation/kbuild/modules.txt>.
1947 config FB_TMIO_ACCELL
1948 bool "tmiofb acceleration"
1953 tristate "Samsung S3C framebuffer support"
1954 depends on FB && S3C_DEV_FB
1955 select FB_CFB_FILLRECT
1956 select FB_CFB_COPYAREA
1957 select FB_CFB_IMAGEBLIT
1959 Frame buffer driver for the built-in FB controller in the Samsung
1960 SoC line from the S3C2443 onwards, including the S3C2416, S3C2450,
1961 and the S3C64XX series such as the S3C6400 and S3C6410.
1963 These chips all have the same basic framebuffer design with the
1964 actual capabilities depending on the chip. For instance the S3C6400
1965 and S3C6410 support 4 hardware windows whereas the S3C24XX series
1966 currently only have two.
1968 Currently the support is only for the S3C6400 and S3C6410 SoCs.
1970 config FB_S3C_DEBUG_REGWRITE
1971 bool "Debug register writes"
1974 Show all register writes via printk(KERN_DEBUG)
1977 tristate "S3C2410 LCD framebuffer support"
1978 depends on FB && ARCH_S3C2410
1979 select FB_CFB_FILLRECT
1980 select FB_CFB_COPYAREA
1981 select FB_CFB_IMAGEBLIT
1983 Frame buffer driver for the built-in LCD controller in the Samsung
1986 This driver is also available as a module ( = code which can be
1987 inserted and removed from the running kernel whenever you want). The
1988 module will be called s3c2410fb. If you want to compile it as a module,
1989 say M here and read <file:Documentation/kbuild/modules.txt>.
1992 config FB_S3C2410_DEBUG
1993 bool "S3C2410 lcd debug messages"
1994 depends on FB_S3C2410
1996 Turn on debugging messages. Note that you can set/unset at run time
2000 bool "NUC900 LCD framebuffer support"
2001 depends on FB && ARCH_W90X900
2002 select FB_CFB_FILLRECT
2003 select FB_CFB_COPYAREA
2004 select FB_CFB_IMAGEBLIT
2006 Frame buffer driver for the built-in LCD controller in the Nuvoton
2009 config GPM1040A0_320X240
2010 bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
2011 depends on FB_NUC900
2013 config FB_NUC900_DEBUG
2014 bool "NUC900 lcd debug messages"
2015 depends on FB_NUC900
2017 Turn on debugging messages. Note that you can set/unset at run time
2021 tristate "Silicon Motion SM501 framebuffer support"
2022 depends on FB && MFD_SM501
2023 select FB_CFB_FILLRECT
2024 select FB_CFB_COPYAREA
2025 select FB_CFB_IMAGEBLIT
2027 Frame buffer driver for the CRT and LCD controllers in the Silicon
2030 This driver is also available as a module ( = code which can be
2031 inserted and removed from the running kernel whenever you want). The
2032 module will be called sm501fb. If you want to compile it as a module,
2033 say M here and read <file:Documentation/kbuild/modules.txt>.
2038 config FB_PNX4008_DUM
2039 tristate "Display Update Module support on Philips PNX4008 board"
2040 depends on FB && ARCH_PNX4008
2042 Say Y here to enable support for PNX4008 Display Update Module (DUM)
2044 config FB_PNX4008_DUM_RGB
2045 tristate "RGB Framebuffer support on Philips PNX4008 board"
2046 depends on FB_PNX4008_DUM
2047 select FB_CFB_FILLRECT
2048 select FB_CFB_COPYAREA
2049 select FB_CFB_IMAGEBLIT
2051 Say Y here to enable support for PNX4008 RGB Framebuffer
2053 config FB_IBM_GXT4500
2054 tristate "Framebuffer support for IBM GXT4500P adaptor"
2055 depends on FB && PPC
2056 select FB_CFB_FILLRECT
2057 select FB_CFB_COPYAREA
2058 select FB_CFB_IMAGEBLIT
2060 Say Y here to enable support for the IBM GXT4500P display
2061 adaptor, found on some IBM System P (pSeries) machines.
2064 tristate "PS3 GPU framebuffer driver"
2065 depends on FB && PS3_PS3AV
2066 select FB_SYS_FILLRECT
2067 select FB_SYS_COPYAREA
2068 select FB_SYS_IMAGEBLIT
2070 select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
2072 Include support for the virtual frame buffer in the PS3 platform.
2074 config FB_PS3_DEFAULT_SIZE_M
2075 int "PS3 default frame buffer size (in MiB)"
2079 This is the default size (in MiB) of the virtual frame buffer in
2081 The default value can be overridden on the kernel command line
2082 using the "ps3fb" option (e.g. "ps3fb=9M");
2085 tristate "Xilinx frame buffer support"
2086 depends on FB && (XILINX_VIRTEX || MICROBLAZE)
2087 select FB_CFB_FILLRECT
2088 select FB_CFB_COPYAREA
2089 select FB_CFB_IMAGEBLIT
2091 Include support for the Xilinx ML300/ML403 reference design
2092 framebuffer. ML300 carries a 640*480 LCD display on the board,
2093 ML403 uses a standard DB15 VGA connector.
2096 tristate "Cobalt server LCD frame buffer support"
2097 depends on FB && MIPS_COBALT
2100 bool "SH7760/SH7763/SH7720/SH7721 LCDC support"
2101 depends on FB && (CPU_SUBTYPE_SH7760 || CPU_SUBTYPE_SH7763 \
2102 || CPU_SUBTYPE_SH7720 || CPU_SUBTYPE_SH7721)
2103 select FB_CFB_FILLRECT
2104 select FB_CFB_COPYAREA
2105 select FB_CFB_IMAGEBLIT
2107 Support for the SH7760/SH7763/SH7720/SH7721 integrated
2108 (D)STN/TFT LCD Controller.
2109 Supports display resolutions up to 1024x1024 pixel, grayscale and
2110 color operation, with depths ranging from 1 bpp to 8 bpp monochrome
2111 and 8, 15 or 16 bpp color; 90 degrees clockwise display rotation for
2112 panels <= 320 pixel horizontal resolution.
2115 tristate "DA8xx/OMAP-L1xx Framebuffer support"
2116 depends on FB && ARCH_DAVINCI_DA8XX
2117 select FB_CFB_FILLRECT
2118 select FB_CFB_COPYAREA
2119 select FB_CFB_IMAGEBLIT
2121 This is the frame buffer device driver for the TI LCD controller
2122 found on DA8xx/OMAP-L1xx SoCs.
2126 tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
2128 select FB_SYS_FILLRECT
2129 select FB_SYS_COPYAREA
2130 select FB_SYS_IMAGEBLIT
2133 This is a `virtual' frame buffer device. It operates on a chunk of
2134 unswappable kernel memory instead of on the memory of a graphics
2135 board. This means you cannot see any output sent to this frame
2136 buffer device, while it does consume precious memory. The main use
2137 of this frame buffer device is testing and debugging the frame
2138 buffer subsystem. Do NOT enable it for normal systems! To protect
2139 the innocent, it has to be enabled explicitly at boot time using the
2140 kernel option `video=vfb:'.
2142 To compile this driver as a module, choose M here: the
2143 module will be called vfb. In order to load it, you must use
2144 the vfb_enable=1 option.
2148 config XEN_FBDEV_FRONTEND
2149 tristate "Xen virtual frame buffer support"
2150 depends on FB && XEN
2151 select FB_SYS_FILLRECT
2152 select FB_SYS_COPYAREA
2153 select FB_SYS_IMAGEBLIT
2155 select FB_DEFERRED_IO
2156 select XEN_XENBUS_FRONTEND
2159 This driver implements the front-end of the Xen virtual
2160 frame buffer driver. It communicates with a back-end
2164 tristate "E-Ink Metronome/8track controller support"
2166 select FB_SYS_FILLRECT
2167 select FB_SYS_COPYAREA
2168 select FB_SYS_IMAGEBLIT
2170 select FB_DEFERRED_IO
2172 This driver implements support for the E-Ink Metronome
2173 controller. The pre-release name for this device was 8track
2174 and could also have been called by some vendors as PVI-nnnn.
2177 tristate "Fujitsu MB862xx GDC support"
2179 select FB_CFB_FILLRECT
2180 select FB_CFB_COPYAREA
2181 select FB_CFB_IMAGEBLIT
2183 Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers.
2185 config FB_MB862XX_PCI_GDC
2186 bool "Carmine/Coral-P(A) GDC"
2187 depends on PCI && FB_MB862XX
2189 This enables framebuffer support for Fujitsu Carmine/Coral-P(A)
2190 PCI graphics controller devices.
2192 config FB_MB862XX_LIME
2194 depends on FB_MB862XX
2195 depends on OF && !FB_MB862XX_PCI_GDC
2197 select FB_FOREIGN_ENDIAN
2198 select FB_LITTLE_ENDIAN
2200 Framebuffer support for Fujitsu Lime GDC on host CPU bus.
2203 tristate "EP93XX frame buffer support"
2204 depends on FB && ARCH_EP93XX
2205 select FB_CFB_FILLRECT
2206 select FB_CFB_COPYAREA
2207 select FB_CFB_IMAGEBLIT
2209 Framebuffer driver for the Cirrus Logic EP93XX series of processors.
2210 This driver is also available as a module. The module will be called
2213 config FB_PRE_INIT_FB
2214 bool "Don't reinitialize, use bootloader's GDC/Display configuration"
2215 depends on FB && FB_MB862XX_LIME
2217 Select this option if display contents should be inherited as set by
2221 tristate "MSM Framebuffer support"
2222 depends on FB && ARCH_MSM
2223 select FB_CFB_FILLRECT
2224 select FB_CFB_COPYAREA
2225 select FB_CFB_IMAGEBLIT
2228 tristate "MX3 Framebuffer support"
2229 depends on FB && MX3_IPU
2230 select FB_CFB_FILLRECT
2231 select FB_CFB_COPYAREA
2232 select FB_CFB_IMAGEBLIT
2235 This is a framebuffer device for the i.MX31 LCD Controller. So
2236 far only synchronous displays are supported. If you plan to use
2237 an LCD display with your i.MX31 system, say Y here.
2239 config FB_BROADSHEET
2240 tristate "E-Ink Broadsheet/Epson S1D13521 controller support"
2242 select FB_SYS_FILLRECT
2243 select FB_SYS_COPYAREA
2244 select FB_SYS_IMAGEBLIT
2246 select FB_DEFERRED_IO
2248 This driver implements support for the E-Ink Broadsheet
2249 controller. The release name for this device was Epson S1D13521
2250 and could also have been called by other names when coupled with
2254 tristate "JZ4740 LCD framebuffer support"
2255 depends on FB && MACH_JZ4740
2256 select FB_SYS_FILLRECT
2257 select FB_SYS_COPYAREA
2258 select FB_SYS_IMAGEBLIT
2260 Framebuffer support for the JZ4740 SoC.
2262 source "drivers/video/omap/Kconfig"
2263 source "drivers/video/omap2/Kconfig"
2265 source "drivers/video/backlight/Kconfig"
2266 source "drivers/video/display/Kconfig"
2269 source "drivers/video/console/Kconfig"
2272 if FB || SGI_NEWPORT_CONSOLE
2273 source "drivers/video/logo/Kconfig"