Kconfig 46 KB

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