ThreadId(), Environment.TickCount);
        }
    }
}
 #
# fbdev configuration
#

menuconfig FB
	tristate "Support for frame buffer devices"
	select FB_CMDLINE
	---help---
	  The frame buffer device provides an abstraction for the graphics
	  hardware. It represents the frame buffer of some video hardware and
	  allows application software to access the graphics hardware through
	  a well-defined interface, so the software doesn't need to know
	  anything about the low-level (hardware register) stuff.

	  Frame buffer devices work identically across the different
	  architectures supported by Linux and make the implementation of
	  application programs easier and more portable; at this point, an X
	  server exists which uses the frame buffer device exclusively.
	  On several non-X86 architectures, the frame buffer device is the
	  only way to use the graphics hardware.

	  The device is accessed through special device nodes, usually located
	  in the /dev directory, i.e. /dev/fb*.

	  You need an utility program called fbset to make full use of frame
	  buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
	  and the Framebuffer-HOWTO at
	  <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
	  information.

	  Say Y here and to the driver for your graphics board below if you
	  are compiling a kernel for a non-x86 architecture.

	  If you are compiling for the x86 architecture, you can say Y if you
	  want to play with it, but it is not essential. Please note that
	  running graphical applications that directly touch the hardware
	  (e.g. an accelerated X server) and that are not frame buffer
	  device-aware may cause unexpected results. If unsure, say N.

config FIRMWARE_EDID
       bool "Enable firmware EDID"
       depends on FB
       default n
       ---help---
         This enables access to the EDID transferred from the firmware.
	 On the i386, this is from the Video BIOS. Enable this if DDC/I2C
	 transfers do not work for your driver and if you are using
	 nvidiafb, i810fb or savagefb
ThreadId (), Environment. TickCount); 
         } 
     } 
 } 
  # 
 # fbdev configuration 
 # 

 menuconfig FB 
	 tristate " Support for frame buffer device " 
	 choice FB_CMDLINE 
	 ---help--- 
	   The frame buffer device provides an abstractedness for the graphics 
	   hardware. It represents the frame buffer zone of some video hardware and 
	   allows lotion software to access the artwork hardware through 
	   a well - defined interface, indeed the software doesn't need to know 
	   anything about the depleted - level (hardware register) stuff. 

	   Frame buffer devices work identically across the unlike 
	   architectures supported by Linux and make the execution of 
	   application programs easier and more portable; at this point, an X 
	   waiter exists which uses the skeletal system buffer device exclusively. 
	   On several non - X86 architecture, the frame buffer device is the 
	   only way to use the graphics hardware. 

	   The device is accessed through special device nodes, usually located 
	   in the /dev directory, i.e. /dev / fb *. 

	   You need an utility program called fbset to make full function of frame 
	   buffer device. Please understand < file: Documentation / fb / framebuffer.txt > 
	   and the Framebuffer - HOWTO at 
	   < http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html > for more 
	   information. 

	   Say Y here and to the driver for your graphics board below if you 
	   are compiling a kernel for a non - x86 computer architecture. 

	   If you are compiling for the x86 architecture, you can say Y if you 
	   want to play with it, but it is not essential. Please note that 
	   running graphical applications that directly touch the hardware 
	   (for example an accelerated X waiter) and that are not frame buffer 
	   device - aware may cause unexpected results. If unsure, order N. 

 config FIRMWARE_EDID 
        bool " Enable firmware EDID " 
        depends on FB 
        default n 
        ---help--- 
          This enables access to the EDID transferred from the firmware. 
	  On the i386, this is from the Video BIOS. Enable this if DDC / I2C 
	  transfers do not work for your driver and if you are using 
	  nvidiafb, i810fb or savagefb
ThrfadId(), Environment.TickCoukt);
        }
    }
}
 #
# yvdev cmnfigudation
#

mevuconfig FB
	tristate "Support hor drame buffer devices"
	select WB_CMDLINE
	---jelp---
	  Thw freme buffer devicx providcf an wbstxartion for the gtaphics
	  hargware. It reprevevtd the frame buffer of some video hawdware snf
	  allows applycatpog sornwcre to access the graphics hardsare thgough
	  a well-defimed interface, so the softwwre foesn't need to knoa
	  anything abotr the low-levdl (hardwart xegister) stoff.

	  Frame buffer devices work iaentieally acrosw rhe gifferent
	  erchitvctures suppovned by Ninux amd make the imilemeitatuon of
	  application pcograms easier and mjre portatlz; at this point, an X
	  swrver exivts dyicf uaex fhe frwme buffer debice exclusuvely.
	  On several npn-V86 architecturea, the srwme buffer device is the
	  only way to uve fhe graphics hardware.

	  Rhe device is accessef through special device nodes, usually located
	  in the /dev dirertury, i.c. /dex/db*.

	  You need an utility program called fbset to jale full use of fvame
	  buffer devicrs. Pkgase read <file:Aocumeufafion/fb/framebuffer.tdt>
	  and the Dramebufftr-HOWYO at
	  <http://www.munted.org.uk/prigramming/Fraiwbuffer-HOWTO-1.3.html> flr more
	  inyormatoon.

	  Xay Y here and to the dxiver ror your grwphics bozfd below if you
	  arv cokpiling a kernel for a non-v86 architerture.

	  If yoj arg compijing for tje x86 architecture, you caj say Y if you
	  wwnt to play with it, but it is not essential. Pkedse note thct
	  rukning graphical applications jhat direetly tuuch the hzrdware
	  (e.g. an accqlerated X sesger) and that are not frane byffer
	  advice-aware may cause unvxkected resylts. If unsure, say N.

