⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 kconfig

📁 基于ti公司davinci系统的视频preview引擎驱动
💻
📖 第 1 页 / 共 3 页
字号:
	  "Symmetric Multi Processing" above, you should say Y here to read	  and set the RTC in an SMP compatible fashion.	  If you think you have a use for such a device (such as periodic data	  sampling), then say Y here, and read <file:Documentation/rtc.txt>	  for details.	  To compile this driver as a module, choose M here: the	  module will be called rtc.config RTC_HISTOGRAM	tristate "Real Time Clock Histogram Support"	depends on RTC	---help---	  If you say Y here then the kernel will track the delivery and	  wakeup latency of /dev/rtc using tasks and will report a	  histogram to the kernel log when the application closes /dev/rtc.config BLOCKER	tristate "Priority Inheritance Debugging (Blocker) Device Support"	---help---	  If you say Y here then a device will be created that the userspace	  pi_test suite uses to test and measure kernel locking primitives.config SGI_DS1286	tristate "SGI DS1286 RTC support"	depends on SGI_IP22	help	  If you say Y here and create a character special file /dev/rtc with	  major number 10 and minor number 135 using mknod ("man mknod"), you	  will get access to the real time clock built into your computer.	  Every SGI has such a clock built in. It reports status information	  via the file /proc/rtc and its behaviour is set by various ioctls on	  /dev/rtc.config SGI_IP27_RTC	bool "SGI M48T35 RTC support"	depends on SGI_IP27	help	  If you say Y here and create a character special file /dev/rtc with	  major number 10 and minor number 135 using mknod ("man mknod"), you	  will get access to the real time clock built into your computer.	  Every SGI has such a clock built in. It reports status information	  via the file /proc/rtc and its behaviour is set by various ioctls on	  /dev/rtc.config SA1100_RTC	bool "SA11x0/PXA2xx RTC support"	depends on ARCH_SA1100 || ARCH_PXA	help	  If you say Y here and create a character special file /dev/rtc with	  major number 10 and minor number 135 using mknod ("man mknod"), you	  will get access to the real time clock built into your SA11x0 or	  PXA2xx CPU. It reports status information via the file /proc/rtc	  and its behaviour is set by various ioctls on /dev/rtc.	  To compile this driver as a module, choose M here: the	  module will be called sa1100-rtc.config GEN_RTC	tristate "Generic /dev/rtc emulation"	depends on RTC!=y && !IA64 && !ARM	---help---	  If you say Y here and create a character special file /dev/rtc with	  major number 10 and minor number 135 using mknod ("man mknod"), you	  will get access to the real time clock (or hardware clock) built	  into your computer.	  It reports status information via the file /proc/driver/rtc and its	  behaviour is set by various ioctls on /dev/rtc. If you enable the	  "extended RTC operation" below it will also provide an emulation	  for RTC_UIE which is required by some programs and may improve	  precision in some cases.	  To compile this driver as a module, choose M here: the	  module will be called genrtc.config GEN_RTC_X	bool "Extended RTC operation"	depends on GEN_RTC	help	  Provides an emulation for RTC_UIE which is required by some programs	  and may improve precision of the generic RTC support in some cases.config EFI_RTC	bool "EFI Real Time Clock Services"	depends on IA64config OMAP_RTC	bool "TI OMAP Real Time Clock"	depends on ARCH_OMAP1510 || ARCH_OMAP16XX || ARCH_OMAP730	help	  Support for TI OMAP RTCconfig DS1302	tristate "DS1302 RTC support"	depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)	help	  If you say Y here and create a character special file /dev/rtc with	  major number 121 and minor number 0 using mknod ("man mknod"), you	  will get access to the real time clock (or hardware clock) built	  into your computer.config S3C2410_RTC	bool "S3C2410 RTC Driver"	depends on ARCH_S3C2410	help	  RTC (Realtime Clock) driver for the clock inbuilt into the	  Samsung S3C2410. This can provide periodic interrupt rates	  from 1Hz to 64Hz for user programs, and wakeup from Alarm.config DAVINCI_RTC	bool "TI DaVinci Real Time Clock"	depends on ARCH_DAVINCI && MACH_DAVINCI_EVM && I2C_DAVINCI	help	  Support for TI DaVinci RTCconfig COBALT_LCD	bool "Support for Cobalt LCD"	depends on MIPS_COBALT	help	  This option enables support for the LCD display and buttons found	  on Cobalt systems through a misc device.config DTLK	tristate "Double Talk PC internal speech card support"	help	  This driver is for the DoubleTalk PC, a speech synthesizer	  manufactured by RC Systems (<http://www.rcsys.com/>).  It is also	  called the `internal DoubleTalk'.	  To compile this driver as a module, choose M here: the	  module will be called dtlk.config R3964	tristate "Siemens R3964 line discipline"	---help---	  This driver allows synchronous communication with devices using the	  Siemens R3964 packet protocol. Unless you are dealing with special	  hardware like PLCs, you are unlikely to need this.	  To compile this driver as a module, choose M here: the	  module will be called n_r3964.	  If unsure, say N.config APPLICOM	tristate "Applicom intelligent fieldbus card support"	depends on PCI	---help---	  This driver provides the kernel-side support for the intelligent	  fieldbus cards made by Applicom International. More information	  about these cards can be found on the WWW at the address	  <http://www.applicom-int.com/>, or by email from David Woodhouse	  <dwmw2@infradead.org>.	  To compile this driver as a module, choose M here: the	  module will be called applicom.	  If unsure, say N.config SONYPI	tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"	depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT	---help---	  This driver enables access to the Sony Programmable I/O Control	  Device which can be found in many (all ?) Sony Vaio laptops.	  If you have one of those laptops, read	  <file:Documentation/sonypi.txt>, and say Y or M here.	  To compile this driver as a module, choose M here: the	  module will be called sonypi.menu "Ftape, the floppy tape device driver"config FTAPE	tristate "Ftape (QIC-80/Travan) support"	depends on BROKEN_ON_SMP && (ALPHA || X86)	---help---	  If you have a tape drive that is connected to your floppy	  controller, say Y here.	  Some tape drives (like the Seagate "Tape Store 3200" or the Iomega	  "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"	  controller of their own. These drives (and their companion	  controllers) are also supported if you say Y here.	  If you have a special controller (such as the CMS FC-10, FC-20,	  Mountain Mach-II, or any controller that is based on the Intel 82078	  FDC like the high speed controllers by Seagate and Exabyte and	  Iomega's "Ditto Dash") you must configure it by selecting the	  appropriate entries from the "Floppy tape controllers" sub-menu	  below and possibly modify the default values for the IRQ and DMA	  channel and the IO base in ftape's configuration menu.	  If you want to use your floppy tape drive on a PCI-bus based system,	  please read the file <file:drivers/char/ftape/README.PCI>.	  The ftape kernel driver is also available as a runtime loadable	  module. To compile this driver as a module, choose M here: the	  module will be called ftape.	  Note that the Ftape-HOWTO is out of date (sorry) and documents the	  older version 2.08 of this software but still contains useful	  information.  There is a web page with more recent documentation at	  <http://www.instmath.rwth-aachen.de/~heine/ftape/>.  This page	  always contains the latest release of the ftape driver and useful	  information (backup software, ftape related patches and	  documentation, FAQ).  Note that the file system interface has	  changed quite a bit compared to previous versions of ftape.  Please	  read <file:Documentation/ftape.txt>.source "drivers/char/ftape/Kconfig"endmenusource "drivers/char/agp/Kconfig"source "drivers/char/drm/Kconfig"source "drivers/char/pcmcia/Kconfig"config XILINX_UARTLITE	tristate "Xilinx UART Lite support"	depends on XILINX_VIRTEX	select XILINX_EDKconfig XILINX_UARTLITE_CONSOLE	bool "  Console on UART Lite port"	depends on XILINX_UARTLITEconfig MWAVE	tristate "ACP Modem (Mwave) support"	depends on X86	select SERIAL_8250	---help---	  The ACP modem (Mwave) for Linux is a WinModem. It is composed of a	  kernel driver and a user level application. Together these components	  support direct attachment to public switched telephone networks (PSTNs)	  and support selected world wide countries.	  This version of the ACP Modem driver supports the IBM Thinkpad 600E,	  600, and 770 that include on board ACP modem hardware.	  The modem also supports the standard communications port interface	  (ttySx) and is compatible with the Hayes AT Command Set.	  The user level application needed to use this driver can be found at	  the IBM Linux Technology Center (LTC) web site:	  <http://www.ibm.com/linux/ltc/>.	  If you own one of the above IBM Thinkpads which has the Mwave chipset	  in it, say Y.	  To compile this driver as a module, choose M here: the	  module will be called mwave.config SCx200_GPIO	tristate "NatSemi SCx200 GPIO Support"	depends on SCx200	help	  Give userspace access to the GPIO pins on the National	  Semiconductor SCx200 processors.	  If compiled as a module, it will be called scx200_gpio.config XILINX_GPIO	tristate "Xilinx GPIO support"	depends on XILINX_VIRTEX	select XILINX_EDK	help	  This driver supports GPIO IP from Xilinx EDKconfig XILINX_CHAR_LCD	tristate "Xilinx character LCD"	depends on MEMEC_2VPX	help	  Select this if you want to use 16 characters by 2 lines LCD	  found on e.g. Memec Virtex-II Pro Development Board.config XILINX_TS	tristate "Xilinx touchscreen"	depends on XILINX_ML300	select XILINX_EDK	help	  Touchscreen support for Xilinx ML300 boardconfig XILINX_SPI	tristate "Xilinx SPI"	depends on XILINX_ML300	select XILINX_EDK	help	  Simple SPI driver for Xilinx ML300 boardconfig RAW_DRIVER	tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)"	help	  The raw driver permits block devices to be bound to /dev/raw/rawN.	  Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.	  See the raw(8) manpage for more details.          The raw driver is deprecated and may be removed from 2.7          kernels.  Applications should simply open the device (eg /dev/hda1)          with the O_DIRECT flag.config HPET	bool "HPET - High Precision Event Timer" if (X86 || IA64)	default n	depends on ACPI	help	  If you say Y here, you will have a miscdevice named "/dev/hpet/".  Each	  open selects one of the timers supported by the HPET.  The timers are	  non-periodioc and/or periodic.config HPET_RTC_IRQ	bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC	default n	depends on HPET	help	  If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It	  is assumed the platform called hpet_alloc with the RTC IRQ values for	  the HPET timers.config HPET_MMAP	bool "Allow mmap of HPET"	default y	depends on HPET	help	  If you say Y here, user applications will be able to mmap	  the HPET registers.	  In some hardware implementations, the page containing HPET	  registers may also contain other things that shouldn't be	  exposed to the user.  If this applies to your hardware,	  say N here.config MAX_RAW_DEVS	int "Maximum number of RAW devices to support (1-8192)"	depends on RAW_DRIVER	default "256"	help	  The maximum number of RAW devices that are supported.	  Default is 256. Increase this number in case you need lots of	  raw devices.config RESIZER	tristate "DaVinci Resizer Driver"	default n	help		DaVinci Resizer Driver.config HANGCHECK_TIMER	tristate "Hangcheck timer"	depends on X86_64 || X86	help	  The hangcheck-timer module detects when the system has gone	  out to lunch past a certain margin.  It can reboot the system	  or merely print a warning.config MMTIMER	tristate "MMTIMER Memory mapped RTC for SGI Altix"	depends on IA64_GENERIC || IA64_SGI_SN2	default y	help	  The mmtimer device allows direct userspace access to the	  Altix system timer.endmenu

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -