Kconfig 53 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209121012111212121312141215121612171218121912201221122212231224122512261227122812291230123112321233123412351236123712381239124012411242124312441245124612471248124912501251125212531254125512561257125812591260126112621263126412651266126712681269127012711272127312741275127612771278127912801281128212831284128512861287128812891290129112921293129412951296129712981299130013011302130313041305130613071308130913101311131213131314131513161317131813191320132113221323132413251326132713281329133013311332133313341335133613371338133913401341134213431344134513461347134813491350135113521353135413551356135713581359136013611362136313641365136613671368136913701371137213731374137513761377137813791380138113821383138413851386138713881389139013911392139313941395139613971398139914001401140214031404140514061407140814091410141114121413141414151416141714181419142014211422142314241425142614271428142914301431143214331434143514361437143814391440144114421443144414451446144714481449145014511452145314541455145614571458145914601461146214631464146514661467146814691470147114721473147414751476147714781479148014811482148314841485148614871488148914901491149214931494149514961497149814991500150115021503150415051506150715081509151015111512151315141515151615171518151915201521152215231524152515261527152815291530153115321533153415351536153715381539154015411542154315441545154615471548154915501551155215531554155515561557155815591560156115621563156415651566156715681569157015711572157315741575157615771578157915801581158215831584158515861587158815891590159115921593159415951596159715981599160016011602160316041605160616071608160916101611161216131614161516161617161816191620162116221623162416251626162716281629163016311632163316341635163616371638163916401641164216431644164516461647164816491650165116521653165416551656165716581659166016611662166316641665166616671668166916701671167216731674167516761677167816791680168116821683168416851686168716881689169016911692169316941695169616971698169917001701170217031704170517061707170817091710171117121713171417151716
  1. #
  2. # Video configuration
  3. #
  4. menu "Graphics support"
  5. source "drivers/video/backlight/Kconfig"
  6. source "drivers/video/display/Kconfig"
  7. config FB
  8. tristate "Support for frame buffer devices"
  9. ---help---
  10. The frame buffer device provides an abstraction for the graphics
  11. hardware. It represents the frame buffer of some video hardware and
  12. allows application software to access the graphics hardware through
  13. a well-defined interface, so the software doesn't need to know
  14. anything about the low-level (hardware register) stuff.
  15. Frame buffer devices work identically across the different
  16. architectures supported by Linux and make the implementation of
  17. application programs easier and more portable; at this point, an X
  18. server exists which uses the frame buffer device exclusively.
  19. On several non-X86 architectures, the frame buffer device is the
  20. only way to use the graphics hardware.
  21. The device is accessed through special device nodes, usually located
  22. in the /dev directory, i.e. /dev/fb*.
  23. You need an utility program called fbset to make full use of frame
  24. buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
  25. and the Framebuffer-HOWTO at
  26. <http://www.tahallah.demon.co.uk/programming/prog.html> for more
  27. information.
  28. Say Y here and to the driver for your graphics board below if you
  29. are compiling a kernel for a non-x86 architecture.
  30. If you are compiling for the x86 architecture, you can say Y if you
  31. want to play with it, but it is not essential. Please note that
  32. running graphical applications that directly touch the hardware
  33. (e.g. an accelerated X server) and that are not frame buffer
  34. device-aware may cause unexpected results. If unsure, say N.
  35. config FIRMWARE_EDID
  36. bool "Enable firmware EDID"
  37. depends on FB
  38. default n
  39. ---help---
  40. This enables access to the EDID transferred from the firmware.
  41. On the i386, this is from the Video BIOS. Enable this if DDC/I2C
  42. transfers do not work for your driver and if you are using
  43. nvidiafb, i810fb or savagefb.
  44. In general, choosing Y for this option is safe. If you
  45. experience extremely long delays while booting before you get
  46. something on your display, try setting this to N. Matrox cards in
  47. combination with certain motherboards and monitors are known to
  48. suffer from this problem.
  49. config FB_DDC
  50. tristate
  51. depends on FB
  52. select I2C_ALGOBIT
  53. select I2C
  54. default n
  55. config FB_CFB_FILLRECT
  56. tristate
  57. depends on FB
  58. default n
  59. ---help---
  60. Include the cfb_fillrect function for generic software rectangle
  61. filling. This is used by drivers that don't provide their own
  62. (accelerated) version.
  63. config FB_CFB_COPYAREA
  64. tristate
  65. depends on FB
  66. default n
  67. ---help---
  68. Include the cfb_copyarea function for generic software area copying.
  69. This is used by drivers that don't provide their own (accelerated)
  70. version.
  71. config FB_CFB_IMAGEBLIT
  72. tristate
  73. depends on FB
  74. default n
  75. ---help---
  76. Include the cfb_imageblit function for generic software image
  77. blitting. This is used by drivers that don't provide their own
  78. (accelerated) version.
  79. config FB_DEFERRED_IO
  80. bool
  81. depends on FB
  82. default y
  83. config FB_SVGALIB
  84. tristate
  85. depends on FB
  86. default n
  87. ---help---
  88. Common utility functions useful to fbdev drivers of VGA-based
  89. cards.
  90. config FB_MACMODES
  91. tristate
  92. depends on FB
  93. default n
  94. config FB_BACKLIGHT
  95. bool
  96. depends on FB
  97. select BACKLIGHT_LCD_SUPPORT
  98. select BACKLIGHT_CLASS_DEVICE
  99. default n
  100. config FB_MODE_HELPERS
  101. bool "Enable Video Mode Handling Helpers"
  102. depends on FB
  103. default n
  104. ---help---
  105. This enables functions for handling video modes using the
  106. Generalized Timing Formula and the EDID parser. A few drivers rely
  107. on this feature such as the radeonfb, rivafb, and the i810fb. If
  108. your driver does not take advantage of this feature, choosing Y will
  109. just increase the kernel size by about 5K.
  110. config FB_TILEBLITTING
  111. bool "Enable Tile Blitting Support"
  112. depends on FB
  113. default n
  114. ---help---
  115. This enables tile blitting. Tile blitting is a drawing technique
  116. where the screen is divided into rectangular sections (tiles), whereas
  117. the standard blitting divides the screen into pixels. Because the
  118. default drawing element is a tile, drawing functions will be passed
  119. parameters in terms of number of tiles instead of number of pixels.
  120. For example, to draw a single character, instead of using bitmaps,
  121. an index to an array of bitmaps will be used. To clear or move a
  122. rectangular section of a screen, the rectangle will be described in
  123. terms of number of tiles in the x- and y-axis.
  124. This is particularly important to one driver, matroxfb. If
  125. unsure, say N.
  126. comment "Frame buffer hardware drivers"
  127. depends on FB
  128. config FB_CIRRUS
  129. tristate "Cirrus Logic support"
  130. depends on FB && (ZORRO || PCI)
  131. select FB_CFB_FILLRECT
  132. select FB_CFB_COPYAREA
  133. select FB_CFB_IMAGEBLIT
  134. ---help---
  135. This enables support for Cirrus Logic GD542x/543x based boards on
  136. Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
  137. If you have a PCI-based system, this enables support for these
  138. chips: GD-543x, GD-544x, GD-5480.
  139. Please read the file <file:Documentation/fb/cirrusfb.txt>.
  140. Say N unless you have such a graphics board or plan to get one
  141. before you next recompile the kernel.
  142. config FB_PM2
  143. tristate "Permedia2 support"
  144. depends on FB && ((AMIGA && BROKEN) || PCI)
  145. select FB_CFB_FILLRECT
  146. select FB_CFB_COPYAREA
  147. select FB_CFB_IMAGEBLIT
  148. help
  149. This is the frame buffer device driver for the Permedia2 AGP frame
  150. buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
  151. product page at
  152. <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
  153. config FB_PM2_FIFO_DISCONNECT
  154. bool "enable FIFO disconnect feature"
  155. depends on FB_PM2 && PCI
  156. help
  157. Support the Permedia2 FIFO disconnect feature (see CONFIG_FB_PM2).
  158. config FB_ARMCLCD
  159. tristate "ARM PrimeCell PL110 support"
  160. depends on FB && ARM && ARM_AMBA
  161. select FB_CFB_FILLRECT
  162. select FB_CFB_COPYAREA
  163. select FB_CFB_IMAGEBLIT
  164. help
  165. This framebuffer device driver is for the ARM PrimeCell PL110
  166. Colour LCD controller. ARM PrimeCells provide the building
  167. blocks for System on a Chip devices.
  168. If you want to compile this as a module (=code which can be
  169. inserted into and removed from the running kernel), say M
  170. here and read <file:Documentation/kbuild/modules.txt>. The module
  171. will be called amba-clcd.
  172. choice
  173. depends on FB_ARMCLCD && (ARCH_LH7A40X || ARCH_LH7952X)
  174. prompt "LCD Panel"
  175. default FB_ARMCLCD_SHARP_LQ035Q7DB02
  176. config FB_ARMCLCD_SHARP_LQ035Q7DB02_HRTFT
  177. bool "LogicPD LCD 3.5\" QVGA w/HRTFT IC"
  178. help
  179. This is an implementation of the Sharp LQ035Q7DB02, a 3.5"
  180. color QVGA, HRTFT panel. The LogicPD device includes
  181. an integrated HRTFT controller IC.
  182. The native resolution is 240x320.
  183. config FB_ARMCLCD_SHARP_LQ057Q3DC02
  184. bool "LogicPD LCD 5.7\" QVGA"
  185. help
  186. This is an implementation of the Sharp LQ057Q3DC02, a 5.7"
  187. color QVGA, TFT panel. The LogicPD device includes an
  188. The native resolution is 320x240.
  189. config FB_ARMCLCD_SHARP_LQ64D343
  190. bool "LogicPD LCD 6.4\" VGA"
  191. help
  192. This is an implementation of the Sharp LQ64D343, a 6.4"
  193. color VGA, TFT panel. The LogicPD device includes an
  194. The native resolution is 640x480.
  195. config FB_ARMCLCD_SHARP_LQ10D368
  196. bool "LogicPD LCD 10.4\" VGA"
  197. help
  198. This is an implementation of the Sharp LQ10D368, a 10.4"
  199. color VGA, TFT panel. The LogicPD device includes an
  200. The native resolution is 640x480.
  201. config FB_ARMCLCD_SHARP_LQ121S1DG41
  202. bool "LogicPD LCD 12.1\" SVGA"
  203. help
  204. This is an implementation of the Sharp LQ121S1DG41, a 12.1"
  205. color SVGA, TFT panel. The LogicPD device includes an
  206. The native resolution is 800x600.
  207. This panel requires a clock rate may be an integer fraction
  208. of the base LCDCLK frequency. The driver will select the
  209. highest frequency available that is lower than the maximum
  210. allowed. The panel may flicker if the clock rate is
  211. slower than the recommended minimum.
  212. config FB_ARMCLCD_AUO_A070VW01_WIDE
  213. bool "AU Optronics A070VW01 LCD 7.0\" WIDE"
  214. help
  215. This is an implementation of the AU Optronics, a 7.0"
  216. WIDE Color. The native resolution is 234x480.
  217. config FB_ARMCLCD_HITACHI
  218. bool "Hitachi Wide Screen 800x480"
  219. help
  220. This is an implementation of the Hitachi 800x480.
  221. endchoice
  222. config FB_ACORN
  223. bool "Acorn VIDC support"
  224. depends on (FB = y) && ARM && (ARCH_ACORN || ARCH_CLPS7500)
  225. select FB_CFB_FILLRECT
  226. select FB_CFB_COPYAREA
  227. select FB_CFB_IMAGEBLIT
  228. help
  229. This is the frame buffer device driver for the Acorn VIDC graphics
  230. hardware found in Acorn RISC PCs and other ARM-based machines. If
  231. unsure, say N.
  232. config FB_CLPS711X
  233. bool "CLPS711X LCD support"
  234. depends on (FB = y) && ARM && ARCH_CLPS711X
  235. select FB_CFB_FILLRECT
  236. select FB_CFB_COPYAREA
  237. select FB_CFB_IMAGEBLIT
  238. help
  239. Say Y to enable the Framebuffer driver for the CLPS7111 and
  240. EP7212 processors.
  241. config FB_SA1100
  242. bool "SA-1100 LCD support"
  243. depends on (FB = y) && ARM && ARCH_SA1100
  244. select FB_CFB_FILLRECT
  245. select FB_CFB_COPYAREA
  246. select FB_CFB_IMAGEBLIT
  247. help
  248. This is a framebuffer device for the SA-1100 LCD Controller.
  249. See <http://www.linux-fbdev.org/> for information on framebuffer
  250. devices.
  251. If you plan to use the LCD display with your SA-1100 system, say
  252. Y here.
  253. config FB_IMX
  254. tristate "Motorola i.MX LCD support"
  255. depends on FB && ARM && ARCH_IMX
  256. select FB_CFB_FILLRECT
  257. select FB_CFB_COPYAREA
  258. select FB_CFB_IMAGEBLIT
  259. config FB_CYBER2000
  260. tristate "CyberPro 2000/2010/5000 support"
  261. depends on FB && PCI && (BROKEN || !SPARC64)
  262. select FB_CFB_FILLRECT
  263. select FB_CFB_COPYAREA
  264. select FB_CFB_IMAGEBLIT
  265. help
  266. This enables support for the Integraphics CyberPro 20x0 and 5000
  267. VGA chips used in the Rebel.com Netwinder and other machines.
  268. Say Y if you have a NetWinder or a graphics card containing this
  269. device, otherwise say N.
  270. config FB_APOLLO
  271. bool
  272. depends on (FB = y) && APOLLO
  273. default y
  274. select FB_CFB_FILLRECT
  275. select FB_CFB_IMAGEBLIT
  276. config FB_Q40
  277. bool
  278. depends on (FB = y) && Q40
  279. default y
  280. select FB_CFB_FILLRECT
  281. select FB_CFB_COPYAREA
  282. select FB_CFB_IMAGEBLIT
  283. config FB_AMIGA
  284. tristate "Amiga native chipset support"
  285. depends on FB && AMIGA
  286. help
  287. This is the frame buffer device driver for the builtin graphics
  288. chipset found in Amigas.
  289. To compile this driver as a module, choose M here: the
  290. module will be called amifb.
  291. config FB_AMIGA_OCS
  292. bool "Amiga OCS chipset support"
  293. depends on FB_AMIGA
  294. help
  295. This enables support for the original Agnus and Denise video chips,
  296. found in the Amiga 1000 and most A500's and A2000's. If you intend
  297. to run Linux on any of these systems, say Y; otherwise say N.
  298. config FB_AMIGA_ECS
  299. bool "Amiga ECS chipset support"
  300. depends on FB_AMIGA
  301. help
  302. This enables support for the Enhanced Chip Set, found in later
  303. A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
  304. you intend to run Linux on any of these systems, say Y; otherwise
  305. say N.
  306. config FB_AMIGA_AGA
  307. bool "Amiga AGA chipset support"
  308. depends on FB_AMIGA
  309. help
  310. This enables support for the Advanced Graphics Architecture (also
  311. known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
  312. and CD32. If you intend to run Linux on any of these systems, say Y;
  313. otherwise say N.
  314. config FB_FM2
  315. bool "Amiga FrameMaster II/Rainbow II support"
  316. depends on (FB = y) && ZORRO
  317. select FB_CFB_FILLRECT
  318. select FB_CFB_COPYAREA
  319. select FB_CFB_IMAGEBLIT
  320. help
  321. This is the frame buffer device driver for the Amiga FrameMaster
  322. card from BSC (exhibited 1992 but not shipped as a CBM product).
  323. config FB_ARC
  324. tristate "Arc Monochrome LCD board support"
  325. depends on FB && X86
  326. select FB_CFB_FILLRECT
  327. select FB_CFB_COPYAREA
  328. select FB_CFB_IMAGEBLIT
  329. help
  330. This enables support for the Arc Monochrome LCD board. The board
  331. is based on the KS-108 lcd controller and is typically a matrix
  332. of 2*n chips. This driver was tested with a 128x64 panel. This
  333. driver supports it for use with x86 SBCs through a 16 bit GPIO
  334. interface (8 bit data, 8 bit control). If you anticipate using
  335. this driver, say Y or M; otherwise say N. You must specify the
  336. GPIO IO address to be used for setting control and data.
  337. config FB_ATARI
  338. bool "Atari native chipset support"
  339. depends on (FB = y) && ATARI
  340. select FB_CFB_FILLRECT
  341. select FB_CFB_COPYAREA
  342. select FB_CFB_IMAGEBLIT
  343. help
  344. This is the frame buffer device driver for the builtin graphics
  345. chipset found in Ataris.
  346. config FB_OF
  347. bool "Open Firmware frame buffer device support"
  348. depends on (FB = y) && (PPC64 || PPC_OF) && (!PPC_PSERIES || PCI)
  349. select FB_CFB_FILLRECT
  350. select FB_CFB_COPYAREA
  351. select FB_CFB_IMAGEBLIT
  352. select FB_MACMODES
  353. help
  354. Say Y if you want support with Open Firmware for your graphics
  355. board.
  356. config FB_CONTROL
  357. bool "Apple \"control\" display support"
  358. depends on (FB = y) && PPC_PMAC && PPC32
  359. select FB_CFB_FILLRECT
  360. select FB_CFB_COPYAREA
  361. select FB_CFB_IMAGEBLIT
  362. select FB_MACMODES
  363. help
  364. This driver supports a frame buffer for the graphics adapter in the
  365. Power Macintosh 7300 and others.
  366. config FB_PLATINUM
  367. bool "Apple \"platinum\" display support"
  368. depends on (FB = y) && PPC_PMAC && PPC32
  369. select FB_CFB_FILLRECT
  370. select FB_CFB_COPYAREA
  371. select FB_CFB_IMAGEBLIT
  372. select FB_MACMODES
  373. help
  374. This driver supports a frame buffer for the "platinum" graphics
  375. adapter in some Power Macintoshes.
  376. config FB_VALKYRIE
  377. bool "Apple \"valkyrie\" display support"
  378. depends on (FB = y) && (MAC || (PPC_PMAC && PPC32))
  379. select FB_CFB_FILLRECT
  380. select FB_CFB_COPYAREA
  381. select FB_CFB_IMAGEBLIT
  382. select FB_MACMODES
  383. help
  384. This driver supports a frame buffer for the "valkyrie" graphics
  385. adapter in some Power Macintoshes.
  386. config FB_CT65550
  387. bool "Chips 65550 display support"
  388. depends on (FB = y) && PPC32
  389. select FB_CFB_FILLRECT
  390. select FB_CFB_COPYAREA
  391. select FB_CFB_IMAGEBLIT
  392. help
  393. This is the frame buffer device driver for the Chips & Technologies
  394. 65550 graphics chip in PowerBooks.
  395. config FB_ASILIANT
  396. bool "Asiliant (Chips) 69000 display support"
  397. depends on (FB = y) && PCI
  398. select FB_CFB_FILLRECT
  399. select FB_CFB_COPYAREA
  400. select FB_CFB_IMAGEBLIT
  401. help
  402. This is the frame buffer device driver for the Asiliant 69030 chipset
  403. config FB_IMSTT
  404. bool "IMS Twin Turbo display support"
  405. depends on (FB = y) && PCI
  406. select FB_CFB_IMAGEBLIT
  407. select FB_MACMODES if PPC
  408. help
  409. The IMS Twin Turbo is a PCI-based frame buffer card bundled with
  410. many Macintosh and compatible computers.
  411. config FB_VGA16
  412. tristate "VGA 16-color graphics support"
  413. depends on FB && (X86 || PPC)
  414. select FB_CFB_FILLRECT
  415. select FB_CFB_COPYAREA
  416. select FB_CFB_IMAGEBLIT
  417. help
  418. This is the frame buffer device driver for VGA 16 color graphic
  419. cards. Say Y if you have such a card.
  420. To compile this driver as a module, choose M here: the
  421. module will be called vga16fb.
  422. config FB_STI
  423. tristate "HP STI frame buffer device support"
  424. depends on FB && PARISC
  425. select FB_CFB_FILLRECT
  426. select FB_CFB_COPYAREA
  427. select FB_CFB_IMAGEBLIT
  428. default y
  429. ---help---
  430. STI refers to the HP "Standard Text Interface" which is a set of
  431. BIOS routines contained in a ROM chip in HP PA-RISC based machines.
  432. Enabling this option will implement the linux framebuffer device
  433. using calls to the STI BIOS routines for initialisation.
  434. If you enable this option, you will get a planar framebuffer device
  435. /dev/fb which will work on the most common HP graphic cards of the
  436. NGLE family, including the artist chips (in the 7xx and Bxxx series),
  437. HCRX, HCRX24, CRX, CRX24 and VisEG series.
  438. It is safe to enable this option, so you should probably say "Y".
  439. config FB_MAC
  440. bool "Generic Macintosh display support"
  441. depends on (FB = y) && MAC
  442. select FB_CFB_FILLRECT
  443. select FB_CFB_COPYAREA
  444. select FB_CFB_IMAGEBLIT
  445. select FB_MACMODES
  446. # bool ' Apple DAFB display support' CONFIG_FB_DAFB
  447. config FB_HP300
  448. bool
  449. depends on (FB = y) && HP300
  450. select FB_CFB_FILLRECT
  451. select FB_CFB_IMAGEBLIT
  452. default y
  453. config FB_TGA
  454. tristate "TGA framebuffer support"
  455. depends on FB && ALPHA
  456. select FB_CFB_FILLRECT
  457. select FB_CFB_COPYAREA
  458. select FB_CFB_IMAGEBLIT
  459. select BITREVERSE
  460. help
  461. This is the frame buffer device driver for generic TGA graphic
  462. cards. Say Y if you have one of those.
  463. config FB_VESA
  464. bool "VESA VGA graphics support"
  465. depends on (FB = y) && X86
  466. select FB_CFB_FILLRECT
  467. select FB_CFB_COPYAREA
  468. select FB_CFB_IMAGEBLIT
  469. select VIDEO_SELECT
  470. help
  471. This is the frame buffer device driver for generic VESA 2.0
  472. compliant graphic cards. The older VESA 1.2 cards are not supported.
  473. You will get a boot time penguin logo at no additional cost. Please
  474. read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
  475. config FB_IMAC
  476. bool "Intel-based Macintosh Framebuffer Support"
  477. depends on (FB = y) && X86 && EFI
  478. select FB_CFB_FILLRECT
  479. select FB_CFB_COPYAREA
  480. select FB_CFB_IMAGEBLIT
  481. help
  482. This is the frame buffer device driver for the Intel-based Macintosh
  483. config FB_HECUBA
  484. tristate "Hecuba board support"
  485. depends on FB && X86 && MMU
  486. select FB_CFB_FILLRECT
  487. select FB_CFB_COPYAREA
  488. select FB_CFB_IMAGEBLIT
  489. select FB_DEFERRED_IO
  490. help
  491. This enables support for the Hecuba board. This driver was tested
  492. with an E-Ink 800x600 display and x86 SBCs through a 16 bit GPIO
  493. interface (8 bit data, 4 bit control). If you anticpate using
  494. this driver, say Y or M; otherwise say N. You must specify the
  495. GPIO IO address to be used for setting control and data.
  496. config FB_HGA
  497. tristate "Hercules mono graphics support"
  498. depends on FB && X86
  499. select FB_CFB_FILLRECT
  500. select FB_CFB_COPYAREA
  501. select FB_CFB_IMAGEBLIT
  502. help
  503. Say Y here if you have a Hercules mono graphics card.
  504. To compile this driver as a module, choose M here: the
  505. module will be called hgafb.
  506. As this card technology is 15 years old, most people will answer N
  507. here.
  508. config FB_HGA_ACCEL
  509. bool "Hercules mono Acceleration functions (EXPERIMENTAL)"
  510. depends on FB_HGA && EXPERIMENTAL
  511. ---help---
  512. This will compile the Hercules mono graphics with
  513. acceleration functions.
  514. config FB_SGIVW
  515. tristate "SGI Visual Workstation framebuffer support"
  516. depends on FB && X86_VISWS
  517. select FB_CFB_FILLRECT
  518. select FB_CFB_COPYAREA
  519. select FB_CFB_IMAGEBLIT
  520. help
  521. SGI Visual Workstation support for framebuffer graphics.
  522. config FB_GBE
  523. bool "SGI Graphics Backend frame buffer support"
  524. depends on (FB = y) && (SGI_IP32 || X86_VISWS)
  525. select FB_CFB_FILLRECT
  526. select FB_CFB_COPYAREA
  527. select FB_CFB_IMAGEBLIT
  528. help
  529. This is the frame buffer device driver for SGI Graphics Backend.
  530. This chip is used in SGI O2 and Visual Workstation 320/540.
  531. config FB_GBE_MEM
  532. int "Video memory size in MB"
  533. depends on FB_GBE
  534. default 4
  535. help
  536. This is the amount of memory reserved for the framebuffer,
  537. which can be any value between 1MB and 8MB.
  538. config FB_SBUS
  539. bool "SBUS and UPA framebuffers"
  540. depends on (FB = y) && SPARC
  541. help
  542. Say Y if you want support for SBUS or UPA based frame buffer device.
  543. config FB_BW2
  544. bool "BWtwo support"
  545. depends on (FB = y) && (SPARC && FB_SBUS)
  546. select FB_CFB_FILLRECT
  547. select FB_CFB_COPYAREA
  548. select FB_CFB_IMAGEBLIT
  549. help
  550. This is the frame buffer device driver for the BWtwo frame buffer.
  551. config FB_CG3
  552. bool "CGthree support"
  553. depends on (FB = y) && (SPARC && FB_SBUS)
  554. select FB_CFB_FILLRECT
  555. select FB_CFB_COPYAREA
  556. select FB_CFB_IMAGEBLIT
  557. help
  558. This is the frame buffer device driver for the CGthree frame buffer.
  559. config FB_CG6
  560. bool "CGsix (GX,TurboGX) support"
  561. depends on (FB = y) && (SPARC && FB_SBUS)
  562. select FB_CFB_COPYAREA
  563. select FB_CFB_IMAGEBLIT
  564. help
  565. This is the frame buffer device driver for the CGsix (GX, TurboGX)
  566. frame buffer.
  567. config FB_PVR2
  568. tristate "NEC PowerVR 2 display support"
  569. depends on FB && SH_DREAMCAST
  570. select FB_CFB_FILLRECT
  571. select FB_CFB_COPYAREA
  572. select FB_CFB_IMAGEBLIT
  573. ---help---
  574. Say Y here if you have a PowerVR 2 card in your box. If you plan to
  575. run linux on your Dreamcast, you will have to say Y here.
  576. This driver may or may not work on other PowerVR 2 cards, but is
  577. totally untested. Use at your own risk. If unsure, say N.
  578. To compile this driver as a module, choose M here: the
  579. module will be called pvr2fb.
  580. You can pass several parameters to the driver at boot time or at
  581. module load time. The parameters look like "video=pvr2:XXX", where
  582. the meaning of XXX can be found at the end of the main source file
  583. (<file:drivers/video/pvr2fb.c>). Please see the file
  584. <file:Documentation/fb/pvr2fb.txt>.
  585. config FB_EPSON1355
  586. bool "Epson 1355 framebuffer support"
  587. depends on (FB = y) && (SUPERH || ARCH_CEIVA)
  588. select FB_CFB_FILLRECT
  589. select FB_CFB_COPYAREA
  590. select FB_CFB_IMAGEBLIT
  591. help
  592. Build in support for the SED1355 Epson Research Embedded RAMDAC
  593. LCD/CRT Controller (since redesignated as the S1D13505) as a
  594. framebuffer. Product specs at
  595. <http://www.erd.epson.com/vdc/html/products.htm>.
  596. config FB_S1D13XXX
  597. tristate "Epson S1D13XXX framebuffer support"
  598. depends on FB
  599. select FB_CFB_FILLRECT
  600. select FB_CFB_COPYAREA
  601. select FB_CFB_IMAGEBLIT
  602. help
  603. Support for S1D13XXX framebuffer device family (currently only
  604. working with S1D13806). Product specs at
  605. <http://www.erd.epson.com/vdc/html/legacy_13xxx.htm>
  606. config FB_NVIDIA
  607. tristate "nVidia Framebuffer Support"
  608. depends on FB && PCI
  609. select FB_BACKLIGHT if FB_NVIDIA_BACKLIGHT
  610. select FB_MODE_HELPERS
  611. select FB_CFB_FILLRECT
  612. select FB_CFB_COPYAREA
  613. select FB_CFB_IMAGEBLIT
  614. select BITREVERSE
  615. help
  616. This driver supports graphics boards with the nVidia chips, TNT
  617. and newer. For very old chipsets, such as the RIVA128, then use
  618. the rivafb.
  619. Say Y if you have such a graphics board.
  620. To compile this driver as a module, choose M here: the
  621. module will be called nvidiafb.
  622. config FB_NVIDIA_I2C
  623. bool "Enable DDC Support"
  624. depends on FB_NVIDIA
  625. select FB_DDC
  626. help
  627. This enables I2C support for nVidia Chipsets. This is used
  628. only for getting EDID information from the attached display
  629. allowing for robust video mode handling and switching.
  630. Because fbdev-2.6 requires that drivers must be able to
  631. independently validate video mode parameters, you should say Y
  632. here.
  633. config FB_NVIDIA_BACKLIGHT
  634. bool "Support for backlight control"
  635. depends on FB_NVIDIA
  636. default y
  637. help
  638. Say Y here if you want to control the backlight of your display.
  639. config FB_RIVA
  640. tristate "nVidia Riva support"
  641. depends on FB && PCI
  642. select FB_BACKLIGHT if FB_RIVA_BACKLIGHT
  643. select FB_MODE_HELPERS
  644. select FB_CFB_FILLRECT
  645. select FB_CFB_COPYAREA
  646. select FB_CFB_IMAGEBLIT
  647. select BITREVERSE
  648. help
  649. This driver supports graphics boards with the nVidia Riva/Geforce
  650. chips.
  651. Say Y if you have such a graphics board.
  652. To compile this driver as a module, choose M here: the
  653. module will be called rivafb.
  654. config FB_RIVA_I2C
  655. bool "Enable DDC Support"
  656. depends on FB_RIVA
  657. select FB_DDC
  658. help
  659. This enables I2C support for nVidia Chipsets. This is used
  660. only for getting EDID information from the attached display
  661. allowing for robust video mode handling and switching.
  662. Because fbdev-2.6 requires that drivers must be able to
  663. independently validate video mode parameters, you should say Y
  664. here.
  665. config FB_RIVA_DEBUG
  666. bool "Lots of debug output from Riva(nVidia) driver"
  667. depends on FB_RIVA
  668. default n
  669. help
  670. Say Y here if you want the Riva driver to output all sorts
  671. of debugging information to provide to the maintainer when
  672. something goes wrong.
  673. config FB_RIVA_BACKLIGHT
  674. bool "Support for backlight control"
  675. depends on FB_RIVA
  676. default y
  677. help
  678. Say Y here if you want to control the backlight of your display.
  679. config FB_I810
  680. tristate "Intel 810/815 support (EXPERIMENTAL)"
  681. depends on FB && EXPERIMENTAL && PCI && X86_32
  682. select AGP
  683. select AGP_INTEL
  684. select FB_MODE_HELPERS
  685. select FB_CFB_FILLRECT
  686. select FB_CFB_COPYAREA
  687. select FB_CFB_IMAGEBLIT
  688. help
  689. This driver supports the on-board graphics built in to the Intel 810
  690. and 815 chipsets. Say Y if you have and plan to use such a board.
  691. To compile this driver as a module, choose M here: the
  692. module will be called i810fb.
  693. For more information, please read
  694. <file:Documentation/fb/intel810.txt>
  695. config FB_I810_GTF
  696. bool "use VESA Generalized Timing Formula"
  697. depends on FB_I810
  698. help
  699. If you say Y, then the VESA standard, Generalized Timing Formula
  700. or GTF, will be used to calculate the required video timing values
  701. per video mode. Since the GTF allows nondiscrete timings
  702. (nondiscrete being a range of values as opposed to discrete being a
  703. set of values), you'll be able to use any combination of horizontal
  704. and vertical resolutions, and vertical refresh rates without having
  705. to specify your own timing parameters. This is especially useful
  706. to maximize the performance of an aging display, or if you just
  707. have a display with nonstandard dimensions. A VESA compliant
  708. monitor is recommended, but can still work with non-compliant ones.
  709. If you need or want this, then select this option. The timings may
  710. not be compliant with Intel's recommended values. Use at your own
  711. risk.
  712. If you say N, the driver will revert to discrete video timings
  713. using a set recommended by Intel in their documentation.
  714. If unsure, say N.
  715. config FB_I810_I2C
  716. bool "Enable DDC Support"
  717. depends on FB_I810 && FB_I810_GTF
  718. select FB_DDC
  719. help
  720. config FB_INTEL
  721. tristate "Intel 830M/845G/852GM/855GM/865G/915G/945G support (EXPERIMENTAL)"
  722. depends on FB && EXPERIMENTAL && PCI && X86
  723. select AGP
  724. select AGP_INTEL
  725. select FB_MODE_HELPERS
  726. select FB_CFB_FILLRECT
  727. select FB_CFB_COPYAREA
  728. select FB_CFB_IMAGEBLIT
  729. help
  730. This driver supports the on-board graphics built in to the Intel
  731. 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets.
  732. Say Y if you have and plan to use such a board.
  733. If you say Y here and want DDC/I2C support you must first say Y to
  734. "I2C support" and "I2C bit-banging support" in the character devices
  735. section.
  736. If you say M here then "I2C support" and "I2C bit-banging support"
  737. can be build either as modules or built-in.
  738. To compile this driver as a module, choose M here: the
  739. module will be called intelfb.
  740. For more information, please read <file:Documentation/fb/intelfb.txt>
  741. config FB_INTEL_DEBUG
  742. bool "Intel driver Debug Messages"
  743. depends on FB_INTEL
  744. ---help---
  745. Say Y here if you want the Intel driver to output all sorts
  746. of debugging information to provide to the maintainer when
  747. something goes wrong.
  748. config FB_INTEL_I2C
  749. bool "DDC/I2C for Intel framebuffer support"
  750. depends on FB_INTEL
  751. select FB_DDC
  752. default y
  753. help
  754. Say Y here if you want DDC/I2C support for your on-board Intel graphics.
  755. config FB_MATROX
  756. tristate "Matrox acceleration"
  757. depends on FB && PCI
  758. select FB_CFB_FILLRECT
  759. select FB_CFB_COPYAREA
  760. select FB_CFB_IMAGEBLIT
  761. select FB_TILEBLITTING
  762. select FB_MACMODES if PPC_PMAC
  763. ---help---
  764. Say Y here if you have a Matrox Millennium, Matrox Millennium II,
  765. Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
  766. Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
  767. Matrox G400, G450 or G550 card in your box.
  768. To compile this driver as a module, choose M here: the
  769. module will be called matroxfb.
  770. You can pass several parameters to the driver at boot time or at
  771. module load time. The parameters look like "video=matrox:XXX", and
  772. are described in <file:Documentation/fb/matroxfb.txt>.
  773. config FB_MATROX_MILLENIUM
  774. bool "Millennium I/II support"
  775. depends on FB_MATROX
  776. help
  777. Say Y here if you have a Matrox Millennium or Matrox Millennium II
  778. video card. If you select "Advanced lowlevel driver options" below,
  779. you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
  780. packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
  781. also use font widths different from 8.
  782. config FB_MATROX_MYSTIQUE
  783. bool "Mystique support"
  784. depends on FB_MATROX
  785. help
  786. Say Y here if you have a Matrox Mystique or Matrox Mystique 220
  787. video card. If you select "Advanced lowlevel driver options" below,
  788. you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
  789. packed pixel and 32 bpp packed pixel. You can also use font widths
  790. different from 8.
  791. config FB_MATROX_G
  792. bool "G100/G200/G400/G450/G550 support"
  793. depends on FB_MATROX
  794. ---help---
  795. Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
  796. video card. If you select "Advanced lowlevel driver options", you
  797. should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
  798. pixel and 32 bpp packed pixel. You can also use font widths
  799. different from 8.
  800. If you need support for G400 secondary head, you must first say Y to
  801. "I2C support" in the character devices section, and then to
  802. "Matrox I2C support" and "G400 second head support" here in the
  803. framebuffer section. G450/G550 secondary head and digital output
  804. are supported without additional modules.
  805. The driver starts in monitor mode. You must use the matroxset tool
  806. (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
  807. swap primary and secondary head outputs, or to change output mode.
  808. Secondary head driver always start in 640x480 resolution and you
  809. must use fbset to change it.
  810. Do not forget that second head supports only 16 and 32 bpp
  811. packed pixels, so it is a good idea to compile them into the kernel
  812. too. You can use only some font widths, as the driver uses generic
  813. painting procedures (the secondary head does not use acceleration
  814. engine).
  815. G450/G550 hardware can display TV picture only from secondary CRTC,
  816. and it performs no scaling, so picture must have 525 or 625 lines.
  817. config FB_MATROX_I2C
  818. tristate "Matrox I2C support"
  819. depends on FB_MATROX
  820. select FB_DDC
  821. ---help---
  822. This drivers creates I2C buses which are needed for accessing the
  823. DDC (I2C) bus present on all Matroxes, an I2C bus which
  824. interconnects Matrox optional devices, like MGA-TVO on G200 and
  825. G400, and the secondary head DDC bus, present on G400 only.
  826. You can say Y or M here if you want to experiment with monitor
  827. detection code. You must say Y or M here if you want to use either
  828. second head of G400 or MGA-TVO on G200 or G400.
  829. If you compile it as module, it will create a module named
  830. i2c-matroxfb.
  831. config FB_MATROX_MAVEN
  832. tristate "G400 second head support"
  833. depends on FB_MATROX_G && FB_MATROX_I2C
  834. ---help---
  835. WARNING !!! This support does not work with G450 !!!
  836. Say Y or M here if you want to use a secondary head (meaning two
  837. monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
  838. head is not compatible with accelerated XFree 3.3.x SVGA servers -
  839. secondary head output is blanked while you are in X. With XFree
  840. 3.9.17 preview you can use both heads if you use SVGA over fbdev or
  841. the fbdev driver on first head and the fbdev driver on second head.
  842. If you compile it as module, two modules are created,
  843. matroxfb_crtc2 and matroxfb_maven. Matroxfb_maven is needed for
  844. both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
  845. also load i2c-matroxfb to get it to run.
  846. The driver starts in monitor mode and you must use the matroxset
  847. tool (available at
  848. <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
  849. PAL or NTSC or to swap primary and secondary head outputs.
  850. Secondary head driver also always start in 640x480 resolution, you
  851. must use fbset to change it.
  852. Also do not forget that second head supports only 16 and 32 bpp
  853. packed pixels, so it is a good idea to compile them into the kernel
  854. too. You can use only some font widths, as the driver uses generic
  855. painting procedures (the secondary head does not use acceleration
  856. engine).
  857. config FB_MATROX_MULTIHEAD
  858. bool "Multihead support"
  859. depends on FB_MATROX
  860. ---help---
  861. Say Y here if you have more than one (supported) Matrox device in
  862. your computer and you want to use all of them for different monitors
  863. ("multihead"). If you have only one device, you should say N because
  864. the driver compiled with Y is larger and a bit slower, especially on
  865. ia32 (ix86).
  866. If you said M to "Matrox unified accelerated driver" and N here, you
  867. will still be able to use several Matrox devices simultaneously:
  868. insert several instances of the module matroxfb into the kernel
  869. with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
  870. for the different Matrox devices. This method is slightly faster but
  871. uses 40 KB of kernel memory per Matrox card.
  872. There is no need for enabling 'Matrox multihead support' if you have
  873. only one Matrox card in the box.
  874. config FB_RADEON
  875. tristate "ATI Radeon display support"
  876. depends on FB && PCI
  877. select FB_BACKLIGHT if FB_RADEON_BACKLIGHT
  878. select FB_MODE_HELPERS
  879. select FB_CFB_FILLRECT
  880. select FB_CFB_COPYAREA
  881. select FB_CFB_IMAGEBLIT
  882. select FB_MACMODES if PPC_OF
  883. help
  884. Choose this option if you want to use an ATI Radeon graphics card as
  885. a framebuffer device. There are both PCI and AGP versions. You
  886. don't need to choose this to run the Radeon in plain VGA mode.
  887. If you say Y here and want DDC/I2C support you must first say Y to
  888. "I2C support" and "I2C bit-banging support" in the character devices
  889. section.
  890. If you say M here then "I2C support" and "I2C bit-banging support"
  891. can be build either as modules or built-in.
  892. There is a product page at
  893. http://apps.ati.com/ATIcompare/
  894. config FB_RADEON_I2C
  895. bool "DDC/I2C for ATI Radeon support"
  896. depends on FB_RADEON
  897. select FB_DDC
  898. default y
  899. help
  900. Say Y here if you want DDC/I2C support for your Radeon board.
  901. config FB_RADEON_BACKLIGHT
  902. bool "Support for backlight control"
  903. depends on FB_RADEON
  904. default y
  905. help
  906. Say Y here if you want to control the backlight of your display.
  907. config FB_RADEON_DEBUG
  908. bool "Lots of debug output from Radeon driver"
  909. depends on FB_RADEON
  910. default n
  911. help
  912. Say Y here if you want the Radeon driver to output all sorts
  913. of debugging information to provide to the maintainer when
  914. something goes wrong.
  915. config FB_ATY128
  916. tristate "ATI Rage128 display support"
  917. depends on FB && PCI
  918. select FB_CFB_FILLRECT
  919. select FB_CFB_COPYAREA
  920. select FB_CFB_IMAGEBLIT
  921. select FB_BACKLIGHT if FB_ATY128_BACKLIGHT
  922. select FB_MACMODES if PPC_PMAC
  923. help
  924. This driver supports graphics boards with the ATI Rage128 chips.
  925. Say Y if you have such a graphics board and read
  926. <file:Documentation/fb/aty128fb.txt>.
  927. To compile this driver as a module, choose M here: the
  928. module will be called aty128fb.
  929. config FB_ATY128_BACKLIGHT
  930. bool "Support for backlight control"
  931. depends on FB_ATY128
  932. default y
  933. help
  934. Say Y here if you want to control the backlight of your display.
  935. config FB_ATY
  936. tristate "ATI Mach64 display support" if PCI || ATARI
  937. depends on FB && !SPARC32
  938. select FB_CFB_FILLRECT
  939. select FB_CFB_COPYAREA
  940. select FB_CFB_IMAGEBLIT
  941. select FB_BACKLIGHT if FB_ATY_BACKLIGHT
  942. select FB_MACMODES if PPC
  943. help
  944. This driver supports graphics boards with the ATI Mach64 chips.
  945. Say Y if you have such a graphics board.
  946. To compile this driver as a module, choose M here: the
  947. module will be called atyfb.
  948. config FB_ATY_CT
  949. bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support"
  950. depends on PCI && FB_ATY
  951. default y if SPARC64 && FB_PCI
  952. help
  953. Say Y here to support use of ATI's 64-bit Rage boards (or other
  954. boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
  955. framebuffer device. The ATI product support page for these boards
  956. is at <http://support.ati.com/products/pc/mach64/>.
  957. config FB_ATY_GENERIC_LCD
  958. bool "Mach64 generic LCD support (EXPERIMENTAL)"
  959. depends on FB_ATY_CT
  960. help
  961. Say Y if you have a laptop with an ATI Rage LT PRO, Rage Mobility,
  962. Rage XC, or Rage XL chipset.
  963. config FB_ATY_GX
  964. bool "Mach64 GX support" if PCI
  965. depends on FB_ATY
  966. default y if ATARI
  967. help
  968. Say Y here to support use of the ATI Mach64 Graphics Expression
  969. board (or other boards based on the Mach64 GX chipset) as a
  970. framebuffer device. The ATI product support page for these boards
  971. is at
  972. <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
  973. config FB_ATY_BACKLIGHT
  974. bool "Support for backlight control"
  975. depends on FB_ATY
  976. default y
  977. help
  978. Say Y here if you want to control the backlight of your display.
  979. config FB_S3
  980. tristate "S3 Trio/Virge support"
  981. depends on FB && PCI
  982. select FB_CFB_FILLRECT
  983. select FB_CFB_COPYAREA
  984. select FB_CFB_IMAGEBLIT
  985. select FB_TILEBLITTING
  986. select FB_SVGALIB
  987. ---help---
  988. Driver for graphics boards with S3 Trio / S3 Virge chip.
  989. config FB_SAVAGE
  990. tristate "S3 Savage support"
  991. depends on FB && PCI && EXPERIMENTAL
  992. select FB_MODE_HELPERS
  993. select FB_CFB_FILLRECT
  994. select FB_CFB_COPYAREA
  995. select FB_CFB_IMAGEBLIT
  996. help
  997. This driver supports notebooks and computers with S3 Savage PCI/AGP
  998. chips.
  999. Say Y if you have such a graphics card.
  1000. To compile this driver as a module, choose M here; the module
  1001. will be called savagefb.
  1002. config FB_SAVAGE_I2C
  1003. bool "Enable DDC2 Support"
  1004. depends on FB_SAVAGE
  1005. select FB_DDC
  1006. help
  1007. This enables I2C support for S3 Savage Chipsets. This is used
  1008. only for getting EDID information from the attached display
  1009. allowing for robust video mode handling and switching.
  1010. Because fbdev-2.6 requires that drivers must be able to
  1011. independently validate video mode parameters, you should say Y
  1012. here.
  1013. config FB_SAVAGE_ACCEL
  1014. bool "Enable Console Acceleration"
  1015. depends on FB_SAVAGE
  1016. default n
  1017. help
  1018. This option will compile in console acceleration support. If
  1019. the resulting framebuffer console has bothersome glitches, then
  1020. choose N here.
  1021. config FB_SIS
  1022. tristate "SiS/XGI display support"
  1023. depends on FB && PCI
  1024. select FB_CFB_FILLRECT
  1025. select FB_CFB_COPYAREA
  1026. select FB_CFB_IMAGEBLIT
  1027. help
  1028. This is the frame buffer device driver for the SiS 300, 315, 330
  1029. and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
  1030. Specs available at <http://www.sis.com> and <http://www.xgitech.com>.
  1031. To compile this driver as a module, choose M here; the module
  1032. will be called sisfb.
  1033. config FB_SIS_300
  1034. bool "SiS 300 series support"
  1035. depends on FB_SIS
  1036. help
  1037. Say Y here to support use of the SiS 300/305, 540, 630 and 730.
  1038. config FB_SIS_315
  1039. bool "SiS 315/330/340 series and XGI support"
  1040. depends on FB_SIS
  1041. help
  1042. Say Y here to support use of the SiS 315, 330 and 340 series
  1043. (315/H/PRO, 55x, 650, 651, 740, 330, 661, 741, 760, 761) as well
  1044. as XGI V3XT, V5, V8 and Z7.
  1045. config FB_NEOMAGIC
  1046. tristate "NeoMagic display support"
  1047. depends on FB && PCI
  1048. select FB_MODE_HELPERS
  1049. select FB_CFB_FILLRECT
  1050. select FB_CFB_COPYAREA
  1051. select FB_CFB_IMAGEBLIT
  1052. help
  1053. This driver supports notebooks with NeoMagic PCI chips.
  1054. Say Y if you have such a graphics card.
  1055. To compile this driver as a module, choose M here: the
  1056. module will be called neofb.
  1057. config FB_KYRO
  1058. tristate "IMG Kyro support"
  1059. depends on FB && PCI
  1060. select FB_CFB_FILLRECT
  1061. select FB_CFB_COPYAREA
  1062. select FB_CFB_IMAGEBLIT
  1063. help
  1064. Say Y here if you have a STG4000 / Kyro / PowerVR 3 based
  1065. graphics board.
  1066. To compile this driver as a module, choose M here: the
  1067. module will be called kyrofb.
  1068. config FB_3DFX
  1069. tristate "3Dfx Banshee/Voodoo3 display support"
  1070. depends on FB && PCI
  1071. select FB_CFB_IMAGEBLIT
  1072. select FB_CFB_FILLRECT
  1073. select FB_CFB_COPYAREA
  1074. help
  1075. This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
  1076. chips. Say Y if you have such a graphics board.
  1077. To compile this driver as a module, choose M here: the
  1078. module will be called tdfxfb.
  1079. config FB_3DFX_ACCEL
  1080. bool "3Dfx Banshee/Voodoo3 Acceleration functions (EXPERIMENTAL)"
  1081. depends on FB_3DFX && EXPERIMENTAL
  1082. ---help---
  1083. This will compile the 3Dfx Banshee/Voodoo3 frame buffer device
  1084. with acceleration functions.
  1085. config FB_VOODOO1
  1086. tristate "3Dfx Voodoo Graphics (sst1) support"
  1087. depends on FB && PCI
  1088. select FB_CFB_FILLRECT
  1089. select FB_CFB_COPYAREA
  1090. select FB_CFB_IMAGEBLIT
  1091. ---help---
  1092. Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
  1093. Voodoo2 (cvg) based graphics card.
  1094. To compile this driver as a module, choose M here: the
  1095. module will be called sstfb.
  1096. WARNING: Do not use any application that uses the 3D engine
  1097. (namely glide) while using this driver.
  1098. Please read the <file:Documentation/fb/README-sstfb.txt> for supported
  1099. options and other important info support.
  1100. config FB_CYBLA
  1101. tristate "Cyberblade/i1 support"
  1102. depends on FB && PCI && X86_32 && !64BIT
  1103. select FB_CFB_IMAGEBLIT
  1104. select VIDEO_SELECT
  1105. ---help---
  1106. This driver is supposed to support the Trident Cyberblade/i1
  1107. graphics core integrated in the VIA VT8601A North Bridge,
  1108. also known as VIA Apollo PLE133.
  1109. Status:
  1110. - Developed, tested and working on EPIA 5000 and EPIA 800.
  1111. - Does work reliable on all systems with CRT/LCD connected to
  1112. normal VGA ports.
  1113. - Should work on systems that do use the internal LCD port, but
  1114. this is absolutely not tested.
  1115. Character imageblit, copyarea and rectangle fill are hw accelerated,
  1116. ypan scrolling is used by default.
  1117. Please do read <file:Documentation/fb/cyblafb/*>.
  1118. To compile this driver as a module, choose M here: the
  1119. module will be called cyblafb.
  1120. config FB_TRIDENT
  1121. tristate "Trident support"
  1122. depends on FB && PCI
  1123. select FB_CFB_FILLRECT
  1124. select FB_CFB_COPYAREA
  1125. select FB_CFB_IMAGEBLIT
  1126. ---help---
  1127. This driver is supposed to support graphics boards with the
  1128. Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
  1129. but also on some motherboards. For more information, read
  1130. <file:Documentation/fb/tridentfb.txt>
  1131. Cyberblade/i1 support will be removed soon, use the cyblafb driver
  1132. instead.
  1133. Say Y if you have such a graphics board.
  1134. To compile this driver as a module, choose M here: the
  1135. module will be called tridentfb.
  1136. config FB_TRIDENT_ACCEL
  1137. bool "Trident Acceleration functions (EXPERIMENTAL)"
  1138. depends on FB_TRIDENT && EXPERIMENTAL
  1139. ---help---
  1140. This will compile the Trident frame buffer device with
  1141. acceleration functions.
  1142. config FB_PM3
  1143. tristate "Permedia3 support"
  1144. depends on FB && PCI && BROKEN
  1145. help
  1146. This is the frame buffer device driver for the 3DLabs Permedia3
  1147. chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
  1148. similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
  1149. and maybe other boards.
  1150. config FB_AU1100
  1151. bool "Au1100 LCD Driver"
  1152. depends on (FB = y) && EXPERIMENTAL && PCI && MIPS && MIPS_PB1100=y
  1153. config FB_AU1200
  1154. bool "Au1200 LCD Driver"
  1155. depends on (FB = y) && MIPS && SOC_AU1200
  1156. select FB_CFB_FILLRECT
  1157. select FB_CFB_COPYAREA
  1158. select FB_CFB_IMAGEBLIT
  1159. help
  1160. This is the framebuffer driver for the AMD Au1200 SOC. It can drive
  1161. various panels and CRTs by passing in kernel cmd line option
  1162. au1200fb:panel=<name>.
  1163. source "drivers/video/geode/Kconfig"
  1164. config FB_FFB
  1165. bool "Creator/Creator3D/Elite3D support"
  1166. depends on FB_SBUS && SPARC64
  1167. select FB_CFB_COPYAREA
  1168. select FB_CFB_IMAGEBLIT
  1169. help
  1170. This is the frame buffer device driver for the Creator, Creator3D,
  1171. and Elite3D graphics boards.
  1172. config FB_TCX
  1173. bool "TCX (SS4/SS5 only) support"
  1174. depends on FB_SBUS
  1175. select FB_CFB_FILLRECT
  1176. select FB_CFB_COPYAREA
  1177. select FB_CFB_IMAGEBLIT
  1178. help
  1179. This is the frame buffer device driver for the TCX 24/8bit frame
  1180. buffer.
  1181. config FB_CG14
  1182. bool "CGfourteen (SX) support"
  1183. depends on FB_SBUS
  1184. select FB_CFB_FILLRECT
  1185. select FB_CFB_COPYAREA
  1186. select FB_CFB_IMAGEBLIT
  1187. help
  1188. This is the frame buffer device driver for the CGfourteen frame
  1189. buffer on Desktop SPARCsystems with the SX graphics option.
  1190. config FB_P9100
  1191. bool "P9100 (Sparcbook 3 only) support"
  1192. depends on FB_SBUS
  1193. select FB_CFB_FILLRECT
  1194. select FB_CFB_COPYAREA
  1195. select FB_CFB_IMAGEBLIT
  1196. help
  1197. This is the frame buffer device driver for the P9100 card
  1198. supported on Sparcbook 3 machines.
  1199. config FB_LEO
  1200. bool "Leo (ZX) support"
  1201. depends on FB_SBUS
  1202. select FB_CFB_FILLRECT
  1203. select FB_CFB_COPYAREA
  1204. select FB_CFB_IMAGEBLIT
  1205. help
  1206. This is the frame buffer device driver for the SBUS-based Sun ZX
  1207. (leo) frame buffer cards.
  1208. config FB_XVR500
  1209. bool "Sun XVR-500 3DLABS Wildcat support"
  1210. depends on FB && PCI && SPARC64
  1211. select FB_CFB_FILLRECT
  1212. select FB_CFB_COPYAREA
  1213. select FB_CFB_IMAGEBLIT
  1214. help
  1215. This is the framebuffer device for the Sun XVR-500 and similar
  1216. graphics cards based upon the 3DLABS Wildcat chipset. The driver
  1217. only works on sparc64 systems where the system firwmare has
  1218. mostly initialized the card already. It is treated as a
  1219. completely dumb framebuffer device.
  1220. config FB_XVR2500
  1221. bool "Sun XVR-2500 3DLABS Wildcat support"
  1222. depends on FB && PCI && SPARC64
  1223. select FB_CFB_FILLRECT
  1224. select FB_CFB_COPYAREA
  1225. select FB_CFB_IMAGEBLIT
  1226. help
  1227. This is the framebuffer device for the Sun XVR-2500 and similar
  1228. graphics cards based upon the 3DLABS Wildcat chipset. The driver
  1229. only works on sparc64 systems where the system firwmare has
  1230. mostly initialized the card already. It is treated as a
  1231. completely dumb framebuffer device.
  1232. config FB_PCI
  1233. bool "PCI framebuffers"
  1234. depends on (FB = y) && PCI && SPARC
  1235. config FB_IGA
  1236. bool "IGA 168x display support"
  1237. depends on SPARC32 && FB_PCI
  1238. select FB_CFB_FILLRECT
  1239. select FB_CFB_COPYAREA
  1240. select FB_CFB_IMAGEBLIT
  1241. help
  1242. This is the framebuffer device for the INTERGRAPHICS 1680 and
  1243. successor frame buffer cards.
  1244. config FB_HIT
  1245. tristate "HD64461 Frame Buffer support"
  1246. depends on FB && HD64461
  1247. select FB_CFB_FILLRECT
  1248. select FB_CFB_COPYAREA
  1249. select FB_CFB_IMAGEBLIT
  1250. help
  1251. This is the frame buffer device driver for the Hitachi HD64461 LCD
  1252. frame buffer card.
  1253. config FB_PMAG_AA
  1254. bool "PMAG-AA TURBOchannel framebuffer support"
  1255. depends on (FB = y) && TC
  1256. select FB_CFB_FILLRECT
  1257. select FB_CFB_COPYAREA
  1258. select FB_CFB_IMAGEBLIT
  1259. help
  1260. Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
  1261. used mainly in the MIPS-based DECstation series.
  1262. config FB_PMAG_BA
  1263. tristate "PMAG-BA TURBOchannel framebuffer support"
  1264. depends on FB && TC
  1265. select FB_CFB_FILLRECT
  1266. select FB_CFB_COPYAREA
  1267. select FB_CFB_IMAGEBLIT
  1268. help
  1269. Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
  1270. used mainly in the MIPS-based DECstation series.
  1271. config FB_PMAGB_B
  1272. tristate "PMAGB-B TURBOchannel framebuffer support"
  1273. depends on TC
  1274. select FB_CFB_FILLRECT
  1275. select FB_CFB_COPYAREA
  1276. select FB_CFB_IMAGEBLIT
  1277. help
  1278. Support for the PMAGB-B TURBOchannel framebuffer card used mainly
  1279. in the MIPS-based DECstation series. The card is currently only
  1280. supported in 1280x1024x8 mode.
  1281. config FB_MAXINE
  1282. bool "Maxine (Personal DECstation) onboard framebuffer support"
  1283. depends on (FB = y) && MACH_DECSTATION
  1284. select FB_CFB_FILLRECT
  1285. select FB_CFB_COPYAREA
  1286. select FB_CFB_IMAGEBLIT
  1287. help
  1288. Support for the onboard framebuffer (1024x768x8) in the Personal
  1289. DECstation series (Personal DECstation 5000/20, /25, /33, /50,
  1290. Codename "Maxine").
  1291. config FB_TX3912
  1292. bool "TMPTX3912/PR31700 frame buffer support"
  1293. depends on (FB = y) && NINO
  1294. select FB_CFB_FILLRECT
  1295. select FB_CFB_COPYAREA
  1296. select FB_CFB_IMAGEBLIT
  1297. help
  1298. The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
  1299. see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
  1300. Say Y here to enable kernel support for the on-board framebuffer.
  1301. config FB_G364
  1302. bool "G364 frame buffer support"
  1303. depends on (FB = y) && (MIPS_MAGNUM_4000 || OLIVETTI_M700)
  1304. select FB_CFB_FILLRECT
  1305. select FB_CFB_COPYAREA
  1306. select FB_CFB_IMAGEBLIT
  1307. help
  1308. The G364 driver is the framebuffer used in MIPS Magnum 4000 and
  1309. Olivetti M700-10 systems.
  1310. config FB_68328
  1311. bool "Motorola 68328 native frame buffer support"
  1312. depends on (FB = y) && (M68328 || M68EZ328 || M68VZ328)
  1313. select FB_CFB_FILLRECT
  1314. select FB_CFB_COPYAREA
  1315. select FB_CFB_IMAGEBLIT
  1316. help
  1317. Say Y here if you want to support the built-in frame buffer of
  1318. the Motorola 68328 CPU family.
  1319. config FB_PXA
  1320. tristate "PXA LCD framebuffer support"
  1321. depends on FB && ARCH_PXA
  1322. select FB_CFB_FILLRECT
  1323. select FB_CFB_COPYAREA
  1324. select FB_CFB_IMAGEBLIT
  1325. ---help---
  1326. Frame buffer driver for the built-in LCD controller in the Intel
  1327. PXA2x0 processor.
  1328. This driver is also available as a module ( = code which can be
  1329. inserted and removed from the running kernel whenever you want). The
  1330. module will be called pxafb. If you want to compile it as a module,
  1331. say M here and read <file:Documentation/kbuild/modules.txt>.
  1332. If unsure, say N.
  1333. config FB_PXA_PARAMETERS
  1334. bool "PXA LCD command line parameters"
  1335. default n
  1336. depends on FB_PXA
  1337. ---help---
  1338. Enable the use of kernel command line or module parameters
  1339. to configure the physical properties of the LCD panel when
  1340. using the PXA LCD driver.
  1341. This option allows you to override the panel parameters
  1342. supplied by the platform in order to support multiple
  1343. different models of flatpanel. If you will only be using a
  1344. single model of flatpanel then you can safely leave this
  1345. option disabled.
  1346. <file:Documentation/fb/pxafb.txt> describes the available parameters.
  1347. config FB_MBX
  1348. tristate "2700G LCD framebuffer support"
  1349. depends on FB && ARCH_PXA
  1350. select FB_CFB_FILLRECT
  1351. select FB_CFB_COPYAREA
  1352. select FB_CFB_IMAGEBLIT
  1353. ---help---
  1354. Framebuffer driver for the Intel 2700G (Marathon) Graphics
  1355. Accelerator
  1356. config FB_MBX_DEBUG
  1357. bool "Enable debugging info via debugfs"
  1358. depends on FB_MBX && DEBUG_FS
  1359. default n
  1360. ---help---
  1361. Enable this if you want debugging information using the debug
  1362. filesystem (debugfs)
  1363. If unsure, say N.
  1364. config FB_W100
  1365. tristate "W100 frame buffer support"
  1366. depends on FB && PXA_SHARPSL
  1367. select FB_CFB_FILLRECT
  1368. select FB_CFB_COPYAREA
  1369. select FB_CFB_IMAGEBLIT
  1370. ---help---
  1371. Frame buffer driver for the w100 as found on the Sharp SL-Cxx series.
  1372. This driver is also available as a module ( = code which can be
  1373. inserted and removed from the running kernel whenever you want). The
  1374. module will be called w100fb. If you want to compile it as a module,
  1375. say M here and read <file:Documentation/kbuild/modules.txt>.
  1376. If unsure, say N.
  1377. config FB_S3C2410
  1378. tristate "S3C2410 LCD framebuffer support"
  1379. depends on FB && ARCH_S3C2410
  1380. select FB_CFB_FILLRECT
  1381. select FB_CFB_COPYAREA
  1382. select FB_CFB_IMAGEBLIT
  1383. ---help---
  1384. Frame buffer driver for the built-in LCD controller in the Samsung
  1385. S3C2410 processor.
  1386. This driver is also available as a module ( = code which can be
  1387. inserted and removed from the running kernel whenever you want). The
  1388. module will be called s3c2410fb. If you want to compile it as a module,
  1389. say M here and read <file:Documentation/kbuild/modules.txt>.
  1390. If unsure, say N.
  1391. config FB_S3C2410_DEBUG
  1392. bool "S3C2410 lcd debug messages"
  1393. depends on FB_S3C2410
  1394. help
  1395. Turn on debugging messages. Note that you can set/unset at run time
  1396. through sysfs
  1397. config FB_SM501
  1398. tristate "Silicon Motion SM501 framebuffer support"
  1399. depends on FB && MFD_SM501
  1400. select FB_CFB_FILLRECT
  1401. select FB_CFB_COPYAREA
  1402. select FB_CFB_IMAGEBLIT
  1403. ---help---
  1404. Frame buffer driver for the CRT and LCD controllers in the Silicon
  1405. Motion SM501.
  1406. This driver is also available as a module ( = code which can be
  1407. inserted and removed from the running kernel whenever you want). The
  1408. module will be called sm501fb. If you want to compile it as a module,
  1409. say M here and read <file:Documentation/modules.txt>.
  1410. If unsure, say N.
  1411. config FB_PNX4008_DUM
  1412. tristate "Display Update Module support on Philips PNX4008 board"
  1413. depends on FB && ARCH_PNX4008
  1414. ---help---
  1415. Say Y here to enable support for PNX4008 Display Update Module (DUM)
  1416. config FB_PNX4008_DUM_RGB
  1417. tristate "RGB Framebuffer support on Philips PNX4008 board"
  1418. depends on FB_PNX4008_DUM
  1419. select FB_CFB_FILLRECT
  1420. select FB_CFB_COPYAREA
  1421. select FB_CFB_IMAGEBLIT
  1422. ---help---
  1423. Say Y here to enable support for PNX4008 RGB Framebuffer
  1424. config FB_IBM_GXT4500
  1425. tristate "Framebuffer support for IBM GXT4500P adaptor"
  1426. depends on PPC
  1427. select FB_CFB_FILLRECT
  1428. select FB_CFB_COPYAREA
  1429. select FB_CFB_IMAGEBLIT
  1430. ---help---
  1431. Say Y here to enable support for the IBM GXT4500P display
  1432. adaptor, found on some IBM System P (pSeries) machines.
  1433. config FB_PS3
  1434. bool "PS3 GPU framebuffer driver"
  1435. depends on (FB = y) && PS3_PS3AV
  1436. select FB_CFB_FILLRECT
  1437. select FB_CFB_COPYAREA
  1438. select FB_CFB_IMAGEBLIT
  1439. ---help---
  1440. Include support for the virtual frame buffer in the PS3 platform.
  1441. config FB_PS3_DEFAULT_SIZE_M
  1442. int "PS3 default frame buffer size (in MiB)"
  1443. depends on FB_PS3
  1444. default 18
  1445. ---help---
  1446. This is the default size (in MiB) of the virtual frame buffer in
  1447. the PS3.
  1448. The default value can be overridden on the kernel command line
  1449. using the "ps3fb" option (e.g. "ps3fb=9M");
  1450. config FB_VIRTUAL
  1451. tristate "Virtual Frame Buffer support (ONLY FOR TESTING!)"
  1452. depends on FB
  1453. select FB_CFB_FILLRECT
  1454. select FB_CFB_COPYAREA
  1455. select FB_CFB_IMAGEBLIT
  1456. ---help---
  1457. This is a `virtual' frame buffer device. It operates on a chunk of
  1458. unswappable kernel memory instead of on the memory of a graphics
  1459. board. This means you cannot see any output sent to this frame
  1460. buffer device, while it does consume precious memory. The main use
  1461. of this frame buffer device is testing and debugging the frame
  1462. buffer subsystem. Do NOT enable it for normal systems! To protect
  1463. the innocent, it has to be enabled explicitly at boot time using the
  1464. kernel option `video=vfb:'.
  1465. To compile this driver as a module, choose M here: the
  1466. module will be called vfb. In order to load it, you must use
  1467. the vfb_enable=1 option.
  1468. If unsure, say N.
  1469. if VT
  1470. source "drivers/video/console/Kconfig"
  1471. endif
  1472. if FB || SGI_NEWPORT_CONSOLE
  1473. source "drivers/video/logo/Kconfig"
  1474. endif
  1475. endmenu