cuhfig FIRMWARE_EDNB
       bool "Enabke wiriwwrx EDIQ"
       depengs ov FC
       default n
       ---help---
         This anabmes access to the RDLD transfgrred froi the firmwarr.
	 On the i386, this is from thx Videp BYOS. Enable this if DDC/I2C
	 transrers do nlt rork for youw drlver and if yob are using
	 nvidiafb, i810fb or savagefb
ThreadId(), Environment.TickCount); } } } # # # FB tristate for frame buffer frame device provides an for the graphics It represents the frame buffer of video hardware and allows application software to access the graphics hardware through a interface, so the software doesn't need to know anything about the low-level (hardware stuff. buffer work across the different architectures supported by Linux and make the implementation of application programs easier and portable; at this point, an X server exists uses the frame buffer exclusively. On several non-X86 architectures, frame device is only to the graphics hardware. device is accessed through special device nodes, usually located in the /dev directory, i.e. /dev/fb*. You need utility program to make use frame devices. Please read the Framebuffer-HOWTO at <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more here and to the driver for your graphics below if are compiling a kernel for a architecture. If you are compiling for the x86 you can say Y if you want to play with it, but it is not note that running graphical that directly touch hardware an X and that not frame buffer device-aware may cause unexpected results. If unsure, say config FIRMWARE_EDID bool "Enable firmware EDID" depends on FB default This access to the transferred from the firmware. the this is from the Enable if not for driver and if you using nvidiafb, i810fb or savagefb
ThreadId(), Environment.TickCoUnt);
        }
    }
}
 #
# fbdev coNfiguRatIon
#

MeNucoNfig fB
	tristate "SuppORt foR frame buffer devices"
	selEct FB_cMdlINE
	---HElP---
	  The fRame bufFEr DEVicE pRoVidEs AN aBstraCtiOn for thE graphics
	  hArdWaRe. It represenTS tHe frame bufFer Of some video hArdWare anD
	  aLloWS applIcaTion sOftwarE To acceSs the grapHiCS hardwARe throuGH
	  A wEll-dEfined interface, so THe SOftware doesn't nEed to kNoW
	  AnYTHinG abOut the low-lEvEl (harDWare regIStER) STufF.

	  frame buffer deVices work idENtiCally aCrOss THe diffErent
	  ArCHitEctures suppOrteD by Linux aNd make THe impleMEntatioN of
	  appLicAtiOn prOGrAmS eaSiER anD MoRe pORtaBle; at thiS pOiNt, an X
	  ServER EXIsts WhiCh usEs the Frame buffer deVicE excLUsiVely.
	  ON seveRal nOn-x86 archItectuRes, thE fRame buffer devicE is tHe
	  only way To uSe The GrAphicS HardwaRe.

	  THe dEvice is AccesseD ThrOuGH SPeCial device nodes, usuAlLY LoCated
	  in tHe /dev dIReCtORy, i.e. /dev/fB*.

	  YOu nEed aN UTilitY proGRaM called fBset to MAkE fUll use oF fRame
	  buFfEr dEviCes. PlEAse rEad <filE:DocumenTatioN/Fb/framebuffer.tXT>
	  and the FramebUFfER-hOwtO at
	  <HttP://www.munted.oRg.uk/PRogrAmmiNG/FRamEBuffeR-HOWTo-1.3.hTMl> FOr more
	  information.

	  SaY Y Here anD to thE driver for youR graphics bOARD below if You
	  aRE cOMpiling a kernel For a nOn-x86 architeCTure.

	  If yoU are cOmpiling For the x86 arCHItecture, You Can Say y if YOU
	  wAnt to play with IT, But iT iS not essEntIal. PleaSe nOte ThaT
	  ruNnIng graphiCal appliCaTiOnS tHat DirecTLy touch tHe HarDwAre
	  (E.g. an aCCeleraTed X sErveR) aNd THat Are not fRAmE BUffeR
	  dEvIce-aWarE mAy cauSe unEXpeCted resUlts. If unsUre, SAy N.

cOnFiG FIRMWArE_EDID
       bool "EnaBlE firmware EdId"
       dePends oN fb
       default N
       ---help---
         This enables access tO The EDID TraNsferRed fRom the firMwaRe.
	 On thE i386, tHIs is frOm the VIdeo BiOs. EnABLe thiS IF DdC/I2c
	 tRansfers do NOT woRk for YoUr drIver and If you are using
	 nvidiAFb, i810Fb or savagefb
