Kconfig 6.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219
  1. #
  2. # PCMCIA bus subsystem configuration
  3. #
  4. # Right now the non-CardBus choices are not supported
  5. # by the integrated kernel driver.
  6. #
  7. menu "PCCARD (PCMCIA/CardBus) support"
  8. config PCCARD
  9. tristate "PCCard (PCMCIA/CardBus) support"
  10. select HOTPLUG
  11. ---help---
  12. Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
  13. computer. These are credit-card size devices such as network cards,
  14. modems or hard drives often used with laptops computers. There are
  15. actually two varieties of these cards: the older 16 bit PCMCIA cards
  16. and the newer 32 bit CardBus cards.
  17. To compile this driver as modules, choose M here: the
  18. module will be called pcmcia_core.
  19. if PCCARD
  20. config PCMCIA_DEBUG
  21. bool "Enable PCCARD debugging"
  22. help
  23. Say Y here to enable PCMCIA subsystem debugging. You
  24. will need to choose the debugging level either via the
  25. kernel command line, or module options depending whether
  26. you build the PCMCIA as modules.
  27. The kernel command line options are:
  28. pcmcia_core.pc_debug=N
  29. ds.pc_debug=N
  30. sa11xx_core.pc_debug=N
  31. The module option is called pc_debug=N
  32. In all the above examples, N is the debugging verbosity
  33. level.
  34. config PCMCIA
  35. tristate "16-bit PCMCIA support"
  36. default y
  37. ---help---
  38. This option enables support for 16-bit PCMCIA cards. Most older
  39. PC-cards are such 16-bit PCMCIA cards, so unless you know you're
  40. only using 32-bit CardBus cards, say Y or M here.
  41. To use 16-bit PCMCIA cards, you will need supporting software from
  42. David Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
  43. for location). Please also read the PCMCIA-HOWTO, available from
  44. <http://www.tldp.org/docs.html#howto>.
  45. To compile this driver as modules, choose M here: the
  46. module will be called pcmcia.
  47. If unsure, say Y.
  48. config PCMCIA_LOAD_CIS
  49. bool "Load CIS updates from userspace (EXPERIMENTAL)"
  50. depends on PCMCIA && EXPERIMENTAL
  51. select FW_LOADER
  52. default y
  53. help
  54. Some PCMCIA cards require an updated Card Information Structure (CIS)
  55. to be loaded from userspace to work correctly. If you say Y here,
  56. and your userspace is arranged correctly, this will be loaded
  57. automatically using the in-kernel firmware loader and the hotplug
  58. subsystem, instead of relying on cardmgr from pcmcia-cs to do so.
  59. If unsure, say Y.
  60. config CARDBUS
  61. bool "32-bit CardBus support"
  62. depends on PCI
  63. default y
  64. ---help---
  65. CardBus is a bus mastering architecture for PC-cards, which allows
  66. for 32 bit PC-cards (the original PCMCIA standard specifies only
  67. a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
  68. To use 32 bit PC-cards, you also need a CardBus compatible host
  69. bridge. Virtually all modern PCMCIA bridges do this, and most of
  70. them are "yenta-compatible", so say Y or M there, too.
  71. If unsure, say Y.
  72. comment "PC-card bridges"
  73. config YENTA
  74. tristate "CardBus yenta-compatible bridge support"
  75. depends on PCI
  76. #fixme: remove dependendcy on CARDBUS
  77. depends on CARDBUS
  78. select PCCARD_NONSTATIC
  79. ---help---
  80. This option enables support for CardBus host bridges. Virtually
  81. all modern PCMCIA bridges are CardBus compatible. A "bridge" is
  82. the hardware inside your computer that PCMCIA cards are plugged
  83. into.
  84. To compile this driver as modules, choose M here: the
  85. module will be called yenta_socket.
  86. If unsure, say Y.
  87. config PD6729
  88. tristate "Cirrus PD6729 compatible bridge support"
  89. depends on PCMCIA && PCI
  90. select PCCARD_NONSTATIC
  91. help
  92. This provides support for the Cirrus PD6729 PCI-to-PCMCIA bridge
  93. device, found in some older laptops and PCMCIA card readers.
  94. config I82092
  95. tristate "i82092 compatible bridge support"
  96. depends on PCMCIA && PCI
  97. select PCCARD_NONSTATIC
  98. help
  99. This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
  100. found in some older laptops and more commonly in evaluation boards for the
  101. chip.
  102. config I82365
  103. tristate "i82365 compatible bridge support"
  104. depends on PCMCIA && ISA
  105. select PCCARD_NONSTATIC
  106. help
  107. Say Y here to include support for ISA-bus PCMCIA host bridges that
  108. are register compatible with the Intel i82365. These are found on
  109. older laptops and ISA-bus card readers for desktop systems. A
  110. "bridge" is the hardware inside your computer that PCMCIA cards are
  111. plugged into. If unsure, say N.
  112. config TCIC
  113. tristate "Databook TCIC host bridge support"
  114. depends on PCMCIA
  115. select PCCARD_NONSTATIC
  116. help
  117. Say Y here to include support for the Databook TCIC family of PCMCIA
  118. host bridges. These are only found on a handful of old systems.
  119. "Bridge" is the name used for the hardware inside your computer that
  120. PCMCIA cards are plugged into. If unsure, say N.
  121. config HD64465_PCMCIA
  122. tristate "HD64465 host bridge support"
  123. depends on HD64465 && PCMCIA
  124. config PCMCIA_AU1X00
  125. tristate "Au1x00 pcmcia support"
  126. depends on SOC_AU1X00 && PCMCIA
  127. config PCMCIA_SA1100
  128. tristate "SA1100 support"
  129. depends on ARM && ARCH_SA1100 && PCMCIA
  130. help
  131. Say Y here to include support for SA11x0-based PCMCIA or CF
  132. sockets, found on HP iPAQs, Yopy, and other StrongARM(R)/
  133. Xscale(R) embedded machines.
  134. This driver is also available as a module called sa1100_cs.
  135. config PCMCIA_SA1111
  136. tristate "SA1111 support"
  137. depends on ARM && ARCH_SA1100 && SA1111 && PCMCIA
  138. help
  139. Say Y here to include support for SA1111-based PCMCIA or CF
  140. sockets, found on the Jornada 720, Graphicsmaster and other
  141. StrongARM(R)/Xscale(R) embedded machines.
  142. This driver is also available as a module called sa1111_cs.
  143. config PCMCIA_PXA2XX
  144. tristate "PXA2xx support"
  145. depends on ARM && ARCH_PXA && PCMCIA
  146. help
  147. Say Y here to include support for the PXA2xx PCMCIA controller
  148. config PCMCIA_PROBE
  149. bool
  150. default y if ISA && !ARCH_SA1100 && !ARCH_CLPS711X
  151. config M32R_PCC
  152. bool "M32R PCMCIA I/F"
  153. depends on M32R && CHIP_M32700 && PCMCIA
  154. select PCCARD_NONSTATIC
  155. help
  156. Say Y here to use the M32R PCMCIA controller.
  157. config M32R_CFC
  158. bool "M32R CF I/F Controller"
  159. depends on M32R && (PLAT_USRV || PLAT_M32700UT || PLAT_MAPPI2 || PLAT_MAPPI3 || PLAT_OPSPUT)
  160. select PCCARD_NONSTATIC
  161. help
  162. Say Y here to use the M32R CompactFlash controller.
  163. config M32R_CFC_NUM
  164. int "M32R CF I/F number"
  165. depends on M32R_CFC
  166. default "1" if PLAT_USRV || PLAT_M32700UT || PLAT_MAPPI2 || PLAT_MAPPI3 || PLAT_OPSPUT
  167. help
  168. Set the number of M32R CF slots.
  169. config PCMCIA_VRC4171
  170. tristate "NEC VRC4171 Card Controllers support"
  171. depends on VRC4171 && PCMCIA
  172. config PCMCIA_VRC4173
  173. tristate "NEC VRC4173 CARDU support"
  174. depends on CPU_VR41XX && PCI && PCMCIA
  175. config PCCARD_NONSTATIC
  176. tristate
  177. endif # PCCARD
  178. endmenu