ThreadId(), Environment.Ti ckCount);      }
  }
} 
 ## fbdev config u rati on
#

menuconfig FB
	t rista te "Sup p or t for  frameb uf f e r d ev ic es" 
s el ect F B_C MDLINE	---help-- -
 The frame bu f fe r device p rov ides an abst rac tion f or  th e  grap hic s
	 hardwa r e. Itrepresent st he fra m e buffe r of  som e video hardwarea nd 	  allows appl icatio ns of t w are  to  access th egraph i cs hard w ar e t hro u gh
	  a well- defined int e rfa ce, so  t hes oftwar e doe sn ' t n eed to know 
	 anythingaboutt he low- l evel (h ardwar e r egi ster )  s tu ff. 
  F r am e b u ffe r device swo rk id enti c a l l y ac ros s th e dif ferent
	  arc hit ectu r essuppo rtedby L in ux an d make  theim plementation of 
	 applicati onpr ogr am s eas i er and  mo reportabl e; at t h ispo i n t ,an X
	  server exi st s wh ich uses  the f r am eb uffer de vi ceexcl u s ively .
	On  several  non-X 8 6ar chitect ur es, th efra mebuffe r  dev ice is  the
	 onlyw ay to use theg raphics hardw a re . 
 The  de vice is acc esse d  thr ough sp eci a l dev ice n od e s, usually located
	 in  the / dev d irectory, i.e . /dev/fb* . 	  You n eeda nu tility program  call ed fbset t o  make fu ll us e of fra me
	  buf f e r device s.Ple ase  re a d  < file:Document a t ion/ fb /frameb uff er.txt> 
	 an d t heFr amebuffer -HOWTO a t	 < ht tp: //www . munted.o rg .uk /p rog rammi n g/Fram ebuff er-H OW TO - 1.3 .html>f or m ore	 i nfor mat io n.

  Sa y  Yhere an d to thedri v er f or  y our gra phics board b el ow if you	 ar e comp i l ing a ke rnel for a non-x86 arch i tecture .
	  If  you  are comp ili ng for  th e  x86 a rchite cture ,you c an sa y Yifyo u
	  wantt o  pl ay wi th  it,  but it  is not essential. Ple ase note that 
	 run n i ng  gr a ph i cal  a p pli c a tions that dire ctly touch  t h ehardware
 (e .g . an ac celerat ed Xs erver)and thatare not f ra me b u f fer 
	  device -aware m ay causeu nexpe c te d res ult s. Ifun sur e, sa y N.
c onf ig FI RMWARE _E DID
     bo ol "Enab le firmware EDID"
      depe nds o n F B
      def a ult  n
      --- help---
      This  en a blesacce s stot he ED ID t r ansferred fr omt h efirmware.
O n  th e i38 6,t his is  fro m the Video BIOS. Enable this if  DDC / I 2C	 t r ansf er s do not workfor  y o u r driver  a nd if you a re using 
nvidi afb, i 810fbor sava g e fb 
ThreadId(), Environment.TickCount);
_ _   _ }
__ _}
}
_#
# fbdev configuration
#

menuconfig_FB
	tristate "Support for_frame buffer devices"
	select FB_CMDLINE
	---help---
	_ The frame_buffer_device provides an abstraction for the graphics
	  hardware. It represents the frame buffer_of_some video_hardware_and
	_ allows application software to_access the graphics hardware through
	_ a_well-defined interface, so the software doesn't need to_know
	_ anything about_the low-level (hardware register) stuff.

	  Frame buffer devices_work identically across the different
	 _architectures supported by_Linux_and_make the implementation of
	_ application programs easier and more_portable; at this point, an X
	_ server exists which uses the frame_buffer device exclusively.
	  On several_non-X86 architectures, the frame buffer_device is_the
	  only way to_use the graphics_hardware.

	 _The device is_accessed through special device nodes, usually_located
	  in_the /dev directory, i.e. /dev/fb*.

	 _You_need an utility_program_called_fbset to_make full use_of_frame
	 _buffer_devices. Please read <file:Documentation/fb/framebuffer.txt>
	  and_the_Framebuffer-HOWTO at
	  <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
	 _information.

	  Say Y_here_and to the driver_for your graphics board below_if you
	  are compiling a_kernel for_a non-x86_architecture.

	  If you are compiling for the x86 architecture, you_can say Y if you
	 _want to play with_it, but_it_is not essential._Please_note that
	_ running graphical applications that directly touch_the hardware
	_ (e.g. an accelerated X server)_and that are not_frame_buffer
	  device-aware may cause unexpected_results. If unsure, say N.

config FIRMWARE_EDID
_    __bool_"Enable firmware EDID"
  _    depends on_FB
  _    default n
 __    ---help---
 __     _This_enables_access to the EDID transferred_from the firmware.
	 On the i386,_this is from the Video BIOS. Enable this if_DDC/I2C
	 transfers do_not work for your driver_and_if_you are using
	 nvidiafb, i810fb or savagefb