Skip to content

Instantly share code, notes, and snippets.

@dubiousjim

dubiousjim/kconfig-diff.py

Last active January 31, 2017 14:21
Download ZIP
Kernel config choices and symbols that differ between Alpine's linux-grsec, linux-xenguest, and linux-virt-grsec.
Raw
kconfig-diff.py
#!/usr/bin/ipython2 -i
"""
This script should be run from a folder residing at the toplevel of the kernel source tree, and which also contains
https://raw.github.com/ulfalizer/Kconfiglib/master/kconfiglib.py
Invoke as follows:
./kconfig-diff.py x86 DEFAULT kern1.conf kern2.conf kern3.conf
You can pass up to four arguments after the architecture; these should be paths of kernel config files, or the keyword
DEFAULT for the default kernel settings. The latter can be used only in the first slot.
Running the script will start an interactive IPython session (or you can change the shebang line to make it a plain Python session)
pre-loaded with kconfiglib.Config objects representing the different configs.
Some sample operations:
>>> DEFAULT, kern1, kern2, kern3
(<kconfiglib.Config instance at 0x977970c>,
<kconfiglib.Config instance at 0xb6ad36c>,
<kconfiglib.Config instance at 0xd820a6c>,
<kconfiglib.Config instance at 0xf98f62c>)
kern1.conf and kernelconfig.kern1 both get saved as the global object 'kern1'; otherwise, refer to the Config objects as one, two, ...
>>> one_s, one_c = kern1.diffs
>>> two_s, two_c = kern2.diffs
>>> three_s, three_c = kern3.diffs
>>> map(len,[one_s, one_c, two_s, two_c, three_s, three_c])
[2946, 25, 331, 6, 1469, 10]
This indicates that kern1 differs from the DEFAULT settings in 2946 modifiable symbols and 25 modifiable choices. Differences which are forced
by other selections aren't included here; only differences that could be immediately changed. If the DEFAULT config was selected, only the first
succeeding config is compared to it. Otherwise, configs are compared to all of the configurations that precede them in the argv list: so
kern2 is compared to kern1, and kern3 is compared to both kern2 and kern1. Hence the lengths 1496, 10 for kern3 indicate that that there are 1496
modifiable symbols where kern3 differs from one or both of kern1 and kern2, and 10 modifiable choices where it differs from them.
The elements in the lists three_s and three_c are strings, that look like this:
>>> print three_s[0]
Symbol RD_BZIP2
Type : bool
Value : "n"
User value : "n"
Kern2 config : 'n'
Kern1 config : 'y'
Visibility : "y"
General setup
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support initial ramdisks compressed using bzip2" if EXPERT && BLK_DEV_INITRD (value: "y")
Default values:
!EXPERT (value: "n")
Condition: BLK_DEV_INITRD (value: "y")
Selects:
DECOMPRESS_BZIP2 if BLK_DEV_INITRD (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV_INITRD (value: "y")
Locations: ../usr/Kconfig:57
Support loading of a bzip2 encoded initial ramdisk or cpio buffer
If unsure, say N.
Notice the lines "Value" and "User value". The "User value" is a legal setting in the config file for the given symbol type; however, it may not be honored depending on other configuration selections. "Value" is what will really be honored (and displayed in the kernel `make menuconfig` display). Notice also that the Values for kern2 and kern1 are displayed here. One of these will differ from the Value for kern3, or this entry wouldn't have been added to kern3.diffs[0].
Choices are formatted a bit differently:
>>> print three_c[0]
Choice
Name (for named choices): (no name)
Type : bool
Selected symbol : DEFAULT_DEADLINE
User value : DEFAULT_DEADLINE
Kern2 config : DEFAULT_CFQ
Kern1 config : DEFAULT_CFQ
Mode : "y"
Visibility : "y"
IO Schedulers
Optional : false
Prompts:
"Default I/O scheduler"
Defaults:
DEFAULT_CFQ
Choice symbols:
DEFAULT_DEADLINE DEFAULT_CFQ DEFAULT_NOOP
Additional dependencies from enclosing menus and if's:
BLOCK (value: "y")
Locations: ../block/Kconfig.iosched:42
Select the I/O scheduler which will be used by default for all
block devices.
See the below source, run `pydoc kconfiglib`, and see https://github.com/ulfalizer/Kconfiglib/tree/master/examples
for more information.
"""
print
import os, sys
from collections import defaultdict
try:
with open('../Makefile') as f:
version = []
line = f.readline()
if not line.startswith('VERSION ='):
raise IOError
version.append(line[10:-1])
line = f.readline()
if not line.startswith('PATCHLEVEL ='):
raise IOError
line = line[13:-1] or '0'
version.append(line)
line = f.readline()
if not line.startswith('SUBLEVEL ='):
raise IOError
line = line[11:-1] or '0'
version.append(line)
line = f.readline()
if not line.startswith('EXTRAVERSION ='):
raise IOError
line = line[15:-1]
if line:
version.append(line)
version = '.'.join(version)
except IOError:
print >> sys.stderr, "Parent directory is not a kernel source tree."
sys.exit(1)
argv = sys.argv
assert argv[1] == 'x86' or argv[1] == 'x86_64', "First argument should be x86 or x86_64"
os.environ.update({'srctree':'..','SRCARCH':argv[1],'ARCH':argv[1],'KERNELVERSION':version})
# sys.path.insert(0, '../Kconfiglib')
import kconfiglib as K
def f(self, x):
assert x.is_choice()
xn = x.symbol_names
for y in self.get_choices():
res = len(xn.intersection(y.symbol_names))
# res = xn == y.symbol_names
if res:
return y
K.Config.get_choice = f
# instance.get_choice = types.MethodType(K_get_choice, instance, K)
def f(self):
d = defaultdict(lambda: None)
for x in self.get_choices():
d[x.symbol_names] = x
return d
K.Config.get_choice_dict = f
def f(self):
ps = []
p = self.get_parent()
while p is not None:
ps.insert(0, p)
p = p.get_parent()
return ps
K.Item.get_parents = f
del f
argv = argv[2:]
if len(argv) < 2 or len(argv) > 4:
print >> sys.stderr, "Supply 2-4 kernel configs (or DEFAULT) to compare."
sys.exit(1)
G = globals()
for i,p in enumerate(argv):
k = K.Config('../Kconfig')
k.config_path = p
if p == 'DEFAULT':
assert i==0, "DEFAULT config should be specified first."
k.config_name = 'DEFAULT'
G['DEFAULT'] = k
else:
print("loading {0}...".format(p))
k.load_config(p)
p = p.split('/')[-1]
if p.startswith('kernelconfig.'):
k.config_name = p[13:]
try:
G[k.config_name] = k
except IOError:
pass
elif p.endswith('.conf'):
k.config_name = p[:-5]
try:
G[k.config_name] = k
except IOError:
pass
else:
k.config_name = p
k.choice_symbols=[]
k.non_choice_symbols=[]
for sym in k:
(k.choice_symbols if sym.is_choice_symbol() else k.non_choice_symbols).append(sym)
for s in k.non_choice_symbols:
s.others = {}
for c in k.get_choices():
c.symbol_names = frozenset(s.get_name() for s in c.get_symbols())
sel = c.get_selection()
c.sel_name = sel.get_name() if sel else None
c.others = {}
argv[i] = k
if len(argv) == 2:
one, two = argv
elif len(argv) == 3:
one, two, three = argv
elif len(argv) == 4:
one, two, three, four = argv
def cmp_symbols(s, t):
assert s.is_symbol() and t.is_symbol()
sv, tv = s.get_value(), t.get_value()
if sv == tv:
return False
elif not s.is_modifiable():
return 0
elif s.get_type() in (K.TRISTATE, K.BOOL):
u, l = s.get_upper_bound(), s.get_lower_bound()
if K.tri_less(tv, l) and not K.tri_greater(sv, l):
return "pinlow"
elif K.tri_greater(tv, u) and not K.tri_less(sv, u):
return "pinhi"
return True # values are deliberately different
def cmp_choices(c, d):
assert c.is_choice() and d.is_choice()
cm, dm = c.get_mode(), d.get_mode()
if cm != dm:
return 0 if cm == 'n' or c.get_visibility() == 'n' else True
if cm == 'n':
return False
elif cm == 'y':
return c.sel_name != d.sel_name
else:
assert cm == 'm'
cs = set(s.get_name() for s in c.get_symbols() if s.get_value() == 'm')
ds = set(s.get_name() for s in d.get_symbols() if s.get_value() == 'm')
return cs != ds
def cmp_all(xk, yk):
xname = xk.config_name
yname = yk.config_name
for y in yk.non_choice_symbols:
y.others[xname] = None
for x in xk.non_choice_symbols:
y = yk.get_symbol(x.get_name())
if y is None:
# symbol in xk but not yk
x.others[yname] = None
else:
res = cmp_symbols(x, y)
x.others[yname] = y.others[xname] = res
for y in yk.get_choices():
y.others[xname] = (None, None, None)
yc = yk.get_choice_dict()
for x in xk.get_choices():
# at least in kernel 3.9.2, choice_symbols are always BOOL or TRISTATE
y = yc[x.symbol_names]
if y is None:
# choice in xk but not yk
x.others[yname] = (None, None, None)
else:
res = cmp_choices(x, y)
x.others[yname] = (res, y, y.sel_name)
y.others[xname] = (res, x, x.sel_name)
argv[0].bad_symbols = frozenset([])
argv[0].bad_choices = frozenset([])
for j in range(1, len(argv)):
jk = argv[j]
jk.bad_symbols = set()
jk.bad_choices = set()
for i in range(0, j):
ik = argv[i]
if j > 1 and ik.config_name == 'DEFAULT':
continue
print "comparing {0} and {1}...".format(jk.config_name, ik.config_name)
cmp_all(jk, ik)
jk.bad_symbols.update(s.get_name() for s in jk.non_choice_symbols if s.others[ik.config_name] or s.get_name() in ik.bad_symbols)
jk.bad_choices.update(c.symbol_names for c in jk.get_choices() if c.others[ik.config_name][0] or c.symbol_names in ik.bad_choices)
# take symbol objects, in original order
js = [s for s in jk.non_choice_symbols if s.get_name() in jk.bad_symbols]
# take choice objects, in original order
jc = [c for c in jk.get_choices() if c.symbol_names in jk.bad_choices]
if j == 1 and argv[0].config_name == 'DEFAULT':
jk.bad_symbols = argv[0].bad_symbols
jk.bad_choices = argv[0].bad_choices
# jsymbols holds non-choice symbol diffs
jsymbols = []
for s in js:
sz = str(s).splitlines()
sname = s.get_name()
# sz.insert(5, "Location :")
pars = [p.get_title() for p in s.get_parents()]
for i,p in enumerate(pars):
pars[i] = ' '*(i+1)+p
sz[5:5] = pars
# for i in range(j-1, -1, -1):
for i in range(0, j):
ik = argv[i]
iname = ik.config_name
if j > 1 and ik.config_name == 'DEFAULT':
continue
t = ik.get_symbol(sname)
sz.insert(4, '{0} config {1}: {2}'.format(iname.title(), ' '*(7-len(iname)), repr(t.get_value()) if t else 'None'))
txt = '\n'.join(sz)
h = s.get_help()
if h:
txt = txt + '\n\n' + h
jsymbols.append(txt)
# jchoices holds choice diffs
jchoices = []
for c in jc:
cz = str(c).splitlines()
# cz.insert(7, "Location :")
pars = [p.get_title() for p in c.get_parents()]
for i,p in enumerate(pars):
pars[i] = ' '*(i+1)+p
cz[7:7] = pars
# for i in range(j-1, -1, -1):
for i in range(0, j):
ik = argv[i]
if j > 1 and ik.config_name == 'DEFAULT':
continue
iname = ik.config_name
(_,_,sel) = c.others[iname]
cz.insert(5, "{0} config {1}: {2}".format(iname.title(), ' '*(8-len(iname)), sel if sel else 'None'))
txt = '\n'.join(cz)
h = c.get_help()
if h:
txt = txt + '\n\n' + h
jchoices.append(txt)
jk.diffs = (jsymbols, jchoices)
Raw
kernel_comparisons
This file has been truncated, but you can view the full file.
Choice
Name (for named choices): (no name)
Type : bool
Selected symbol : DEFAULT_DEADLINE
User value : DEFAULT_DEADLINE
Xen config : DEFAULT_CFQ
Main config : DEFAULT_CFQ
Mode : "y"
Visibility : "y"
IO Schedulers
Optional : false
Prompts:
"Default I/O scheduler"
Defaults:
DEFAULT_CFQ
Choice symbols:
DEFAULT_DEADLINE DEFAULT_CFQ DEFAULT_NOOP
Additional dependencies from enclosing menus and if's:
BLOCK (value: "y")
Locations: ../block/Kconfig.iosched:42
Select the I/O scheduler which will be used by default for all
block devices.
Choice
Name (for named choices): (no name)
Type : bool
Selected symbol : M586TSC
User value : M586TSC
Xen config : MCORE2
Main config : M586
Mode : "y"
Visibility : "y"
Processor type and features
Optional : false
Prompts:
"Processor family"
Defaults:
M686 if X86_32 (value: "y")
GENERIC_CPU if X86_64 (value: "n")
Choice symbols:
M486 M586 M586TSC M586MMX M686 MPENTIUMII MPENTIUMIII MPENTIUMM MPENTIUM4 MK6 MK7 MK8 MCRUSOE MEFFICEON MWINCHIPC6 MWINCHIP3D MELAN MGEODEGX1 MGEODE_LX MCYRIXIII MVIAC3_2 MVIAC7 MPSC MCORE2 MATOM GENERIC_CPU
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig.cpu:2
Choice
Name (for named choices): (no name)
Type : bool
Selected symbol : PREEMPT_NONE
User value : PREEMPT_NONE
Xen config : PREEMPT_NONE
Main config : PREEMPT_VOLUNTARY
Mode : "y"
Visibility : "y"
Processor type and features
Optional : false
Prompts:
"Preemption Model"
Defaults:
PREEMPT_NONE
Choice symbols:
PREEMPT_NONE PREEMPT_VOLUNTARY PREEMPT
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../kernel/Kconfig.preempt:2
Choice
Name (for named choices): (no name)
Type : bool
Selected symbol : HIGHMEM64G
User value : HIGHMEM64G
Xen config : HIGHMEM64G
Main config : HIGHMEM4G
Mode : "y"
Visibility : "y"
Processor type and features
Optional : false
Prompts:
"High Memory Support" if X86_32 (value: "y")
Defaults:
HIGHMEM64G if X86_NUMAQ && X86_32 (value: "n")
HIGHMEM4G if X86_32 (value: "y")
Choice symbols:
NOHIGHMEM HIGHMEM4G HIGHMEM64G
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:1096
Choice
Name (for named choices): (no name)
Type : bool
Selected symbol : FLATMEM_MANUAL
User value : FLATMEM_MANUAL
Xen config : SPARSEMEM_MANUAL
Main config : FLATMEM_MANUAL
Mode : "y"
Visibility : "y"
Processor type and features
Optional : false
Prompts:
"Memory model" if SELECT_MEMORY_MODEL (value: "y")
Defaults:
DISCONTIGMEM_MANUAL if ARCH_DISCONTIGMEM_DEFAULT && SELECT_MEMORY_MODEL (value: "n")
SPARSEMEM_MANUAL if ARCH_SPARSEMEM_DEFAULT && SELECT_MEMORY_MODEL (value: "n")
FLATMEM_MANUAL if SELECT_MEMORY_MODEL (value: "y")
Choice symbols:
FLATMEM_MANUAL DISCONTIGMEM_MANUAL SPARSEMEM_MANUAL
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../mm/Kconfig:5
Choice
Name (for named choices): (no name)
Type : bool
Selected symbol : HZ_100
User value : HZ_100
Xen config : HZ_100
Main config : HZ_300
Mode : "y"
Visibility : "y"
Processor type and features
Optional : false
Prompts:
"Timer frequency"
Defaults:
HZ_250
Choice symbols:
HZ_100 HZ_250 HZ_300 HZ_1000
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../kernel/Kconfig.hz:5
Allows the configuration of the timer frequency. It is customary
to have the timer interrupt run at 1000 Hz but 100 Hz may be more
beneficial for servers and NUMA systems that do not need to have
a fast response for user interaction and that may experience bus
contention and cacheline bounces as a result of timer interrupts.
Note that the timer interrupt occurs on each processor in an SMP
environment leading to NR_CPUS * HZ number of timer interrupts
per second.
Choice
Name (for named choices): (no name)
Type : bool
Selected symbol : PCIEASPM_DEFAULT
User value : PCIEASPM_DEFAULT
Xen config : None
Main config : PCIEASPM_DEFAULT
Mode : "y"
Visibility : "y"
Bus options (PCI etc.)
Optional : false
Prompts:
"Default ASPM policy" if PCIEASPM (value: "y")
Defaults:
PCIEASPM_DEFAULT if PCIEASPM (value: "y")
Choice symbols:
PCIEASPM_DEFAULT PCIEASPM_POWERSAVE PCIEASPM_PERFORMANCE
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/pci/pcie/Kconfig:58
Choice
Name (for named choices): (no name)
Type : bool
Selected symbol : SCTP_DEFAULT_COOKIE_HMAC_MD5
User value : SCTP_DEFAULT_COOKIE_HMAC_MD5
Xen config : SCTP_DEFAULT_COOKIE_HMAC_NONE
Main config : SCTP_DEFAULT_COOKIE_HMAC_MD5
Mode : "y"
Visibility : "y"
Networking options
Optional : false
Prompts:
"Default SCTP cookie HMAC encoding"
Defaults:
SCTP_DEFAULT_COOKIE_HMAC_MD5
Choice symbols:
SCTP_DEFAULT_COOKIE_HMAC_MD5 SCTP_DEFAULT_COOKIE_HMAC_SHA1 SCTP_DEFAULT_COOKIE_HMAC_NONE
Additional dependencies from enclosing menus and if's:
IP_SCTP && NET (value: "m")
Locations: ../net/sctp/Kconfig:69
This option sets the default sctp cookie hmac algorithm
when in doubt select 'md5'
Choice
Name (for named choices): (no name)
Type : bool
Selected symbol : THERMAL_DEFAULT_GOV_STEP_WISE
User value : THERMAL_DEFAULT_GOV_STEP_WISE
Xen config : None
Main config : THERMAL_DEFAULT_GOV_STEP_WISE
Mode : "y"
Visibility : "y"
Device Drivers
Optional : false
Prompts:
"Default Thermal governor"
Defaults:
THERMAL_DEFAULT_GOV_STEP_WISE
Choice symbols:
THERMAL_DEFAULT_GOV_STEP_WISE THERMAL_DEFAULT_GOV_FAIR_SHARE THERMAL_DEFAULT_GOV_USER_SPACE
Additional dependencies from enclosing menus and if's:
THERMAL (value: "y")
Locations: ../drivers/thermal/Kconfig:23
This option sets which thermal governor shall be loaded at
startup. If in doubt, select 'step_wise'.
Choice
Name (for named choices): (no name)
Type : bool
Selected symbol : ROMFS_BACKED_BY_BLOCK
User value : ROMFS_BACKED_BY_BLOCK
Xen config : None
Main config : ROMFS_BACKED_BY_BLOCK
Mode : "y"
Visibility : "y"
File systems
Optional : false
Prompts:
"RomFS backing stores" if ROMFS_FS (value: "m")
Defaults:
ROMFS_BACKED_BY_BLOCK if ROMFS_FS (value: "m")
Choice symbols:
ROMFS_BACKED_BY_BLOCK ROMFS_BACKED_BY_MTD ROMFS_BACKED_BY_BOTH
Additional dependencies from enclosing menus and if's:
MISC_FILESYSTEMS (value: "y")
Locations: ../fs/romfs/Kconfig:21
Select the backing stores to be supported.
*******************************
Symbol RD_BZIP2
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
General setup
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support initial ramdisks compressed using bzip2" if EXPERT && BLK_DEV_INITRD (value: "y")
Default values:
!EXPERT (value: "n")
Condition: BLK_DEV_INITRD (value: "y")
Selects:
DECOMPRESS_BZIP2 if BLK_DEV_INITRD (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV_INITRD (value: "y")
Locations: ../usr/Kconfig:57
Support loading of a bzip2 encoded initial ramdisk or cpio buffer
If unsure, say N.
Symbol RD_LZMA
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
General setup
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support initial ramdisks compressed using LZMA" if EXPERT && BLK_DEV_INITRD (value: "y")
Default values:
!EXPERT (value: "n")
Condition: BLK_DEV_INITRD (value: "y")
Selects:
DECOMPRESS_LZMA if BLK_DEV_INITRD (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV_INITRD (value: "y")
Locations: ../usr/Kconfig:66
Support loading of a LZMA encoded initial ramdisk or cpio buffer
If unsure, say N.
Symbol RD_XZ
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
General setup
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support initial ramdisks compressed using XZ" if EXPERT && BLK_DEV_INITRD (value: "y")
Default values:
!EXPERT (value: "n")
Condition: BLK_DEV_INITRD (value: "y")
Selects:
DECOMPRESS_XZ if BLK_DEV_INITRD (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV_INITRD (value: "y")
Locations: ../usr/Kconfig:75
Support loading of a XZ encoded initial ramdisk or cpio buffer.
If unsure, say N.
Symbol RD_LZO
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
General setup
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support initial ramdisks compressed using LZO" if EXPERT && BLK_DEV_INITRD (value: "y")
Default values:
!EXPERT (value: "n")
Condition: BLK_DEV_INITRD (value: "y")
Selects:
DECOMPRESS_LZO if BLK_DEV_INITRD (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV_INITRD (value: "y")
Locations: ../usr/Kconfig:84
Support loading of a LZO encoded initial ramdisk or cpio buffer
If unsure, say N.
Symbol CC_OPTIMIZE_FOR_SIZE
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
General setup
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Optimize for size"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../init/Kconfig:1167
Enabling this option will pass "-Os" instead of "-O2" to gcc
resulting in a smaller kernel.
If unsure, say N.
Symbol PCSPKR_PLATFORM
Type : bool
Value : "n"
User value : "n"
Xen config : 'y'
Main config : 'y'
Visibility : "y"
General setup
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable PC-Speaker support" if EXPERT && HAVE_PCSPKR_PLATFORM (value: "y")
Default values:
y (value: "y")
Condition: HAVE_PCSPKR_PLATFORM (value: "y")
Selects:
I8253_LOCK if HAVE_PCSPKR_PLATFORM (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../init/Kconfig:1295
This option allows to disable the internal PC-Speaker
support, saving some memory.
Symbol EMBEDDED
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
General setup
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Embedded system"
Default values:
(no default values)
Selects:
EXPERT
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../init/Kconfig:1381
This option should be enabled if compiling the kernel for
an embedded system so certain expert options are available
for configuration.
Symbol PROFILING
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
General setup
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Profiling support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../init/Kconfig:1540
Say Y here to enable the extended profiling support mechanisms used
by profilers such as OProfile.
Symbol KPROBES
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
General setup
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Kprobes" if MODULES && HAVE_KPROBES (value: "y")
Default values:
(no default values)
Selects:
KALLSYMS if MODULES && HAVE_KPROBES (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/Kconfig:37
Kprobes allows you to trap at almost any kernel address and
execute a callback function. register_kprobe() establishes
a probepoint and specifies the callback. Kprobes is useful
for kernel debugging, non-intrusive instrumentation and testing.
If in doubt, say "N".
Symbol IOSCHED_DEADLINE
Type : tristate
Value : "y"
User value : "y"
Xen config : 'm'
Main config : 'm'
Visibility : "y"
IO Schedulers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Deadline I/O scheduler"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
CCW && BLOCK && BLK_DEV && DASD (value: "n")
Additional dependencies from enclosing menus and if's:
BLOCK (value: "y")
Locations: ../block/Kconfig.iosched:15
The deadline I/O scheduler is simple and compact. It will provide
CSCAN service with FIFO expiration of requests, switching to
a new point in the service tree and doing a batch of IO from there
in case of expiry.
Symbol IOSCHED_CFQ
Type : tristate
Value : "n"
User value : "n"
Xen config : 'y'
Main config : 'y'
Visibility : "y"
IO Schedulers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CFQ I/O scheduler"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLOCK (value: "y")
Locations: ../block/Kconfig.iosched:24
The CFQ I/O scheduler tries to distribute bandwidth equally
among all processes in the system. It should provide a fair
and low latency working environment, suitable for both desktop
and server systems.
This is the default I/O scheduler.
Symbol X86_MPPARSE
Type : bool
Value : "n"
User value : "n"
Xen config : 'y'
Main config : 'y'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable MPS table" if (ACPI || SFI) && X86_LOCAL_APIC (value: "y")
Default values:
y (value: "y")
Condition: X86_LOCAL_APIC (value: "y")
Selects:
(no selects)
Reverse dependencies:
X86_32_NON_STANDARD && PCI && X86_NUMAQ (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:315
For old smp systems that do not have proper acpi support. Newer systems
(esp with 64bit cpus) with acpi support, MADT and DSDT will override it
Symbol X86_BIGSMP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support for big SMP systems with more than 8 CPUs" if X86_32 && SMP (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:323
This option is needed for the systems that have more than 8 CPUs
Symbol X86_EXTENDED_PLATFORM
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support for extended (non-PC) x86 platforms"
"Support for extended (non-PC) x86 platforms"
Default values:
y (value: "y")
Condition: (none)
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
X86_64 (value: "n")
Locations: ../arch/x86/Kconfig:334 ../arch/x86/Kconfig:358
If you disable this option then the kernel will only support
standard PC platforms. (which covers the vast majority of
systems out there.)
If you enable this option then you'll be able to select support
for the following (non-PC) 64 bit x86 platforms:
Numascale NumaChip
ScaleMP vSMP
SGI Ultraviolet
If you have one of these systems, or if you want to build a
generic distribution kernel, say Y here - otherwise say N.
Symbol X86_EXTENDED_PLATFORM
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support for extended (non-PC) x86 platforms"
"Support for extended (non-PC) x86 platforms"
Default values:
y (value: "y")
Condition: (none)
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
X86_64 (value: "n")
Locations: ../arch/x86/Kconfig:334 ../arch/x86/Kconfig:358
If you disable this option then the kernel will only support
standard PC platforms. (which covers the vast majority of
systems out there.)
If you enable this option then you'll be able to select support
for the following (non-PC) 64 bit x86 platforms:
Numascale NumaChip
ScaleMP vSMP
SGI Ultraviolet
If you have one of these systems, or if you want to build a
generic distribution kernel, say Y here - otherwise say N.
Symbol PARAVIRT_TIME_ACCOUNTING
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'n'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Paravirtual steal time accounting"
Default values:
n (value: "n")
Condition: (none)
Selects:
PARAVIRT
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PARAVIRT_GUEST (value: "y")
Locations: ../arch/x86/Kconfig:609
Select this option to enable fine granularity task steal time
accounting. Time spent executing other tasks in parallel with
the current vCPU is discounted from the vCPU power. To account for
that, there can be a small performance impact.
If in doubt, say N here.
Symbol XEN
Type : bool
Value : "y"
User value : "y"
Xen config : 'y'
Main config : 'n'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Xen guest support" if (X86_64 || X86_32 && X86_PAE && !X86_VISWS) && X86_TSC (value: "y")
Default values:
(no default values)
Selects:
PARAVIRT if (X86_64 || X86_32 && X86_PAE && !X86_VISWS) && X86_TSC (value: "y")
PARAVIRT_CLOCK if (X86_64 || X86_32 && X86_PAE && !X86_VISWS) && X86_TSC (value: "y")
XEN_HAVE_PVMMU if (X86_64 || X86_32 && X86_PAE && !X86_VISWS) && X86_TSC (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PARAVIRT_GUEST (value: "y")
Locations: ../arch/x86/xen/Kconfig:5
This is the Linux Xen port. Enabling this will allow the
kernel to boot in a paravirtualized environment under the
Xen hypervisor.
Symbol KVM_GUEST
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"KVM Guest support (including kvmclock)"
Default values:
y (value: "y")
Condition: PARAVIRT_GUEST (value: "y")
Selects:
PARAVIRT
PARAVIRT
PARAVIRT_CLOCK
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PARAVIRT_GUEST (value: "y")
Locations: ../arch/x86/Kconfig:623
This option enables various optimizations for running under the KVM
hypervisor. It includes a paravirtualized clock, so that instead
of relying on a PIT (or probably other) emulation by the
underlying device model, the host provides the guest with
timing infrastructure such as time of day, and system time
Symbol PARAVIRT_SPINLOCKS
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'n'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Paravirtualization layer for spinlocks" if PARAVIRT && SMP (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PARAVIRT_GUEST (value: "y")
Locations: ../arch/x86/Kconfig:646
Paravirtualized spinlocks allow a pvops backend to replace the
spinlock implementation with something virtualization-friendly
(for example, block the virtual CPU rather than spinning).
Unfortunately the downside is an up to 5% performance hit on
native kernels, with various workloads.
If you are unsure how to answer this question, answer N.
Symbol NR_CPUS
Type : int
Value : "32"
User value : "32"
Xen config : '8'
Main config : '32'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Ranges:
[2, 8] if SMP && X86_32 && !X86_BIGSMP (value: "n")
[2, 512] if SMP && !MAXSMP (value: "y")
Prompts:
"Maximum number of CPUs" if SMP && !MAXSMP (value: "y")
Default values:
"1" (value: "n")
Condition: !SMP (value: "n")
"4096" (value: "n")
Condition: MAXSMP (value: "n")
"32" (value: "n")
Condition: SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000) (value: "y")
"8" (value: "n")
Condition: SMP (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:808
This allows you to specify the maximum number of CPUs which this
kernel will support. The maximum supported value is 512 and the
minimum value which makes sense is 2.
This is purely to save memory - each supported CPU adds
approximately eight kilobytes to the kernel image.
Symbol TOSHIBA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Toshiba Laptop support" if X86_32 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:963
This adds a driver to safely access the System Management Mode of
the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
not work on models with a Phoenix BIOS. The System Management Mode
is used to set the BIOS and power saving options on Toshiba portables.
For information on utilities to make use of this driver see the
Toshiba Linux utilities web site at:
<http://www.buzzard.org.uk/toshiba/>.
Say Y if you intend to run this kernel on a Toshiba portable.
Say N otherwise.
Symbol I8K
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Dell laptop support"
Default values:
(no default values)
Selects:
HWMON
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:979
This adds a driver to safely access the System Management Mode
of the CPU on the Dell Inspiron 8000. The System Management Mode
is used to read cpu temperature and cooling fan status and to
control the fans on the I8K portables.
This driver has been tested only on the Inspiron 8000 but it may
also work with other Dell laptops. You can force loading on other
models by passing the parameter `force=1' to the module. Use at
your own risk.
For information on utilities to make use of this driver see the
I8K Linux utilities web site at:
<http://people.debian.org/~dz/i8k/>
Say Y if you intend to run this kernel on a Dell Inspiron 8000.
Say N otherwise.
Symbol X86_REBOOTFIXUPS
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable X86 board specific fixups for reboot" if X86_32 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
PCI && PCI_GODIRECT && X86_32 && X86_EXTENDED_PLATFORM && X86_INTEL_CE || X86_32 && X86_EXTENDED_PLATFORM && X86_RDC321X (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:1000
This enables chipset and/or board specific fixups to be done
in order to get reboot to work correctly. This is only needed on
some combinations of hardware and BIOS. The symptom, for which
this config is intended, is when reboot ends with a stalled/hung
system.
Currently, the only fixup is for the Geode machines using
CS5530A and CS5536 chipsets and the RDC R-321x SoC.
Say Y if you want to enable the fixup. Currently, it's safe to
enable this option even if you don't need it.
Say N otherwise.
Symbol MICROCODE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CPU microcode loading support"
Default values:
(no default values)
Selects:
FW_LOADER
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:1017
If you say Y here, you will be able to update the microcode on
certain Intel and AMD processors. The Intel support is for the
IA32 family, e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4,
Xeon etc. The AMD support is for families 0x10 and later. You will
obviously need the actual microcode binary data itself which is not
shipped with the Linux kernel.
This option selects the general module only, you need to select
at least one vendor specific module as well.
To compile this driver as a module, choose M here: the module
will be called microcode.
Symbol MICROCODE_INTEL
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel microcode loading support" if MICROCODE (value: "m")
Default values:
MICROCODE (value: "m")
Condition: MICROCODE (value: "m")
Selects:
FW_LOADER if MICROCODE (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:1035
This options enables microcode patch loading support for Intel
processors.
For latest news and information on obtaining all the required
Intel ingredients for this driver, check:
<http://www.urbanmyth.org/microcode/>.
Symbol MICROCODE_AMD
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD microcode loading support" if MICROCODE (value: "m")
Default values:
(no default values)
Selects:
FW_LOADER if MICROCODE (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:1048
If you select this option, microcode patch loading support for AMD
processors will be enabled.
Symbol MICROCODE_INTEL_EARLY
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Early load microcode" if MICROCODE_INTEL && BLK_DEV_INITRD (value: "y")
Default values:
y (value: "y")
Condition: MICROCODE_INTEL && BLK_DEV_INITRD (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:1064
This option provides functionality to read additional microcode data
at the beginning of initrd image. The data tells kernel to load
microcode to CPU's as early as possible. No functional change if no
microcode data is glued to the initrd, therefore it's safe to say Y.
Symbol DEFAULT_MMAP_MIN_ADDR
Type : int
Value : "65536"
User value : "65536"
Xen config : '4096'
Main config : '4096'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Low address space to protect from user allocation" if MMU (value: "y")
Default values:
65536 (value: "n")
Condition: MMU (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../mm/Kconfig:313
This is the portion of low virtual memory which should be protected
from userspace allocation. Keeping a user from writing to low pages
can help reduce the impact of kernel NULL pointer bugs.
For most ia64, ppc64 and x86 users with lots of address space
a value of 65536 is reasonable and should cause no problems.
On arm and other archs it should not be higher than 32768.
Programs which use vm86 functionality or have some need to map
this low address space will need CAP_SYS_RAWIO or disable this
protection by setting the value to 0.
This value can be changed after boot using the
/proc/sys/vm/mmap_min_addr tunable.
Symbol TRANSPARENT_HUGEPAGE
Type : bool
Value : "n"
User value : "n"
Xen config : 'y'
Main config : 'y'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Transparent Hugepage Support" if HAVE_ARCH_TRANSPARENT_HUGEPAGE (value: "y")
Default values:
(no default values)
Selects:
COMPACTION if HAVE_ARCH_TRANSPARENT_HUGEPAGE (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../mm/Kconfig:379
Transparent Hugepages allows the kernel to use huge pages and
huge tlb transparently to the applications whenever possible.
This feature can improve computing performance to certain
applications by speeding up page faults during memory
allocation, by reducing the number of tlb misses and by speeding
up the pagetable walking.
If memory constrained on embedded, you may want to say N.
Symbol CLEANCACHE
Type : bool
Value : "y"
User value : "y"
Xen config : 'y'
Main config : 'n'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable cleancache driver to cache clean pages if tmem is present"
Default values:
n (value: "n")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../mm/Kconfig:435
Cleancache can be thought of as a page-granularity victim cache
for clean pages that the kernel's pageframe replacement algorithm
(PFRA) would like to keep around, but can't since there isn't enough
memory. So when the PFRA "evicts" a page, it first attempts to use
cleancache code to put the data contained in that page into
"transcendent memory", memory that is not directly accessible or
addressable by the kernel and is of unknown and possibly
time-varying size. And when a cleancache-enabled
filesystem wishes to access a page in a file on disk, it first
checks cleancache to see if it already contains it; if it does,
the page is copied into the kernel and a disk access is avoided.
When a transcendent memory driver is available (such as zcache or
Xen transcendent memory), a significant I/O reduction
may be achieved. When none is available, all cleancache calls
are reduced to a single pointer-compare-against-NULL resulting
in a negligible performance hit.
If unsure, say Y to enable cleancache
Symbol FRONTSWAP
Type : bool
Value : "n"
User value : "n"
Xen config : 'y'
Main config : 'n'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable frontswap to cache swap pages if tmem is present" if SWAP (value: "y")
Default values:
n (value: "n")
Condition: SWAP (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../mm/Kconfig:458
Frontswap is so named because it can be thought of as the opposite
of a "backing" store for a swap device. The data is stored into
"transcendent memory", memory that is not directly accessible or
addressable by the kernel and is of unknown and possibly
time-varying size. When space in transcendent memory is available,
a significant swap I/O reduction may be achieved. When none is
available, all frontswap calls are reduced to a single pointer-
compare-against-NULL resulting in a negligible performance hit
and swap data is stored as normal on the matching swap device.
If unsure, say Y to enable frontswap.
Symbol MATH_EMULATION
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Math emulation" if X86_32 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:1419
Linux can emulate a math coprocessor (used for floating point
operations) if you don't have one. 486DX and Pentium processors have
a math coprocessor built in, 486SX and 386 do not, unless you added
a 487DX or 387, respectively. (The messages during boot time can
give you some hints here ["man dmesg"].) Everyone needs either a
coprocessor or this emulation.
If you don't have a math coprocessor, you need to say Y here; if you
say Y here even though you have a coprocessor, the coprocessor will
be used nevertheless. (This behavior can be changed with the kernel
command line option "no387", which comes handy if your coprocessor
is broken. Try "man bootparam" or see the documentation of your boot
loader (lilo or loadlin) about how to pass options to the kernel at
boot time.) This means that it is a good idea to say Y here if you
intend to use this kernel on different machines.
More information about the internals of the Linux math coprocessor
emulation can be found in <file:arch/x86/math-emu/README>.
If you are not sure, say Y; apart from resulting in a 66 KB bigger
kernel, it won't hurt.
Symbol SECCOMP
Type : bool
Value : "n"
User value : "n"
Xen config : 'y'
Main config : 'y'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable seccomp to safely compute untrusted bytecode"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:1574
This kernel feature is useful for number crunching applications
that may need to compute untrusted bytecode during their
execution. By using pipes or other transports made available to
the process as file descriptors supporting the read/write
syscalls, it's possible to isolate those applications in
their own address space using seccomp. Once seccomp is
enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
and the task is only allowed to execute a few safe syscalls
defined by each seccomp mode.
If unsure, say Y. Only embedded should say N here.
Symbol PHYSICAL_START
Type : hex
Value : "0x1000000"
User value : "0x1000000"
Xen config : '0x100000'
Main config : '0x1000000'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Physical address where the kernel is loaded" if EXPERT || CRASH_DUMP (value: "y")
Default values:
"0x1000000" (value: "n")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:1646
This gives the physical address where the kernel is loaded.
If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
bzImage will decompress itself to above physical address and
run from there. Otherwise, bzImage will run from the address where
it has been loaded by the boot loader and will ignore above physical
address.
In normal kdump cases one does not have to set/change this option
as now bzImage can be compiled as a completely relocatable image
(CONFIG_RELOCATABLE=y) and be used to load and run from a different
address. This option is mainly useful for the folks who don't want
to use a bzImage for capturing the crash dump and want to use a
vmlinux instead. vmlinux is not relocatable hence a kernel needs
to be specifically compiled to run from a specific memory area
(normally a reserved region) and this option comes handy.
So if you are using bzImage for capturing the crash dump,
leave the value here unchanged to 0x1000000 and set
CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
for capturing the crash dump change this value to start of
the reserved region. In other words, it can be set based on
the "X" value as specified in the "crashkernel=YM@XM"
command line boot parameter passed to the panic-ed
kernel. Please take a look at Documentation/kdump/kdump.txt
for more details about crash dumps.
Usage of bzImage for capturing the crash dump is recommended as
one does not have to build two kernels. Same kernel can be used
as production kernel and capture kernel. Above option should have
gone away after relocatable bzImage support is introduced. But it
is present because there are users out there who continue to use
vmlinux for dump capture. This option should go away down the
line.
Don't change this unless you know what you are doing.
Symbol PHYSICAL_ALIGN
Type : hex
Value : "0x1000000"
User value : "0x1000000"
Xen config : '0x100000'
Main config : '0x1000000'
Visibility : "y"
Processor type and features
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Ranges:
[0x200000, 0x1000000] if PAX_KERNEXEC && X86_PAE (value: "n")
[0x400000, 0x1000000] if PAX_KERNEXEC && !X86_PAE (value: "n")
[0x2000, 0x1000000]
Prompts:
"Alignment value to which kernel should be aligned" if X86_32 (value: "y")
Default values:
"0x1000000" (value: "n")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:1709
This value puts the alignment restrictions on physical address
where kernel is loaded and run from. Kernel is compiled for an
address which meets above alignment restriction.
If bootloader loads the kernel at a non-aligned address and
CONFIG_RELOCATABLE is set, kernel will move itself to nearest
address aligned to above value and run from there.
If bootloader loads the kernel at a non-aligned address and
CONFIG_RELOCATABLE is not set, kernel will ignore the run time
load address and decompress itself to the address it has been
compiled for and run from there. The address for which kernel is
compiled already meets above alignment restrictions. Hence the
end result is that kernel runs from a physical address meeting
above alignment restrictions.
Don't change this unless you know what you are doing.
Symbol SUSPEND
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Suspend to RAM and standby" if ARCH_SUSPEND_POSSIBLE (value: "y")
Default values:
y (value: "y")
Condition: ARCH_SUSPEND_POSSIBLE (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../kernel/power/Kconfig:1
Allow the system to enter sleep states in which main memory is
powered and thus its contents are preserved, such as the
suspend-to-RAM state (e.g. the ACPI S3 state).
Symbol ACPI
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ACPI (Advanced Configuration and Power Interface) Support" if !IA64_HP_SIM && (IA64 || X86) && PCI (value: "y")
Default values:
y (value: "y")
Condition: !IA64_HP_SIM && (IA64 || X86) && PCI (value: "y")
Selects:
PNP if !IA64_HP_SIM && (IA64 || X86) && PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/acpi/Kconfig:5
Advanced Configuration and Power Interface (ACPI) support for
Linux requires an ACPI-compliant platform (hardware/firmware),
and assumes the presence of OS-directed configuration and power
management (OSPM) software. This option will enlarge your
kernel by about 70K.
Linux ACPI provides a robust functional replacement for several
legacy configuration and power management interfaces, including
the Plug-and-Play BIOS specification (PnP BIOS), the
MultiProcessor Specification (MPS), and the Advanced Power
Management (APM) specification. If both ACPI and APM support
are configured, ACPI is used.
The project home page for the Linux ACPI subsystem is here:
<http://www.lesswatts.org/projects/acpi/>
Linux support for ACPI is based on Intel Corporation's ACPI
Component Architecture (ACPI CA). For more information on the
ACPI CA, see:
<http://acpica.org/>
ACPI is an open industry specification co-developed by
Hewlett-Packard, Intel, Microsoft, Phoenix, and Toshiba.
The specification is available at:
<http://www.acpi.info>
Symbol ACPI_PROCFS
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Deprecated /proc/acpi files" if PROC_FS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:46
For backwards compatibility, this option allows
deprecated /proc/acpi/ files to exist, even when
they have been replaced by functions in /sys.
This option has no effect on /proc/acpi/ files
and functions which do not yet exist in /sys.
Say N to delete /proc/acpi/ files that have moved to /sys/
Symbol ACPI_PROCFS_POWER
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Deprecated power /proc/acpi directories" if PROC_FS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:59
For backwards compatibility, this option allows
deprecated power /proc/acpi/ directories to exist, even when
they have been replaced by functions in /sys.
The deprecated directories (and their replacements) include:
/proc/acpi/battery/* (/sys/class/power_supply/*)
/proc/acpi/ac_adapter/* (sys/class/power_supply/*)
This option has no effect on /proc/acpi/ directories
and functions, which do not yet exist in /sys
This option, together with the proc directories, will be
deleted in 2.6.39.
Say N to delete power /proc/acpi/ directories that have moved to /sys/
Symbol ACPI_EC_DEBUGFS
Type : tristate
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"EC read/write access through /sys/kernel/debug/ec"
Default values:
n (value: "n")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:76
Say N to disable Embedded Controller /sys/kernel/debug interface
Be aware that using this interface can confuse your Embedded
Controller in a way that a normal reboot is not enough. You then
have to power off your system, and remove the laptop battery for
some seconds.
An Embedded Controller typically is available on laptops and reads
sensor values like battery state and temperature.
The kernel accesses the EC through ACPI parsed code provided by BIOS
tables. This option allows to access the EC directly without ACPI
code being involved.
Thus this option is a debug option that helps to write ACPI drivers
and can be used to identify ACPI code or EC firmware bugs.
Symbol ACPI_PROC_EVENT
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Deprecated /proc/acpi/event support" if PROC_FS (value: "y")
Default values:
y (value: "y")
Condition: PROC_FS (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:94
A user-space daemon, acpid, typically reads /proc/acpi/event
and handles all ACPI-generated events.
These events are now delivered to user-space either
via the input layer or as netlink events.
This build option enables the old code for legacy
user-space implementation. After some time, this will
be moved under CONFIG_ACPI_PROCFS, and then deleted.
Say Y here to retain the old behaviour. Say N if your
user-space is newer than kernel 2.6.23 (September 2007).
Symbol ACPI_AC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AC Adapter" if X86 (value: "y")
Default values:
y (value: "y")
Condition: X86 (value: "y")
Selects:
POWER_SUPPLY if X86 (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:112
This driver supports the AC Adapter object, which indicates
whether a system is on AC or not. If you have a system that can
switch between A/C and battery, say Y.
To compile this driver as a module, choose M here:
the module will be called ac.
Symbol ACPI_BATTERY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Battery" if X86 (value: "y")
Default values:
y (value: "y")
Condition: X86 (value: "y")
Selects:
POWER_SUPPLY if X86 (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:125
This driver adds support for battery information through
/proc/acpi/battery. If you have a mobile system with a battery,
say Y.
To compile this driver as a module, choose M here:
the module will be called battery.
Symbol ACPI_BUTTON
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Button" if INPUT (value: "y")
Default values:
y (value: "y")
Condition: INPUT (value: "y")
Selects:
(no selects)
Reverse dependencies:
DRM && AGP && AGP_INTEL && ACPI && HAS_IOMEM && DRM_I915 (value: "m")
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:138
This driver handles events on the power, sleep, and lid buttons.
A daemon reads /proc/acpi/event and perform user-defined actions
such as shutting down the system. This is necessary for
software-controlled poweroff.
To compile this driver as a module, choose M here:
the module will be called button.
Symbol ACPI_FAN
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fan"
Default values:
y (value: "y")
Condition: (none)
Selects:
THERMAL
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:166
This driver supports ACPI fan devices, allowing user-mode
applications to perform basic fan control (on, off, status).
To compile this driver as a module, choose M here:
the module will be called fan.
Symbol ACPI_DOCK
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Dock"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:177
This driver supports ACPI-controlled docking stations and removable
drive bays such as the IBM Ultrabay and the Dell Module Bay.
Symbol ACPI_PROCESSOR
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Processor"
Default values:
y (value: "y")
Condition: (none)
Selects:
THERMAL
CPU_IDLE
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:189
This driver installs ACPI as the idle handler for Linux and uses
ACPI C2 and C3 processor states to save power on systems that
support it. It is required by several flavors of cpufreq
performance-state drivers.
To compile this driver as a module, choose M here:
the module will be called processor.
Symbol ACPI_PROCESSOR_AGGREGATOR
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'n'
Visibility : "m"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Processor Aggregator" if ACPI_PROCESSOR && X86 (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:220
ACPI 4.0 defines processor Aggregator, which enables OS to perform
specific processor configuration and control that applies to all
processors in the platform. Currently only logical processor idling
is defined, which is to reduce power consumption. This driver
supports the new device.
Symbol ACPI_THERMAL
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Thermal Zone" if ACPI_PROCESSOR (value: "m")
Default values:
y (value: "y")
Condition: ACPI_PROCESSOR (value: "m")
Selects:
THERMAL if ACPI_PROCESSOR (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:231
This driver supports ACPI thermal zones. Most mobile and
some desktop systems support ACPI thermal zones. It is HIGHLY
recommended that this option be enabled, as your processor(s)
may be damaged without it.
To compile this driver as a module, choose M here:
the module will be called thermal.
Symbol ACPI_BLACKLIST_YEAR
Type : int
Value : "0"
User value : "0"
Xen config : ''
Main config : '0'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Disable ACPI for systems before Jan 1st this year" if X86_32 (value: "y")
Default values:
0 (value: "n")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:278
Enter a 4-digit year, e.g., 2001, to disable ACPI by default
on platforms with DMI BIOS date before January 1st that year.
"acpi=force" can be used to override this mechanism.
Enter 0 to disable this mechanism and allow ACPI to
run by default no matter what the year. (default)
Symbol ACPI_PCI_SLOT
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PCI slot detection driver" if SYSFS (value: "y")
Default values:
n (value: "n")
Condition: SYSFS (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:309
This driver creates entries in /sys/bus/pci/slots/ for all PCI
slots in the system. This can help correlate PCI bus addresses,
i.e., segment/bus/device/function tuples, with physical slots in
the system. If you are unsure, say N.
Symbol X86_PM_TIMER
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Power Management Timer Support" if EXPERT && X86 (value: "y")
Default values:
y (value: "y")
Condition: X86 (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:319
The Power Management Timer is available on all ACPI-capable,
in most cases even if ACPI is unusable or blacklisted.
This timing source is not affected by power management features
like aggressive processor idling, throttling, frequency and/or
voltage scaling, unlike the commonly used Time Stamp Counter
(TSC) timing source.
You should nearly always say Y here because many modern
systems require this timer.
Symbol ACPI_SBS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Smart Battery System" if X86 (value: "y")
Default values:
(no default values)
Selects:
POWER_SUPPLY if X86 (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:364
This driver supports the Smart Battery System, another
type of access to battery information, found on some laptops.
To compile this driver as a module, choose M here:
the modules will be called sbs and sbshc.
Symbol ACPI_HED
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Hardware Error Device"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
ACPI_APEI && X86 && ACPI && ACPI_APEI_GHES (value: "n")
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/Kconfig:375
This driver supports the Hardware Error Device (PNP0C33),
which is used to report some hardware errors notified via
SCI, mainly the corrected errors.
Symbol ACPI_APEI
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ACPI Platform Error Interface (APEI)" if X86 (value: "y")
Default values:
(no default values)
Selects:
MISC_FILESYSTEMS if X86 (value: "y")
PSTORE if X86 (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/apei/Kconfig:1
APEI allows to report errors (for example from the chipset)
to the operating system. This improves NMI handling
especially. In addition it supports error serialization and
error injection.
Symbol ACPI_APEI_EINJ
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"APEI Error INJection (EINJ)" if ACPI_APEI && DEBUG_FS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/apei/Kconfig:42
EINJ provides a hardware error injection mechanism, it is
mainly used for debugging and testing the other parts of
APEI and some other RAS features.
Symbol ACPI_APEI_ERST_DEBUG
Type : tristate
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"APEI Error Record Serialization Table (ERST) Debug Support" if ACPI_APEI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI (value: "y")
Locations: ../drivers/acpi/apei/Kconfig:50
ERST is a way provided by APEI to save and retrieve hardware
error information to and from a persistent store. Enable this
if you want to debugging and testing the ERST kernel support
and firmware implementation.
Symbol CPU_FREQ
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
CPU Frequency scaling
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CPU Frequency scaling"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/cpufreq/Kconfig:3
CPU Frequency scaling allows you to change the clock speed of
CPUs on the fly. This is a nice method to save power, because
the lower the CPU clock speed, the less power the CPU consumes.
Note that this driver doesn't automatically change the CPU
clock speed, you need to either enable a dynamic cpufreq governor
(see below) after boot, or use a userspace tool.
For details, take a look at <file:Documentation/cpu-freq>.
If in doubt, say N.
Symbol CPU_IDLE
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CPU idle PM support"
Default values:
y (value: "y")
Condition: ACPI || PPC_PSERIES (value: "y")
Selects:
(no selects)
Reverse dependencies:
ACPI_PROCESSOR && ACPI (value: "m")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/cpuidle/Kconfig:2
CPU idle is a generic framework for supporting software-controlled
idle processor power management. It includes modular cross-platform
governors that can be swapped during runtime.
If you're using an ACPI-enabled platform, you should say Y here.
Symbol INTEL_IDLE
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Power management and ACPI options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Cpuidle Driver for Intel Processors" if CPU_IDLE && X86 && CPU_SUP_INTEL (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/idle/Kconfig:1
Enable intel_idle, a cpuidle driver that includes knowledge of
native Intel hardware idle features. The acpi_idle driver
can be configured at the same time, in order to handle
processors intel_idle does not support.
Symbol PCI_CNB20LE_QUIRK
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Read CNB20LE Host Bridge Windows" if EXPERT && PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../arch/x86/Kconfig:2085
Read the PCI windows out of the CNB20LE host bridge. This allows
PCI hotplug to work on systems with the CNB20LE chipset which do
not have ACPI.
There's no public spec for this chipset, and this functionality
is known to be incomplete.
You should say N unless you know you need this.
Symbol PCIEPORTBUS
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PCI Express support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/pci/pcie/Kconfig:4
This automatically enables PCI Express Port Bus support. Users can
choose Native Hot-Plug support, Advanced Error Reporting support,
Power Management Event support and Virtual Channel support to run
on PCI Express Ports (Root or Switch).
Symbol HOTPLUG_PCI_PCIE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PCI Express Hotplug driver" if HOTPLUG_PCI && PCIEPORTBUS (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/pci/pcie/Kconfig:16
Say Y here if you have a motherboard that supports PCI Express Native
Hotplug
To compile this driver as a module, choose M here: the
module will be called pciehp.
When in doubt, say N.
Symbol PCIEASPM
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PCI Express ASPM control" if PCI && PCIEPORTBUS && EXPERT (value: "y")
Default values:
y (value: "y")
Condition: PCI && PCIEPORTBUS (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/pci/pcie/Kconfig:33
This enables OS control over PCI Express ASPM (Active State
Power Management) and Clock Power Management. ASPM supports
state L0/L0s/L1.
ASPM is initially set up by the firmware. With this option enabled,
Linux can modify this state in order to disable ASPM on known-bad
hardware or configurations and enable it when known-safe.
ASPM can be disabled or enabled at runtime via
/sys/module/pcie_aspm/parameters/policy
When in doubt, say Y.
Symbol XEN_PCIDEV_FRONTEND
Type : tristate
Value : "y"
User value : "y"
Xen config : 'm'
Main config : 'n'
Visibility : "y"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Xen PCI Frontend" if PCI && X86 && XEN (value: "y")
Default values:
y (value: "y")
Condition: PCI && X86 && XEN (value: "y")
Selects:
HOTPLUG if PCI && X86 && XEN (value: "y")
PCI_XEN if PCI && X86 && XEN (value: "y")
XEN_XENBUS_FRONTEND if PCI && X86 && XEN (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/pci/Kconfig:55
The PCI device frontend driver allows the kernel to import arbitrary
PCI devices from a PCI backend to support PCI driver domains.
Symbol PCI_IOAPIC
Type : tristate
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PCI IO-APIC hotplug support" if PCI && ACPI && HOTPLUG && X86 (value: "y")
Default values:
!X86 (value: "n")
Condition: PCI && ACPI && HOTPLUG (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/pci/Kconfig:112
Symbol SCx200
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"NatSemi SCx200 support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
X86_32 (value: "y")
Locations: ../arch/x86/Kconfig:2139
This provides basic support for National Semiconductor's
(now AMD's) Geode processors. The driver probes for the
PCI-IDs of several on-chip devices, so its a good dependency
for other scx200_* drivers.
If compiled as a module, the driver is named scx200.
Symbol SCx200HR_TIMER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"NatSemi SCx200 27MHz High-Resolution Timer Support" if SCx200 (value: "m")
Default values:
y (value: "y")
Condition: SCx200 (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
X86_32 (value: "y")
Locations: ../arch/x86/Kconfig:2149
This driver provides a clocksource built upon the on-chip
27MHz high-resolution timer. Its also a workaround for
NSC Geode SC-1100's buggy TSC, which loses time when the
processor goes idle (as is done by the scheduler). The
other workaround is idle=poll boot option.
Symbol ALIX
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PCEngines ALIX System Support (LED setup)"
Default values:
(no default values)
Selects:
GPIOLIB
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
X86_32 (value: "y")
Locations: ../arch/x86/Kconfig:2211
This option enables system support for the PCEngines ALIX.
At present this just sets up LEDs for GPIO control on
ALIX2/3/6 boards. However, other system specific setup should
get added here.
Note: You must still enable the drivers for GPIO and LED support
(GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs
Note: You have to set alix.force=1 for boards with Award BIOS.
Symbol NET5501
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Soekris Engineering net5501 System Support (LEDS, GPIO, etc)"
Default values:
(no default values)
Selects:
GPIOLIB
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
X86_32 (value: "y")
Locations: ../arch/x86/Kconfig:2225
This option enables system support for the Soekris Engineering net5501.
Symbol GEOS
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Traverse Technologies GEOS System Support (LEDS, GPIO, etc)" if DMI (value: "y")
Default values:
(no default values)
Selects:
GPIOLIB if DMI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
X86_32 (value: "y")
Locations: ../arch/x86/Kconfig:2231
This option enables system support for the Traverse Technologies GEOS.
Symbol PCCARD
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PCCard (PCMCIA/CardBus) support" if HOTPLUG (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/pcmcia/Kconfig:5
Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
computer. These are credit-card size devices such as network cards,
modems or hard drives often used with laptops computers. There are
actually two varieties of these cards: 16 bit PCMCIA and 32 bit
CardBus cards.
To compile this driver as modules, choose M here: the
module will be called pcmcia_core.
Symbol HOTPLUG_PCI
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support for PCI Hotplug" if PCI && HOTPLUG && SYSFS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/pci/hotplug/Kconfig:5
Say Y here if you have a motherboard with a PCI Hotplug controller.
This allows you to add and remove PCI cards while the machine is
powered up and running.
To compile this driver as a module, choose M here: the
module will be called pci_hotplug.
When in doubt, say N.
Symbol HOTPLUG_PCI_ACPI
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ACPI PCI Hotplug driver" if !ACPI_DOCK && ACPI || ACPI_DOCK (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HOTPLUG_PCI (value: "m")
Locations: ../drivers/pci/hotplug/Kconfig:54
Say Y here if you have a system that supports PCI Hotplug using
ACPI.
To compile this driver as a module, choose M here: the
module will be called acpiphp.
When in doubt, say N.
Symbol HOTPLUG_PCI_ACPI_IBM
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ACPI PCI Hotplug driver IBM extensions" if HOTPLUG_PCI_ACPI (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HOTPLUG_PCI (value: "m")
Locations: ../drivers/pci/hotplug/Kconfig:66
Say Y here if you have an IBM system that supports PCI Hotplug using
ACPI.
To compile this driver as a module, choose M here: the
module will be called acpiphp_ibm.
When in doubt, say N.
Symbol HOTPLUG_PCI_CPCI
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CompactPCI Hotplug driver"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HOTPLUG_PCI (value: "m")
Locations: ../drivers/pci/hotplug/Kconfig:78
Say Y here if you have a CompactPCI system card with CompactPCI
hotswap support per the PICMG 2.1 specification.
When in doubt, say N.
Symbol HOTPLUG_PCI_SHPC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Bus options (PCI etc.)
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SHPC PCI Hotplug driver"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HOTPLUG_PCI (value: "m")
Locations: ../drivers/pci/hotplug/Kconfig:111
Say Y here if you have a motherboard with a SHPC PCI Hotplug
controller.
To compile this driver as a module, choose M here: the
module will be called shpchp.
When in doubt, say N.
Symbol PACKET_DIAG
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Packet: sockets monitoring interface" if PACKET (value: "m")
Default values:
n (value: "n")
Condition: PACKET (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/packet/Kconfig:18
Support for PF_PACKET sockets monitoring interface used by the ss tool.
If unsure, say Y.
Symbol XFRM_STATISTICS
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Transformation statistics" if INET && XFRM && PROC_FS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/xfrm/Kconfig:44
This statistics is not a SNMP/MIB specification but shows
statistics about transformation error (or almost error) factor
at packet processing for developer.
If unsure, say N.
Symbol IP_PNP
Type : bool
Value : "y"
User value : "y"
Xen config : 'y'
Main config : 'n'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IP: kernel level autoconfiguration"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NET (value: "y")
Locations: ../net/ipv4/Kconfig:110
This enables automatic configuration of IP addresses of devices and
of the routing table during kernel boot, based on either information
supplied on the kernel command line or by BOOTP or RARP protocols.
You need to say Y only for diskless machines requiring network
access to boot (in which case you want to say Y to "Root file system
on NFS" as well), because all other machines configure the network
in their startup scripts.
Symbol IP_PNP_DHCP
Type : bool
Value : "y"
User value : "y"
Xen config : 'y'
Main config : 'n'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IP: DHCP support" if IP_PNP (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NET (value: "y")
Locations: ../net/ipv4/Kconfig:121
If you want your Linux box to mount its whole root file system (the
one containing the directory /) from some other computer over the
net via NFS and you want the IP address of your computer to be
discovered automatically at boot time using the DHCP protocol (a
special protocol designed for doing this job), say Y here. In case
the boot ROM of your network card was designed for booting Linux and
does DHCP itself, providing all necessary information on the kernel
command line, you can say N here.
If unsure, say Y. Note that if you want to use DHCP, a DHCP server
must be operating on your network. Read
<file:Documentation/filesystems/nfs/nfsroot.txt> for details.
Symbol IP_PNP_BOOTP
Type : bool
Value : "y"
User value : "y"
Xen config : 'y'
Main config : 'n'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IP: BOOTP support" if IP_PNP (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NET (value: "y")
Locations: ../net/ipv4/Kconfig:138
If you want your Linux box to mount its whole root file system (the
one containing the directory /) from some other computer over the
net via NFS and you want the IP address of your computer to be
discovered automatically at boot time using the BOOTP protocol (a
special protocol designed for doing this job), say Y here. In case
the boot ROM of your network card was designed for booting Linux and
does BOOTP itself, providing all necessary information on the kernel
command line, you can say N here. If unsure, say Y. Note that if you
want to use BOOTP, a BOOTP server must be operating on your network.
Read <file:Documentation/filesystems/nfs/nfsroot.txt> for details.
Symbol IP_PNP_RARP
Type : bool
Value : "y"
User value : "y"
Xen config : 'y'
Main config : 'n'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IP: RARP support" if IP_PNP (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NET (value: "y")
Locations: ../net/ipv4/Kconfig:153
If you want your Linux box to mount its whole root file system (the
one containing the directory /) from some other computer over the
net via NFS and you want the IP address of your computer to be
discovered automatically at boot time using the RARP protocol (an
older protocol which is being obsoleted by BOOTP and DHCP), say Y
here. Note that if you want to use RARP, a RARP server must be
operating on your network. Read
<file:Documentation/filesystems/nfs/nfsroot.txt> for details.
Symbol NET_IPVTI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Virtual (secure) IP: tunneling" if INET_XFRM_MODE_TUNNEL (value: "m")
Default values:
(no default values)
Selects:
INET_TUNNEL if INET_XFRM_MODE_TUNNEL (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NET (value: "y")
Locations: ../net/ipv4/Kconfig:313
Tunneling means encapsulating data of one protocol type within
another protocol and sending it over a channel that understands the
encapsulating protocol. This can be used with xfrm mode tunnel to give
the notion of a secure tunnel for IPSEC and then use routing protocol
on top.
Symbol IPV6_GRE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IPv6: GRE tunnel"
Default values:
(no default values)
Selects:
IPV6_TUNNEL
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NET && IPV6 (value: "m")
Locations: ../net/ipv6/Kconfig:201
Tunneling means encapsulating data of one protocol type within
another protocol and sending it over a channel that understands the
encapsulating protocol. This particular tunneling driver implements
GRE (Generic Routing Encapsulation) and at this time allows
encapsulating of IPv4 or IPv6 over existing IPv6 infrastructure.
This driver is useful if the other endpoint is a Cisco router: Cisco
likes GRE much better than the other Linux tunneling driver ("IP
tunneling" above). In addition, GRE allows multicast redistribution
through the tunnel.
Saying M here will produce a module called ip6_gre. If unsure, say N.
Symbol NETWORK_PHY_TIMESTAMPING
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Timestamping in PHY devices"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/Kconfig:91
This allows timestamping of network packets by PHYs with
hardware timestamping capabilities. This option adds some
overhead in the transmit and receive paths.
If you are unsure how to answer this question, answer N.
Symbol NETFILTER
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Network packet filtering framework (Netfilter)"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/Kconfig:100
Netfilter is a framework for filtering and mangling network packets
that pass through your Linux box.
The most common use of packet filtering is to run your Linux box as
a firewall protecting a local network from the Internet. The type of
firewall provided by this kernel support is called a "packet
filter", which means that it can reject individual network packets
based on type, source, destination etc. The other kind of firewall,
a "proxy-based" one, is more secure but more intrusive and more
bothersome to set up; it inspects the network traffic much more
closely, modifies it and has knowledge about the higher level
protocols, which a packet filter lacks. Moreover, proxy-based
firewalls often require changes to the programs running on the local
clients. Proxy-based firewalls don't need support by the kernel, but
they are often combined with a packet filter, which only works if
you say Y here.
You should also say Y here if you intend to use your Linux box as
the gateway to the Internet for a local network of machines without
globally valid IP addresses. This is called "masquerading": if one
of the computers on your local network wants to send something to
the outside, your box can "masquerade" as that computer, i.e. it
forwards the traffic to the intended outside destination, but
modifies the packets to make it look like they came from the
firewall box itself. It works both ways: if the outside host
replies, the Linux box will silently forward the traffic to the
correct local computer. This way, the computers on your local net
are completely invisible to the outside world, even though they can
reach the outside and can receive replies. It is even possible to
run globally visible servers from within a masqueraded local network
using a mechanism called portforwarding. Masquerading is also often
called NAT (Network Address Translation).
Another use of Netfilter is in transparent proxying: if a machine on
the local network tries to connect to an outside host, your Linux
box can transparently forward the traffic to a local server,
typically a caching proxy server.
Yet another use of Netfilter is building a bridging firewall. Using
a bridge with Network packet filtering enabled makes iptables "see"
the bridged traffic. For filtering on the lower network and Ethernet
protocols over the bridge, use ebtables (under bridge netfilter
configuration).
Various modules exist for netfilter which replace the previous
masquerading (ipmasqadm), packet filtering (ipchains), transparent
proxying, and portforwarding mechanisms. Please see
<file:Documentation/Changes> under "iptables" for the location of
these packages.
Symbol NETFILTER_ADVANCED
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Advanced netfilter configuration" if NETFILTER (value: "y")
Default values:
y (value: "y")
Condition: NETFILTER (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET (value: "y")
Locations: ../net/Kconfig:162
If you say Y here you can select between all the netfilter modules.
If you say N the more unusual ones will not be shown and the
basic ones needed by most people will default to 'M'.
If unsure, say Y.
Symbol BRIDGE_NETFILTER
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Bridged IP/ARP packets filtering" if BRIDGE && NETFILTER && INET && NETFILTER_ADVANCED (value: "m")
Default values:
y (value: "y")
Condition: BRIDGE && NETFILTER && INET && NETFILTER_ADVANCED (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET (value: "y")
Locations: ../net/Kconfig:173
Enabling this option will let arptables resp. iptables see bridged
ARP resp. IP traffic. If you want a bridging firewall, you probably
want this option enabled.
Enabling or disabling this option doesn't enable or disable
ebtables.
If unsure, say N.
Symbol NETFILTER_NETLINK_ACCT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Netfilter NFACCT over NFNETLINK interface" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NETFILTER_NETLINK if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES && NETFILTER_ADVANCED && NETFILTER_XT_MATCH_NFACCT (value: "m")
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET (value: "y")
Locations: ../net/netfilter/Kconfig:7
If this option is enabled, the kernel will include support
for extended accounting via NFNETLINK.
Symbol NETFILTER_NETLINK_QUEUE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Netfilter NFQUEUE over NFNETLINK interface" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NETFILTER_NETLINK if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES && NETFILTER_ADVANCED && NETFILTER_XT_TARGET_NFQUEUE (value: "m")
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET (value: "y")
Locations: ../net/netfilter/Kconfig:15
If this option is enabled, the kernel will include support
for queueing packets via NFNETLINK.
Symbol NETFILTER_NETLINK_LOG
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Netfilter LOG over NFNETLINK interface"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
NETFILTER_NETLINK
Reverse dependencies:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES && NETFILTER_XT_TARGET_NFLOG (value: "m")
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET (value: "y")
Locations: ../net/netfilter/Kconfig:23
If this option is enabled, the kernel will include support
for logging packets via NFNETLINK.
This obsoletes the existing ipt_ULOG and ebg_ulog mechanisms,
and is also scheduled to replace the old syslog-based ipt_LOG
and ip6t_LOG modules.
Symbol NF_CONNTRACK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Netfilter connection tracking support"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET (value: "y")
Locations: ../net/netfilter/Kconfig:35
Connection tracking keeps a record of what packets have passed
through your machine, in order to figure out how they are related
into connections.
This is required to do Masquerading or other kinds of Network
Address Translation. It can also be used to enhance packet
filtering (see `Connection state match support' below).
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_CONNTRACK_SECMARK
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Connection tracking security mark support" if NETWORK_SECMARK (value: "y")
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n && NETWORK_SECMARK (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:60
This option enables security markings to be applied to
connections. Typically they are copied to connections from
packets using the CONNSECMARK target and copied back from
connections to packets with the same target, with the packets
being originally labeled via SECMARK.
If unsure, say 'N'.
Symbol NF_CONNTRACK_ZONES
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Connection tracking zones" if NETFILTER_ADVANCED && NETFILTER_XT_TARGET_CT (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:73
This option enables support for connection tracking zones.
Normally, each connection needs to have a unique system wide
identity. Connection tracking zones allow to have multiple
connections using the same identity, as long as they are
contained in different zones.
If unsure, say `N'.
Symbol NF_CONNTRACK_PROCFS
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Supply CT list in procfs (OBSOLETE)" if PROC_FS (value: "y")
Default values:
y (value: "y")
Condition: PROC_FS (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:86
This option enables for the list of known conntrack entries
to be shown in procfs under net/netfilter/nf_conntrack. This
is considered obsolete in favor of using the conntrack(8)
tool which uses Netlink.
Symbol NF_CONNTRACK_EVENTS
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Connection tracking events" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:96
If this option is enabled, the connection tracking code will
provide a notifier chain that can be used by other kernel code
to get notified about changes in the connection tracking state.
If unsure, say `N'.
Symbol NF_CONNTRACK_TIMEOUT
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Connection tracking timeout" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:106
This option enables support for connection tracking timeout
extension. This allows you to attach timeout policies to flow
via the CT target.
If unsure, say `N'.
Symbol NF_CONNTRACK_TIMESTAMP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Connection tracking timestamping" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:116
This option enables support for connection tracking timestamping.
This allows you to store the flow start-time and to obtain
the flow-stop time (once it has been destroyed) via Connection
tracking events.
If unsure, say `N'.
Symbol NF_CT_PROTO_DCCP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"DCCP protocol connection tracking support" if NETFILTER_ADVANCED (value: "y")
Default values:
IP_DCCP (value: "m")
Condition: NETFILTER_ADVANCED (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:133
With this option enabled, the layer 3 independent connection
tracking code will be able to do state tracking on DCCP connections.
If unsure, say 'N'.
Symbol NF_CT_PROTO_SCTP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCTP protocol connection tracking support" if NETFILTER_ADVANCED (value: "y")
Default values:
IP_SCTP (value: "m")
Condition: NETFILTER_ADVANCED (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:146
With this option enabled, the layer 3 independent connection
tracking code will be able to do state tracking on SCTP connections.
If you want to compile it as a module, say M here and read
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
Symbol NF_CT_PROTO_UDPLITE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"UDP-Lite protocol connection tracking support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:157
With this option enabled, the layer 3 independent connection
tracking code will be able to do state tracking on UDP-Lite
connections.
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_CONNTRACK_AMANDA
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Amanda backup protocol support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
TEXTSEARCH if NETFILTER_ADVANCED (value: "y")
TEXTSEARCH_KMP if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:167
If you are running the Amanda backup package <http://www.amanda.org/>
on this machine or machines that will be MASQUERADED through this
machine, then you may want to enable this feature. This allows the
connection tracking and natting code to allow the sub-channels that
Amanda requires for communication of the backup data, messages and
index.
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_CONNTRACK_FTP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"FTP protocol support"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:182
Tracking FTP connections is problematic: special helpers are
required for tracking them, and doing masquerading and other forms
of Network Address Translation on them.
This is FTP support on Layer 3 independent connection tracking.
Layer 3 independent connection tracking is experimental scheme
which generalize ip_conntrack to support other layer 3 protocols.
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_CONNTRACK_H323
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"H.323 protocol support" if (IPV6 || IPV6 = n) && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:196
H.323 is a VoIP signalling protocol from ITU-T. As one of the most
important VoIP protocols, it is widely used by voice hardware and
software including voice gateways, IP phones, Netmeeting, OpenPhone,
Gnomemeeting, etc.
With this module you can support H.323 on a connection tracking/NAT
firewall.
This module supports RAS, Fast Start, H.245 Tunnelling, Call
Forwarding, RTP/RTCP and T.120 based audio, video, fax, chat,
whiteboard, file transfer, etc. For more information, please
visit http://nath323.sourceforge.net/.
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_CONNTRACK_IRC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IRC protocol support"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:216
There is a commonly-used extension to IRC called
Direct Client-to-Client Protocol (DCC). This enables users to send
files to each other, and also chat to each other without the need
of a server. DCC Sending is used anywhere you send files over IRC,
and DCC Chat is most commonly used by Eggdrop bots. If you are
using NAT, this extension will enable you to send files and initiate
chats. Note that you do NOT need this extension to get files or
have others initiate chats, or everything else in IRC.
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_CONNTRACK_NETBIOS_NS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"NetBIOS name service protocol support"
Default values:
(no default values)
Selects:
NF_CONNTRACK_BROADCAST
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:234
NetBIOS name service requests are sent as broadcast messages from an
unprivileged port and responded to with unicast messages to the
same port. This make them hard to firewall properly because connection
tracking doesn't deal with broadcasts. This helper tracks locally
originating NetBIOS name service requests and the corresponding
responses. It relies on correct IP address configuration, specifically
netmask and broadcast address. When properly configured, the output
of "ip address show" should look similar to this:
$ ip -4 address show eth0
4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
inet 172.16.2.252/24 brd 172.16.2.255 scope global eth0
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_CONNTRACK_SNMP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SNMP service protocol support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NF_CONNTRACK_BROADCAST if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:253
SNMP service requests are sent as broadcast messages from an
unprivileged port and responded to with unicast messages to the
same port. This make them hard to firewall properly because connection
tracking doesn't deal with broadcasts. This helper tracks locally
originating SNMP service requests and the corresponding
responses. It relies on correct IP address configuration, specifically
netmask and broadcast address.
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_CONNTRACK_PPTP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PPtP protocol support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NF_CT_PROTO_GRE if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:268
This module adds support for PPTP (Point to Point Tunnelling
Protocol, RFC2637) connection tracking and NAT.
If you are running PPTP sessions over a stateful firewall or NAT
box, you may want to enable this feature.
Please note that not all PPTP modes of operation are supported yet.
Specifically these limitations exist:
- Blindly assumes that control connections are always established
in PNS->PAC direction. This is a violation of RFC2637.
- Only supports a single call within each session
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_CONNTRACK_SANE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SANE protocol support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:287
SANE is a protocol for remote access to scanners as implemented
by the 'saned' daemon. Like FTP, it uses separate control and
data connections.
With this module you can support SANE on a connection tracking
firewall.
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_CONNTRACK_SIP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SIP protocol support"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:300
SIP is an application-layer control protocol that can establish,
modify, and terminate multimedia sessions (conferences) such as
Internet telephony calls. With the ip_conntrack_sip and
the nf_nat_sip modules you can support the protocol on a connection
tracking/NATing firewall.
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_CONNTRACK_TFTP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"TFTP protocol support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:312
TFTP connection tracking helper, this is required depending
on how restrictive your ruleset is.
If you are using a tftp client behind -j SNAT or -j MASQUERADING
you will need this.
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_CT_NETLINK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Connection tracking netlink interface"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
NETFILTER_NETLINK
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:323
This option enables support for a netlink-based userspace interface
Symbol NF_CT_NETLINK_TIMEOUT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Connection tracking timeout tuning via Netlink" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NETFILTER_NETLINK if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NF_CONNTRACK (value: "m")
Locations: ../net/netfilter/Kconfig:330
This option enables support for connection tracking timeout
fine-grain tuning. This allows you to attach specific timeout
policies to flows, instead of using the global timeout policy.
If unsure, say `N'.
Symbol NETFILTER_TPROXY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Transparent proxying support" if IP_NF_MANGLE && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET (value: "y")
Locations: ../net/netfilter/Kconfig:414
This option enables transparent proxying support, that is,
support for handling non-locally bound IPv4 TCP and UDP sockets.
For it to work you will have to configure certain iptables rules
and use policy routing. For more information on how to set it up
see Documentation/networking/tproxy.txt.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XTABLES
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Netfilter Xtables support (required for ip_tables)"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
(no selects)
Reverse dependencies:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES || INET && NETFILTER && NETFILTER && NET && NETFILTER_ADVANCED && IP_NF_ARPTABLES || INET && IPV6 && INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES || BRIDGE && NETFILTER && NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET (value: "y")
Locations: ../net/netfilter/Kconfig:427
This is required if you intend to use any of ip_tables,
ip6_tables or arp_tables.
Symbol NETFILTER_XT_SET
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"set target and match support" if IP_SET && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:465
This option adds the "SET" target and "set" match.
Using this target and match, you can add/delete and match
elements in the sets created by ipset(8).
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_TARGET_CHECKSUM
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CHECKSUM target support" if (IP_NF_MANGLE || IP6_NF_MANGLE) && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:491
This option adds a `CHECKSUM' target, which can be used in the iptables mangle
table.
You can use this target to compute and fill in the checksum in
a packet that lacks a checksum. This is particularly useful,
if you need to work around old applications such as dhcp clients,
that do not work well with checksum offloads, but don't want to disable
checksum offload in your device.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_TARGET_CLASSIFY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""CLASSIFY" target support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:507
This option adds a `CLASSIFY' target, which enables the user to set
the priority of a packet. Some qdiscs can use this value for
classification, among these are:
atm, cbq, dsmark, pfifo_fast, htb, prio
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_TARGET_CONNMARK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""CONNMARK" target support" if NF_CONNTRACK && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
NETFILTER_XT_CONNMARK if NF_CONNTRACK && NETFILTER_ADVANCED (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:519
This is a backwards-compat option for the user's convenience
(e.g. when running oldconfig). It selects
CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
Symbol NETFILTER_XT_TARGET_CONNSECMARK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""CONNSECMARK" target support" if NF_CONNTRACK && NF_CONNTRACK_SECMARK (value: "m")
Default values:
m (value: "m")
Condition: NF_CONNTRACK && NF_CONNTRACK_SECMARK && NETFILTER_ADVANCED = n (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:529
The CONNSECMARK target copies security markings from packets
to connections, and restores security markings from connections
to packets (if the packets are not already marked). This would
normally be used in conjunction with the SECMARK target.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_TARGET_DSCP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""DSCP" and "TOS" target support" if (IP_NF_MANGLE || IP6_NF_MANGLE) && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:553
This option adds a `DSCP' target, which allows you to manipulate
the IPv4/IPv6 header DSCP field (differentiated services codepoint).
The DSCP field can have any value between 0x0 and 0x3f inclusive.
It also adds the "TOS" target, which allows you to create rules in
the "mangle" table which alter the Type Of Service field of an IPv4
or the Priority field of an IPv6 packet, prior to routing.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_TARGET_HMARK
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""HMARK" target support" if (IP6_NF_IPTABLES || IP6_NF_IPTABLES = n) && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:584
This option adds the "HMARK" target.
The target allows you to create rules in the "raw" and "mangle" tables
which set the skbuff mark by means of hash calculation within a given
range. The nfmark can influence the routing method (see "Use netfilter
MARK value as routing key") and can also be used by other subsystems to
change their behaviour.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_TARGET_IDLETIMER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IDLETIMER target support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:599
This option adds the `IDLETIMER' target. Each matching packet
resets the timer associated with label specified when the rule is
added. When the timer expires, it triggers a sysfs notification.
The remaining time for expiration can be read via sysfs.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_TARGET_LOG
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"LOG target support"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:635
This option adds a `LOG' target, which allows you to create rules in
any iptables table which records the packet header to the syslog.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_TARGET_MARK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""MARK" target support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NETFILTER_XT_MARK if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:644
This is a backwards-compat option for the user's convenience
(e.g. when running oldconfig). It selects
CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
Symbol NETFILTER_XT_TARGET_NFLOG
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""NFLOG" target support"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
NETFILTER_NETLINK_LOG
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:663
This option enables the NFLOG target, which allows to LOG
messages through nfnetlink_log.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_TARGET_NFQUEUE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""NFQUEUE" target Support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NETFILTER_NETLINK_QUEUE if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:673
This target replaced the old obsolete QUEUE target.
As opposed to QUEUE, it supports 65535 different queues,
not just one.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_TARGET_NOTRACK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""NOTRACK" target support (DEPRECATED)" if NF_CONNTRACK && (IP_NF_RAW || IP6_NF_RAW) && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
NETFILTER_XT_TARGET_CT if NF_CONNTRACK && (IP_NF_RAW || IP6_NF_RAW) && NETFILTER_ADVANCED (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:685
Symbol NETFILTER_XT_TARGET_TEE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""TEE" - packet cloning to alternate destination" if NETFILTER_ADVANCED && (IPV6 || IPV6 = n) && (!NF_CONNTRACK || NF_CONNTRACK) (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:713
This option adds a "TEE" target with which a packet can be cloned and
this clone be rerouted to another nexthop.
Symbol NETFILTER_XT_TARGET_TPROXY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""TPROXY" target support" if NETFILTER_TPROXY && NETFILTER_XTABLES && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
NF_DEFRAG_IPV4 if NETFILTER_TPROXY && NETFILTER_XTABLES && NETFILTER_ADVANCED (value: "m")
NF_DEFRAG_IPV6 if NETFILTER_TPROXY && NETFILTER_XTABLES && NETFILTER_ADVANCED && IP6_NF_IPTABLES (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:722
This option adds a `TPROXY' target, which is somewhat similar to
REDIRECT. It can only be used in the mangle table and is useful
to redirect traffic to a transparent proxy. It does _not_ depend
on Netfilter connection tracking and NAT, unlike REDIRECT.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_TARGET_TRACE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""TRACE" target support" if (IP_NF_RAW || IP6_NF_RAW) && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:737
The TRACE target allows you to mark packets so that the kernel
will log every rule which match the packets as those traverse
the tables, chains, rules.
If you want to compile it as a module, say M here and read
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
Symbol NETFILTER_XT_TARGET_SECMARK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""SECMARK" target support" if NETWORK_SECMARK (value: "y")
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n && NETWORK_SECMARK (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:749
The SECMARK target allows security marking of network
packets, for use with security subsystems.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_TARGET_TCPMSS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""TCPMSS" target support" if IPV6 || IPV6 = n (value: "m")
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n && (IPV6 || IPV6 = n) (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:759
This option adds a `TCPMSS' target, which allows you to alter the
MSS value of TCP SYN packets, to control the maximum size for that
connection (usually limiting it to your outgoing interface's MTU
minus 40).
This is used to overcome criminally braindead ISPs or servers which
block ICMP Fragmentation Needed packets. The symptoms of this
problem are that everything works fine from your Linux
firewall/router, but machines behind it can never exchange large
packets:
1) Web browsers connect, then hang with no data received.
2) Small mail works fine, but large emails hang.
3) ssh works fine, but scp hangs after initial handshaking.
Workaround: activate this option and add a rule to your firewall
configuration like:
iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_TARGET_TCPOPTSTRIP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""TCPOPTSTRIP" target support" if (IP_NF_MANGLE || IP6_NF_MANGLE) && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:785
This option adds a "TCPOPTSTRIP" target, which allows you to strip
TCP options from TCP packets.
Symbol NETFILTER_XT_MATCH_ADDRTYPE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""addrtype" address type match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:797
This option allows you to match what routing thinks of an address,
eg. UNICAST, LOCAL, BROADCAST, ...
If you want to compile it as a module, say M here and read
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
Symbol NETFILTER_XT_MATCH_BPF
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""bpf" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:807
BPF matching applies a linux socket filter to each packet and
accepts those for which the filter returns non-zero.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_CLUSTER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""cluster" match support" if NF_CONNTRACK && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:816
This option allows you to build work-load-sharing clusters of
network servers/stateful firewalls without having a dedicated
load-balancing router/server/switch. Basically, this match returns
true when the packet must be handled by this cluster node. Thus,
all nodes see all packets and this match decides which node handles
what packets. The work-load sharing algorithm is based on source
address hashing.
If you say Y or M here, try `iptables -m cluster --help` for
more information.
Symbol NETFILTER_XT_MATCH_COMMENT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""comment" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:832
This option adds a `comment' dummy-match, which allows you to put
comments in your iptables ruleset.
If you want to compile it as a module, say M here and read
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
Symbol NETFILTER_XT_MATCH_CONNBYTES
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""connbytes" per-connection counter match support" if NF_CONNTRACK && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:842
This option adds a `connbytes' match, which allows you to match the
number of bytes and/or packets for each direction within a connection.
If you want to compile it as a module, say M here and read
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
Symbol NETFILTER_XT_MATCH_CONNLABEL
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""connlabel" match support" if NF_CONNTRACK && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
NF_CONNTRACK_LABELS if NF_CONNTRACK && NETFILTER_ADVANCED (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:853
This match allows you to test and assign userspace-defined labels names
to a connection. The kernel only stores bit values - mapping
names to bits is done by userspace.
Unlike connmark, more than 32 flag bits may be assigned to a
connection simultaneously.
Symbol NETFILTER_XT_MATCH_CONNLIMIT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""connlimit" match support"" if NF_CONNTRACK && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:866
This match allows you to match against the number of parallel
connections to a server per client IP address (or address block).
Symbol NETFILTER_XT_MATCH_CONNMARK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""connmark" connection mark match support" if NF_CONNTRACK && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
NETFILTER_XT_CONNMARK if NF_CONNTRACK && NETFILTER_ADVANCED (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:874
This is a backwards-compat option for the user's convenience
(e.g. when running oldconfig). It selects
CONFIG_NETFILTER_XT_CONNMARK (combined connmark/CONNMARK module).
Symbol NETFILTER_XT_MATCH_CONNTRACK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""conntrack" connection tracking match support" if NF_CONNTRACK (value: "m")
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n && NF_CONNTRACK (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:884
This is a general conntrack match module, a superset of the state match.
It allows matching on additional conntrack information, which is
useful in complex configurations, such as NAT gateways with multiple
internet links or tunnels.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_CPU
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""cpu" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:897
CPU matching allows you to match packets based on the CPU
currently handling the packet.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_DCCP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""dccp" protocol match support" if NETFILTER_ADVANCED (value: "y")
Default values:
IP_DCCP (value: "m")
Condition: NETFILTER_ADVANCED (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:906
With this option enabled, you will be able to use the iptables
`dccp' match in order to match on DCCP source/destination ports
and DCCP flags.
If you want to compile it as a module, say M here and read
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
Symbol NETFILTER_XT_MATCH_DEVGROUP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""devgroup" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:918
This options adds a `devgroup' match, which allows to match on the
device group a network device is assigned to.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_DSCP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""dscp" and "tos" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:927
This option adds a `DSCP' match, which allows you to match against
the IPv4/IPv6 header DSCP field (differentiated services codepoint).
The DSCP field can have any value between 0x0 and 0x3f inclusive.
It will also add a "tos" match, which allows you to match packets
based on the Type Of Service fields of the IPv4 packet (which share
the same bits as DSCP).
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_ESP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""esp" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:951
This match extension allows you to match a range of SPIs
inside ESP header of IPSec packets.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_HASHLIMIT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""hashlimit" match support" if (IP6_NF_IPTABLES || IP6_NF_IPTABLES = n) && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:970
This option adds a `hashlimit' match.
As opposed to `limit', this match dynamically creates a hash table
of limit buckets, based on your selection of source/destination
addresses and/or ports.
It enables you to express policies like `10kpps for any given
destination address' or `500pps from any given source address'
with a single rule.
Symbol NETFILTER_XT_MATCH_HELPER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""helper" match support" if NF_CONNTRACK && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:985
Helper matching allows you to match packets in dynamic connections
tracked by a conntrack-helper, ie. ip_conntrack_ftp
To compile it as a module, choose M here. If unsure, say Y.
Symbol NETFILTER_XT_MATCH_IPRANGE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""iprange" address range match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1003
This option adds a "iprange" match, which allows you to match based on
an IP address range. (Normal iptables only matches on single addresses
with an optional mask.)
If unsure, say M.
Symbol NETFILTER_XT_MATCH_IPVS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""ipvs" match support" if IP_VS && NETFILTER_ADVANCED && NF_CONNTRACK (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1013
This option allows you to match against IPVS properties of a packet.
If unsure, say N.
Symbol NETFILTER_XT_MATCH_LENGTH
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""length" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1023
This option allows you to match the length of a packet against a
specific value or range of values.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_LIMIT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""limit" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1032
limit matching allows you to control the rate at which a rule can be
matched: mainly useful in combination with the LOG target ("LOG
target support", below) and to avoid some Denial of Service attacks.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_MAC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""mac" address match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1042
MAC matching allows you to match packets based on the source
Ethernet address of the packet.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_MARK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""mark" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NETFILTER_XT_MARK if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1051
This is a backwards-compat option for the user's convenience
(e.g. when running oldconfig). It selects
CONFIG_NETFILTER_XT_MARK (combined mark/MARK module).
Symbol NETFILTER_XT_MATCH_MULTIPORT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""multiport" Multiple port match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1060
Multiport matching allows you to match TCP or UDP packets based on
a series of source or destination ports: normally a rule can only
match a single range of ports.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_NFACCT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""nfacct" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NETFILTER_NETLINK_ACCT if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1070
This option allows you to use the extended accounting through
nfnetlink_acct.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_OSF
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""osf" Passive OS fingerprint match" if NETFILTER_ADVANCED && NETFILTER_NETLINK (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1080
This option selects the Passive OS Fingerprinting match module
that allows to passively match the remote operating system by
analyzing incoming TCP SYN packets.
Rules and loading software can be downloaded from
http://www.ioremap.net/projects/osf
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_OWNER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""owner" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1093
Socket owner matching allows you to match locally-generated packets
based on who created the socket: the user or group. It is also
possible to check whether a socket actually exists.
Symbol NETFILTER_XT_MATCH_POLICY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IPsec "policy" match support" if XFRM (value: "y")
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n && XFRM (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1101
Policy matching allows you to match packets based on the
IPsec policy that was used during decapsulation/will
be used during encapsulation.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_PHYSDEV
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""physdev" match support" if BRIDGE && BRIDGE_NETFILTER && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1112
Physdev packet matching matches against the physical bridge ports
the IP packet arrived on or will leave by.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_PKTTYPE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""pkttype" packet type match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1122
Packet type matching allows you to match a packet by
its "class", eg. BROADCAST, MULTICAST, ...
Typical usage:
iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_QUOTA
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""quota" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1134
This option adds a `quota' match, which allows to match on a
byte counter.
If you want to compile it as a module, say M here and read
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
Symbol NETFILTER_XT_MATCH_RATEEST
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""rateest" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NETFILTER_XT_TARGET_RATEEST if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1144
This option adds a `rateest' match, which allows to match on the
rate estimated by the RATEEST target.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_REALM
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""realm" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
IP_ROUTE_CLASSID if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1154
This option adds a `realm' match, which allows you to use the realm
key from the routing subsystem inside iptables.
This match pretty much resembles the CONFIG_NET_CLS_ROUTE4 option
in tc world.
If you want to compile it as a module, say M here and read
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
Symbol NETFILTER_XT_MATCH_RECENT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""recent" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1168
This match is used for creating one or many lists of recently
used addresses and then matching against that/those list(s).
Short options are available by using 'iptables -m recent -h'
Official Website: <http://snowman.net/projects/ipt_recent/>
Symbol NETFILTER_XT_MATCH_SCTP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""sctp" protocol match support" if NETFILTER_ADVANCED (value: "y")
Default values:
IP_SCTP (value: "m")
Condition: NETFILTER_ADVANCED (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1178
With this option enabled, you will be able to use the
`sctp' match in order to match on SCTP source/destination ports
and SCTP chunk types.
If you want to compile it as a module, say M here and read
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
Symbol NETFILTER_XT_MATCH_SOCKET
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""socket" match support" if NETFILTER_TPROXY && NETFILTER_XTABLES && NETFILTER_ADVANCED && (!NF_CONNTRACK || NF_CONNTRACK) (value: "m")
Default values:
(no default values)
Selects:
NF_DEFRAG_IPV4 if NETFILTER_TPROXY && NETFILTER_XTABLES && NETFILTER_ADVANCED && (!NF_CONNTRACK || NF_CONNTRACK) (value: "m")
NF_DEFRAG_IPV6 if NETFILTER_TPROXY && NETFILTER_XTABLES && NETFILTER_ADVANCED && (!NF_CONNTRACK || NF_CONNTRACK) && IP6_NF_IPTABLES (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1190
This option adds a `socket' match, which can be used to match
packets for which a TCP or UDP socket lookup finds a valid socket.
It can be used in combination with the MARK target and policy
routing to implement full featured non-locally bound sockets.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_STATE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""state" match support" if NF_CONNTRACK (value: "m")
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n && NF_CONNTRACK (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1206
Connection state matching allows you to match packets based on their
relationship to a tracked connection (ie. previous packets). This
is a powerful tool for packet classification.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_STATISTIC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""statistic" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1217
This option adds a `statistic' match, which allows you to match
on packets periodically or randomly with a given percentage.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_STRING
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""string" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
TEXTSEARCH if NETFILTER_ADVANCED (value: "y")
TEXTSEARCH_KMP if NETFILTER_ADVANCED (value: "y")
TEXTSEARCH_BM if NETFILTER_ADVANCED (value: "y")
TEXTSEARCH_FSM if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1226
This option adds a `string' match, which allows you to look for
pattern matchings in packets.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_TCPMSS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""tcpmss" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1239
This option adds a `tcpmss' match, which allows you to examine the
MSS value of TCP SYN packets, which control the maximum packet size
for that connection.
To compile it as a module, choose M here. If unsure, say N.
Symbol NETFILTER_XT_MATCH_TIME
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""time" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1249
This option adds a "time" match, which allows you to match based on
the packet arrival time (at the machine which netfilter is running)
on) or departure time/date (for locally generated packets).
If you say Y here, try `iptables -m time --help` for
more information.
If you want to compile it as a module, say M here.
If unsure, say N.
Symbol NETFILTER_XT_MATCH_U32
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Core Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""u32" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET && INET && NETFILTER && NETFILTER && NET && NETFILTER_XTABLES (value: "m")
Locations: ../net/netfilter/Kconfig:1263
u32 allows you to extract quantities of up to 4 bytes from a packet,
AND them with specified masks, shift them by specified amounts and
test whether the results are in any of a set of specified ranges.
The specification of what to extract is general enough to skip over
headers with lengths stored in the packet, as in IP or TCP header
lengths.
Details and examples are in the kernel module source.
Symbol IP_SET
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IP set support" if INET && NETFILTER && NETFILTER_NETLINK (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET (value: "y")
Locations: ../net/netfilter/ipset/Kconfig:1
This option adds IP set support to the kernel.
In order to define and use the sets, you need the userspace utility
ipset(8). You can use the sets in netfilter via the "set" match
and "SET" target.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_SET_MAX
Type : int
Value : "256"
User value : "256"
Xen config : '2'
Main config : '256'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Ranges:
[2, 65534]
Prompts:
"Maximum number of IP sets" if IP_SET (value: "m")
Default values:
256 (value: "n")
Condition: IP_SET (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_SET (value: "m")
Locations: ../net/netfilter/ipset/Kconfig:15
You can define here default value of the maximum number
of IP sets for the kernel.
The value can be overriden by the 'max_sets' module
parameter of the 'ip_set' module.
Symbol IP_SET_BITMAP_IP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"bitmap:ip set support" if IP_SET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_SET (value: "m")
Locations: ../net/netfilter/ipset/Kconfig:27
This option adds the bitmap:ip set type support, by which one
can store IPv4 addresses (or network addresse) from a range.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_SET_BITMAP_IPMAC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"bitmap:ip,mac set support" if IP_SET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_SET (value: "m")
Locations: ../net/netfilter/ipset/Kconfig:36
This option adds the bitmap:ip,mac set type support, by which one
can store IPv4 address and (source) MAC address pairs from a range.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_SET_BITMAP_PORT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"bitmap:port set support" if IP_SET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_SET (value: "m")
Locations: ../net/netfilter/ipset/Kconfig:45
This option adds the bitmap:port set type support, by which one
can store TCP/UDP port numbers from a range.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_SET_HASH_IP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"hash:ip set support" if IP_SET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_SET (value: "m")
Locations: ../net/netfilter/ipset/Kconfig:54
This option adds the hash:ip set type support, by which one
can store arbitrary IPv4 or IPv6 addresses (or network addresses)
in a set.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_SET_HASH_IPPORT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"hash:ip,port set support" if IP_SET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_SET (value: "m")
Locations: ../net/netfilter/ipset/Kconfig:64
This option adds the hash:ip,port set type support, by which one
can store IPv4/IPv6 address and protocol/port pairs.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_SET_HASH_IPPORTIP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"hash:ip,port,ip set support" if IP_SET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_SET (value: "m")
Locations: ../net/netfilter/ipset/Kconfig:73
This option adds the hash:ip,port,ip set type support, by which
one can store IPv4/IPv6 address, protocol/port, and IPv4/IPv6
address triples in a set.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_SET_HASH_IPPORTNET
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"hash:ip,port,net set support" if IP_SET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_SET (value: "m")
Locations: ../net/netfilter/ipset/Kconfig:83
This option adds the hash:ip,port,net set type support, by which
one can store IPv4/IPv6 address, protocol/port, and IPv4/IPv6
network address/prefix triples in a set.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_SET_HASH_NET
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"hash:net set support" if IP_SET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_SET (value: "m")
Locations: ../net/netfilter/ipset/Kconfig:93
This option adds the hash:net set type support, by which
one can store IPv4/IPv6 network address/prefix elements in a set.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_SET_HASH_NETPORT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"hash:net,port set support" if IP_SET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_SET (value: "m")
Locations: ../net/netfilter/ipset/Kconfig:102
This option adds the hash:net,port set type support, by which
one can store IPv4/IPv6 network address/prefix and
protocol/port pairs as elements in a set.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_SET_HASH_NETIFACE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"hash:net,iface set support" if IP_SET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_SET (value: "m")
Locations: ../net/netfilter/ipset/Kconfig:112
This option adds the hash:net,iface set type support, by which
one can store IPv4/IPv6 network address/prefix and
interface name pairs as elements in a set.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_SET_LIST_SET
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"list:set set support" if IP_SET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_SET (value: "m")
Locations: ../net/netfilter/ipset/Kconfig:122
This option adds the list:set set type support. In this
kind of set one can store the name of other sets and it forms
an ordered union of the member sets.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_VS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IP virtual server support" if NET && INET && NETFILTER && (NF_CONNTRACK || NF_CONNTRACK = n) (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET (value: "y")
Locations: ../net/netfilter/ipvs/Kconfig:4
IP Virtual Server support will let you build a high-performance
virtual server based on cluster of two or more real servers. This
option must be enabled for at least one of the clustered computers
that will take care of intercepting incoming connections to a
single IP address and scheduling them to real servers.
Three request dispatching techniques are implemented, they are
virtual server via NAT, virtual server via tunneling and virtual
server via direct routing. The several scheduling algorithms can
be used to choose which server the connection is directed to,
thus load balancing can be achieved among the servers. For more
information and its administration program, please visit the
following URL: <http://www.linuxvirtualserver.org/>.
If you want to compile it in kernel, say Y. To compile it as a
module, choose M here. If unsure, say N.
Symbol IP_VS_IPV6
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IPv6 support for IPVS" if IPV6 = y || IP_VS = IPV6 (value: "y")
Default values:
(no default values)
Selects:
IP6_NF_IPTABLES if IPV6 = y || IP_VS = IPV6 (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:28
Add IPv6 support to IPVS.
Say Y if unsure.
Symbol IP_VS_TAB_BITS
Type : int
Value : "12"
User value : "12"
Xen config : '8'
Main config : '12'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Ranges:
[8, 20]
Prompts:
"IPVS connection table size (the Nth power of 2)"
Default values:
12 (value: "n")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:44
The IPVS connection hash table uses the chaining scheme to handle
hash collisions. Using a big IPVS connection hash table will greatly
reduce conflicts when there are hundreds of thousands of connections
in the hash table.
Note the table size must be power of 2. The table size will be the
value of 2 to the your input number power. The number to choose is
from 8 to 20, the default number is 12, which means the table size
is 4096. Don't input the number too small, otherwise you will lose
performance on it. You can adapt the table size yourself, according
to your virtual server application. It is good to set the table size
not far less than the number of connections per second multiplying
average lasting time of connection in the table. For example, your
virtual server gets 200 connections per second, the connection lasts
for 200 seconds in average in the connection table, the table size
should be not far less than 200x200, it is good to set the table
size 32768 (2**15).
Another note that each connection occupies 128 bytes effectively and
each hash entry uses 8 bytes, so you can estimate how much memory is
needed for your box.
You can overwrite this number setting conn_tab_bits module parameter
or by appending ip_vs.conn_tab_bits=? to the kernel command line
if IP VS was compiled built-in.
Symbol IP_VS_PROTO_TCP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"TCP load balancing support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:77
This option enables support for load balancing TCP transport
protocol. Say Y if unsure.
Symbol IP_VS_PROTO_UDP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"UDP load balancing support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:83
This option enables support for load balancing UDP transport
protocol. Say Y if unsure.
Symbol IP_VS_PROTO_ESP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ESP load balancing support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:92
This option enables support for load balancing ESP (Encapsulation
Security Payload) transport protocol. Say Y if unsure.
Symbol IP_VS_PROTO_AH
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AH load balancing support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:98
This option enables support for load balancing AH (Authentication
Header) transport protocol. Say Y if unsure.
Symbol IP_VS_PROTO_SCTP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCTP load balancing support"
Default values:
(no default values)
Selects:
LIBCRC32C
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:104
This option enables support for load balancing SCTP transport
protocol. Say Y if unsure.
Symbol IP_VS_RR
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"round-robin scheduling"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:113
The robin-robin scheduling algorithm simply directs network
connections to different real servers in a round-robin manner.
If you want to compile it in kernel, say Y. To compile it as a
module, choose M here. If unsure, say N.
Symbol IP_VS_WRR
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"weighted round-robin scheduling"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:122
The weighted robin-robin scheduling algorithm directs network
connections to different real servers based on server weights
in a round-robin manner. Servers with higher weights receive
new connections first than those with less weights, and servers
with higher weights get more connections than those with less
weights and servers with equal weights get equal connections.
If you want to compile it in kernel, say Y. To compile it as a
module, choose M here. If unsure, say N.
Symbol IP_VS_LC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"least-connection scheduling"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:135
The least-connection scheduling algorithm directs network
connections to the server with the least number of active
connections.
If you want to compile it in kernel, say Y. To compile it as a
module, choose M here. If unsure, say N.
Symbol IP_VS_WLC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"weighted least-connection scheduling"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:145
The weighted least-connection scheduling algorithm directs network
connections to the server with the least active connections
normalized by the server weight.
If you want to compile it in kernel, say Y. To compile it as a
module, choose M here. If unsure, say N.
Symbol IP_VS_LBLC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"locality-based least-connection scheduling"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:155
The locality-based least-connection scheduling algorithm is for
destination IP load balancing. It is usually used in cache cluster.
This algorithm usually directs packet destined for an IP address to
its server if the server is alive and under load. If the server is
overloaded (its active connection numbers is larger than its weight)
and there is a server in its half load, then allocate the weighted
least-connection server to this IP address.
If you want to compile it in kernel, say Y. To compile it as a
module, choose M here. If unsure, say N.
Symbol IP_VS_LBLCR
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"locality-based least-connection with replication scheduling"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:169
The locality-based least-connection with replication scheduling
algorithm is also for destination IP load balancing. It is
usually used in cache cluster. It differs from the LBLC scheduling
as follows: the load balancer maintains mappings from a target
to a set of server nodes that can serve the target. Requests for
a target are assigned to the least-connection node in the target's
server set. If all the node in the server set are over loaded,
it picks up a least-connection node in the cluster and adds it
in the sever set for the target. If the server set has not been
modified for the specified time, the most loaded node is removed
from the server set, in order to avoid high degree of replication.
If you want to compile it in kernel, say Y. To compile it as a
module, choose M here. If unsure, say N.
Symbol IP_VS_DH
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"destination hashing scheduling"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:187
The destination hashing scheduling algorithm assigns network
connections to the servers through looking up a statically assigned
hash table by their destination IP addresses.
If you want to compile it in kernel, say Y. To compile it as a
module, choose M here. If unsure, say N.
Symbol IP_VS_SH
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"source hashing scheduling"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:197
The source hashing scheduling algorithm assigns network
connections to the servers through looking up a statically assigned
hash table by their source IP addresses.
If you want to compile it in kernel, say Y. To compile it as a
module, choose M here. If unsure, say N.
Symbol IP_VS_SED
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"shortest expected delay scheduling"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:207
The shortest expected delay scheduling algorithm assigns network
connections to the server with the shortest expected delay. The
expected delay that the job will experience is (Ci + 1) / Ui if
sent to the ith server, in which Ci is the number of connections
on the ith server and Ui is the fixed service rate (weight)
of the ith server.
If you want to compile it in kernel, say Y. To compile it as a
module, choose M here. If unsure, say N.
Symbol IP_VS_NQ
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"never queue scheduling"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:220
The never queue scheduling algorithm adopts a two-speed model.
When there is an idle server available, the job will be sent to
the idle server, instead of waiting for a fast one. When there
is no idle server available, the job will be sent to the server
that minimize its expected delay (The Shortest Expected Delay
scheduling algorithm).
If you want to compile it in kernel, say Y. To compile it as a
module, choose M here. If unsure, say N.
Symbol IP_VS_SH_TAB_BITS
Type : int
Value : "8"
User value : "8"
Xen config : '4'
Main config : '8'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Ranges:
[4, 20]
Prompts:
"IPVS source hashing table size (the Nth power of 2)"
Default values:
8 (value: "n")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:235
The source hashing scheduler maps source IPs to destinations
stored in a hash table. This table is tiled by each destination
until all slots in the table are filled. When using weights to
allow destinations to receive more connections, the table is
tiled an amount proportional to the weights specified. The table
needs to be large enough to effectively fit all the destinations
multiplied by their respective weights.
Symbol IP_VS_NFCT
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Netfilter connection tracking" if NF_CONNTRACK (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
IP_VS_PROTO_TCP && NF_CONNTRACK && NF_NAT && NF_CONNTRACK_FTP && NETFILTER && NET && IP_VS && IP_VS_FTP (value: "n")
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:265
The Netfilter connection tracking support allows the IPVS
connection state to be exported to the Netfilter framework
for filtering purposes.
Symbol IP_VS_PE_SIP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SIP persistence engine" if IP_VS_PROTO_UDP && NF_CONNTRACK_SIP (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && IP_VS (value: "m")
Locations: ../net/netfilter/ipvs/Kconfig:273
Allow persistence based on the SIP Call-ID
Symbol NF_CONNTRACK_IPV4
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IPv4 connection tracking support (required for NAT)" if NF_CONNTRACK (value: "m")
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n && NF_CONNTRACK (value: "n")
Selects:
NF_DEFRAG_IPV4 if NF_CONNTRACK (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET (value: "y")
Locations: ../net/ipv4/netfilter/Kconfig:12
Connection tracking keeps a record of what packets have passed
through your machine, in order to figure out how they are related
into connections.
This is IPv4 support on Layer 3 independent connection tracking.
Layer 3 independent connection tracking is experimental scheme
which generalize ip_conntrack to support other layer 3 protocols.
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_CONNTRACK_PROC_COMPAT
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"proc/sysctl compatibility with old connection tracking" if NF_CONNTRACK_PROCFS && NF_CONNTRACK_IPV4 (value: "m")
Default values:
y (value: "y")
Condition: NF_CONNTRACK_PROCFS && NF_CONNTRACK_IPV4 (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET (value: "y")
Locations: ../net/ipv4/netfilter/Kconfig:28
This option enables /proc and sysctl compatibility with the old
layer 3 dependent connection tracking. This is needed to keep
old programs that have not been adapted to the new names working.
If unsure, say Y.
Symbol IP_NF_IPTABLES
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IP tables support (required for filtering/masq/NAT)"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
NETFILTER_XTABLES
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET (value: "y")
Locations: ../net/ipv4/netfilter/Kconfig:39
iptables is a general, extensible packet identification framework.
The packet filtering and full NAT (masquerading, port forwarding,
etc) subsystems now use this: say `Y' or `M' here if you want to use
either of those.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_NF_MATCH_AH
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""ah" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:54
This match extension allows you to match a range of SPIs
inside AH header of IPSec packets.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_NF_MATCH_ECN
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""ecn" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NETFILTER_XT_MATCH_ECN if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:63
This is a backwards-compat option for the user's convenience
(e.g. when running oldconfig). It selects
CONFIG_NETFILTER_XT_MATCH_ECN.
Symbol IP_NF_MATCH_RPFILTER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""rpfilter" reverse path filter match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:72
This option allows you to match packets whose replies would
go out via the interface the packet came in.
To compile it as a module, choose M here. If unsure, say N.
The module will be called ipt_rpfilter.
Symbol IP_NF_MATCH_TTL
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""ttl" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NETFILTER_XT_MATCH_HL if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:82
This is a backwards-compat option for the user's convenience
(e.g. when running oldconfig). It selects
CONFIG_NETFILTER_XT_MATCH_HL.
Symbol IP_NF_FILTER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Packet filtering"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:92
Packet filtering defines a table `filter', which has a series of
rules for simple packet filtering at local input, forwarding and
local output. See the man page for iptables(8).
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_NF_TARGET_REJECT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"REJECT target support" if IP_NF_FILTER (value: "m")
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n && IP_NF_FILTER (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:102
The REJECT target allows a filtering rule to specify that an ICMP
error should be issued in response to an incoming packet, rather
than silently being dropped.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_NF_TARGET_ULOG
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ULOG target support"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:113
This option enables the old IPv4-only "ipt_ULOG" implementation
which has been obsoleted by the new "nfnetlink_log" code (see
CONFIG_NETFILTER_NETLINK_LOG).
This option adds a `ULOG' target, which allows you to create rules in
any iptables table. The packet is passed to a userspace logging
daemon using netlink multicast sockets; unlike the LOG target
which can only be viewed through syslog.
The appropriate userspace logging daemon (ulogd) may be obtained from
<http://www.netfilter.org/projects/ulogd/index.html>
To compile it as a module, choose M here. If unsure, say N.
Symbol NF_NAT_IPV4
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IPv4 NAT" if NF_CONNTRACK_IPV4 (value: "m")
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n && NF_CONNTRACK_IPV4 (value: "n")
Selects:
NF_NAT if NF_CONNTRACK_IPV4 (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:133
The IPv4 NAT option allows masquerading, port forwarding and other
forms of full Network Address Port Translation. It is controlled by
the `nat' table in iptables: see the man page for iptables(8).
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_NF_MANGLE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Packet mangling"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:220
This option adds a `mangle' table to iptables: see the man page for
iptables(8). This table is used for various packet alterations
which can effect how the packet is routed.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_NF_TARGET_CLUSTERIP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CLUSTERIP target support" if IP_NF_MANGLE && NF_CONNTRACK_IPV4 && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
NF_CONNTRACK_MARK if IP_NF_MANGLE && NF_CONNTRACK_IPV4 && NETFILTER_ADVANCED (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:230
The CLUSTERIP target allows you to build load-balancing clusters of
network servers without having a dedicated load-balancing
router/server/switch.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_NF_TARGET_ECN
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ECN target support" if IP_NF_MANGLE && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:243
This option adds a `ECN' target, which can be used in the iptables mangle
table.
You can use this target to remove the ECN bits from the IPv4 header of
an IP packet. This is particularly useful, if you need to work around
existing ECN blackholes on the internet, but don't want to disable
ECN support in general.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_NF_TARGET_TTL
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""TTL" target support" if NETFILTER_ADVANCED && IP_NF_MANGLE (value: "m")
Default values:
(no default values)
Selects:
NETFILTER_XT_TARGET_HL if NETFILTER_ADVANCED && IP_NF_MANGLE (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:258
This is a backwards-compatible option for the user's convenience
(e.g. when running oldconfig). It selects
CONFIG_NETFILTER_XT_TARGET_HL.
Symbol IP_NF_RAW
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"raw table support (required for NOTRACK/TRACE)"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_IPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:268
This option adds a `raw' table to iptables. This table is the very
first in the netfilter framework and hooks in at the PREROUTING
and OUTPUT chains.
If you want to compile it as a module, say M here and read
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
Symbol IP_NF_ARPTABLES
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ARP tables support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NETFILTER_XTABLES if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET (value: "y")
Locations: ../net/ipv4/netfilter/Kconfig:292
arptables is a general, extensible packet identification framework.
The ARP packet filtering and mangling (manipulation)subsystems
use this: say Y or M here if you want to use either of those.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_NF_ARPFILTER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ARP packet filtering"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_ARPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:305
ARP packet filtering defines a table `filter', which has a series of
rules for simple ARP packet filtering at local input and
local output. On a bridge, you can also specify filtering rules
for forwarded ARP packets. See the man page for arptables(8).
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_NF_ARP_MANGLE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IP: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ARP payload mangling"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && NETFILTER && NETFILTER && NET && IP_NF_ARPTABLES (value: "m")
Locations: ../net/ipv4/netfilter/Kconfig:315
Allows altering the ARP packet payload: source and destination
hardware and network addresses.
Symbol NF_CONNTRACK_IPV6
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IPv6 connection tracking support" if INET && IPV6 && NF_CONNTRACK (value: "m")
Default values:
m (value: "m")
Condition: INET && IPV6 && NF_CONNTRACK && NETFILTER_ADVANCED = n (value: "n")
Selects:
NF_DEFRAG_IPV6 if INET && IPV6 && NF_CONNTRACK (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:12
Connection tracking keeps a record of what packets have passed
through your machine, in order to figure out how they are related
into connections.
This is IPv6 support on Layer 3 independent connection tracking.
Layer 3 independent connection tracking is experimental scheme
which generalize ip_conntrack to support other layer 3 protocols.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP6_NF_MATCH_AH
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""ah" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:44
This module allows one to match AH packets.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP6_NF_MATCH_EUI64
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""eui64" address check" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:52
This module performs checking on the IPv6 source address
Compares the last 64 bits with the EUI64 (delivered
from the MAC address) address
To compile it as a module, choose M here. If unsure, say N.
Symbol IP6_NF_MATCH_FRAG
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""frag" Fragmentation header match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:62
frag matching allows you to match packets based on the fragmentation
header of the packet.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP6_NF_MATCH_OPTS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""hbh" hop-by-hop and "dst" opts header match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:71
This allows one to match packets based on the hop-by-hop
and destination options headers of a packet.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP6_NF_MATCH_HL
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""hl" hoplimit match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
NETFILTER_XT_MATCH_HL if NETFILTER_ADVANCED (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:80
This is a backwards-compat option for the user's convenience
(e.g. when running oldconfig). It selects
CONFIG_NETFILTER_XT_MATCH_HL.
Symbol IP6_NF_MATCH_IPV6HEADER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""ipv6header" IPv6 Extension Headers Match"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:89
This module allows one to match packets based upon
the ipv6 extension headers.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP6_NF_MATCH_MH
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""mh" match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:98
This module allows one to match MH packets.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP6_NF_MATCH_RPFILTER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""rpfilter" reverse path filter match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:106
This option allows you to match packets whose replies would
go out via the interface the packet came in.
To compile it as a module, choose M here. If unsure, say N.
The module will be called ip6t_rpfilter.
Symbol IP6_NF_MATCH_RT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""rt" Routing header match support" if NETFILTER_ADVANCED (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:116
rt matching allows you to match packets based on the routing
header of the packet.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP6_NF_TARGET_HL
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
""HL" hoplimit target support" if NETFILTER_ADVANCED && IP6_NF_MANGLE (value: "m")
Default values:
(no default values)
Selects:
NETFILTER_XT_TARGET_HL if NETFILTER_ADVANCED && IP6_NF_MANGLE (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:126
This is a backwards-compatible option for the user's convenience
(e.g. when running oldconfig). It selects
CONFIG_NETFILTER_XT_TARGET_HL.
Symbol IP6_NF_FILTER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Packet filtering"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:135
Packet filtering defines a table `filter', which has a series of
rules for simple packet filtering at local input, forwarding and
local output. See the man page for iptables(8).
To compile it as a module, choose M here. If unsure, say N.
Symbol IP6_NF_TARGET_REJECT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"REJECT target support" if IP6_NF_FILTER (value: "m")
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n && IP6_NF_FILTER (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:145
The REJECT target allows a filtering rule to specify that an ICMPv6
error should be issued in response to an incoming packet, rather
than silently being dropped.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP6_NF_MANGLE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Packet mangling"
Default values:
m (value: "m")
Condition: NETFILTER_ADVANCED = n (value: "n")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:156
This option adds a `mangle' table to iptables: see the man page for
iptables(8). This table is used for various packet alterations
which can effect how the packet is routed.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP6_NF_RAW
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"raw table support (required for TRACE)"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:166
This option adds a `raw' table to ip6tables. This table is the very
first in the netfilter framework and hooks in at the PREROUTING
and OUTPUT chains.
If you want to compile it as a module, say M here and read
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
Symbol NF_NAT_IPV6
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
IPv6: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IPv6 NAT" if NF_CONNTRACK_IPV6 && NETFILTER_ADVANCED (value: "m")
Default values:
(no default values)
Selects:
NF_NAT if NF_CONNTRACK_IPV6 && NETFILTER_ADVANCED (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INET && IPV6 && NETFILTER && NETFILTER && NET && IP6_NF_IPTABLES (value: "m")
Locations: ../net/ipv6/netfilter/Kconfig:187
The IPv6 NAT option allows masquerading, port forwarding and other
forms of full Network Address Port Translation. It is controlled by
the `nat' table in ip6tables, see the man page for ip6tables(8).
To compile it as a module, choose M here. If unsure, say N.
Symbol DECNET_NF_GRABULATOR
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
DECnet: Netfilter Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Routing message grabulator (for userland routing daemon)"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
DECNET && NETFILTER && NETFILTER_ADVANCED && NETFILTER && NET (value: "m")
Locations: ../net/decnet/netfilter/Kconfig:9
Enable this module if you want to use the userland DECnet routing
daemon. You will also need to enable routing support for DECnet
unless you just want to monitor routing messages from other nodes.
Symbol BRIDGE_NF_EBTABLES
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Ethernet Bridge tables (ebtables) support" if BRIDGE && NETFILTER (value: "m")
Default values:
(no default values)
Selects:
NETFILTER_XTABLES if BRIDGE && NETFILTER (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET (value: "y")
Locations: ../net/bridge/netfilter/Kconfig:5
ebtables is a general, extensible frame/packet identification
framework. Say 'Y' or 'M' here if you want to do Ethernet
filtering/NAT/brouting on the Ethernet bridge.
Symbol BRIDGE_EBT_BROUTE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: broute table support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:19
The ebtables broute table is used to define rules that decide between
bridging and routing frames, giving Linux the functionality of a
brouter. See the man page for ebtables(8) and examples on the ebtables
website.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_T_FILTER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: filter table support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:29
The ebtables filter table is used to define frame filtering rules at
local input, forwarding and local output. See the man page for
ebtables(8).
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_T_NAT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: nat table support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:38
The ebtables nat table is used to define rules that alter the MAC
source address (MAC SNAT) or the MAC destination address (MAC DNAT).
See the man page for ebtables(8).
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_802_3
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: 802.3 filter support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:49
This option adds matching support for 802.3 Ethernet frames.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_AMONG
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: among filter support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:56
This option adds the among match, which allows matching the MAC source
and/or destination address on a list of addresses. Optionally,
MAC/IP address pairs can be matched, f.e. for anti-spoofing rules.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_ARP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: ARP filter support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:65
This option adds the ARP match, which allows ARP and RARP header field
filtering.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_IP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: IP filter support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:73
This option adds the IP match, which allows basic IP header field
filtering.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_IP6
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: IP6 filter support" if BRIDGE_NF_EBTABLES && IPV6 (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:81
This option adds the IP6 match, which allows basic IPV6 header field
filtering.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_LIMIT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: limit match support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:90
This option adds the limit match, which allows you to control
the rate at which a rule can be matched. This match is the
equivalent of the iptables limit match.
If you want to compile it as a module, say M here and read
<file:Documentation/kbuild/modules.txt>. If unsure, say `N'.
Symbol BRIDGE_EBT_MARK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: mark filter support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:100
This option adds the mark match, which allows matching frames based on
the 'nfmark' value in the frame. This can be set by the mark target.
This value is the same as the one used in the iptables mark match and
target.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_PKTTYPE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: packet type filter support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:110
This option adds the packet type match, which allows matching on the
type of packet based on its Ethernet "class" (as determined by
the generic networking code): broadcast, multicast,
for this host alone or for another host.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_STP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: STP filter support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:120
This option adds the Spanning Tree Protocol match, which
allows STP header field filtering.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_VLAN
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: 802.1Q VLAN filter support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:128
This option adds the 802.1Q vlan match, which allows the filtering of
802.1Q vlan fields.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_ARPREPLY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: arp reply target support" if BRIDGE_NF_EBTABLES && INET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:138
This option adds the arp reply target, which allows
automatically sending arp replies to arp requests.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_DNAT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: dnat target support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:147
This option adds the MAC DNAT target, which allows altering the MAC
destination address of frames.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_MARK_T
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: mark target support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:155
This option adds the mark target, which allows marking frames by
setting the 'nfmark' value in the frame.
This value is the same as the one used in the iptables mark match and
target.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_REDIRECT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: redirect target support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:165
This option adds the MAC redirect target, which allows altering the MAC
destination address of a frame to that of the device it arrived on.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_SNAT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: snat target support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:173
This option adds the MAC SNAT target, which allows altering the MAC
source address of frames.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_LOG
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: log support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:183
This option adds the log watcher, that you can use in any rule
in any ebtables table. It records info about the frame header
to the syslog.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_ULOG
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: ulog support (OBSOLETE)"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:192
This option enables the old bridge-specific "ebt_ulog" implementation
which has been obsoleted by the new "nfnetlink_log" code (see
CONFIG_NETFILTER_NETLINK_LOG).
This option adds the ulog watcher, that you can use in any rule
in any ebtables table. The packet is passed to a userspace
logging daemon using netlink multicast sockets. This differs
from the log watcher in the sense that the complete packet is
sent to userspace instead of a descriptive text and that
netlink multicast sockets are used instead of the syslog.
To compile it as a module, choose M here. If unsure, say N.
Symbol BRIDGE_EBT_NFLOG
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ebt: nflog support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETFILTER && NET && BRIDGE_NF_EBTABLES (value: "m")
Locations: ../net/bridge/netfilter/Kconfig:208
This option enables the nflog watcher, which allows to LOG
messages through the netfilter logging API, which can use
either the old LOG target, the old ULOG target or nfnetlink_log
as backend.
This option adds the nflog watcher, that you can use in any rule
in any ebtables table.
To compile it as a module, choose M here. If unsure, say N.
Symbol IP_DCCP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"The DCCP Protocol" if INET (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/dccp/Kconfig:1
Datagram Congestion Control Protocol (RFC 4340)
From http://www.ietf.org/rfc/rfc4340.txt:
The Datagram Congestion Control Protocol (DCCP) is a transport
protocol that implements bidirectional, unicast connections of
congestion-controlled, unreliable datagrams. It should be suitable
for use by applications such as streaming media, Internet telephony,
and on-line games.
To compile this protocol support as a module, choose M here: the
module will be called dccp.
If in doubt, say N.
Symbol IP_DCCP_CCID3
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
DCCP CCIDs Configuration
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CCID-3 (TCP-Friendly)"
Default values:
y (value: "y")
Condition: IP_DCCP = y || IP_DCCP = "m" (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
IP_DCCP && NET (value: "m")
Locations: ../net/dccp/ccids/Kconfig:13
CCID-3 denotes TCP-Friendly Rate Control (TFRC), an equation-based
rate-controlled congestion control mechanism. TFRC is designed to
be reasonably fair when competing for bandwidth with TCP-like flows,
where a flow is "reasonably fair" if its sending rate is generally
within a factor of two of the sending rate of a TCP flow under the
same conditions. However, TFRC has a much lower variation of
throughput over time compared with TCP, which makes CCID-3 more
suitable than CCID-2 for applications such streaming media where a
relatively smooth sending rate is of importance.
CCID-3 is further described in RFC 4342,
http://www.ietf.org/rfc/rfc4342.txt
The TFRC congestion control algorithms were initially described in
RFC 5348.
This text was extracted from RFC 4340 (sec. 10.2),
http://www.ietf.org/rfc/rfc4340.txt
If in doubt, say N.
Symbol SCTP_COOKIE_HMAC_MD5
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable optional MD5 hmac cookie generation"
Default values:
(no default values)
Selects:
CRYPTO_HMAC if SCTP_COOKIE_HMAC_MD5 (value: "y")
CRYPTO_MD5 if SCTP_COOKIE_HMAC_MD5 (value: "y")
Reverse dependencies:
SCTP_DEFAULT_COOKIE_HMAC_MD5 (value: "y")
Additional dependencies from enclosing menus and if's:
IP_SCTP && NET (value: "m")
Locations: ../net/sctp/Kconfig:95
Enable optional MD5 hmac based SCTP cookie generation
Symbol SCTP_COOKIE_HMAC_SHA1
Type : bool
Value : "n"
User value : "n"
Xen config : 'y'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable optional SHA1 hmac cookie generation"
Default values:
(no default values)
Selects:
CRYPTO_HMAC if SCTP_COOKIE_HMAC_SHA1 (value: "n")
CRYPTO_SHA1 if SCTP_COOKIE_HMAC_SHA1 (value: "n")
Reverse dependencies:
SCTP_DEFAULT_COOKIE_HMAC_SHA1 (value: "n")
Additional dependencies from enclosing menus and if's:
IP_SCTP && NET (value: "m")
Locations: ../net/sctp/Kconfig:102
Enable optional SHA1 hmac based SCTP cookie generation
Symbol RDS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"The RDS Protocol" if INET (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/rds/Kconfig:2
The RDS (Reliable Datagram Sockets) protocol provides reliable,
sequenced delivery of datagrams over Infiniband, iWARP,
or TCP.
Symbol TIPC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"The TIPC Protocol" if INET (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/tipc/Kconfig:5
The Transparent Inter Process Communication (TIPC) protocol is
specially designed for intra cluster communication. This protocol
originates from Ericsson where it has been used in carrier grade
cluster applications for many years.
For more information about TIPC, see http://tipc.sourceforge.net.
This protocol support is also available as a module ( = code which
can be inserted in and removed from the running kernel whenever you
want). The module will be called tipc. If you want to compile it
as a module, say M here and read <file:Documentation/kbuild/modules.txt>.
If in doubt, say N.
Symbol TIPC_PORTS
Type : int
Value : "8191"
User value : "8191"
Xen config : '127'
Main config : '8191'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Ranges:
[127, 65535]
Prompts:
"Maximum number of ports in a node" if TIPC (value: "m")
Default values:
"8191" (value: "n")
Condition: TIPC (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/tipc/Kconfig:23
Specifies how many ports can be supported by a node.
Can range from 127 to 65535 ports; default is 8191.
Setting this to a smaller value saves some memory,
setting it to higher allows for more ports.
Symbol ATM
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Asynchronous Transfer Mode (ATM)"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/atm/Kconfig:5
ATM is a high-speed networking technology for Local Area Networks
and Wide Area Networks. It uses a fixed packet size and is
connection oriented, allowing for the negotiation of minimum
bandwidth requirements.
In order to participate in an ATM network, your Linux box needs an
ATM networking card. If you have that, say Y here and to the driver
of your ATM card below.
Note that you need a set of user-space programs to actually make use
of ATM. See the file <file:Documentation/networking/atm.txt> for
further details.
Symbol ATM_CLIP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Classical IP over ATM" if ATM && INET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/atm/Kconfig:21
Classical IP over ATM for PVCs and SVCs, supporting InARP and
ATMARP. If you want to communication with other IP hosts on your ATM
network, you will typically either say Y here or to "LAN Emulation
(LANE)" below.
Symbol ATM_LANE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"LAN Emulation (LANE) support" if ATM (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/atm/Kconfig:40
LAN Emulation emulates services of existing LANs across an ATM
network. Besides operating as a normal ATM end station client, Linux
LANE client can also act as an proxy client bridging packets between
ELAN and Ethernet segments. You need LANE if you want to try MPOA.
Symbol ATM_MPOA
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Multi-Protocol Over ATM (MPOA) support" if ATM && INET && ATM_LANE != n (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/atm/Kconfig:49
Multi-Protocol Over ATM allows ATM edge devices such as routers,
bridges and ATM attached hosts establish direct ATM VCs across
subnetwork boundaries. These shortcut connections bypass routers
enhancing overall network performance.
Symbol ATM_BR2684
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RFC1483/2684 Bridged protocols" if ATM && INET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/atm/Kconfig:58
ATM PVCs can carry ethernet PDUs according to RFC2684 (formerly 1483)
This device will act like an ethernet from the kernels point of view,
with the traffic being carried by ATM PVCs (currently 1 PVC/device).
This is sometimes used over DSL lines. If in doubt, say N.
Symbol L2TP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Layer Two Tunneling Protocol (L2TP)" if (IPV6 || IPV6 = n) && INET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/l2tp/Kconfig:5
Layer Two Tunneling Protocol
From RFC 2661 <http://www.ietf.org/rfc/rfc2661.txt>.
L2TP facilitates the tunneling of packets across an
intervening network in a way that is as transparent as
possible to both end-users and applications.
L2TP is often used to tunnel PPP traffic over IP
tunnels. One IP tunnel may carry thousands of individual PPP
connections. L2TP is also used as a VPN protocol, popular
with home workers to connect to their offices.
L2TPv3 allows other protocols as well as PPP to be carried
over L2TP tunnels. L2TPv3 is defined in RFC 3931
<http://www.ietf.org/rfc/rfc3931.txt>.
The kernel component handles only L2TP data packets: a
userland daemon handles L2TP the control protocol (tunnel
and session setup). One such daemon is OpenL2TP
(http://openl2tp.org/).
If you don't need L2TP, say N. To compile all L2TP code as
modules, choose M here.
Symbol L2TP_DEBUGFS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"L2TP debugfs support" if L2TP && DEBUG_FS (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/l2tp/Kconfig:35
Support for l2tp directory in debugfs filesystem. This may be
used to dump internal state of the l2tp drivers for problem
analysis.
If unsure, say 'Y'.
To compile this driver as a module, choose M here. The module
will be called l2tp_debugfs.
Symbol L2TP_V3
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"L2TPv3 support" if L2TP (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/l2tp/Kconfig:48
Layer Two Tunneling Protocol Version 3
From RFC 3931 <http://www.ietf.org/rfc/rfc3931.txt>.
The Layer Two Tunneling Protocol (L2TP) provides a dynamic
mechanism for tunneling Layer 2 (L2) "circuits" across a
packet-oriented data network (e.g., over IP). L2TP, as
originally defined in RFC 2661, is a standard method for
tunneling Point-to-Point Protocol (PPP) [RFC1661] sessions.
L2TP has since been adopted for tunneling a number of other
L2 protocols, including ATM, Frame Relay, HDLC and even raw
ethernet frames.
If you are connecting to L2TPv3 equipment, or you want to
tunnel raw ethernet frames using L2TP, say Y here. If
unsure, say N.
Symbol L2TP_IP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"L2TP IP encapsulation for L2TPv3" if L2TP_V3 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/l2tp/Kconfig:69
Support for L2TP-over-IP socket family.
The L2TPv3 protocol defines two possible encapsulations for
L2TP frames, namely UDP and plain IP (without UDP). This
driver provides a new L2TPIP socket family with which
userspace L2TPv3 daemons may create L2TP/IP tunnel sockets
when UDP encapsulation is not required. When L2TP is carried
in IP packets, it used IP protocol number 115, so this port
must be enabled in firewalls.
To compile this driver as a module, choose M here. The module
will be called l2tp_ip.
Symbol L2TP_ETH
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"L2TP ethernet pseudowire support for L2TPv3" if L2TP_V3 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/l2tp/Kconfig:86
Support for carrying raw ethernet frames over L2TPv3.
From RFC 4719 <http://www.ietf.org/rfc/rfc4719.txt>.
The Layer 2 Tunneling Protocol, Version 3 (L2TPv3) can be
used as a control protocol and for data encapsulation to set
up Pseudowires for transporting layer 2 Packet Data Units
across an IP network [RFC3931].
This driver provides an ethernet virtual interface for each
L2TP ethernet pseudowire instance. Standard Linux tools may
be used to assign an IP address to the local virtual
interface, or add the interface to a bridge.
If you are using L2TPv3, you will almost certainly want to
enable this option.
To compile this driver as a module, choose M here. The module
will be called l2tp_eth.
Symbol BRIDGE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"802.1d Ethernet Bridging" if IPV6 || IPV6 = n (value: "m")
Default values:
(no default values)
Selects:
LLC if IPV6 || IPV6 = n (value: "m")
STP if IPV6 || IPV6 = n (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/bridge/Kconfig:5
If you say Y here, then your Linux box will be able to act as an
Ethernet bridge, which means that the different Ethernet segments it
is connected to will appear as one Ethernet to the participants.
Several such bridges can work together to create even larger
networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
As this is a standard, Linux bridges will cooperate properly with
other third party bridge products.
In order to use the Ethernet bridge, you'll need the bridge
configuration tools; see <file:Documentation/networking/bridge.txt>
for location. Please read the Bridge mini-HOWTO for more
information.
If you enable iptables support along with the bridge support then you
turn your bridge into a bridging IP firewall.
iptables will then see the IP packets being bridged, so you need to
take this into account when setting up your firewall rules.
Enabling arptables support when bridging will let arptables see
bridged ARP traffic in the arptables FORWARD chain.
To compile this code as a module, choose M here: the module
will be called bridge.
If unsure, say N.
Symbol BRIDGE_IGMP_SNOOPING
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IGMP/MLD snooping" if BRIDGE && INET (value: "m")
Default values:
y (value: "y")
Condition: BRIDGE && INET (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/bridge/Kconfig:36
If you say Y here, then the Ethernet bridge will be able selectively
forward multicast traffic based on IGMP/MLD traffic received from
each port.
Say N to exclude this support and reduce the binary size.
If unsure, say Y.
Symbol BRIDGE_VLAN_FILTERING
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VLAN filtering" if BRIDGE && VLAN_8021Q (value: "m")
Default values:
n (value: "n")
Condition: BRIDGE && VLAN_8021Q (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/bridge/Kconfig:50
If you say Y here, then the Ethernet bridge will be able selectively
receive and forward traffic based on VLAN information in the packet
any VLAN information configured on the bridge port or bridge device.
Say N to exclude this support and reduce the binary size.
If unsure, say Y.
Symbol VLAN_8021Q
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"802.1Q VLAN Support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/8021q/Kconfig:5
Select this and you will be able to create 802.1Q VLAN interfaces
on your ethernet interfaces. 802.1Q VLAN supports almost
everything a regular ethernet interface does, including
firewalling, bridging, and of course IP traffic. You will need
the 'vconfig' tool from the VLAN project in order to effectively
use VLANs. See the VLAN web page for more information:
<http://www.candelatech.com/~greear/vlan.html>
To compile this code as a module, choose M here: the module
will be called 8021q.
If unsure, say N.
Symbol VLAN_8021Q_MVRP
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"MVRP (Multiple VLAN Registration Protocol) support" if VLAN_8021Q (value: "m")
Default values:
(no default values)
Selects:
MRP if VLAN_8021Q (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/8021q/Kconfig:31
Select this to enable MVRP end-system support. MVRP is used for
automatic propagation of registered VLANs to switches; it
supersedes GVRP and is not backwards-compatible.
If unsure, say N.
Symbol DECNET
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"DECnet Support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/decnet/Kconfig:4
The DECnet networking protocol was used in many products made by
Digital (now Compaq). It provides reliable stream and sequenced
packet communications over which run a variety of services similar
to those which run over TCP/IP.
To find some tools to use with the kernel layer support, please
look at Patrick Caulfield's web site:
<http://linux-decnet.sourceforge.net/>.
More detailed documentation is available in
<file:Documentation/networking/decnet.txt>.
Be sure to say Y to "/proc file system support" and "Sysctl support"
below when using DECnet, since you will need sysctl support to aid
in configuration at run time.
The DECnet code is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module is called decnet.
Symbol DECNET_ROUTER
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"DECnet: router support" if DECNET (value: "m")
Default values:
(no default values)
Selects:
FIB_RULES if DECNET (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/decnet/Kconfig:27
Add support for turning your DECnet Endnode into a level 1 or 2
router. This is an experimental, but functional option. If you
do say Y here, then make sure that you also say Y to "Kernel/User
network link driver", "Routing messages" and "Network packet
filtering". The first two are required to allow configuration via
rtnetlink (you will need Alexey Kuznetsov's iproute2 package
from <ftp://ftp.tux.org/pub/net/ip-routing/>). The "Network packet
filtering" option will be required for the forthcoming routing daemon
to work.
See <file:Documentation/networking/decnet.txt> for more information.
Symbol LLC2
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ANSI/IEEE 802.2 LLC type 2 Support"
Default values:
(no default values)
Selects:
LLC
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/llc/Kconfig:5
This is a Logical Link Layer type 2, connection oriented support.
Select this if you want to have support for PF_LLC sockets.
Symbol IPX
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"The IPX protocol"
Default values:
(no default values)
Selects:
LLC
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/ipx/Kconfig:4
This is support for the Novell networking protocol, IPX, commonly
used for local networks of Windows machines. You need it if you
want to access Novell NetWare file or print servers using the Linux
Novell client ncpfs (available from
<ftp://platan.vc.cvut.cz/pub/linux/ncpfs/>) or from
within the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO,
available from <http://www.tldp.org/docs.html#howto>). In order
to do the former, you'll also have to say Y to "NCP file system
support", below.
IPX is similar in scope to IP, while SPX, which runs on top of IPX,
is similar to TCP.
To turn your Linux box into a fully featured NetWare file server and
IPX router, say Y here and fetch either lwared from
<ftp://ibiblio.org/pub/Linux/system/network/daemons/> or
mars_nwe from <ftp://www.compu-art.de/mars_nwe/>. For more
information, read the IPX-HOWTO available from
<http://www.tldp.org/docs.html#howto>.
The IPX driver would enlarge your kernel by about 16 KB. To compile
this driver as a module, choose M here: the module will be called ipx.
Unless you want to integrate your Linux box with a local Novell
network, say N.
Symbol ATALK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Appletalk protocol support"
Default values:
(no default values)
Selects:
LLC
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../drivers/net/appletalk/Kconfig:4
AppleTalk is the protocol that Apple computers can use to communicate
on a network. If your Linux box is connected to such a network and you
wish to connect to it, say Y. You will need to use the netatalk package
so that your Linux box can act as a print and file server for Macs as
well as access AppleTalk printers. Check out
<http://www.zettabyte.net/netatalk/> on the WWW for details.
EtherTalk is the name used for AppleTalk over Ethernet and the
cheaper and slower LocalTalk is AppleTalk over a proprietary Apple
network using serial links. EtherTalk and LocalTalk are fully
supported by Linux.
General information about how to connect Linux, Windows machines and
Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. The
NET3-4-HOWTO, available from
<http://www.tldp.org/docs.html#howto>, contains valuable
information as well.
To compile this driver as a module, choose M here: the module will be
called appletalk. You almost certainly want to compile it as a
module so you can restart your AppleTalk stack without rebooting
your machine. I hear that the GNU boycott of Apple is over, so
even politically correct people are allowed to say Y here.
Symbol DEV_APPLETALK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Appletalk interfaces support" if ATALK (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../drivers/net/appletalk/Kconfig:31
AppleTalk is the protocol that Apple computers can use to communicate
on a network. If your Linux box is connected to such a network, and wish
to do IP over it, or you have a LocalTalk card and wish to use it to
connect to the AppleTalk network, say Y.
Symbol IPDDP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Appletalk-IP driver support" if DEV_APPLETALK && ATALK (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../drivers/net/appletalk/Kconfig:78
This allows IP networking for users who only have AppleTalk
networking available. This feature is experimental. With this
driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
box is stuck on an AppleTalk only network) or decapsulate (e.g. if
you want your Linux box to act as an Internet gateway for a zoo of
AppleTalk connected Macs). Please see the file
<file:Documentation/networking/ipddp.txt> for more information.
If you say Y here, the AppleTalk-IP support will be compiled into
the kernel. In this case, you can either use encapsulation or
decapsulation, but not both. With the following two questions, you
decide which one you want.
To compile the AppleTalk-IP support as a module, choose M here: the
module will be called ipddp.
In this case, you will be able to use both encapsulation and
decapsulation simultaneously, by loading two copies of the module
and specifying different values for the module option ipddp_mode.
Symbol IPDDP_ENCAP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IP to Appletalk-IP Encapsulation support" if IPDDP (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../drivers/net/appletalk/Kconfig:101
If you say Y here, the AppleTalk-IP code will be able to encapsulate
IP packets inside AppleTalk frames; this is useful if your Linux box
is stuck on an AppleTalk network (which hopefully contains a
decapsulator somewhere). Please see
<file:Documentation/networking/ipddp.txt> for more information. If
you said Y to "AppleTalk-IP driver support" above and you say Y
here, then you cannot say Y to "AppleTalk-IP to IP Decapsulation
support", below.
Symbol IPDDP_DECAP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Appletalk-IP to IP Decapsulation support" if IPDDP (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../drivers/net/appletalk/Kconfig:114
If you say Y here, the AppleTalk-IP code will be able to decapsulate
AppleTalk-IP frames to IP packets; this is useful if you want your
Linux box to act as an Internet gateway for an AppleTalk network.
Please see <file:Documentation/networking/ipddp.txt> for more
information. If you said Y to "AppleTalk-IP driver support" above
and you say Y here, then you cannot say Y to "IP to AppleTalk-IP
Encapsulation support", above.
Symbol X25
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CCITT X.25 Packet Layer"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/x25/Kconfig:5
X.25 is a set of standardized network protocols, similar in scope to
frame relay; the one physical line from your box to the X.25 network
entry point can carry several logical point-to-point connections
(called "virtual circuits") to other computers connected to the X.25
network. Governments, banks, and other organizations tend to use it
to connect to each other or to form Wide Area Networks (WANs). Many
countries have public X.25 networks. X.25 consists of two
protocols: the higher level Packet Layer Protocol (PLP) (say Y here
if you want that) and the lower level data link layer protocol LAPB
(say Y to "LAPB Data Link Driver" below if you want that).
You can read more about X.25 at <http://www.sangoma.com/x25.htm> and
<http://www.cisco.com/univercd/cc/td/doc/product/software/ios11/cbook/cx25.htm>.
Information about X.25 for Linux is contained in the files
<file:Documentation/networking/x25.txt> and
<file:Documentation/networking/x25-iface.txt>.
One connects to an X.25 network either with a dedicated network card
using the X.21 protocol (not yet supported by Linux) or one can do
X.25 over a standard telephone line using an ordinary modem (say Y
to "X.25 async driver" below) or over Ethernet using an ordinary
Ethernet card and the LAPB over Ethernet (say Y to "LAPB Data Link
Driver" and "LAPB over Ethernet driver" below).
To compile this driver as a module, choose M here: the module
will be called x25. If unsure, say N.
Symbol LAPB
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"LAPB Data Link Driver"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/lapb/Kconfig:5
Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
the lower) part of the X.25 protocol. It offers a reliable
connection service to exchange data frames with one other host, and
it is used to transport higher level protocols (mostly X.25 Packet
Layer, the higher part of X.25, but others are possible as well).
Usually, LAPB is used with specialized X.21 network cards, but Linux
currently supports LAPB only over Ethernet connections. If you want
to use LAPB connections over Ethernet, say Y here and to "LAPB over
Ethernet driver" below. Read
<file:Documentation/networking/lapb-module.txt> for technical
details.
To compile this driver as a module, choose M here: the
module will be called lapb. If unsure, say N.
Symbol PHONET
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Phonet protocols family"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/phonet/Kconfig:5
The Phone Network protocol (PhoNet) is a packet-oriented
communication protocol developed by Nokia for use with its modems.
This is required for Maemo to use cellular data connectivity (if
supported). It can also be used to control Nokia phones
from a Linux computer, although AT commands may be easier to use.
To compile this driver as a module, choose M here: the module
will be called phonet. If unsure, say N.
Symbol IEEE802154
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IEEE Std 802.15.4 Low-Rate Wireless Personal Area Networks support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/ieee802154/Kconfig:1
IEEE Std 802.15.4 defines a low data rate, low power and low
complexity short range wireless personal area networks. It was
designed to organise networks of sensors, switches, etc automation
devices. Maximum allowed data rate is 250 kb/s and typical personal
operating space around 10m.
Say Y here to compile LR-WPAN support into the kernel or say M to
compile it as modules.
Symbol IEEE802154_6LOWPAN
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"6lowpan support over IEEE 802.15.4" if IEEE802154 && IPV6 (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/ieee802154/Kconfig:13
IPv6 compression over IEEE 802.15.4.
Symbol MAC802154
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Generic IEEE 802.15.4 Soft Networking Stack (mac802154)" if IEEE802154 (value: "m")
Default values:
(no default values)
Selects:
CRC_CCITT if IEEE802154 (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/mac802154/Kconfig:1
This option enables the hardware independent IEEE 802.15.4
networking stack for SoftMAC devices (the ones implementing
only PHY level of IEEE 802.15.4 standard).
Note: this implementation is neither certified, nor feature
complete! Compatibility with other implementations hasn't
been tested yet!
If you plan to use HardMAC IEEE 802.15.4 devices, you can
say N here. Alternatievly you can say M to compile it as
module.
Symbol NET_SCH_ATM
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ATM Virtual Circuits (ATM)" if ATM (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET_SCHED && NET (value: "y")
Locations: ../net/sched/Kconfig:86
Say Y here if you want to use the ATM pseudo-scheduler. This
provides a framework for invoking classifiers, which in turn
select classes of this queuing discipline. Each class maps
the flow(s) it is handling to a given virtual circuit.
See the top of <file:net/sched/sch_atm.c> for more details.
To compile this code as a module, choose M here: the
module will be called sch_atm.
Symbol NET_SCH_CODEL
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Controlled Delay AQM (CODEL)"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET_SCHED && NET (value: "y")
Locations: ../net/sched/Kconfig:253
Say Y here if you want to use the Controlled Delay (CODEL)
packet scheduling algorithm.
To compile this driver as a module, choose M here: the module
will be called sch_codel.
If unsure, say N.
Symbol NET_SCH_FQ_CODEL
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fair Queue Controlled Delay AQM (FQ_CODEL)"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET_SCHED && NET (value: "y")
Locations: ../net/sched/Kconfig:264
Say Y here if you want to use the FQ Controlled Delay (FQ_CODEL)
packet scheduling algorithm.
To compile this driver as a module, choose M here: the module
will be called sch_fq_codel.
If unsure, say N.
Symbol NET_SCH_PLUG
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Plug network traffic until release (PLUG)"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET_SCHED && NET (value: "y")
Locations: ../net/sched/Kconfig:285
This queuing discipline allows userspace to plug/unplug a network
output queue, using the netlink interface. When it receives an
enqueue command it inserts a plug into the outbound queue that
causes following packets to enqueue until a dequeue command arrives
over netlink, causing the plug to be removed and resuming the normal
packet flow.
This module also provides a generic "network output buffering"
functionality (aka output commit), wherein upon arrival of a dequeue
command, only packets up to the first plug are released for delivery.
The Remus HA project uses this module to enable speculative execution
of virtual machines by allowing the generated network output to be rolled
back if needed.
For more information, please refer to http://wiki.xensource.com/xenwiki/Remus
Say Y here if you are using this kernel for Xen dom0 and
want to protect Xen guests with Remus.
To compile this code as a module, choose M here: the
module will be called sch_plug.
Symbol NET_EMATCH_IPSET
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IPset" if NET_EMATCH && IP_SET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET_SCHED && NET (value: "y")
Locations: ../net/sched/Kconfig:520
Say Y here if you want to be able to classify packets based on
ipset membership.
To compile this code as a module, choose M here: the
module will be called em_ipset.
Symbol NET_ACT_IPT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IPtables targets" if NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET_SCHED && NET (value: "y")
Locations: ../net/sched/Kconfig:578
Say Y here to be able to invoke iptables targets after successful
classification.
To compile this code as a module, choose M here: the
module will be called act_ipt.
Symbol OPENVSWITCH
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Open vSwitch"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/openvswitch/Kconfig:5
Open vSwitch is a multilayer Ethernet switch targeted at virtualized
environments. In addition to supporting a variety of features
expected in a traditional hardware switch, it enables fine-grained
programmatic extension and flow-based control of the network. This
control is useful in a wide variety of applications but is
particularly important in multi-server virtualization deployments,
which are often characterized by highly dynamic endpoints and the
need to maintain logical abstractions for multiple tenants.
The Open vSwitch datapath provides an in-kernel fast path for packet
forwarding. It is complemented by a userspace daemon, ovs-vswitchd,
which is able to accept configuration from a variety of sources and
translate it into packet processing rules.
See http://openvswitch.org for more information and userspace
utilities.
To compile this code as a module, choose M here: the module will be
called openvswitch.
If unsure, say N.
Symbol VSOCKETS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Networking options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Virtual Socket protocol"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/vmw_vsock/Kconfig:5
Virtual Socket Protocol is a socket protocol similar to TCP/IP
allowing comunication between Virtual Machines and hypervisor
or host.
You should also select one or more hypervisor-specific transports
below.
To compile this driver as a module, choose M here: the module
will be called vsock. If unsure, say N.
Symbol IRDA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IrDA (infrared) subsystem support" if NET && !S390 (value: "y")
Default values:
(no default values)
Selects:
CRC_CCITT if NET && !S390 (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/irda/Kconfig:5
Say Y here if you want to build support for the IrDA (TM) protocols.
The Infrared Data Associations (tm) specifies standards for wireless
infrared communication and is supported by most laptops and PDA's.
To use Linux support for the IrDA (tm) protocols, you will also need
some user-space utilities like irattach. For more information, see
the file <file:Documentation/networking/irda.txt>. You also want to
read the IR-HOWTO, available at
<http://www.tldp.org/docs.html#howto>.
If you want to exchange bits of data (vCal, vCard) with a PDA, you
will need to install some OBEX application, such as OpenObex :
<http://sourceforge.net/projects/openobex/>
To compile this support as a module, choose M here: the module will
be called irda.
Symbol BT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Bluetooth subsystem support" if NET && !S390 && (RFKILL || !RFKILL) (value: "y")
Default values:
(no default values)
Selects:
CRC16 if NET && !S390 && (RFKILL || !RFKILL) (value: "y")
CRYPTO if NET && !S390 && (RFKILL || !RFKILL) (value: "y")
CRYPTO_BLKCIPHER if NET && !S390 && (RFKILL || !RFKILL) (value: "y")
CRYPTO_AES if NET && !S390 && (RFKILL || !RFKILL) (value: "y")
CRYPTO_ECB if NET && !S390 && (RFKILL || !RFKILL) (value: "y")
CRYPTO_SHA256 if NET && !S390 && (RFKILL || !RFKILL) (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/bluetooth/Kconfig:5
Bluetooth is low-cost, low-power, short-range wireless technology.
It was designed as a replacement for cables and other short-range
technologies like IrDA. Bluetooth operates in personal area range
that typically extends up to 10 meters. More information about
Bluetooth can be found at <http://www.bluetooth.com/>.
Linux Bluetooth subsystem consist of several layers:
Bluetooth Core
HCI device and connection manager, scheduler
SCO audio links
L2CAP (Logical Link Control and Adaptation Protocol)
SMP (Security Manager Protocol) on LE (Low Energy) links
HCI Device drivers (Interface to the hardware)
RFCOMM Module (RFCOMM Protocol)
BNEP Module (Bluetooth Network Encapsulation Protocol)
CMTP Module (CAPI Message Transport Protocol)
HIDP Module (Human Interface Device Protocol)
Say Y here to compile Bluetooth support into the kernel or say M to
compile it as module (bluetooth).
To use Linux Bluetooth subsystem, you will need several user-space
utilities like hciconfig and bluetoothd. These utilities and updates
to Bluetooth kernel modules are provided in the BlueZ packages. For
more information, see <http://www.bluez.org/>.
Symbol AF_RXRPC
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RxRPC session sockets" if INET (value: "y")
Default values:
(no default values)
Selects:
CRYPTO if INET (value: "y")
KEYS if INET (value: "y")
Reverse dependencies:
INET && NETWORK_FILESYSTEMS && AFS_FS (value: "n")
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/rxrpc/Kconfig:5
Say Y or M here to include support for RxRPC session sockets (just
the transport part, not the presentation part: (un)marshalling is
left to the application).
These are used for AFS kernel filesystem and userspace utilities.
This module at the moment only supports client operations and is
currently incomplete.
See Documentation/networking/rxrpc.txt.
Symbol WIRELESS
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Wireless" if !S390 (value: "y")
Default values:
y (value: "y")
Condition: !S390 (value: "y")
Selects:
(no selects)
Reverse dependencies:
!S390 && NET && NETDEVICES && WLAN (value: "n")
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/Kconfig:319
Symbol WIMAX
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"WiMAX Wireless Broadband support" if RFKILL || !RFKILL (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/wimax/Kconfig:5
Select to configure support for devices that provide
wireless broadband connectivity using the WiMAX protocol
(IEEE 802.16).
Please note that most of these devices require signing up
for a service plan with a provider.
The different WiMAX drivers can be enabled in the menu entry
Device Drivers > Network device support > WiMAX Wireless
Broadband devices
If unsure, it is safe to select M (module).
Symbol RFKILL
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RF switch subsystem support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/rfkill/Kconfig:4
Say Y here if you want to have control over RF switches
found on many WiFi and Bluetooth cards.
To compile this driver as a module, choose M here: the
module will be called rfkill.
Symbol NET_9P
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Plan 9 Resource Sharing Support (9P2000)" if NET (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/9p/Kconfig:5
If you say Y here, you will get experimental support for
Plan 9 resource sharing via the 9P2000 protocol.
See <http://v9fs.sf.net> for more information.
If unsure, say N.
Symbol NET_9P_VIRTIO
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"9P Virtio Transport" if VIRTIO (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET_9P && NET (value: "m")
Locations: ../net/9p/Kconfig:18
This builds support for a transports between
guest partitions and a host partition.
Symbol CEPH_LIB
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Ceph core library" if INET (value: "y")
Default values:
n (value: "n")
Condition: INET (value: "y")
Selects:
LIBCRC32C if INET (value: "y")
CRYPTO_AES if INET (value: "y")
CRYPTO if INET (value: "y")
KEYS if INET (value: "y")
Reverse dependencies:
INET && BLOCK && BLK_DEV && BLK_DEV_RBD || INET && NETWORK_FILESYSTEMS && CEPH_FS (value: "m")
Additional dependencies from enclosing menus and if's:
NET (value: "y")
Locations: ../net/ceph/Kconfig:1
Choose Y or M here to include cephlib, which provides the
common functionality to both the Ceph filesystem and
to the rados block device (rbd).
More information at http://ceph.newdream.net/.
If unsure, say N.
Symbol STANDALONE
Type : bool
Value : "n"
User value : "n"
Xen config : 'y'
Main config : 'y'
Visibility : "y"
Device Drivers
Generic Driver Options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Select only drivers that don't need compile-time external firmware"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/base/Kconfig:59
Select this option if you don't have magic firmware for drivers that
need it.
If unsure, say Y.
Symbol PREVENT_FIRMWARE_BUILD
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'n'
Visibility : "y"
Device Drivers
Generic Driver Options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Prevent firmware from being built"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/base/Kconfig:68
Say yes to avoid building firmware. Firmware is usually shipped
with the driver and only when updating the firmware should a
rebuild be made.
If unsure, say Y here.
Symbol FW_LOADER_USER_HELPER
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'n'
Visibility : "y"
Device Drivers
Generic Driver Options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fallback user-helper invocation for firmware loading" if FW_LOADER (value: "m")
Default values:
y (value: "y")
Condition: FW_LOADER (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/base/Kconfig:148
This option enables / disables the invocation of user-helper
(e.g. udev) for loading firmware files as a fallback after the
direct file loading in kernel fails. The user-mode helper is
no longer required unless you have a special firmware file that
resides in a non-standard path.
Symbol DEBUG_DEVRES
Type : bool
Value : "n"
User value : "n"
Xen config : 'y'
Main config : 'y'
Visibility : "y"
Device Drivers
Generic Driver Options
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Managed device resources verbose debug messages" if DEBUG_KERNEL (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/base/Kconfig:170
This option enables kernel parameter devres.log. If set to
non-zero, devres debug messages are printed. Select this if
you are having a problem with devres or want to debug
resource management for a managed device. devres.log can be
switched on and off from sysfs node.
If you are unsure about this, Say N here.
Symbol MTD
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Memory Technology Device (MTD) support" if GENERIC_IO (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/mtd/Kconfig:1
Memory Technology Devices are flash, RAM and similar chips, often
used for solid state file systems on embedded devices. This option
will provide the generic support for MTD drivers to register
themselves with the kernel and for potential users of MTD devices
to enumerate the devices which are present and obtain a handle on
them. It will also allow you to select individual drivers for
particular hardware and users of MTD devices. If unsure, say N.
Symbol PARPORT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Parallel port support" if HAS_IOMEM (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/parport/Kconfig:8
If you want to use devices connected to your machine's parallel port
(the connector at the computer with 25 holes), e.g. printer, ZIP
drive, PLIP link (Parallel Line Internet Protocol is mainly used to
create a mini network by connecting the parallel ports of two local
machines) etc., then you need to say Y here; please read
<file:Documentation/parport.txt> and
<file:drivers/parport/BUGS-parport>.
For extensive information about drivers for many devices attaching
to the parallel port see <http://www.torque.net/linux-pp.html> on
the WWW.
It is possible to share a single parallel port among several devices
and it is safe to compile all the corresponding drivers into the
kernel. To compile parallel port support as a module, choose M here:
the module will be called parport.
If you have more than one parallel port and want to specify which
port and IRQ to be used by this driver at module load time, take a
look at <file:Documentation/parport.txt>.
If unsure, say Y.
Symbol PARPORT_PC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PC-style hardware" if (!SPARC64 || PCI) && !SPARC32 && !M32R && !FRV && !S390 && (!M68K || ISA) && !MN10300 && !AVR32 && !BLACKFIN && !XTENSA (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PARPORT (value: "m")
Locations: ../drivers/parport/Kconfig:36
You should say Y here if you have a PC-style parallel port. All
IBM PC compatible computers and some Alphas have PC-style
parallel ports. PA-RISC owners should only say Y here if they
have a SuperIO parallel port.
To compile this driver as a module, choose M here: the
module will be called parport_pc.
If unsure, say Y.
Symbol PARPORT_SERIAL
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Multi-IO cards (parallel and serial)" if SERIAL_8250_PCI && PARPORT_PC && PCI (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PARPORT (value: "m")
Locations: ../drivers/parport/Kconfig:50
This adds support for multi-IO PCI cards that have parallel and
serial ports. You should say Y or M here. If you say M, the module
will be called parport_serial.
Symbol PARPORT_AX88796
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AX88796 Parallel Port"
Default values:
(no default values)
Selects:
PARPORT_NOT_PC
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PARPORT (value: "m")
Locations: ../drivers/parport/Kconfig:136
Say Y here if you need support for the parallel port hardware on
the AX88796 network controller chip. This code is also available
as a module (say M), called parport_ax88796.
The driver is not dependent on the AX88796 network driver, and
should not interfere with the networking functions of the chip.
Symbol BLK_DEV_FD
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Normal floppy disk support" if ARCH_MAY_HAVE_PC_FDC (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:18
If you want to use the floppy disk drive(s) of your PC under Linux,
say Y. Information about this driver, especially important for IBM
Thinkpad users, is contained in
<file:Documentation/blockdev/floppy.txt>.
That file also contains the location of the Floppy driver FAQ as
well as location of the fdutils package used to configure additional
parameters of the driver at run time.
To compile this driver as a module, choose M here: the
module will be called floppy.
Symbol BLK_DEV_PCIESSD_MTIP32XX
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Block Device Driver for Micron PCIe SSDs" if PCI && GENERIC_HARDIRQS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/mtip32xx/Kconfig:5
This enables the block driver for Micron PCIe SSDs.
Symbol BLK_CPQ_DA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Compaq SMART2 support" if PCI && VIRT_TO_BUS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:108
This is the driver for Compaq Smart Array controllers. Everyone
using these boards should say Y here. See the file
<file:Documentation/blockdev/cpqarray.txt> for the current list of
boards supported by this driver, and for further information on the
use of this driver.
Symbol BLK_CPQ_CISS_DA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Compaq Smart Array 5xxx support" if PCI (value: "y")
Default values:
(no default values)
Selects:
CHECK_SIGNATURE if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:118
This is the driver for Compaq Smart Array 5xxx controllers.
Everyone using these boards should say Y here.
See <file:Documentation/blockdev/cciss.txt> for the current list of
boards supported by this driver, and for further information
on the use of this driver.
Symbol BLK_DEV_DAC960
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Mylex DAC960/DAC1100 PCI RAID Controller support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:144
This driver adds support for the Mylex DAC960, AcceleRAID, and
eXtremeRAID PCI RAID controllers. See the file
<file:Documentation/blockdev/README.DAC960> for further information
about this driver.
To compile this driver as a module, choose M here: the
module will be called DAC960.
Symbol BLK_DEV_UMEM
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Micro Memory MM5415 Battery Backed RAM support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:156
Saying Y here will include support for the MM5415 family of
battery backed (Non-volatile) RAM cards.
<http://www.umem.com/>
The cards appear as block devices that can be partitioned into
as many as 15 partitions.
To compile this driver as a module, choose M here: the
module will be called umem.
The umem driver has not yet been allocated a MAJOR number, so
one is chosen dynamically.
Symbol BLK_DEV_DRBD
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"DRBD Distributed Replicated Block Device support" if PROC_FS && INET (value: "y")
Default values:
n (value: "n")
Condition: PROC_FS && INET (value: "y")
Selects:
LRU_CACHE if PROC_FS && INET (value: "y")
LIBCRC32C if PROC_FS && INET (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/drbd/Kconfig:8
NOTE: In order to authenticate connections you have to select
CRYPTO_HMAC and a hash function as well.
DRBD is a shared-nothing, synchronously replicated block device. It
is designed to serve as a building block for high availability
clusters and in this context, is a "drop-in" replacement for shared
storage. Simplistically, you could see it as a network RAID 1.
Each minor device has a role, which can be 'primary' or 'secondary'.
On the node with the primary device the application is supposed to
run and to access the device (/dev/drbdX). Every write is sent to
the local 'lower level block device' and, across the network, to the
node with the device in 'secondary' state. The secondary device
simply writes the data to its lower level block device.
DRBD can also be used in dual-Primary mode (device writable on both
nodes), which means it can exhibit shared disk semantics in a
shared-nothing cluster. Needless to say, on top of dual-Primary
DRBD utilizing a cluster file system is necessary to maintain for
cache coherency.
For automatic failover you need a cluster manager (e.g. heartbeat).
See also: http://www.drbd.org/, http://www.linux-ha.org
If unsure, say N.
Symbol BLK_DEV_NVME
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"NVM Express block device" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:308
The NVM Express driver is for solid state drives directly
connected to the PCI or PCI Express bus. If you know you
don't have one of these, it is safe to answer N.
To compile this driver as a module, choose M here: the
module will be called nvme.
Symbol BLK_DEV_OSD
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"OSD object-as-blkdev support" if SCSI_OSD_ULD (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:319
Saying Y or M here will allow the exporting of a single SCSI
OSD (object-based storage) object as a Linux block device.
For example, if you create a 2G object on an OSD device,
you can then use this module to present that 2G object as
a Linux block device.
To compile this driver as a module, choose M here: the
module will be called osdblk.
If unsure, say N.
Symbol BLK_DEV_SX8
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Promise SATA SX8 support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:335
Saying Y or M here will enable support for the
Promise SATA SX8 controllers.
Use devices /dev/sx8/$N and /dev/sx8/$Np$M.
Symbol BLK_DEV_RAM
Type : tristate
Value : "n"
User value : "n"
Xen config : 'y'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RAM block device support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:344
Saying Y here will allow you to use a portion of your RAM memory as
a block device, so that you can make file systems on it, read and
write to it and do all the other things that you can do with normal
block devices (such as hard drives). It is usually used to load and
store a copy of a minimal root file system off of a floppy into RAM
during the initial install of Linux.
Note that the kernel command line option "ramdisk=XX" is now obsolete.
For details, read <file:Documentation/blockdev/ramdisk.txt>.
To compile this driver as a module, choose M here: the
module will be called rd.
Most normal users won't need the RAM disk functionality, and can
thus say N here.
Symbol CDROM_PKTCDVD
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Packet writing on CD/DVD media" if !UML (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:390
If you have a CDROM/DVD drive that supports packet writing, say
Y to include support. It should work with any MMC/Mt Fuji
compliant ATAPI or SCSI drive, which is just about any newer
DVD/CD writer.
Currently only writing to CD-RW, DVD-RW, DVD+RW and DVDRAM discs
is possible.
DVD-RW disks must be in restricted overwrite mode.
See the file <file:Documentation/cdrom/packet-writing.txt>
for further information on the use of this driver.
To compile this driver as a module, choose M here: the
module will be called pktcdvd.
Symbol ATA_OVER_ETH
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ATA over Ethernet support" if NET (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:428
This driver provides Support for ATA over Ethernet block
devices like the Coraid EtherDrive (R) Storage Blade.
Symbol XEN_BLKDEV_FRONTEND
Type : tristate
Value : "y"
User value : "y"
Xen config : 'y'
Main config : 'n'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Xen virtual block device support" if XEN (value: "y")
Default values:
y (value: "y")
Condition: XEN (value: "y")
Selects:
XEN_XENBUS_FRONTEND if XEN (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:467
This driver implements the front-end of the Xen virtual
block device driver. It communicates with a back-end driver
in another domain which drives the actual block device.
Symbol BLK_DEV_RBD
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'n'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Rados block device (RBD)" if INET && BLOCK (value: "y")
Default values:
n (value: "n")
Condition: INET && BLOCK (value: "y")
Selects:
CEPH_LIB if INET && BLOCK (value: "y")
LIBCRC32C if INET && BLOCK (value: "y")
CRYPTO_AES if INET && BLOCK (value: "y")
CRYPTO if INET && BLOCK (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:517
Say Y here if you want include the Rados block device, which stripes
a block device over objects stored in the Ceph distributed object
store.
More information at http://ceph.newdream.net/.
If unsure, say N.
Symbol BLK_DEV_RSXX
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IBM FlashSystem 70/80 PCIe SSD Device Driver" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
BLK_DEV (value: "y")
Locations: ../drivers/block/Kconfig:534
Device driver for IBM's high speed PCIe SSD
storage devices: FlashSystem-70 and FlashSystem-80.
To compile this driver as a module, choose M here: the
module will be called rsxx.
Symbol AD525X_DPOT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices Digital Potentiometers" if (I2C || SPI) && SYSFS (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:13
If you say yes here, you get support for the Analog Devices
AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
AD5271, AD5272, AD5274
digital potentiometer chips.
See Documentation/misc-devices/ad525x_dpot.txt for the
userspace interface.
This driver can also be built as a module. If so, the module
will be called ad525x_dpot.
Symbol IBM_ASM
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Device driver for IBM RSA service processor" if X86 && PCI && INPUT (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:96
This option enables device driver support for in-band access to the
IBM RSA (Condor) service processor in eServer xSeries systems.
The ibmasm device driver allows user space application to access
ASM (Advanced Systems Management) functions on the service
processor. The driver is meant to be used in conjunction with
a user space API.
The ibmasm driver also enables the OS to use the UART on the
service processor board as a regular serial port. To make use of
this feature serial driver support (CONFIG_SERIAL_8250) must be
enabled.
WARNING: This software may not be supported or function
correctly on your IBM server. Please consult the IBM ServerProven
website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
for information on the specific driver level and support statement
for your IBM server.
Symbol PHANTOM
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Sensable PHANToM (PCI)" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:117
Say Y here if you want to build a driver for Sensable PHANToM device.
This driver is only for PCI PHANToMs.
If you choose to build module, its name will be phantom. If unsure,
say N here.
Symbol SGI_IOC4
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SGI IOC4 Base IO support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:142
This option enables basic support for the IOC4 chip on certain
SGI IO controller cards (IO9, IO10, and PCI-RT). This option
does not enable any specific functions on such a card, but provides
necessary infrastructure for other drivers to utilize.
If you have an SGI Altix with an IOC4-based card say Y.
Otherwise say N.
Symbol TIFM_CORE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"TI Flash Media interface support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
PCI && MMC && MMC_TIFM_SD || PCI && MEMSTICK && MEMSTICK_TIFM_MS (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:154
If you want support for Texas Instruments(R) Flash Media adapters
you should select this option and then also choose an appropriate
host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
support', if you have a TI PCI74xx compatible card reader, for
example.
You will also have to select some flash card format drivers. MMC/SD
cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
Interface support (MMC_TIFM_SD)'.
To compile this driver as a module, choose M here: the module will
be called tifm_core.
Symbol ICS932S401
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Integrated Circuits ICS932S401" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:183
If you say yes here you get support for the Integrated Circuits
ICS932S401 clock control chips.
This driver can also be built as a module. If so, the module
will be called ics932s401.
Symbol ENCLOSURE_SERVICES
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enclosure Services"
Default values:
n (value: "n")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:205
Provides support for intelligent enclosures (bays which
contain storage devices). You also need either a host
driver (SCSI/ATA) which supports enclosures
or a SCSI enclosure device (SES) to use these services.
Symbol HP_ILO
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Channel interface driver for the HP iLO processor" if PCI (value: "y")
Default values:
n (value: "n")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:261
The channel interface driver allows applications to communicate
with iLO management processors present on HP ProLiant servers.
Upon loading, the driver creates /dev/hpilo/dXccbN files, which
can be used to gather data from the management processor, via
read and write system calls.
To compile this driver as a module, choose M here: the
module will be called hpilo.
Symbol APDS9802ALS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Medfield Avago APDS9802 ALS Sensor module" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:298
If you say yes here you get support for the ALS APDS9802 ambient
light sensor.
This driver can also be built as a module. If so, the module
will be called apds9802als.
Symbol ISL29003
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intersil ISL29003 ambient light sensor" if I2C && SYSFS (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:308
If you say yes here you get support for the Intersil ISL29003
ambient light sensor.
This driver can also be built as a module. If so, the module
will be called isl29003.
Symbol ISL29020
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intersil ISL29020 ambient light sensor" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:318
If you say yes here you get support for the Intersil ISL29020
ambient light sensor.
This driver can also be built as a module. If so, the module
will be called isl29020.
Symbol SENSORS_TSL2550
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Taos TSL2550 ambient light sensor" if I2C && SYSFS (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:328
If you say yes here you get support for the Taos TSL2550
ambient light sensor.
This driver can also be built as a module. If so, the module
will be called tsl2550.
Symbol SENSORS_BH1780
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ROHM BH1780GLI ambient light sensor" if I2C && SYSFS (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:338
If you say yes here you get support for the ROHM BH1780GLI
ambient light sensor.
This driver can also be built as a module. If so, the module
will be called bh1780gli.
Symbol SENSORS_BH1770
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"BH1770GLC / SFH7770 combined ALS - Proximity sensor" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:348
Say Y here if you want to build a driver for BH1770GLC (ROHM) or
SFH7770 (Osram) combined ambient light and proximity sensor chip.
To compile this driver as a module, choose M here: the
module will be called bh1770glc. If unsure, say N here.
Symbol SENSORS_APDS990X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"APDS990X combined als and proximity sensors" if I2C (value: "m")
Default values:
n (value: "n")
Condition: I2C (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:358
Say Y here if you want to build a driver for Avago APDS990x
combined ambient light and proximity sensor chip.
To compile this driver as a module, choose M here: the
module will be called apds990x. If unsure, say N here.
Symbol HMC6352
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Honeywell HMC6352 compass" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:369
This driver provides support for the Honeywell HMC6352 compass,
providing configuration and heading data via sysfs.
Symbol DS1682
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Dallas DS1682 Total Elapsed Time Recorder with Alarm" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:389
If you say yes here you get support for Dallas Semiconductor
DS1682 Total Elapsed Time Recorder.
This driver can also be built as a module. If so, the module
will be called ds1682.
Symbol VMWARE_BALLOON
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VMware Balloon Driver" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:419
This is VMware physical memory management driver which acts
like a "balloon" that can be inflated to reclaim physical pages
by reserving them in the guest and invalidating them in the
monitor, freeing up the underlying machine pages so they can
be allocated to other guests. The balloon can also be deflated
to allow the guest to use more physical memory.
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called vmw_balloon.
Symbol PCH_PHUB
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/Kconfig:473
This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
processor. The Topcliff has MAC address and Option ROM data in SROM.
This driver can access MAC address and Option ROM data in SROM.
This driver also can be used for LAPIS Semiconductor's IOH,
ML7213/ML7223/ML7831.
ML7213 which is for IVI(In-Vehicle Infotainment) use.
ML7223 IOH is for MP(Media Phone) use.
ML7831 IOH is for general purpose use.
ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
To compile this driver as a module, choose M here: the module will
be called pch_phub.
Symbol C2PORT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Silicon Labs C2 port support"
Default values:
n (value: "n")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/c2port/Kconfig:5
This option enables support for Silicon Labs C2 port used to
program Silicon micro controller chips (and other 8051 compatible).
If your board have no such micro controllers you don't need this
interface at all.
To compile this driver as a module, choose M here: the module will
be called c2port_core. Note that you also need a client module
usually called c2port-*.
If you are not sure, say N here.
Symbol EEPROM_AT24
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
EEPROM support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"I2C EEPROMs / RAMs / ROMs from most vendors" if I2C && SYSFS (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/eeprom/Kconfig:3
Enable this driver to get read/write support to most I2C EEPROMs
and compatible devices like FRAMs, SRAMs, ROMs etc. After you
configure the driver to know about each chip on your target
board. Use these generic chip names, instead of vendor-specific
ones like at24c64, 24lc02 or fm24c04:
24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08,
24c16, 24c32, 24c64, 24c128, 24c256, 24c512, 24c1024
Unless you like data loss puzzles, always be sure that any chip
you configure as a 24c32 (32 kbit) or larger is NOT really a
24c16 (16 kbit) or smaller, and vice versa. Marking the chip
as read-only won't help recover from this. Also, if your chip
has any software write-protect mechanism you may want to review the
code to make sure this driver won't turn it on by accident.
If you use this with an SMBus adapter instead of an I2C adapter,
full functionality is not available. Only smaller devices are
supported (24c16 and below, max 4 kByte).
This driver can also be built as a module. If so, the module
will be called at24.
Symbol EEPROM_LEGACY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
EEPROM support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Old I2C EEPROM reader" if I2C && SYSFS (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/eeprom/Kconfig:41
If you say yes here you get read-only access to the EEPROM data
available on modern memory DIMMs and Sony Vaio laptops via I2C. Such
EEPROMs could theoretically be available on other devices as well.
This driver can also be built as a module. If so, the module
will be called eeprom.
Symbol EEPROM_MAX6875
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
EEPROM support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Maxim MAX6874/5 power supply supervisor" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/eeprom/Kconfig:52
If you say yes here you get read-only support for the user EEPROM of
the Maxim MAX6874/5 EEPROM-programmable, quad power-supply
sequencer/supervisor.
All other features of this chip should be accessed via i2c-dev.
This driver can also be built as a module. If so, the module
will be called max6875.
Symbol CB710_CORE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ENE CB710/720 Flash memory card reader support" if PCI && GENERIC_HARDIRQS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
PCI && GENERIC_HARDIRQS && MMC && MMC_CB710 (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/cb710/Kconfig:1
This option enables support for PCI ENE CB710/720 Flash memory card
reader found in some laptops (ie. some versions of HP Compaq nx9500).
You will also have to select some flash card format drivers (MMC/SD,
MemoryStick).
This driver can also be built as a module. If so, the module
will be called cb710.
Symbol TI_ST
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Misc devices
Texas Instruments shared transport line discipline
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Shared transport core driver" if NET && GPIOLIB && TTY (value: "y")
Default values:
(no default values)
Selects:
FW_LOADER if NET && GPIOLIB && TTY (value: "y")
Reverse dependencies:
VIDEO_V4L2 && RFKILL && GPIOLIB && TTY && NET && RADIO_ADAPTERS && VIDEO_V4L2 && MEDIA_SUPPORT && RADIO_WL128X (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/ti-st/Kconfig:6
This enables the shared transport core driver for TI
BT / FM and GPS combo chips. This enables protocol drivers
to register themselves with core and send data, the responses
are returned to relevant protocol drivers based on their
packet types.
Symbol SENSORS_LIS3_I2C
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"STMicroeletronics LIS3LV02Dx three-axis digital accelerometer (I2C)" if I2C && INPUT (value: "m")
Default values:
n (value: "n")
Condition: I2C && INPUT (value: "m")
Selects:
SENSORS_LIS3LV02D if I2C && INPUT (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/lis3lv02d/Kconfig:22
This driver provides support for the LIS3LV02Dx accelerometer connected
via I2C. The accelerometer data is readable via
/sys/devices/platform/lis3lv02d.
This driver also provides an absolute input class device, allowing
the device to act as a pinball machine-esque joystick.
This driver can also be built as modules. If so, the core module
will be called lis3lv02d and a specific module for the I2C transport
is called lis3lv02d_i2c.
Symbol ALTERA_STAPL
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Altera FPGA firmware download module" if I2C (value: "m")
Default values:
n (value: "n")
Condition: I2C (value: "m")
Selects:
(no selects)
Reverse dependencies:
VIDEO_CX23885 && DVB_CORE && MEDIA_PCI_SUPPORT && MEDIA_SUPPORT && (MEDIA_ANALOG_TV_SUPPORT || MEDIA_DIGITAL_TV_SUPPORT) && MEDIA_ALTERA_CI (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/altera-stapl/Kconfig:3
An Altera FPGA module. Say Y when you want to support this tool.
Symbol VMWARE_VMCI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Misc devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VMware VMCI Driver" if X86 && PCI && NET (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/misc/vmw_vmci/Kconfig:5
This is VMware's Virtual Machine Communication Interface. It enables
high-speed communication between host and guest in a virtual
environment via the VMCI virtual device.
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called vmw_vmci.
Symbol RAID_ATTRS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RAID Transport Class" if BLOCK && SCSI_MOD (value: "y")
Default values:
n (value: "n")
Condition: BLOCK && SCSI_MOD (value: "y")
Selects:
(no selects)
Reverse dependencies:
PCI && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_MPT2SAS || PCI && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_MPT3SAS (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:8
Provides RAID
Symbol SCSI
Type : tristate
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI device support" if BLOCK (value: "y")
Default values:
(no default values)
Selects:
SCSI_DMA if HAS_DMA && BLOCK (value: "y")
Reverse dependencies:
HAS_IOMEM && BLOCK && (!(M32R || M68K || S390) || BROKEN) && ATA (value: "y")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:16
If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
any other SCSI device under Linux, say Y and make sure that you know
the name of your SCSI host adapter (the card inside your computer
that "speaks" the SCSI protocol, also called SCSI controller),
because you will be asked for it.
You also need to say Y here if you have a device which speaks
the SCSI protocol. Examples of this include the parallel port
version of the IOMEGA ZIP drive, USB storage devices, Fibre
Channel, and FireWire storage.
To compile this driver as a module, choose M here and read
<file:Documentation/scsi/scsi.txt>.
The module will be called scsi_mod.
However, do not compile this as a module if your root file system
(the one containing the directory /) is located on a SCSI device.
Symbol SCSI_TGT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI target support" if SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
SCSI && PCI && SCSI_LOWLEVEL && SCSI && SCSI_SRP (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:43
If you want to use SCSI target mode drivers enable this option.
If you choose M, the module will be called scsi_tgt.
Symbol SCSI_PROC_FS
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"legacy /proc/scsi/ support" if SCSI && PROC_FS (value: "y")
Default values:
y (value: "y")
Condition: SCSI && PROC_FS (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:55
This option enables support for the various files in
/proc/scsi. In Linux 2.6 this has been superseded by
files in sysfs but many legacy applications rely on this.
If unsure say Y.
Symbol BLK_DEV_SD
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI disk support" if SCSI (value: "y")
Default values:
(no default values)
Selects:
CRC_T10DIF if BLK_DEV_INTEGRITY && SCSI (value: "n")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:69
If you want to use SCSI hard disks, Fibre Channel disks,
Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
USB storage or the SCSI or parallel port version of
the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
the Disk-HOWTO and the Multi-Disk-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
CD-ROMs.
To compile this driver as a module, choose M here and read
<file:Documentation/scsi/scsi.txt>.
The module will be called sd_mod.
Do not compile this driver as a module if your root file system
(the one containing the directory /) is located on a SCSI disk.
In this case, do not compile the driver for your SCSI host adapter
(below) as a module either.
Symbol CHR_DEV_ST
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI tape support" if SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:91
If you want to use a SCSI tape drive under Linux, say Y and read the
SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>, and
<file:Documentation/scsi/st.txt> in the kernel source. This is NOT
for SCSI CD-ROMs.
To compile this driver as a module, choose M here and read
<file:Documentation/scsi/scsi.txt>. The module will be called st.
Symbol CHR_DEV_OSST
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI OnStream SC-x0 tape support" if SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:104
The OnStream SC-x0 SCSI tape drives cannot be driven by the
standard st driver, but instead need this special osst driver and
use the /dev/osstX char device nodes (major 206). Via usb-storage,
you may be able to drive the USB-x0 and DI-x0 drives as well.
Note that there is also a second generation of OnStream
tape drives (ADR-x0) that supports the standard SCSI-2 commands for
tapes (QIC-157) and can be driven by the standard driver st.
For more information, you may have a look at the SCSI-HOWTO
<http://www.tldp.org/docs.html#howto> and
<file:Documentation/scsi/osst.txt> in the kernel source.
More info on the OnStream driver may be found on
<http://sourceforge.net/projects/osst/>
Please also have a look at the standard st docu, as most of it
applies to osst as well.
To compile this driver as a module, choose M here and read
<file:Documentation/scsi/scsi.txt>. The module will be called osst.
Symbol BLK_DEV_SR
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI CDROM support" if SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:126
If you want to use a CD or DVD drive attached to your computer
by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
Make sure to say Y or M to "ISO 9660 CD-ROM file system support".
To compile this driver as a module, choose M here and read
<file:Documentation/scsi/scsi.txt>.
The module will be called sr_mod.
Symbol BLK_DEV_SR_VENDOR
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable vendor-specific extensions (for SCSI CDROM)" if BLK_DEV_SR (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:140
This enables the usage of vendor specific SCSI commands. This is
required to support multisession CDs with old NEC/TOSHIBA cdrom
drives (and HP Writers). If you have such a drive and get the first
session only, try saying Y here; everybody else says N.
Symbol CHR_DEV_SG
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI generic support" if SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:149
If you want to use SCSI scanners, synthesizers or CD-writers or just
about anything having "SCSI" in its name other than hard disks,
CD-ROMs or tapes, say Y here. These won't be supported by the kernel
directly, so you need some additional software which knows how to
talk to these devices using the SCSI protocol:
For scanners, look at SANE (<http://www.sane-project.org/>). For CD
writer software look at Cdrtools
(<http://cdrecord.berlios.de/private/cdrecord.html>)
and for burning a "disk at once": CDRDAO
(<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
For other devices, it's possible that you'll have to write the
driver software yourself. Please read the file
<file:Documentation/scsi/scsi-generic.txt> for more information.
To compile this driver as a module, choose M here and read
<file:Documentation/scsi/scsi.txt>. The module will be called sg.
If unsure, say N.
Symbol CHR_DEV_SCH
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI media changer support" if SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:174
This is a driver for SCSI media changers. Most common devices are
tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you
don't need this for those tiny 6-slot cdrom changers. Media
changers are listed as "Type: Medium Changer" in /proc/scsi/scsi.
If you have such hardware and want to use it with linux, say Y
here. Check <file:Documentation/scsi/scsi-changer.txt> for details.
If you want to compile this as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/kbuild/modules.txt> and
<file:Documentation/scsi/scsi.txt>. The module will be called ch.o.
If unsure, say N.
Symbol SCSI_MULTI_LUN
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Probe all LUNs on each SCSI device" if SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:200
Some devices support more than one LUN (Logical Unit Number) in order
to allow access to several media, e.g. CD jukebox, USB card reader,
mobile phone in mass storage mode. This option forces the kernel to
probe for all LUNs by default. This setting can be overriden by
max_luns boot/module parameter. Note that this option does not affect
devices conforming to SCSI-3 or higher as they can explicitely report
their number of LUNs. It is safe to say Y here unless you have one of
those rare devices which reacts in an unexpected way when probed for
multiple LUNs.
Symbol SCSI_SCAN_ASYNC
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Asynchronous SCSI scanning" if SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:248
The SCSI subsystem can probe for devices while the rest of the
system continues booting, and even probe devices on different
busses in parallel, leading to a significant speed-up.
If you have built SCSI as modules, enabling this option can
be a problem as the devices may not have been found by the
time your system expects them to have been. You can load the
scsi_wait_scan module to ensure that all scans have completed.
If you build your SCSI drivers into the kernel, then everything
will work fine if you say Y here.
You can override this choice by specifying "scsi_mod.scan=sync"
or async on the kernel's command line.
Symbol SCSI_SPI_ATTRS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
SCSI Transports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Parallel SCSI (SPI) Transport Attributes" if SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
ISA && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_AHA152X || (PCI || EISA) && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_AIC7XXX || PCI && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_AIC79XX || PCI && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_DMX3191D || ISA && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_DTC3280 || ISA && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_GENERIC_NCR5380 || ISA && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_GENERIC_NCR5380_MMIO || MCA && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_NCR_D700 || GSC && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_LASI700 || SNI_RM && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_SNI_53C710 || PCI && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_SYM53C8XX_2 || GSC && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_ZALON || MCA && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_NCR_Q720 || ISA && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_PAS16 || (EISA || MCA) && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_SIM710 || ISA && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_T128 || ARCH_ACORN && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_ACORNSCSI_3 || ARCH_ACORN && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_CUMANA_1 || ARCH_ACORN && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_OAK1 || MACH_JAZZ && SCSI && SCSI_LOWLEVEL && SCSI && JAZZ_ESP || AMIGA && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_A4000T || ZORRO && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_ZORRO7XX || ATARI && SCSI && SCSI_LOWLEVEL && SCSI && ATARI_SCSI || MAC && SCSI = y && SCSI_LOWLEVEL && SCSI && MAC_SCSI || MAC && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_MAC_ESP || MVME147 && SCSI = y && SCSI_LOWLEVEL && SCSI && MVME147_SCSI || MVME16x && SCSI && SCSI_LOWLEVEL && SCSI && MVME16x_SCSI || BVME6000 && SCSI && SCSI_LOWLEVEL && SCSI && BVME6000_SCSI || SUN3 && SCSI && SCSI_LOWLEVEL && SCSI && SUN3_SCSI || SUN3X && SCSI = y && SCSI_LOWLEVEL && SCSI && SUN3X_ESP || SBUS && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_SUNESP || SCSI_LOWLEVEL_PCMCIA && SCSI && PCMCIA && "m" && MODULES && PCMCIA_AHA152X || PCI && SCSI && FUSION && FUSION_SPI (value: "m")
Additional dependencies from enclosing menus and if's:
SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:269
If you wish to export transport-specific information about
each attached SCSI device to sysfs, say Y. Otherwise, say N.
Symbol SCSI_FC_ATTRS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
SCSI Transports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"FiberChannel Transport Attributes" if SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_NETLINK if SCSI (value: "y")
Reverse dependencies:
SCSI_LOWLEVEL && SCSI && LIBFC || PPC_PSERIES && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_IBMVFC || PCI && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_QLA_FC || PCI && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_LPFC || S390 && QDIO && SCSI && SCSI_LOWLEVEL && SCSI && ZFCP || PCI && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_BFA_FC || PCI && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_CHELSIO_FCOE || PCI && SCSI && FUSION && FUSION_FC (value: "m")
Additional dependencies from enclosing menus and if's:
SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:276
If you wish to export transport-specific information about
each attached FiberChannel device to sysfs, say Y.
Otherwise, say N.
Symbol SCSI_FC_TGT_ATTRS
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
SCSI device support
SCSI Transports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI target support for FiberChannel Transport Attributes" if SCSI_FC_ATTRS && (SCSI_TGT = y || SCSI_TGT = SCSI_FC_ATTRS) (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:285
If you want to use SCSI target mode drivers enable this option.
Symbol SCSI_ISCSI_ATTRS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
SCSI Transports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"iSCSI Transport Attributes" if SCSI && NET (value: "y")
Default values:
(no default values)
Selects:
BLK_DEV_BSGLIB if SCSI && NET (value: "y")
Reverse dependencies:
SCSI && INET && SCSI_LOWLEVEL && SCSI && ISCSI_TCP || PCI && INET && SCSI_LOWLEVEL && SCSI && SCSI_CXGB3_ISCSI || PCI && INET && SCSI_LOWLEVEL && SCSI && SCSI_CXGB4_ISCSI || NET && PCI && SCSI_LOWLEVEL && SCSI && SCSI_BNX2_ISCSI || PCI && SCSI && NET && SCSI_LOWLEVEL && SCSI && BE2ISCSI || PCI && SCSI && NET && SCSI_LOWLEVEL && SCSI && SCSI_QLA_ISCSI || SCSI && INET && INFINIBAND_ADDR_TRANS && INFINIBAND && INFINIBAND_ISER (value: "m")
Additional dependencies from enclosing menus and if's:
SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:292
If you wish to export transport-specific information about
each attached iSCSI device to sysfs, say Y.
Otherwise, say N.
Symbol SCSI_SAS_ATTRS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
SCSI Transports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SAS Transport Attributes" if SCSI (value: "y")
Default values:
(no default values)
Selects:
BLK_DEV_BSG if SCSI (value: "y")
Reverse dependencies:
SCSI && SCSI && SCSI_SAS_LIBSAS || PCI && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_MPT2SAS || PCI && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_MPT3SAS || PCI && SCSI && FUSION && FUSION_SAS (value: "m")
Additional dependencies from enclosing menus and if's:
SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:301
If you wish to export transport-specific information about
each attached SAS device to sysfs, say Y.
Symbol SCSI_SAS_LIBSAS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
SCSI Transports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SAS Domain Transport Attributes" if SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_SAS_ATTRS if SCSI (value: "y")
Reverse dependencies:
SCSI_LOWLEVEL && SCSI && PCI && SCSI_AIC94XX || SCSI_LOWLEVEL && SCSI && PCI && SCSI_MVSAS || PCI && SCSI && X86 && SCSI_LOWLEVEL && SCSI && SCSI_ISCI || PCI && SCSI && SCSI_LOWLEVEL && SCSI && SCSI_PM8001 (value: "n")
Additional dependencies from enclosing menus and if's:
SCSI (value: "y")
Locations: ../drivers/scsi/libsas/Kconfig:25
This provides transport specific helpers for SAS drivers which
use the domain device construct (like the aic94xxx).
Symbol SCSI_SAS_ATA
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
SCSI device support
SCSI Transports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ATA support for libsas (requires libata)" if SCSI_SAS_LIBSAS && (ATA = y || ATA = SCSI_SAS_LIBSAS) (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI (value: "y")
Locations: ../drivers/scsi/libsas/Kconfig:33
Builds in ATA support into libsas. Will necessitate
the loading of libata along with libsas.
Symbol SCSI_SAS_HOST_SMP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
SCSI device support
SCSI Transports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support for SMP interpretation for SAS hosts" if SCSI_SAS_LIBSAS (value: "m")
Default values:
y (value: "y")
Condition: SCSI_SAS_LIBSAS (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI (value: "y")
Locations: ../drivers/scsi/libsas/Kconfig:41
Allows sas hosts to receive SMP frames. Selecting this
option builds an SMP interpreter into libsas. Say
N here if you want to save the few kb this consumes.
Symbol SCSI_SRP_ATTRS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
SCSI Transports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SRP Transport Attributes" if SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
SCSI_LOWLEVEL && SCSI && PPC_PSERIES && SCSI_IBMVSCSI || SCSI && INFINIBAND && INFINIBAND_SRP (value: "n")
Additional dependencies from enclosing menus and if's:
SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:311
If you wish to export transport-specific information about
each attached SRP device to sysfs, say Y.
Symbol SCSI_SRP_TGT_ATTRS
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
SCSI device support
SCSI Transports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI target support for SRP Transport Attributes" if SCSI_SRP_ATTRS && (SCSI_TGT = y || SCSI_TGT = SCSI_SRP_ATTRS) (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:318
If you want to use SCSI target mode drivers enable this option.
Symbol SCSI_LOWLEVEL
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI low-level drivers" if SCSI != n (value: "y")
Default values:
y (value: "y")
Condition: SCSI != n (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/Kconfig:327
Symbol ISCSI_TCP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"iSCSI Initiator over TCP/IP" if SCSI && INET (value: "y")
Default values:
(no default values)
Selects:
CRYPTO if SCSI && INET (value: "y")
CRYPTO_MD5 if SCSI && INET (value: "y")
CRYPTO_CRC32C if SCSI && INET (value: "y")
SCSI_ISCSI_ATTRS if SCSI && INET (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:334
The iSCSI Driver provides a host with the ability to access storage
through an IP network. The driver uses the iSCSI protocol to transport
SCSI requests and responses over a TCP/IP network between the host
(the "initiator") and "targets". Architecturally, the iSCSI driver
combines with the host's TCP/IP stack, network drivers, and Network
Interface Card (NIC) to provide the same functions as a SCSI or a
Fibre Channel (FC) adapter driver with a Host Bus Adapter (HBA).
To compile this driver as a module, choose M here: the
module will be called iscsi_tcp.
The userspace component needed to initialize the driver, documentation,
and sample configuration files can be found here:
http://open-iscsi.org
Symbol ISCSI_BOOT_SYSFS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"iSCSI Boot Sysfs Interface"
Default values:
n (value: "n")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
PCI && SCSI && NET && SCSI_LOWLEVEL && SCSI && BE2ISCSI || PCI && SCSI && NET && SCSI_LOWLEVEL && SCSI && SCSI_QLA_ISCSI || ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL && ISCSI_IBFT (value: "n")
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:358
This option enables support for exposing iSCSI boot information
via sysfs to userspace. If you wish to export this information,
say Y. Otherwise, say N.
Symbol SCSI_CXGB3_ISCSI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Chelsio T3 iSCSI support" if PCI && INET (value: "y")
Default values:
(no default values)
Selects:
NETDEVICES if PCI && INET (value: "y")
ETHERNET if PCI && INET (value: "y")
NET_VENDOR_CHELSIO if PCI && INET (value: "y")
CHELSIO_T3 if PCI && INET (value: "y")
SCSI_ISCSI_ATTRS if PCI && INET (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/cxgbi/cxgb3i/Kconfig:1
This driver supports iSCSI offload for the Chelsio T3 devices.
Symbol SCSI_CXGB4_ISCSI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Chelsio T4 iSCSI support" if PCI && INET (value: "y")
Default values:
(no default values)
Selects:
NETDEVICES if PCI && INET (value: "y")
ETHERNET if PCI && INET (value: "y")
NET_VENDOR_CHELSIO if PCI && INET (value: "y")
CHELSIO_T4 if PCI && INET (value: "y")
SCSI_ISCSI_ATTRS if PCI && INET (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/cxgbi/cxgb4i/Kconfig:1
This driver supports iSCSI offload for the Chelsio T4 devices.
Symbol SCSI_BNX2_ISCSI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Broadcom NetXtreme II iSCSI support" if NET && PCI (value: "y")
Default values:
(no default values)
Selects:
SCSI_ISCSI_ATTRS if NET && PCI (value: "y")
NETDEVICES if NET && PCI (value: "y")
ETHERNET if NET && PCI (value: "y")
NET_VENDOR_BROADCOM if NET && PCI (value: "y")
CNIC if NET && PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/bnx2i/Kconfig:1
This driver supports iSCSI offload for the Broadcom NetXtreme II
devices.
Symbol SCSI_BNX2X_FCOE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Broadcom NetXtreme II FCoE support" if PCI (value: "y")
Default values:
(no default values)
Selects:
NETDEVICES if PCI (value: "y")
ETHERNET if PCI (value: "y")
NET_VENDOR_BROADCOM if PCI (value: "y")
LIBFC if PCI (value: "y")
LIBFCOE if PCI (value: "y")
CNIC if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/bnx2fc/Kconfig:1
This driver supports FCoE offload for the Broadcom NetXtreme II
devices.
Symbol BE2ISCSI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ServerEngines' 10Gbps iSCSI - BladeEngine 2" if PCI && SCSI && NET (value: "y")
Default values:
(no default values)
Selects:
SCSI_ISCSI_ATTRS if PCI && SCSI && NET (value: "y")
ISCSI_BOOT_SYSFS if PCI && SCSI && NET (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/be2iscsi/Kconfig:1
This driver implements the iSCSI functionality for ServerEngines'
10Gbps Storage adapter - BladeEngine 2.
Symbol BLK_DEV_3W_XXXX_RAID
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"3ware 5/6/7/8xxx ATA-RAID support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:378
3ware is the only hardware ATA-Raid product in Linux to date.
This card is 2,4, or 8 channel master mode support only.
SCSI support required!!!
<http://www.3ware.com/>
Please read the comments at the top of
<file:drivers/scsi/3w-xxxx.c>.
Symbol SCSI_HPSA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"HP Smart Array SCSI driver" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
CHECK_SIGNATURE if PCI && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:391
This driver supports HP Smart Array Controllers (circa 2009).
It is a SCSI alternative to the cciss driver, which is a block
driver. Anyone wishing to use HP Smart Array controllers who
would prefer the devices be presented to linux as SCSI devices,
rather than as generic block devices should say Y here.
Symbol SCSI_3W_9XXX
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"3ware 9xxx SATA-RAID support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:402
This driver supports the 9000 series 3ware SATA-RAID cards.
<http://www.amcc.com>
Please read the comments at the top of
<file:drivers/scsi/3w-9xxx.c>.
Symbol SCSI_3W_SAS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"3ware 97xx SAS/SATA-RAID support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:413
This driver supports the LSI 3ware 9750 6Gb/s SAS/SATA-RAID cards.
<http://www.lsi.com>
Please read the comments at the top of
<file:drivers/scsi/3w-sas.c>.
Symbol SCSI_ACARD
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ACARD SCSI support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:436
This driver supports the ACARD SCSI host adapter.
Support Chip <ATP870 ATP876 ATP880 ATP885>
To compile this driver as a module, choose M here: the
module will be called atp870u.
Symbol SCSI_AACRAID
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Adaptec AACRAID support" if SCSI && PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:489
This driver supports a variety of Dell, HP, Adaptec, IBM and
ICP storage products. For a list of supported products, refer
to <file:Documentation/scsi/aacraid.txt>.
To compile this driver as a module, choose M here: the module
will be called aacraid.
Symbol SCSI_AIC7XXX
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Adaptec AIC7xxx Fast -> U160 support (New Driver)" if (PCI || EISA) && SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_SPI_ATTRS if (PCI || EISA) && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/aic7xxx/Kconfig.aic7xxx:5
This driver supports all of Adaptec's Fast through Ultra 160 PCI
based SCSI controllers as well as the aic7770 based EISA and VLB
SCSI controllers (the 274x and 284x series). For AAA and ARO based
configurations, only SCSI functionality is provided.
To compile this driver as a module, choose M here: the
module will be called aic7xxx.
Symbol SCSI_AIC7XXX_OLD
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Adaptec AIC7xxx support (old driver)" if (ISA || EISA || PCI) && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:503
WARNING This driver is an older aic7xxx driver and is no longer
under active development. Adaptec, Inc. is writing a new driver to
take the place of this one, and it is recommended that whenever
possible, people should use the new Adaptec written driver instead
of this one. This driver will eventually be phased out entirely.
This is support for the various aic7xxx based Adaptec SCSI
controllers. These include the 274x EISA cards; 284x VLB cards;
2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
motherboard based SCSI controllers from Adaptec. It does not support
the AAA-13x RAID controllers from Adaptec, nor will it likely ever
support them. It does not support the 2920 cards from Adaptec that
use the Future Domain SCSI controller chip. For those cards, you
need the "Future Domain 16xx SCSI support" driver.
In general, if the controller is based on an Adaptec SCSI controller
chip from the aic777x series or the aic78xx series, this driver
should work. The only exception is the 7810 which is specifically
not supported (that's the RAID controller chip on the AAA-13x
cards).
Note that the AHA2920 SCSI host adapter is *not* supported by this
driver; choose "Future Domain 16xx SCSI support" instead if you have
one of those.
Information on the configuration options for this controller can be
found by checking the help file for each of the available
configuration options. You should read
<file:Documentation/scsi/aic7xxx_old.txt> at a minimum before
contacting the maintainer with any questions. The SCSI-HOWTO,
available from <http://www.tldp.org/docs.html#howto>, can also
be of great help.
To compile this driver as a module, choose M here: the
module will be called aic7xxx_old.
Symbol SCSI_AIC79XX
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Adaptec AIC79xx U320 support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_SPI_ATTRS if PCI && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/aic7xxx/Kconfig.aic79xx:5
This driver supports all of Adaptec's Ultra 320 PCI-X
based SCSI controllers.
Symbol SCSI_AIC94XX
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Adaptec AIC94xx SAS/SATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
SCSI_SAS_LIBSAS if PCI (value: "y")
FW_LOADER if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/aic94xx/Kconfig:27
This driver supports Adaptec's SAS/SATA 3Gb/s 64 bit PCI-X
AIC94xx chip based host adapters.
Symbol SCSI_MVSAS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Marvell 88SE64XX/88SE94XX SAS/SATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
SCSI_SAS_LIBSAS if PCI (value: "y")
FW_LOADER if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/mvsas/Kconfig:28
This driver supports Marvell's SAS/SATA 3Gb/s PCI-E 88SE64XX and 6Gb/s
PCI-E 88SE94XX chip based host adapters.
Symbol SCSI_MVUMI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Marvell UMI driver" if SCSI && PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:547
Module for Marvell Universal Message Interface(UMI) driver
To compile this driver as a module, choose M here: the
module will be called mvumi.
Symbol SCSI_DPT_I2O
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Adaptec I2O RAID support " if SCSI && PCI && VIRT_TO_BUS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:556
This driver supports all of Adaptec's I2O based RAID controllers as
well as the DPT SmartRaid V cards. This is an Adaptec maintained
driver by Deanna Bonds. See <file:Documentation/scsi/dpti.txt>.
To compile this driver as a module, choose M here: the
module will be called dpt_i2o.
Symbol SCSI_ADVANSYS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AdvanSys SCSI support" if SCSI && VIRT_TO_BUS && (ISA || EISA || PCI) (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:567
This is a driver for all SCSI host adapters manufactured by
AdvanSys. It is documented in the kernel source in
<file:drivers/scsi/advansys.c>.
To compile this driver as a module, choose M here: the
module will be called advansys.
Symbol SCSI_ARCMSR
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ARECA (ARC11xx/12xx/13xx/16xx) SATA/SAS RAID Host Adapter" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:591
This driver supports all of ARECA's SATA/SAS RAID controller cards.
This is an ARECA-maintained driver by Erich Chen.
If you have any problems, please mail to: <erich@areca.com.tw>.
Areca supports Linux RAID config tools.
Please link <http://www.areca.com.tw>
To compile this driver as a module, choose M here: the
module will be called arcmsr (modprobe arcmsr).
Symbol MEGARAID_NEWGEN
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"LSI Logic New Generation RAID Device Drivers" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/megaraid/Kconfig.megaraid:1
LSI Logic RAID Device Drivers
Symbol MEGARAID_LEGACY
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"LSI Logic Legacy MegaRAID Driver" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/megaraid/Kconfig.megaraid:67
This driver supports the LSI MegaRAID 418, 428, 438, 466, 762, 490
and 467 SCSI host adapters. This driver also support the all U320
RAID controllers
To compile this driver as a module, choose M here: the
module will be called megaraid
Symbol MEGARAID_SAS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"LSI Logic MegaRAID SAS RAID Module" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/megaraid/Kconfig.megaraid:78
Module for LSI Logic's SAS based RAID controllers.
To compile this driver as a module, choose 'm' here.
Module will be called megaraid_sas
Symbol SCSI_MPT2SAS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"LSI MPT Fusion SAS 2.0 Device Driver" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_SAS_ATTRS if PCI && SCSI (value: "y")
RAID_ATTRS if PCI && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/mpt2sas/Kconfig:43
This driver supports PCI-Express SAS 6Gb/s Host Adapters.
Symbol SCSI_MPT3SAS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"LSI MPT Fusion SAS 3.0 Device Driver" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_SAS_ATTRS if PCI && SCSI (value: "y")
RAID_ATTRS if PCI && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/mpt3sas/Kconfig:43
This driver supports PCI-Express SAS 12Gb/s Host Adapters.
Symbol SCSI_UFSHCD
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Universal Flash Storage Controller Driver Core" if SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/ufs/Kconfig:35
This selects the support for UFS devices in Linux, say Y and make
sure that you know the name of your UFS host adapter (the card
inside your computer that "speaks" the UFS protocol, also
called UFS Host Controller), because you will be asked for it.
The module will be called ufshcd.
To compile this driver as a module, choose M here and read
<file:Documentation/scsi/ufs.txt>.
However, do not compile this as a module if your root file system
(the one containing the directory /) is located on a UFS device.
Symbol SCSI_HPTIOP
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"HighPoint RocketRAID 3xxx/4xxx Controller support" if SCSI && PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:609
This option enables support for HighPoint RocketRAID 3xxx/4xxx
controllers.
To compile this driver as a module, choose M here; the module
will be called hptiop. If unsure, say N.
Symbol SCSI_BUSLOGIC
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"BusLogic SCSI support" if (PCI || ISA || MCA) && SCSI && ISA_DMA_API && VIRT_TO_BUS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:619
This is support for BusLogic MultiMaster and FlashPoint SCSI Host
Adapters. Consult the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>, and the files
<file:Documentation/scsi/BusLogic.txt> and
<file:Documentation/scsi/FlashPoint.txt> for more information.
Note that support for FlashPoint is only available for 32-bit
x86 configurations.
To compile this driver as a module, choose M here: the
module will be called BusLogic.
Symbol VMWARE_PVSCSI
Type : tristate
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VMware PVSCSI driver support" if PCI && SCSI && X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:643
This driver supports VMware's para virtualized SCSI HBA.
To compile this driver as a module, choose M here: the
module will be called vmw_pvscsi.
Symbol HYPERV_STORAGE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Microsoft Hyper-V virtual storage driver" if SCSI && HYPERV (value: "m")
Default values:
HYPERV (value: "m")
Condition: SCSI && HYPERV (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:651
Select this option to enable the Hyper-V virtual storage driver.
Symbol LIBFC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"LibFC module"
Default values:
(no default values)
Selects:
SCSI_FC_ATTRS
CRC32
Reverse dependencies:
SCSI_LOWLEVEL && SCSI && PCI && SCSI_BNX2X_FCOE || SCSI_LOWLEVEL && SCSI && LIBFCOE || SCSI_QLA_FC && TARGET_CORE && SCSI_LOWLEVEL && SCSI && TCM_QLA2XXX (value: "m")
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:658
Fibre Channel library module
Symbol LIBFCOE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"LibFCoE module"
Default values:
(no default values)
Selects:
LIBFC
Reverse dependencies:
SCSI_LOWLEVEL && SCSI && PCI && SCSI_BNX2X_FCOE || SCSI_LOWLEVEL && SCSI && PCI && FCOE || PCI && X86 && SCSI_LOWLEVEL && SCSI && FCOE_FNIC (value: "n")
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:665
Library for Fibre Channel over Ethernet module
Symbol FCOE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"FCoE module" if PCI (value: "y")
Default values:
(no default values)
Selects:
LIBFCOE if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:671
Fibre Channel over Ethernet module
Symbol FCOE_FNIC
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Cisco FNIC Driver" if PCI && X86 (value: "y")
Default values:
(no default values)
Selects:
LIBFCOE if PCI && X86 (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:678
This is support for the Cisco PCI-Express FCoE HBA.
To compile this driver as a module, choose M here and read
<file:Documentation/scsi/scsi.txt>.
The module will be called fnic.
Symbol SCSI_DMX3191D
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"DMX3191D SCSI support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_SPI_ATTRS if PCI && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:689
This is support for Domex DMX3191D SCSI Host Adapters.
To compile this driver as a module, choose M here: the
module will be called dmx3191d.
Symbol SCSI_EATA
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support" if (ISA || EISA || PCI) && SCSI && ISA_DMA_API (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:713
This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
ISA and all EISA I/O addresses are probed looking for the "EATA"
signature. The addresses of all the PCI SCSI controllers reported
by the PCI subsystem are probed as well.
You want to read the start of <file:drivers/scsi/eata.c> and the
SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose M here: the
module will be called eata.
Symbol SCSI_EATA_MAX_TAGS
Type : int
Value : "16"
User value : "16"
Xen config : ''
Main config : '16'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"maximum number of queued commands" if SCSI_EATA (value: "m")
Default values:
"16" (value: "n")
Condition: SCSI_EATA (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:748
This specifies how many SCSI commands can be maximally queued for
each probed SCSI device. You should reduce the default value of 16
only if you have disks with buggy or limited tagged command support.
Minimum is 2 and maximum is 62. This value is also the window size
used by the elevator sorting option above. The effective value used
by the driver for each probed SCSI device is reported at boot time.
This is equivalent to the "eata=mq:8" boot option.
Symbol SCSI_FUTURE_DOMAIN
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Future Domain 16xx SCSI/AHA-2920A support" if (ISA || PCI) && SCSI (value: "y")
Default values:
(no default values)
Selects:
CHECK_SIGNATURE if (ISA || PCI) && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:775
This is support for Future Domain's 16-bit SCSI host adapters
(TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
other adapters based on the Future Domain chipsets (Quantum
ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
It is explained in section 3.7 of the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
controller support"). This Future Domain driver works with the older
Adaptec AHA-2920A boards with a Future Domain chip on them.
To compile this driver as a module, choose M here: the
module will be called fdomain.
Symbol SCSI_GDTH
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel/ICP (former GDT SCSI Disk Array) RAID Controller support" if (ISA || EISA || PCI) && SCSI && ISA_DMA_API (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:795
Formerly called GDT SCSI Disk Array Controller Support.
This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
manufactured by Intel Corporation/ICP vortex GmbH. It is documented
in the kernel source in <file:drivers/scsi/gdth.c> and
<file:drivers/scsi/gdth.h>.
To compile this driver as a module, choose M here: the
module will be called gdth.
Symbol SCSI_ISCI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel(R) C600 Series Chipset SAS Controller" if PCI && SCSI && X86 (value: "y")
Default values:
(no default values)
Selects:
SCSI_SAS_LIBSAS if PCI && SCSI && X86 (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:809
This driver supports the 6Gb/s SAS capabilities of the storage
control unit found in the Intel(R) C600 series chipset.
Symbol SCSI_IPS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IBM ServeRAID support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:864
This is support for the IBM ServeRAID hardware RAID controllers.
See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID>
for more information. If this driver does not work correctly
without modification please contact the author by email at
<ipslinux@adaptec.com>.
To compile this driver as a module, choose M here: the
module will be called ips.
Symbol SCSI_INITIO
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Initio 9100U(W) support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:921
This is support for the Initio 91XXU(W) SCSI host adapter. Please
read the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose M here: the
module will be called initio.
Symbol SCSI_INIA100
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Initio INI-A100U2W support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:932
This is support for the Initio INI-A100U2W SCSI host adapter.
Please read the SCSI-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose M here: the
module will be called a100u2w.
Symbol SCSI_STEX
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Promise SuperTrak EX Series support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1073
This driver supports Promise SuperTrak EX series storage controllers.
Promise provides Linux RAID configuration utility for these
controllers. Please visit <http://www.promise.com> to download.
To compile this driver as a module, choose M here: the
module will be called stex.
Symbol SCSI_SYM53C8XX_2
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SYM53C8XX Version 2 SCSI support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_SPI_ATTRS if PCI && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1090
This driver supports the whole NCR53C8XX/SYM53C8XX family of
PCI-SCSI controllers. It also supports the subset of LSI53C10XX
Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
controllers; you need to use the Fusion MPT driver for that.
Please read <file:Documentation/scsi/sym53c8xx_2.txt> for more
information.
Symbol SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
Type : int
Value : "1"
User value : "1"
Xen config : ''
Main config : '1'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"DMA addressing mode" if SCSI_SYM53C8XX_2 (value: "m")
Default values:
"1" (value: "n")
Condition: SCSI_SYM53C8XX_2 (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1104
This option only applies to PCI-SCSI chips that are PCI DAC
capable (875A, 895A, 896, 1010-33, 1010-66, 1000).
When set to 0, the driver will program the chip to only perform
32-bit DMA. When set to 1, the chip will be able to perform DMA
to addresses up to 1TB. When set to 2, the driver supports the
full 64-bit DMA address range, but can only address 16 segments
of 4 GB each. This limits the total addressable range to 64 GB.
Most machines with less than 4GB of memory should use a setting
of 0 for best performance. If your machine has 4GB of memory
or more, you should set this option to 1 (the default).
The still experimental value 2 (64 bit DMA addressing with 16
x 4GB segments limitation) can be used on systems that require
PCI address bits past bit 39 to be set for the addressing of
memory using PCI DAC cycles.
Symbol SCSI_SYM53C8XX_DEFAULT_TAGS
Type : int
Value : "16"
User value : "16"
Xen config : ''
Main config : '16'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Default tagged command queue depth" if SCSI_SYM53C8XX_2 (value: "m")
Default values:
"16" (value: "n")
Condition: SCSI_SYM53C8XX_2 (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1127
This is the default value of the command queue depth the
driver will announce to the generic SCSI layer for devices
that support tagged command queueing. This value can be changed
from the boot command line. This is a soft limit that cannot
exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
Symbol SCSI_SYM53C8XX_MAX_TAGS
Type : int
Value : "64"
User value : "64"
Xen config : ''
Main config : '64'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Maximum number of queued commands" if SCSI_SYM53C8XX_2 (value: "m")
Default values:
"64" (value: "n")
Condition: SCSI_SYM53C8XX_2 (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1138
This option allows you to specify the maximum number of commands
that can be queued to any device, when tagged command queuing is
possible. The driver supports up to 256 queued commands per device.
This value is used as a compiled-in hard limit.
Symbol SCSI_SYM53C8XX_MMIO
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Use memory mapped IO" if SCSI_SYM53C8XX_2 (value: "m")
Default values:
y (value: "y")
Condition: SCSI_SYM53C8XX_2 (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1148
Memory mapped IO is faster than Port IO. Most people should
answer Y here, but some machines may have problems. If you have
to answer N here, please report the problem to the maintainer.
Symbol SCSI_IPR
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IBM Power Linux RAID adapter support" if PCI && SCSI && ATA (value: "y")
Default values:
(no default values)
Selects:
FW_LOADER if PCI && SCSI && ATA (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1157
This driver supports the IBM Power Linux family RAID adapters.
This includes IBM pSeries 5712, 5703, 5709, and 570A, as well
as IBM iSeries 5702, 5703, 5709, and 570A.
Symbol SCSI_QLOGIC_1280
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Qlogic QLA 1240/1x80/1x160 SCSI support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1328
Say Y if you have a QLogic ISP1240/1x80/1x160 SCSI host adapter.
To compile this driver as a module, choose M here: the
module will be called qla1280.
Symbol SCSI_QLA_FC
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"QLogic QLA2XXX Fibre Channel Support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_FC_ATTRS if PCI && SCSI (value: "y")
FW_LOADER if PCI && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/qla2xxx/Kconfig:1
This qla2xxx driver supports all QLogic Fibre Channel
PCI and PCIe host adapters.
By default, firmware for the ISP parts will be loaded
via the Firmware Loader interface.
ISP Firmware Filename
---------- -----------------
21xx ql2100_fw.bin
22xx ql2200_fw.bin
2300, 2312, 6312 ql2300_fw.bin
2322, 6322 ql2322_fw.bin
24xx, 54xx ql2400_fw.bin
25xx ql2500_fw.bin
Upon request, the driver caches the firmware image until
the driver is unloaded.
Firmware images can be retrieved from:
ftp://ftp.qlogic.com/outgoing/linux/firmware/
Symbol SCSI_QLA_ISCSI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"QLogic ISP4XXX and ISP82XX host adapter family support" if PCI && SCSI && NET (value: "y")
Default values:
(no default values)
Selects:
SCSI_ISCSI_ATTRS if PCI && SCSI && NET (value: "y")
ISCSI_BOOT_SYSFS if PCI && SCSI && NET (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/qla4xxx/Kconfig:1
This driver supports the QLogic 40xx (ISP4XXX), 8022 (ISP82XX)
and 8032 (ISP83XX) iSCSI host adapter family.
Symbol SCSI_LPFC
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Emulex LightPulse Fibre Channel Support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_FC_ATTRS if PCI && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1352
This lpfc driver supports the Emulex LightPulse
Family of Fibre Channel PCI host adapters.
Symbol SCSI_DC395x
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Tekram DC395(U/UW/F) and DC315(U) SCSI support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1394
This driver supports PCI SCSI host adapters based on the ASIC
TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants.
This driver works, but is still in experimental status. So better
have a bootable disk and a backup in case of emergency.
Documentation can be found in <file:Documentation/scsi/dc395x.txt>.
To compile this driver as a module, choose M here: the
module will be called dc395x.
Symbol SCSI_DC390T
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Tekram DC390(T) and Am53/79C974 SCSI support" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1409
This driver supports PCI SCSI host adapters based on the Am53C974A
chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
PCscsi/PCnet (Am53/79C974) solutions.
Documentation can be found in <file:Documentation/scsi/tmscsim.txt>.
Note that this driver does NOT support Tekram DC390W/U/F, which are
based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
To compile this driver as a module, choose M here: the
module will be called tmscsim.
Symbol SCSI_DEBUG
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI debugging host simulator" if SCSI (value: "y")
Default values:
(no default values)
Selects:
CRC_T10DIF if SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1519
This is a host adapter simulator that can simulate multiple hosts
each with multiple dummy SCSI devices (disks). It defaults to one
host adapter with one dummy SCSI disk. Each dummy disk uses kernel
RAM as storage (i.e. it is a ramdisk). To save space when multiple
dummy disks are simulated, they share the same kernel RAM for
their storage. See <http://sg.danny.cz/sg/sdebug26.html> for more
information. This driver is primarily of use to those testing the
SCSI and block subsystems. If unsure, say N.
Symbol SCSI_PM8001
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PMC-Sierra SPC 8001 SAS/SATA Based Host Adapter driver" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_SAS_LIBSAS if PCI && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1781
This driver supports PMC-Sierra PCIE SAS/SATA 8x6G SPC 8001 chip
based host adapters.
Symbol SCSI_SRP
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI RDMA Protocol helper library" if SCSI && PCI (value: "y")
Default values:
(no default values)
Selects:
SCSI_TGT if SCSI && PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1789
If you wish to use SRP target drivers, say Y.
To compile this driver as a module, choose M here: the
module will be called libsrp.
Symbol SCSI_VIRTIO
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"virtio-scsi support" if VIRTIO (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SCSI_LOWLEVEL && SCSI (value: "y")
Locations: ../drivers/scsi/Kconfig:1809
This is the virtual HBA driver for virtio. If the kernel will
be used in a virtual machine, say Y or M.
Symbol SCSI_DH
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SCSI Device Handlers" if SCSI (value: "y")
Default values:
n (value: "n")
Condition: SCSI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/device_handler/Kconfig:5
SCSI Device Handlers provide device specific support for
devices utilized in multipath configurations. Say Y here to
select support for specific hardware.
Symbol SCSI_DH_RDAC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"LSI RDAC Device Handler" if SCSI_DH (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/device_handler/Kconfig:14
If you have a LSI RDAC select y. Otherwise, say N.
Symbol SCSI_DH_HP_SW
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"HP/COMPAQ MSA Device Handler" if SCSI_DH (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/device_handler/Kconfig:20
If you have a HP/COMPAQ MSA device that requires START_STOP to
be sent to start it and cannot upgrade the firmware then select y.
Otherwise, say N.
Symbol SCSI_DH_EMC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"EMC CLARiiON Device Handler" if SCSI_DH (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/device_handler/Kconfig:28
If you have a EMC CLARiiON select y. Otherwise, say N.
Symbol SCSI_DH_ALUA
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SPC-3 ALUA Device Handler" if SCSI_DH (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/device_handler/Kconfig:34
SCSI Device handler for generic SPC-3 Asymmetric Logical Unit
Access (ALUA).
Symbol SCSI_OSD_INITIATOR
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"OSD-Initiator library" if SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/osd/Kconfig:14
Enable the OSD-Initiator library (libosd.ko).
NOTE: You must also select CRYPTO_SHA1 + CRYPTO_HMAC and their
dependencies
Symbol SCSI_OSD_ULD
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"OSD Upper Level driver" if SCSI_OSD_INITIATOR (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/osd/Kconfig:22
Build a SCSI upper layer driver that exports /dev/osdX devices
to user-mode for testing and controlling OSD devices. It is also
needed by exofs, for mounting an OSD based file system.
Symbol SCSI_OSD_DPRINT_SENSE
Type : int
Value : "1"
User value : "1"
Xen config : ''
Main config : '1'
Visibility : "y"
Device Drivers
SCSI device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"(0-2) When sense is returned, DEBUG print all sense descriptors" if SCSI_OSD_INITIATOR (value: "m")
Default values:
1 (value: "n")
Condition: SCSI_OSD_INITIATOR (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/scsi/osd/Kconfig:30
When a CHECK_CONDITION status is returned from a target, and a
sense-buffer is retrieved, turning this on will dump a full
sense-decoding message. Setting to 2 will also print recoverable
errors that might be regularly returned for some filesystem
operations.
Symbol ATA
Type : tristate
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Serial ATA and Parallel ATA drivers" if HAS_IOMEM && BLOCK && (!(M32R || M68K || S390) || BROKEN) (value: "y")
Default values:
(no default values)
Selects:
SCSI if HAS_IOMEM && BLOCK && (!(M32R || M68K || S390) || BROKEN) (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/ata/Kconfig:13
If you want to use a ATA hard disk, ATA tape drive, ATA CD-ROM or
any other ATA device under Linux, say Y and make sure that you know
the name of your ATA host adapter (the card inside your computer
that "speaks" the ATA protocol, also called ATA controller),
because you will be asked for it.
NOTE: ATA enables basic SCSI support; *however*,
'SCSI disk support', 'SCSI tape support', or
'SCSI CDROM support' may also be needed,
depending on your hardware configuration.
Symbol ATA_VERBOSE_ERROR
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Verbose ATA error reporting"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA (value: "y")
Locations: ../drivers/ata/Kconfig:37
This option adds parsing of ATA command descriptions and error bits
in libata kernel output, making it easier to interpret.
This option will enlarge the kernel by approx. 6KB. Disable it only
if kernel size is more important than ease of debugging.
If unsure, say Y.
Symbol ATA_ACPI
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ATA ACPI Support" if ACPI && PCI (value: "y")
Default values:
y (value: "y")
Condition: ACPI && PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA (value: "y")
Locations: ../drivers/ata/Kconfig:48
This option adds support for ATA-related ACPI objects.
These ACPI objects add the ability to retrieve taskfiles
from the ACPI BIOS and write them to the disk controller.
These objects may be related to performance, security,
power management, or other areas.
You can disable this at kernel boot time by using the
option libata.noacpi=1
Symbol SATA_PMP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SATA Port Multiplier support"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA (value: "y")
Locations: ../drivers/ata/Kconfig:75
This option adds support for SATA Port Multipliers
(the SATA version of an ethernet hub, or SAS expander).
Symbol SATA_AHCI
Type : tristate
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AHCI SATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA (value: "y")
Locations: ../drivers/ata/Kconfig:84
This option enables support for AHCI Serial ATA.
If unsure, say N.
Symbol SATA_AHCI_PLATFORM
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Platform AHCI SATA support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA (value: "y")
Locations: ../drivers/ata/Kconfig:92
This option enables support for Platform AHCI Serial ATA
controllers.
If unsure, say N.
Symbol SATA_INIC162X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Initio 162x SATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA (value: "y")
Locations: ../drivers/ata/Kconfig:109
This option enables support for Initio 162x Serial ATA.
Symbol SATA_ACARD_AHCI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ACard AHCI variant (ATP 8620)" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA (value: "y")
Locations: ../drivers/ata/Kconfig:115
This option enables support for Acard.
If unsure, say N.
Symbol SATA_SIL24
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Silicon Image 3124/3132 SATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA (value: "y")
Locations: ../drivers/ata/Kconfig:123
This option enables support for Silicon Image 3124/3132 Serial ATA.
If unsure, say N.
Symbol ATA_SFF
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ATA SFF support (for legacy IDE and PATA)"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA (value: "y")
Locations: ../drivers/ata/Kconfig:131
This option adds support for ATA controllers with SFF
compliant or similar programming interface.
SFF is the legacy IDE interface that has been around since
the dawn of time. Almost all PATA controllers have an
SFF interface. Many SATA controllers have an SFF interface
when configured into a legacy compatibility mode.
For users with exclusively modern controllers like AHCI,
Silicon Image 3124, or Marvell 6440, you may choose to
disable this unneeded SFF support.
If unsure, say Y.
Symbol PDC_ADMA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Pacific Digital ADMA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA (value: "y")
Locations: ../drivers/ata/Kconfig:153
This option enables support for Pacific Digital ADMA controllers
If unsure, say N.
Symbol SATA_QSTOR
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Pacific Digital SATA QStor support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA (value: "y")
Locations: ../drivers/ata/Kconfig:170
This option enables support for Pacific Digital Serial ATA QStor.
If unsure, say N.
Symbol SATA_SX4
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Promise SATA SX4 support (Experimental)" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA (value: "y")
Locations: ../drivers/ata/Kconfig:178
This option enables support for Promise Serial ATA SX4.
If unsure, say N.
Symbol ATA_BMDMA
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ATA BMDMA support"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA (value: "y")
Locations: ../drivers/ata/Kconfig:186
This option adds support for SFF ATA controllers with BMDMA
capability. BMDMA stands for bus-master DMA and is the
de facto DMA interface for SFF controllers.
If unsure, say Y.
Symbol ATA_PIIX
Type : tristate
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:200
This option enables support for ICH5/6/7/8 Serial ATA
and support for PATA on the Intel ESB/ICH/PIIX3/PIIX4 series
host controllers.
If unsure, say N.
Symbol SATA_HIGHBANK
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Calxeda Highbank SATA support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:231
This option enables support for the Calxeda Highbank SoC's
onboard SATA.
If unsure, say N.
Symbol SATA_MV
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Marvell SATA support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:239
This option enables support for the Marvell Serial ATA family.
Currently supports 88SX[56]0[48][01] PCI(-X) chips,
as well as the newer [67]042 PCI-X/PCIe and SOC devices.
If unsure, say N.
Symbol SATA_NV
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"NVIDIA SATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:248
This option enables support for NVIDIA Serial ATA.
If unsure, say N.
Symbol SATA_PROMISE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Promise SATA TX2/TX4 support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:256
This option enables support for Promise Serial ATA TX2/TX4.
If unsure, say N.
Symbol SATA_SIL
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Silicon Image SATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:272
This option enables support for Silicon Image Serial ATA.
If unsure, say N.
Symbol SATA_SIS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SiS 964/965/966/180 SATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
PATA_SIS if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:280
This option enables support for SiS Serial ATA on
SiS 964/965/966/180 and Parallel ATA on SiS 180.
The PATA support for SiS 180 requires additionally to
enable the PATA_SIS driver in the config.
If unsure, say N.
Symbol SATA_SVW
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ServerWorks Frodo / Apple K2 SATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:291
This option enables support for Broadcom/Serverworks/Apple K2
SATA support.
If unsure, say N.
Symbol SATA_ULI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ULi Electronics SATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:300
This option enables support for ULi Electronics SATA.
If unsure, say N.
Symbol SATA_VIA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VIA SATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:308
This option enables support for VIA Serial ATA.
If unsure, say N.
Symbol SATA_VITESSE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VITESSE VSC-7174 / INTEL 31244 SATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:316
This option enables support for Vitesse VSC7174 and Intel 31244 Serial ATA.
If unsure, say N.
Symbol PATA_ALI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ALi PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:326
This option enables support for the ALi ATA interfaces
found on the many ALi chipsets.
If unsure, say N.
Symbol PATA_AMD
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD/NVidia PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:335
This option enables support for the AMD and NVidia PATA
interfaces found on the chipsets for Athlon/Athlon64.
If unsure, say N.
Symbol PATA_ARASAN_CF
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ARASAN CompactFlash PATA Controller Support" if DMADEVICES (value: "y")
Default values:
(no default values)
Selects:
DMA_ENGINE if DMADEVICES (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:344
Say Y here to support the ARASAN CompactFlash PATA controller
Symbol PATA_ARTOP
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ARTOP 6210/6260 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:351
This option enables support for ARTOP PATA controllers.
If unsure, say N.
Symbol PATA_ATIIXP
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ATI PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:359
This option enables support for the ATI ATA interfaces
found on the many ATI chipsets.
If unsure, say N.
Symbol PATA_ATP867X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ARTOP/Acard ATP867X PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:368
This option enables support for ARTOP/Acard ATP867X PATA
controllers.
If unsure, say N.
Symbol PATA_CMD64X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CMD64x PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:386
This option enables support for the CMD64x series chips
except for the CMD640.
If unsure, say N.
Symbol PATA_CS5520
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CS5510/5520 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:395
This option enables support for the Cyrix 5510/5520
companion chip used with the MediaGX/Geode processor family.
If unsure, say N.
Symbol PATA_CS5530
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CS5530 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:404
This option enables support for the Cyrix/NatSemi/AMD CS5530
companion chip used with the MediaGX/Geode processor family.
If unsure, say N.
Symbol PATA_CS5536
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CS5536 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:422
This option enables support for the AMD CS5536
companion chip used with the Geode LX processor family.
If unsure, say N.
Symbol PATA_CYPRESS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Cypress CY82C693 PATA support (Very Experimental)" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:431
This option enables support for the Cypress/Contaq CY82C693
chipset found in some Alpha systems
If unsure, say N.
Symbol PATA_EFAR
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"EFAR SLC90E66 support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:440
This option enables support for the EFAR SLC90E66
IDE controller found on some older machines.
If unsure, say N.
Symbol PATA_HPT366
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"HPT 366/368 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:458
This option enables support for the HPT 366 and 368
PATA controllers via the new ATA layer.
If unsure, say N.
Symbol PATA_HPT37X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"HPT 370/370A/371/372/374/302 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:467
This option enables support for the majority of the later HPT
PATA controllers via the new ATA layer.
If unsure, say N.
Symbol PATA_HPT3X2N
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"HPT 371N/372N/302N PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:476
This option enables support for the N variant HPT PATA
controllers via the new ATA layer.
If unsure, say N.
Symbol PATA_HPT3X3
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"HPT 343/363 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:485
This option enables support for the HPT 343/363
PATA controllers via the new ATA layer
If unsure, say N.
Symbol PATA_IT8213
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IT8213 PATA support (Experimental)" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:519
This option enables support for the ITE 821 PATA
controllers via the new ATA layer.
If unsure, say N.
Symbol PATA_IT821X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IT8211/2 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:528
This option enables support for the ITE 8211 and 8212
PATA controllers via the new ATA layer, including RAID
mode.
If unsure, say N.
Symbol PATA_JMICRON
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"JMicron PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:538
Enable support for the JMicron IDE controller, via the new
ATA layer.
If unsure, say N.
Symbol PATA_MARVELL
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Marvell PATA support via legacy mode" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:556
This option enables limited support for the Marvell 88SE61xx ATA
controllers. If you wish to use only the SATA ports then select
the AHCI driver alone. If you wish to the use the PATA port or
both SATA and PATA include this driver.
If unsure, say N.
Symbol PATA_NETCELL
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"NETCELL Revolution RAID support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:577
This option enables support for the Netcell Revolution RAID
PATA controller.
If unsure, say N.
Symbol PATA_NINJA32
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Ninja32/Delkin Cardbus ATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:586
This option enables support for the Ninja32, Delkin and
possibly other brands of Cardbus ATA adapter
If unsure, say N.
Symbol PATA_NS87415
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Nat Semi NS87415 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:595
This option enables support for the National Semiconductor
NS87415 PCI-IDE controller.
If unsure, say N.
Symbol PATA_OLDPIIX
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel PATA old PIIX support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:604
This option enables support for early PIIX PATA support.
If unsure, say N.
Symbol PATA_OPTIDMA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"OPTI FireStar PATA support (Very Experimental)" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:612
This option enables DMA/PIO support for the later OPTi
controllers found on some old motherboards and in some
laptops.
If unsure, say N.
Symbol PATA_PDC2027X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Promise PATA 2027x support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:622
This option enables support for Promise PATA pdc20268 to pdc20277 host adapters.
If unsure, say N.
Symbol PATA_PDC_OLD
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Older Promise PATA controller support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:630
This option enables support for the Promise 20246, 20262, 20263,
20265 and 20267 adapters.
If unsure, say N.
Symbol PATA_RADISYS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RADISYS 82600 PATA support (Experimental)" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:639
This option enables support for the RADISYS 82600
PATA controllers via the new ATA layer
If unsure, say N.
Symbol PATA_RDC
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RDC PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:648
This option enables basic support for the later RDC PATA controllers
controllers via the new ATA layer. For the RDC 1010, you need to
enable the IT821X driver instead.
If unsure, say N.
Symbol PATA_SC1200
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SC1200 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:658
This option enables support for the NatSemi/AMD SC1200 SoC
companion chip used with the Geode processor family.
If unsure, say N.
Symbol PATA_SCH
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel SCH PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:676
This option enables support for Intel SCH PATA on the Intel
SCH (US15W, US15L, UL11L) series host controllers.
If unsure, say N.
Symbol PATA_SERVERWORKS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SERVERWORKS OSB4/CSB5/CSB6/HT1000 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:685
This option enables support for the Serverworks OSB4/CSB5/CSB6 and
HT1000 PATA controllers, via the new ATA layer.
If unsure, say N.
Symbol PATA_SIL680
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CMD / Silicon Image 680 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:694
This option enables support for CMD / Silicon Image 680 PATA.
If unsure, say N.
Symbol PATA_SIS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SiS PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
ATA_SFF && ATA && ATA_BMDMA && PCI && SATA_SIS (value: "n")
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:702
This option enables support for SiS PATA controllers
If unsure, say N.
Symbol PATA_TOSHIBA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Toshiba Piccolo support (Experimental)" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:710
Support for the Toshiba Piccolo controllers. Currently only the
primary channel is supported by this driver.
If unsure, say N.
Symbol PATA_TRIFLEX
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Compaq Triflex PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:719
Enable support for the Compaq 'Triflex' IDE controller as found
on many Compaq Pentium-Pro systems, via the new ATA layer.
If unsure, say N.
Symbol PATA_VIA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VIA PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:728
This option enables support for the VIA PATA interfaces
found on the many VIA chipsets.
If unsure, say N.
Symbol PATA_WINBOND
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Winbond SL82C105 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA && ATA_BMDMA (value: "y")
Locations: ../drivers/ata/Kconfig:748
This option enables support for SL82C105 PATA devices found in the
Netwinder and some other systems
If unsure, say N.
Symbol PATA_CMD640_PCI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CMD640 PCI PATA support (Experimental)" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA (value: "y")
Locations: ../drivers/ata/Kconfig:778
This option enables support for the CMD640 PCI IDE
interface chip. Only the primary channel is currently
supported.
If unsure, say N.
Symbol PATA_MPIIX
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel PATA MPIIX support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA (value: "y")
Locations: ../drivers/ata/Kconfig:807
This option enables support for MPIIX PATA support.
If unsure, say N.
Symbol PATA_NS87410
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Nat Semi NS87410 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA (value: "y")
Locations: ../drivers/ata/Kconfig:815
This option enables support for the National Semiconductor
NS87410 PCI-IDE controller.
If unsure, say N.
Symbol PATA_OPTI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"OPTI621/6215 PATA support (Very Experimental)" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA (value: "y")
Locations: ../drivers/ata/Kconfig:824
This option enables full PIO support for the early Opti ATA
controllers found on some old motherboards.
If unsure, say N.
Symbol PATA_PLATFORM
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Generic platform device PATA support" if EXPERT || PPC || HAVE_PATA_PLATFORM (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA (value: "y")
Locations: ../drivers/ata/Kconfig:851
This option enables support for generic directly connected ATA
devices commonly found on embedded systems.
If unsure, say N.
Symbol PATA_RZ1000
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PC Tech RZ1000 PATA support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA (value: "y")
Locations: ../drivers/ata/Kconfig:886
This option enables basic support for the PC Tech RZ1000/1
PATA controllers via the new ATA layer
If unsure, say N.
Symbol PATA_ACPI
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ACPI firmware driver for PATA" if ATA_ACPI && ATA_BMDMA (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA (value: "y")
Locations: ../drivers/ata/Kconfig:914
This option enables an ACPI method driver which drives
motherboard PATA controller interfaces through the ACPI
firmware in the BIOS. This driver can sometimes handle
otherwise unsupported hardware.
Symbol ATA_GENERIC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Generic ATA support" if PCI && ATA_BMDMA (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA (value: "y")
Locations: ../drivers/ata/Kconfig:923
This option enables support for generic BIOS configured
ATA controllers via the new ATA layer
If unsure, say N.
Symbol PATA_LEGACY
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Legacy ISA PATA support (Experimental)" if ISA || PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
ATA_SFF && ATA && ISA && PATA_QDI || ATA_SFF && ATA && ISA && PATA_WINBOND_VLB (value: "n")
Additional dependencies from enclosing menus and if's:
ATA_SFF && ATA (value: "y")
Locations: ../drivers/ata/Kconfig:932
This option enables support for ISA/VLB/PCI bus legacy PATA
ports and allows them to be accessed via the new ATA layer.
If unsure, say N.
Symbol BLK_DEV_MD
Type : tristate
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RAID support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
BLK_DEV_DM && MD && DM_RAID (value: "m")
Additional dependencies from enclosing menus and if's:
MD (value: "y")
Locations: ../drivers/md/Kconfig:14
This driver lets you combine several hard disk partitions into one
logical block device. This can be used to simply append one
partition to another one or to combine several redundant hard disks
into a RAID1/4/5 device so as to provide protection against hard
disk failures. This is called "Software RAID" since the combining of
the partitions is done by the kernel. "Hardware RAID" means that the
combining is done by a dedicated controller; if you have such a
controller, you do not need to say Y here.
More information about Software RAID on Linux is contained in the
Software RAID mini-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. There you will also learn
where to get the supporting user space utilities raidtools.
If unsure, say N.
Symbol MD_LINEAR
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Linear (append) mode" if BLK_DEV_MD (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
MD (value: "y")
Locations: ../drivers/md/Kconfig:47
If you say Y here, then your multiple devices driver will be able to
use the so-called linear mode, i.e. it will combine the hard disk
partitions by simply appending one to the other.
To compile this as a module, choose M here: the module
will be called linear.
If unsure, say Y.
Symbol MD_RAID0
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RAID-0 (striping) mode" if BLK_DEV_MD (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
MD (value: "y")
Locations: ../drivers/md/Kconfig:60
If you say Y here, then your multiple devices driver will be able to
use the so-called raid0 mode, i.e. it will combine the hard disk
partitions into one logical device in such a fashion as to fill them
up evenly, one chunk here and one chunk there. This will increase
the throughput rate if the partitions reside on distinct disks.
Information about Software RAID on Linux is contained in the
Software-RAID mini-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. There you will also
learn where to get the supporting user space utilities raidtools.
To compile this as a module, choose M here: the module
will be called raid0.
If unsure, say Y.
Symbol MD_RAID1
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RAID-1 (mirroring) mode" if BLK_DEV_MD (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
BLK_DEV_DM && MD && DM_RAID (value: "m")
Additional dependencies from enclosing menus and if's:
MD (value: "y")
Locations: ../drivers/md/Kconfig:80
A RAID-1 set consists of several disk drives which are exact copies
of each other. In the event of a mirror failure, the RAID driver
will continue to use the operational mirrors in the set, providing
an error free MD (multiple device) to the higher levels of the
kernel. In a set with N drives, the available space is the capacity
of a single drive, and the set protects against a failure of (N - 1)
drives.
Information about Software RAID on Linux is contained in the
Software-RAID mini-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. There you will also
learn where to get the supporting user space utilities raidtools.
If you want to use such a RAID-1 set, say Y. To compile this code
as a module, choose M here: the module will be called raid1.
If unsure, say Y.
Symbol MD_RAID10
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RAID-10 (mirrored striping) mode" if BLK_DEV_MD (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
BLK_DEV_DM && MD && DM_RAID (value: "m")
Additional dependencies from enclosing menus and if's:
MD (value: "y")
Locations: ../drivers/md/Kconfig:102
RAID-10 provides a combination of striping (RAID-0) and
mirroring (RAID-1) with easier configuration and more flexible
layout.
Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
be the same size (or at least, only as much as the smallest device
will be used).
RAID-10 provides a variety of layouts that provide different levels
of redundancy and performance.
RAID-10 requires mdadm-1.7.0 or later, available at:
ftp://ftp.kernel.org/pub/linux/utils/raid/mdadm/
If unsure, say Y.
Symbol MD_RAID456
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RAID-4/RAID-5/RAID-6 mode" if BLK_DEV_MD (value: "y")
Default values:
(no default values)
Selects:
RAID6_PQ if BLK_DEV_MD (value: "y")
ASYNC_MEMCPY if BLK_DEV_MD (value: "y")
ASYNC_XOR if BLK_DEV_MD (value: "y")
ASYNC_PQ if BLK_DEV_MD (value: "y")
ASYNC_RAID6_RECOV if BLK_DEV_MD (value: "y")
Reverse dependencies:
BLK_DEV_DM && MD && DM_RAID (value: "m")
Additional dependencies from enclosing menus and if's:
MD (value: "y")
Locations: ../drivers/md/Kconfig:121
A RAID-5 set of N drives with a capacity of C MB per drive provides
the capacity of C * (N - 1) MB, and protects against a failure
of a single drive. For a given sector (row) number, (N - 1) drives
contain data sectors, and one drive contains the parity protection.
For a RAID-4 set, the parity blocks are present on a single drive,
while a RAID-5 set distributes the parity across the drives in one
of the available parity distribution methods.
A RAID-6 set of N drives with a capacity of C MB per drive
provides the capacity of C * (N - 2) MB, and protects
against a failure of any two drives. For a given sector
(row) number, (N - 2) drives contain data sectors, and two
drives contains two independent redundancy syndromes. Like
RAID-5, RAID-6 distributes the syndromes across the drives
in one of the available parity distribution methods.
Information about Software RAID on Linux is contained in the
Software-RAID mini-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. There you will also
learn where to get the supporting user space utilities raidtools.
If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To
compile this code as a module, choose M here: the module
will be called raid456.
If unsure, say Y.
Symbol MD_MULTIPATH
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Multipath I/O support" if BLK_DEV_MD (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
MD (value: "y")
Locations: ../drivers/md/Kconfig:157
MD_MULTIPATH provides a simple multi-path personality for use
the MD framework. It is not under active development. New
projects should consider using DM_MULTIPATH which has more
features and more testing.
If unsure, say N.
Symbol MD_FAULTY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Faulty test module for MD" if BLK_DEV_MD (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
MD (value: "y")
Locations: ../drivers/md/Kconfig:168
The "faulty" module allows for a block device that occasionally returns
read or write errors. It is useful for testing.
In unsure, say N.
Symbol DM_CACHE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Cache target (EXPERIMENTAL)" if BLK_DEV_DM (value: "m")
Default values:
n (value: "n")
Condition: BLK_DEV_DM (value: "m")
Selects:
DM_PERSISTENT_DATA if BLK_DEV_DM (value: "m")
DM_BIO_PRISON if BLK_DEV_DM (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
MD (value: "y")
Locations: ../drivers/md/Kconfig:260
dm-cache attempts to improve performance of a block device by
moving frequently used data to a smaller, higher performance
device. Different 'policy' plugins can be used to change the
algorithms used to select which blocks are promoted, demoted,
cleaned etc. It supports writeback and writethrough modes.
Symbol DM_RAID
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RAID 1/4/5/6/10 target" if BLK_DEV_DM (value: "m")
Default values:
(no default values)
Selects:
MD_RAID1 if BLK_DEV_DM (value: "m")
MD_RAID10 if BLK_DEV_DM (value: "m")
MD_RAID456 if BLK_DEV_DM (value: "m")
BLK_DEV_MD if BLK_DEV_DM (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
MD (value: "y")
Locations: ../drivers/md/Kconfig:298
A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings
A RAID-5 set of N drives with a capacity of C MB per drive provides
the capacity of C * (N - 1) MB, and protects against a failure
of a single drive. For a given sector (row) number, (N - 1) drives
contain data sectors, and one drive contains the parity protection.
For a RAID-4 set, the parity blocks are present on a single drive,
while a RAID-5 set distributes the parity across the drives in one
of the available parity distribution methods.
A RAID-6 set of N drives with a capacity of C MB per drive
provides the capacity of C * (N - 2) MB, and protects
against a failure of any two drives. For a given sector
(row) number, (N - 2) drives contain data sectors, and two
drives contains two independent redundancy syndromes. Like
RAID-5, RAID-6 distributes the syndromes across the drives
in one of the available parity distribution methods.
Symbol DM_LOG_USERSPACE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Mirror userspace logging" if DM_MIRROR && NET (value: "m")
Default values:
(no default values)
Selects:
CONNECTOR if DM_MIRROR && NET (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
MD (value: "y")
Locations: ../drivers/md/Kconfig:324
The userspace logging module provides a mechanism for
relaying the dm-dirty-log API to userspace. Log designs
which are more suited to userspace implementation (e.g.
shared storage logs) or experimental logs can be implemented
by leveraging this framework.
Symbol DM_VERITY
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Verity target support" if BLK_DEV_DM (value: "m")
Default values:
(no default values)
Selects:
CRYPTO if BLK_DEV_DM (value: "m")
CRYPTO_HASH if BLK_DEV_DM (value: "m")
DM_BUFIO if BLK_DEV_DM (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
MD (value: "y")
Locations: ../drivers/md/Kconfig:393
This device-mapper target creates a read-only device that
transparently validates the data on one underlying device against
a pre-generated tree of cryptographic checksums stored on a second
device.
You'll need to activate the digests you're going to use in the
cryptoapi configuration.
To compile this code as a module, choose M here: the module will
be called dm-verity.
If unsure, say N.
Symbol TARGET_CORE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Generic Target Core Mod (TCM) and ConfigFS Infrastructure" if SCSI && BLOCK (value: "y")
Default values:
n (value: "n")
Condition: SCSI && BLOCK (value: "y")
Selects:
CONFIGFS_FS if SCSI && BLOCK (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/target/Kconfig:2
Say Y or M here to enable the TCM Storage Engine and ConfigFS enabled
control path for target_core_mod. This includes built-in TCM RAMDISK
subsystem logic for virtual LUN 0 access
Symbol TCM_IBLOCK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"TCM/IBLOCK Subsystem Plugin for Linux/BLOCK"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
TARGET_CORE (value: "m")
Locations: ../drivers/target/Kconfig:14
Say Y here to enable the TCM/IBLOCK subsystem plugin for non-buffered
access to Linux/Block devices using BIO
Symbol TCM_FILEIO
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"TCM/FILEIO Subsystem Plugin for Linux/VFS"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
TARGET_CORE (value: "m")
Locations: ../drivers/target/Kconfig:20
Say Y here to enable the TCM/FILEIO subsystem plugin for buffered
access to Linux/VFS struct file or struct block_device
Symbol TCM_PSCSI
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"TCM/pSCSI Subsystem Plugin for Linux/SCSI"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
TARGET_CORE (value: "m")
Locations: ../drivers/target/Kconfig:26
Say Y here to enable the TCM/pSCSI subsystem plugin for non-buffered
passthrough access to Linux/SCSI device
Symbol LOOPBACK_TARGET
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"TCM Virtual SAS target and Linux/SCSI LDD fabric loopback module"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
TARGET_CORE (value: "m")
Locations: ../drivers/target/loopback/Kconfig:1
Say Y here to enable the TCM Virtual SAS target and Linux/SCSI LLD
fabric loopback module.
Symbol TCM_FC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"TCM_FC fabric Plugin" if LIBFC (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
TARGET_CORE (value: "m")
Locations: ../drivers/target/tcm_fc/Kconfig:1
Say Y here to enable the TCM FC plugin for accessing FC fabrics in TCM
Symbol ISCSI_TARGET
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Linux-iSCSI.org iSCSI Target Mode Stack" if NET (value: "y")
Default values:
(no default values)
Selects:
CRYPTO if NET (value: "y")
CRYPTO_CRC32C if NET (value: "y")
CRYPTO_CRC32C_INTEL if X86 && NET (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
TARGET_CORE (value: "m")
Locations: ../drivers/target/iscsi/Kconfig:1
Say M here to enable the ConfigFS enabled Linux-iSCSI.org iSCSI
Target Mode Stack.
Symbol SBP_TARGET
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"FireWire SBP-2 fabric module" if FIREWIRE (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
TARGET_CORE (value: "m")
Locations: ../drivers/target/sbp/Kconfig:1
Say Y or M here to enable SCSI target functionality over FireWire.
This enables you to expose SCSI devices to other nodes on the FireWire
bus, for example hard disks. Similar to FireWire Target Disk mode on
many Apple computers.
To compile this driver as a module, say M here: The module will be
called sbp-target.
Symbol FUSION
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fusion MPT device support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/message/fusion/Kconfig:2
Say Y here to get to see options for Fusion Message
Passing Technology (MPT) drivers.
This option alone does not add any kernel code.
If you say N, all options in this submenu will be skipped and disabled.
Symbol FUSION_SPI
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fusion MPT ScsiHost drivers for SPI" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_SPI_ATTRS if PCI && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
FUSION (value: "y")
Locations: ../drivers/message/fusion/Kconfig:14
SCSI HOST support for a parallel SCSI host adapters.
List of supported controllers:
LSI53C1020
LSI53C1020A
LSI53C1030
LSI53C1035
ATTO UL4D
Symbol FUSION_FC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fusion MPT ScsiHost drivers for FC" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_FC_ATTRS if PCI && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
FUSION (value: "y")
Locations: ../drivers/message/fusion/Kconfig:29
SCSI HOST support for a Fiber Channel host adapters.
List of supported controllers:
LSIFC909
LSIFC919
LSIFC919X
LSIFC929
LSIFC929X
LSIFC929XL
LSIFC949X
LSIFC949E
Brocade FC 410/420
Symbol FUSION_SAS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fusion MPT ScsiHost drivers for SAS" if PCI && SCSI (value: "y")
Default values:
(no default values)
Selects:
SCSI_SAS_ATTRS if PCI && SCSI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
FUSION (value: "y")
Locations: ../drivers/message/fusion/Kconfig:48
SCSI HOST support for a SAS host adapters.
List of supported controllers:
LSISAS1064
LSISAS1068
LSISAS1064E
LSISAS1068E
LSISAS1078
Symbol FUSION_MAX_SGE
Type : int
Value : "128"
User value : "128"
Xen config : '16'
Main config : '128'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Ranges:
[16, 128]
Prompts:
"Maximum number of scatter gather entries (16 - 128)"
Default values:
"128" (value: "n")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
FUSION (value: "y")
Locations: ../drivers/message/fusion/Kconfig:63
This option allows you to specify the maximum number of scatter-
gather entries per I/O. The driver default is 128, which matches
SCSI_MAX_PHYS_SEGMENTS. However, it may decreased down to 16.
Decreasing this parameter will reduce memory requirements
on a per controller instance.
Symbol FUSION_CTL
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fusion MPT misc device (ioctl) driver" if FUSION_SPI || FUSION_FC || FUSION_SAS (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
FUSION (value: "y")
Locations: ../drivers/message/fusion/Kconfig:74
The Fusion MPT misc device driver provides specialized control
of MPT adapters via system ioctl calls. Use of ioctl calls to
the MPT driver requires that you create and use a misc device
node ala:
mknod /dev/mptctl c 10 240
One use of this ioctl interface is to perform an upgrade (reflash)
of the MPT adapter firmware. Refer to readme file(s) distributed
with the Fusion MPT linux driver for additional details.
If enabled by saying M to this, a driver named: mptctl
will be compiled.
If unsure whether you really want or need this, say N.
Symbol FIREWIRE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
IEEE 1394 (FireWire) support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"FireWire driver stack"
Default values:
(no default values)
Selects:
CRC_ITU_T
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PCI || BROKEN (value: "y")
Locations: ../drivers/firewire/Kconfig:6
This is the new-generation IEEE 1394 (FireWire) driver stack
a.k.a. Juju, a new implementation designed for robustness and
simplicity.
See http://ieee1394.wiki.kernel.org/index.php/Juju_Migration
for information about migration from the older Linux 1394 stack
to the new driver stack.
To compile this driver as a module, say M here: the module will be
called firewire-core.
Symbol FIREWIRE_OHCI
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
IEEE 1394 (FireWire) support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"OHCI-1394 controllers" if PCI && FIREWIRE && MMU (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PCI || BROKEN (value: "y")
Locations: ../drivers/firewire/Kconfig:20
Enable this driver if you have a FireWire controller based
on the OHCI specification. For all practical purposes, this
is the only chipset in use, so say Y here.
To compile this driver as a module, say M here: The module will be
called firewire-ohci.
Symbol FIREWIRE_SBP2
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
IEEE 1394 (FireWire) support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Storage devices (SBP-2 protocol)" if FIREWIRE && SCSI (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PCI || BROKEN (value: "y")
Locations: ../drivers/firewire/Kconfig:31
This option enables you to use SBP-2 devices connected to a
FireWire bus. SBP-2 devices include storage devices like
harddisks and DVD drives, also some other FireWire devices
like scanners.
To compile this driver as a module, say M here: The module will be
called firewire-sbp2.
You should also enable support for disks, CD-ROMs, etc. in the SCSI
configuration section.
Symbol FIREWIRE_NET
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
IEEE 1394 (FireWire) support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IP networking over 1394" if FIREWIRE && INET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PCI || BROKEN (value: "y")
Locations: ../drivers/firewire/Kconfig:46
This enables IPv4 over IEEE 1394, providing IP connectivity with
other implementations of RFC 2734 as found on several operating
systems. Multicast support is currently limited.
To compile this driver as a module, say M here: The module will be
called firewire-net.
Symbol FIREWIRE_NOSY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
IEEE 1394 (FireWire) support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Nosy - a FireWire traffic sniffer for PCILynx cards" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PCI || BROKEN (value: "y")
Locations: ../drivers/firewire/Kconfig:57
Nosy is an IEEE 1394 packet sniffer that is used for protocol
analysis and in development of IEEE 1394 drivers, applications,
or firmwares.
This driver lets you use a Texas Instruments PCILynx 1394 to PCI
link layer controller TSB12LV21/A/B as a low-budget bus analyzer.
PCILynx is a nowadays very rare IEEE 1394 controller which is
not OHCI 1394 compliant.
The following cards are known to be based on PCILynx or PCILynx-2:
IOI IOI-1394TT (PCI card), Unibrain Fireboard 400 PCI Lynx-2
(PCI card), Newer Technology FireWire 2 Go (CardBus card),
Apple Power Mac G3 blue & white and G4 with PCI graphics
(onboard controller).
To compile this driver as a module, say M here: The module will be
called nosy. Source code of a userspace interface to nosy, called
nosy-dump, can be found in tools/firewire/ of the kernel sources.
If unsure, say N.
Symbol I2O
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"I2O device support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/message/i2o/Kconfig:2
The Intelligent Input/Output (I2O) architecture allows hardware
drivers to be split into two parts: an operating system specific
module called the OSM and an hardware specific module called the
HDM. The OSM can talk to a whole range of HDM's, and ideally the
HDM's are not OS dependent. This allows for the same HDM driver to
be used under different operating systems if the relevant OSM is in
place. In order for this to work, you need to have an I2O interface
adapter card in your computer. This card contains a special I/O
processor (IOP), thus allowing high speeds since the CPU does not
have to deal with I/O.
If you say Y here, you will get a choice of interface adapter
drivers and OSM's with the following questions.
To compile this support as a module, choose M here: the
modules will be called i2o_core.
If unsure, say N.
Symbol I2O_LCT_NOTIFY_ON_CHANGES
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable LCT notification"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2O (value: "m")
Locations: ../drivers/message/i2o/Kconfig:27
Only say N here if you have a I2O controller from SUN. The SUN
firmware doesn't support LCT notification on changes. If this option
is enabled on such a controller the driver will hang up in a endless
loop. On all other controllers say Y.
If unsure, say Y.
Symbol I2O_EXT_ADAPTEC
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable Adaptec extensions"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2O (value: "m")
Locations: ../drivers/message/i2o/Kconfig:38
Say Y for support of raidutils for Adaptec I2O controllers. You also
have to say Y to "I2O Configuration support", "I2O SCSI OSM" below
and to "SCSI generic support" under "SCSI device configuration".
Symbol I2O_EXT_ADAPTEC_DMA64
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'n'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable 64-bit DMA" if I2O_EXT_ADAPTEC && (64BIT || HIGHMEM64G) (value: "y")
Default values:
y (value: "y")
Condition: I2O_EXT_ADAPTEC && (64BIT || HIGHMEM64G) (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2O (value: "m")
Locations: ../drivers/message/i2o/Kconfig:46
Say Y for support of 64-bit DMA transfer mode on Adaptec I2O
controllers.
Note: You need at least firmware version 3709.
Symbol I2O_CONFIG
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"I2O Configuration support" if VIRT_TO_BUS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2O (value: "m")
Locations: ../drivers/message/i2o/Kconfig:55
Say Y for support of the configuration interface for the I2O adapters.
If you have a RAID controller from Adaptec and you want to use the
raidutils to manage your RAID array, you have to say Y here.
To compile this support as a module, choose M here: the
module will be called i2o_config.
Note: If you want to use the new API you have to download the
i2o_config patch from http://i2o.shadowconnect.com/
Symbol I2O_CONFIG_OLD_IOCTL
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable ioctls (OBSOLETE)" if I2O_CONFIG (value: "m")
Default values:
y (value: "y")
Condition: I2O_CONFIG (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2O (value: "m")
Locations: ../drivers/message/i2o/Kconfig:69
Enables old ioctls.
Symbol I2O_BUS
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"I2O Bus Adapter OSM"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2O (value: "m")
Locations: ../drivers/message/i2o/Kconfig:76
Include support for the I2O Bus Adapter OSM. The Bus Adapter OSM
provides access to the busses on the I2O controller. The main purpose
is to rescan the bus to find new devices.
To compile this support as a module, choose M here: the
module will be called i2o_bus.
Symbol I2O_BLOCK
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"I2O Block OSM" if BLOCK (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2O (value: "m")
Locations: ../drivers/message/i2o/Kconfig:86
Include support for the I2O Block OSM. The Block OSM presents disk
and other structured block devices to the operating system. If you
are using an RAID controller, you could access the array only by
the Block OSM driver. But it is possible to access the single disks
by the SCSI OSM driver, for example to monitor the disks.
To compile this support as a module, choose M here: the
module will be called i2o_block.
Symbol I2O_SCSI
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"I2O SCSI OSM" if SCSI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2O (value: "m")
Locations: ../drivers/message/i2o/Kconfig:99
Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
I2O controller. You can use both the SCSI and Block OSM together if
you wish. To access a RAID array, you must use the Block OSM driver.
But you could use the SCSI OSM driver to monitor the single disks.
To compile this support as a module, choose M here: the
module will be called i2o_scsi.
Symbol I2O_PROC
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"I2O /proc support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2O (value: "m")
Locations: ../drivers/message/i2o/Kconfig:111
If you say Y here and to "/proc file system support", you will be
able to read I2O related information from the virtual directory
/proc/i2o.
To compile this support as a module, choose M here: the
module will be called i2o_proc.
Symbol MII
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Generic Media Independent Interface device support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(PCI || EISA) && HAS_IOPORT && ETHERNET && NETDEVICES && NET_VENDOR_3COM && VORTEX || ETHERNET && NETDEVICES && NET_VENDOR_ADAPTEC && PCI && ADAPTEC_STARFIRE || ETHERNET && NETDEVICES && NET_VENDOR_AMD && PCI && AMD8111_ETH || ETHERNET && NETDEVICES && NET_VENDOR_AMD && PCI && PCNET32 || ETHERNET && NETDEVICES && NET_VENDOR_ATHEROS && PCI && ATL2 || ETHERNET && NETDEVICES && NET_VENDOR_ATHEROS && PCI && ATL1 || ETHERNET && NETDEVICES && NET_VENDOR_ATHEROS && PCI && ATL1E || ETHERNET && NETDEVICES && NET_VENDOR_ATHEROS && PCI && ATL1C || ETHERNET && NETDEVICES && NET_BFIN && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537) && BFIN_MAC || SSB_POSSIBLE && HAS_DMA && ETHERNET && NETDEVICES && NET_VENDOR_BROADCOM && B44 || ETHERNET && NETDEVICES && NET_VENDOR_BROADCOM && BCM63XX && BCM63XX_ENET || ARM && ARCH_EP93XX && ETHERNET && NETDEVICES && NET_VENDOR_CIRRUS && EP93XX_ETH || ETHERNET && NETDEVICES && (ARM || BLACKFIN || MIPS || COLDFIRE) && DM9000 || ETHERNET && NETDEVICES && NET_VENDOR_DEC && NET_TULIP && PCI && WINBOND_840 || ETHERNET && NETDEVICES && NET_VENDOR_DLINK && PCI && SUNDANCE || ETHERNET && NETDEVICES && NET_VENDOR_FARADAY && ARM && FTMAC100 || NET_VENDOR_FREESCALE && (CPM1 || CPM2 || PPC_MPC512x) && ETHERNET && NETDEVICES && NET_VENDOR_FREESCALE && FS_ENET || ETHERNET && NETDEVICES && NET_VENDOR_INTEL && PCI && E100 || ETHERNET && NETDEVICES && PCI && IP1000 || ETHERNET && NETDEVICES && PCI && JME || ARM && ARCH_KS8695 && ETHERNET && NETDEVICES && NET_VENDOR_MICREL && ARM_KS8695_ETHER || ETHERNET && NETDEVICES && NET_VENDOR_MICREL && SPI && KS8851 || ETHERNET && NETDEVICES && NET_VENDOR_MICREL && HAS_IOMEM && KS8851_MLL || ETHERNET && NETDEVICES && NET_VENDOR_MICREL && PCI && KSZ884X_PCI || ETHERNET && NETDEVICES && PCI && FEALNX || ETHERNET && NETDEVICES && ARCH_NETX && NET_NETX || ARM && ARCH_W90X900 && ETHERNET && NETDEVICES && NET_VENDOR_NUVOTON && W90P910_ETH || ETHERNET && NETDEVICES && NET_VENDOR_OKI && PCI && PCH_GBE || HAS_IOMEM && HAS_DMA && ETHERNET && NETDEVICES && ETHOC || ETHERNET && NETDEVICES && NET_PACKET_ENGINE && PCI && HAMACHI || ETHERNET && NETDEVICES && NET_VENDOR_REALTEK && PCI && 8139CP || ETHERNET && NETDEVICES && NET_VENDOR_REALTEK && PCI && 8139TOO || ETHERNET && NETDEVICES && NET_VENDOR_REALTEK && PCI && R8169 || (SUPERH || ARCH_SHMOBILE) && (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7734 || CPU_SUBTYPE_SH7757 || ARCH_R8A7740 || ARCH_R8A7779) && ETHERNET && NETDEVICES && SH_ETH || ETHERNET && NETDEVICES && NET_VENDOR_RDC && PCI && R6040 || ETHERNET && NETDEVICES && NET_VENDOR_SIS && PCI && SIS900 || ETHERNET && NETDEVICES && NET_VENDOR_SIS && PCI && SIS190 || PCI && SGI_IP27 && ETHERNET && NETDEVICES && NET_VENDOR_SGI && SGI_IOC3_ETH || ETHERNET && NETDEVICES && NET_VENDOR_SMSC && (ARM || M32R || SUPERH || MIPS || BLACKFIN || MN10300 || COLDFIRE) && SMC91X || ETHERNET && NETDEVICES && NET_VENDOR_SMSC && PCMCIA && PCMCIA_SMC91C92 || ETHERNET && NETDEVICES && NET_VENDOR_SMSC && PCI && EPIC100 || ETHERNET && NETDEVICES && NET_VENDOR_SMSC && (ARM || SUPERH || MN10300) && SMC911X || ETHERNET && NETDEVICES && NET_VENDOR_SMSC && (ARM || SUPERH || BLACKFIN || MIPS || MN10300) && SMSC911X || ETHERNET && NETDEVICES && NET_VENDOR_STMICRO && HAS_IOMEM && STMMAC_ETH || ETHERNET && NETDEVICES && NET_VENDOR_VIA && PCI && VIA_RHINE || ETHERNET && NETDEVICES && NET_VENDOR_VIA && PCI && VIA_VELOCITY || USB && NET && NETDEVICES && USB_PEGASUS || USB && NET && NETDEVICES && USB_RTL8150 || USB && NET && NETDEVICES && USB_USBNET || PCI && NET && "m" && MODULES && NET_VENDOR_SILICOM && STAGING && BPCTL (value: "m")
Additional dependencies from enclosing menus and if's:
NET_CORE && NETDEVICES (value: "y")
Locations: ../drivers/net/Kconfig:103
Most ethernet controllers have MII transceiver either as an external
or internal device. It is safe to say Y or M here even if your
ethernet card lacks MII.
Symbol NET_TEAM_MODE_BROADCAST
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Broadcast mode support" if NET_TEAM (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET_CORE && NETDEVICES && NET_TEAM (value: "m")
Locations: ../drivers/net/team/Kconfig:17
Basic mode where packets are transmitted always by all suitable ports.
All added ports are setup to have team's device address.
To compile this team mode as a module, choose M here: the module
will be called team_mode_broadcast.
Symbol NET_TEAM_MODE_LOADBALANCE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Load-balance mode support" if NET_TEAM (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET_CORE && NETDEVICES && NET_TEAM (value: "m")
Locations: ../drivers/net/team/Kconfig:53
This mode provides load balancing functionality. Tx port selection
is done using BPF function set up from userspace (bpf_hash_func
option)
To compile this team mode as a module, choose M here: the module
will be called team_mode_loadbalance.
Symbol VXLAN
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Virtual eXtensible Local Area Network (VXLAN)" if INET (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NET_CORE && NETDEVICES (value: "y")
Locations: ../drivers/net/Kconfig:151
This allows one to create vxlan virtual interfaces that provide
Layer 2 Networks over Layer 3 Networks. VXLAN is often used
to tunnel virtual network infrastructure in virtualized environments.
For more information see:
http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02
To compile this driver as a module, choose M here: the module
will be called vxlan.
Symbol ARCNET
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ARCnet support" if NETDEVICES && (ISA || PCI || PCMCIA) (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/arcnet/Kconfig:5
If you have a network card of this type, say Y and check out the
(arguably) beautiful poetry in
<file:Documentation/networking/arcnet.txt>.
You need both this driver, and the driver for the particular ARCnet
chipset of your card. If you don't know, then it's probably a
COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset
support" below.
You might also want to have a look at the Ethernet-HOWTO, available
from <http://www.tldp.org/docs.html#howto>(even though ARCnet
is not really Ethernet).
To compile this driver as a module, choose M here. The module will
be called arcnet.
Symbol ATM_DRIVERS
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ATM drivers" if NETDEVICES && ATM (value: "m")
Default values:
y (value: "y")
Condition: NETDEVICES && ATM (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/atm/Kconfig:5
Say Y here to get to see options for Asynchronous Transfer Mode
device drivers. This option alone does not add any kernel code.
If you say N, all options in this submenu will be skipped and disabled.
Symbol NET_DSA_MV88E6060
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Distributed Switch Architecture drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Marvell 88E6060 ethernet switch chip support"
Default values:
(no default values)
Selects:
NET_DSA
NET_DSA_TAG_TRAILER
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAVE_NET_DSA && NETDEVICES (value: "y")
Locations: ../drivers/net/dsa/Kconfig:8
This enables support for the Marvell 88E6060 ethernet switch
chip.
Symbol NET_DSA_MV88E6131
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Distributed Switch Architecture drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Marvell 88E6085/6095/6095F/6131 ethernet switch chip support"
Default values:
(no default values)
Selects:
NET_DSA
NET_DSA_MV88E6XXX
NET_DSA_MV88E6XXX_NEED_PPU
NET_DSA_TAG_DSA
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAVE_NET_DSA && NETDEVICES (value: "y")
Locations: ../drivers/net/dsa/Kconfig:20
This enables support for the Marvell 88E6085/6095/6095F/6131
ethernet switch chips.
Symbol NET_DSA_MV88E6123_61_65
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Distributed Switch Architecture drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Marvell 88E6123/6161/6165 ethernet switch chip support"
Default values:
(no default values)
Selects:
NET_DSA
NET_DSA_MV88E6XXX
NET_DSA_TAG_EDSA
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAVE_NET_DSA && NETDEVICES (value: "y")
Locations: ../drivers/net/dsa/Kconfig:30
This enables support for the Marvell 88E6123/6161/6165
ethernet switch chips.
Symbol ETHERNET
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Ethernet driver support" if NET (value: "y")
Default values:
y (value: "y")
Condition: NET (value: "y")
Selects:
(no selects)
Reverse dependencies:
PCI && INET && SCSI_LOWLEVEL && SCSI && SCSI_CXGB3_ISCSI || PCI && INET && SCSI_LOWLEVEL && SCSI && SCSI_CXGB4_ISCSI || NET && PCI && SCSI_LOWLEVEL && SCSI && SCSI_BNX2_ISCSI || SCSI_LOWLEVEL && SCSI && PCI && SCSI_BNX2X_FCOE (value: "n")
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/Kconfig:5
This section contains all the Ethernet device drivers.
Symbol NET_VENDOR_3COM
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"3Com devices" if ISA || EISA || PCI || PCMCIA (value: "y")
Default values:
y (value: "y")
Condition: ISA || EISA || PCI || PCMCIA (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/3com/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about 3Com cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_ADAPTEC
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Adaptec devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/adaptec/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Adaptec cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_ALTEON
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Alteon devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/alteon/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Alteon cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_AMD
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD devices" if DIO || MACH_DECSTATION || MVME147 || ATARI || SUN3 || SUN3X || SBUS || PCI || ZORRO || ISA && ISA_DMA_API || ARM && ARCH_EBSA110 || ISA || EISA || PCMCIA (value: "y")
Default values:
y (value: "y")
Condition: DIO || MACH_DECSTATION || MVME147 || ATARI || SUN3 || SUN3X || SBUS || PCI || ZORRO || ISA && ISA_DMA_API || ARM && ARCH_EBSA110 || ISA || EISA || PCMCIA (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/amd/Kconfig:5
If you have a network (Ethernet) chipset belonging to this class,
say Y.
Note that the answer to this question does not directly affect
the kernel: saying N will just case the configurator to skip all
the questions regarding AMD chipsets. If you say Y, you will be asked
for your specific chipset/driver in the following questions.
Symbol AMD8111_ETH
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD 8111 (new PCI LANCE) support" if PCI (value: "y")
Default values:
(no default values)
Selects:
CRC32 if PCI (value: "y")
NET_CORE if PCI (value: "y")
MII if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_AMD (value: "y")
Locations: ../drivers/net/ethernet/amd/Kconfig:31
If you have an AMD 8111-based PCI LANCE ethernet card,
answer Y here and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose M here. The module
will be called amd8111e.
Symbol PCNET32
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD PCnet32 PCI support" if PCI (value: "y")
Default values:
(no default values)
Selects:
CRC32 if PCI (value: "y")
NET_CORE if PCI (value: "y")
MII if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_AMD (value: "y")
Locations: ../drivers/net/ethernet/amd/Kconfig:57
If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
answer Y here and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose M here. The module
will be called pcnet32.
Symbol NET_VENDOR_ATHEROS
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Atheros devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/atheros/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Atheros devices. If you say Y, you will be asked
for your specific card in the following questions.
Symbol NET_CADENCE
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Cadence devices" if HAS_IOMEM (value: "y")
Default values:
y (value: "y")
Condition: HAS_IOMEM (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/cadence/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y.
Make sure you know the name of your card. Read the Ethernet-HOWTO,
available from <http://www.tldp.org/docs.html#howto>.
If unsure, say Y.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the remaining Atmel network card questions. If you say Y, you will be
asked for your specific card in the following questions.
Symbol NET_VENDOR_BROADCOM
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Broadcom devices" if SSB_POSSIBLE && HAS_DMA || PCI || BCM63XX || SIBYTE_SB1xxx_SOC (value: "y")
Default values:
y (value: "y")
Condition: SSB_POSSIBLE && HAS_DMA || PCI || BCM63XX || SIBYTE_SB1xxx_SOC (value: "y")
Selects:
(no selects)
Reverse dependencies:
NET && PCI && SCSI_LOWLEVEL && SCSI && SCSI_BNX2_ISCSI || SCSI_LOWLEVEL && SCSI && PCI && SCSI_BNX2X_FCOE (value: "n")
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/broadcom/Kconfig:5
If you have a network (Ethernet) chipset belonging to this class,
say Y.
Note that the answer to this question does not directly affect
the kernel: saying N will just case the configurator to skip all
the questions regarding AMD chipsets. If you say Y, you will be asked
for your specific chipset/driver in the following questions.
Symbol NET_VENDOR_BROCADE
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Brocade devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/brocade/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Brocade cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_CALXEDA_XGMAC
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Calxeda 1G/10G XGMAC Ethernet driver" if HAS_IOMEM (value: "y")
Default values:
(no default values)
Selects:
CRC32 if HAS_IOMEM (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/calxeda/Kconfig:1
This is the driver for the XGMAC Ethernet IP block found on Calxeda
Highbank platforms.
Symbol NET_VENDOR_CHELSIO
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Chelsio devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
PCI && INET && SCSI_LOWLEVEL && SCSI && SCSI_CXGB3_ISCSI || PCI && INET && SCSI_LOWLEVEL && SCSI && SCSI_CXGB4_ISCSI (value: "n")
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/chelsio/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Chelsio devices. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_CISCO
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Cisco devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/cisco/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Cisco cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol DNET
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Dave ethernet support (DNET)" if HAS_IOMEM (value: "y")
Default values:
(no default values)
Selects:
PHYLIB if HAS_IOMEM (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/Kconfig:37
The Dave ethernet interface (DNET) is found on Qong Board FPGA.
Say Y to include support for the DNET chip.
To compile this driver as a module, choose M here: the module
will be called dnet.
Symbol NET_VENDOR_DEC
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Digital Equipment devices" if PCI || EISA || CARDBUS (value: "y")
Default values:
y (value: "y")
Condition: PCI || EISA || CARDBUS (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/dec/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about DEC cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_TULIP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"DEC - Tulip devices" if PCI || EISA || CARDBUS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_DEC (value: "y")
Locations: ../drivers/net/ethernet/dec/tulip/Kconfig:5
This selects the "Tulip" family of EISA/PCI network cards.
Symbol DE2104X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Early DECchip Tulip (dc2104x) PCI support" if PCI (value: "y")
Default values:
(no default values)
Selects:
CRC32 if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_DEC && NET_TULIP (value: "y")
Locations: ../drivers/net/ethernet/dec/tulip/Kconfig:13
This driver is developed for the SMC EtherPower series Ethernet
cards and also works with cards based on the DECchip
21040 (Tulip series) chips. Some LinkSys PCI cards are
of this type. (If your card is NOT SMC EtherPower 10/100 PCI
(smc9332dst), you can also try the driver for "Generic DECchip"
cards, below. However, most people with a network card of this type
will say Y here.) Do read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose M here. The module will
be called de2104x.
Symbol TULIP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"DECchip Tulip (dc2114x) PCI support" if PCI (value: "y")
Default values:
(no default values)
Selects:
CRC32 if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_DEC && NET_TULIP (value: "y")
Locations: ../drivers/net/ethernet/dec/tulip/Kconfig:42
This driver is developed for the SMC EtherPower series Ethernet
cards and also works with cards based on the DECchip
21140 (Tulip series) chips. Some LinkSys PCI cards are
of this type. (If your card is NOT SMC EtherPower 10/100 PCI
(smc9332dst), you can also try the driver for "Generic DECchip"
cards, above. However, most people with a network card of this type
will say Y here.) Do read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose M here. The module will
be called tulip.
Symbol DE4X5
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Generic DECchip & DIGITAL EtherWORKS PCI/EISA" if (PCI || EISA) && (VIRT_TO_BUS || ALPHA || PPC || SPARC) (value: "y")
Default values:
(no default values)
Selects:
CRC32 if (PCI || EISA) && (VIRT_TO_BUS || ALPHA || PPC || SPARC) (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_DEC && NET_TULIP (value: "y")
Locations: ../drivers/net/ethernet/dec/tulip/Kconfig:108
This is support for the DIGITAL series of PCI/EISA Ethernet cards.
These include the DE425, DE434, DE435, DE450 and DE500 models. If
you have a network card of this type, say Y and read the
Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. More specific
information is contained in
<file:Documentation/networking/de4x5.txt>.
To compile this driver as a module, choose M here. The module will
be called de4x5.
Symbol WINBOND_840
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Winbond W89c840 Ethernet support" if PCI (value: "y")
Default values:
(no default values)
Selects:
CRC32 if PCI (value: "y")
NET_CORE if PCI (value: "y")
MII if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_DEC && NET_TULIP (value: "y")
Locations: ../drivers/net/ethernet/dec/tulip/Kconfig:125
This driver is for the Winbond W89c840 chip. It also works with
the TX9882 chip on the Compex RL100-ATX board.
More specific information and updates are available from
<http://www.scyld.com/network/drivers.html>.
Symbol DM9102
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Davicom DM910x/DM980x support" if PCI (value: "y")
Default values:
(no default values)
Selects:
CRC32 if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_DEC && NET_TULIP (value: "y")
Locations: ../drivers/net/ethernet/dec/tulip/Kconfig:137
This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from
Davicom (<http://www.davicom.com.tw/>). If you have such a network
(Ethernet) card, say Y. Some information is contained in the file
<file:Documentation/networking/dmfe.txt>.
To compile this driver as a module, choose M here. The module will
be called dmfe.
Symbol ULI526X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ULi M526x controller support" if PCI (value: "y")
Default values:
(no default values)
Selects:
CRC32 if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_DEC && NET_TULIP (value: "y")
Locations: ../drivers/net/ethernet/dec/tulip/Kconfig:150
This driver is for ULi M5261/M5263 10/100M Ethernet Controller
(<http://www.nvidia.com/page/uli_drivers.html>).
To compile this driver as a module, choose M here. The module will
be called uli526x.
Symbol NET_VENDOR_DLINK
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"D-Link devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/dlink/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about D-Link devices. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_EMULEX
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Emulex devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
ETHERNET && NETDEVICES && PCI && (IPV6 || IPV6 = n) && INFINIBAND && INFINIBAND_OCRDMA (value: "n")
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/emulex/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Emulex cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_EXAR
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Exar devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/neterion/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say
Y and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Exar cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_HP
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"HP devices" if ISA || EISA || PCI (value: "y")
Default values:
y (value: "y")
Condition: ISA || EISA || PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/hp/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about HP cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_INTEL
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel devices"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/intel/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Intel cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol E100
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel(R) PRO/100+ support" if PCI (value: "y")
Default values:
(no default values)
Selects:
NET_CORE if PCI (value: "y")
MII if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_INTEL (value: "y")
Locations: ../drivers/net/ethernet/intel/Kconfig:20
This driver supports Intel(R) PRO/100 family of adapters.
To verify that your adapter is supported, find the board ID number
on the adapter. Look for a label that has a barcode and a number
in the format 123456-001 (six digits hyphen three digits).
Use the above information and the Adapter & Driver ID Guide at:
<http://support.intel.com/support/network/adapter/pro100/21397.htm>
to identify the adapter.
For the latest Intel PRO/100 network driver for Linux, see:
<http://www.intel.com/p/en_US/support/highlights/network/pro100plus>
More specific information on configuring the driver is in
<file:Documentation/networking/e100.txt>.
To compile this driver as a module, choose M here. The module
will be called e100.
Symbol E1000
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel(R) PRO/1000 Gigabit Ethernet support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_INTEL (value: "y")
Locations: ../drivers/net/ethernet/intel/Kconfig:47
This driver supports Intel(R) PRO/1000 gigabit ethernet family of
adapters. For more information on how to identify your adapter, go
to the Adapter & Driver ID Guide at:
<http://support.intel.com/support/network/adapter/pro100/21397.htm>
For general information and support, go to the Intel support
website at:
<http://support.intel.com>
More specific information on configuring the driver is in
<file:Documentation/networking/e1000.txt>.
To compile this driver as a module, choose M here. The module
will be called e1000.
Symbol E1000E
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support" if PCI && (!SPARC32 || BROKEN) (value: "y")
Default values:
(no default values)
Selects:
CRC32 if PCI && (!SPARC32 || BROKEN) (value: "y")
PTP_1588_CLOCK if PCI && (!SPARC32 || BROKEN) (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_INTEL (value: "y")
Locations: ../drivers/net/ethernet/intel/Kconfig:68
This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
ethernet family of adapters. For PCI or PCI-X e1000 adapters,
use the regular e1000 driver For more information on how to
identify your adapter, go to the Adapter & Driver ID Guide at:
<http://support.intel.com/support/network/adapter/pro100/21397.htm>
For general information and support, go to the Intel support
website at:
<http://support.intel.com>
To compile this driver as a module, choose M here. The module
will be called e1000e.
Symbol IGB
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support" if PCI (value: "y")
Default values:
(no default values)
Selects:
PTP_1588_CLOCK if PCI (value: "y")
I2C if PCI (value: "y")
I2C_ALGOBIT if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_INTEL (value: "y")
Locations: ../drivers/net/ethernet/intel/Kconfig:89
This driver supports Intel(R) 82575/82576 gigabit ethernet family of
adapters. For more information on how to identify your adapter, go
to the Adapter & Driver ID Guide at:
<http://support.intel.com/support/network/adapter/pro100/21397.htm>
For general information and support, go to the Intel support
website at:
<http://support.intel.com>
More specific information on configuring the driver is in
<file:Documentation/networking/e1000.txt>.
To compile this driver as a module, choose M here. The module
will be called igb.
Symbol IGBVF
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel(R) 82576 Virtual Function Ethernet support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_INTEL (value: "y")
Locations: ../drivers/net/ethernet/intel/Kconfig:133
This driver supports Intel(R) 82576 virtual functions. For more
information on how to identify your adapter, go to the Adapter &
Driver ID Guide at:
<http://support.intel.com/support/network/adapter/pro100/21397.htm>
For general information and support, go to the Intel support
website at:
<http://support.intel.com>
More specific information on configuring the driver is in
<file:Documentation/networking/e1000.txt>.
To compile this driver as a module, choose M here. The module
will be called igbvf.
Symbol IXGB
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel(R) PRO/10GbE support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_INTEL (value: "y")
Locations: ../drivers/net/ethernet/intel/Kconfig:154
This driver supports Intel(R) PRO/10GbE family of adapters for
PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
instead. For more information on how to identify your adapter, go
to the Adapter & Driver ID Guide at:
<http://support.intel.com/support/network/adapter/pro100/21397.htm>
For general information and support, go to the Intel support
website at:
<http://support.intel.com>
More specific information on configuring the driver is in
<file:Documentation/networking/ixgb.txt>.
To compile this driver as a module, choose M here. The module
will be called ixgb.
Symbol IXGBE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel(R) 10GbE PCI Express adapters support" if PCI (value: "y")
Default values:
(no default values)
Selects:
MDIO if PCI (value: "y")
PTP_1588_CLOCK if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_INTEL (value: "y")
Locations: ../drivers/net/ethernet/intel/Kconfig:176
This driver supports Intel(R) 10GbE PCI Express family of
adapters. For more information on how to identify your adapter, go
to the Adapter & Driver ID Guide at:
<http://support.intel.com/support/network/adapter/pro100/21397.htm>
For general information and support, go to the Intel support
website at:
<http://support.intel.com>
To compile this driver as a module, choose M here. The module
will be called ixgbe.
Symbol NET_VENDOR_I825XX
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel (82586/82593/82596) devices" if NET_VENDOR_INTEL (value: "y")
Default values:
y (value: "y")
Condition: NET_VENDOR_INTEL (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/i825xx/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question does not directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about these devices. If you say Y, you will be asked for
your specific card in the following questions.
Symbol IP1000
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IP1000 Gigabit Ethernet support" if PCI (value: "y")
Default values:
(no default values)
Selects:
NET_CORE if PCI (value: "y")
MII if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/icplus/Kconfig:5
This driver supports IP1000 gigabit Ethernet cards.
To compile this driver as a module, choose M here: the module
will be called ipg. This is recommended.
Symbol JME
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"JMicron(R) PCI-Express Gigabit Ethernet support" if PCI (value: "y")
Default values:
(no default values)
Selects:
CRC32 if PCI (value: "y")
NET_CORE if PCI (value: "y")
MII if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/Kconfig:62
This driver supports the PCI-Express gigabit ethernet adapters
based on JMicron JMC250 chipset.
To compile this driver as a module, choose M here. The module
will be called jme.
Symbol NET_VENDOR_MARVELL
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Marvell devices" if PCI || CPU_PXA168 || MV64X60 || PPC32 || PLAT_ORION || INET (value: "y")
Default values:
y (value: "y")
Condition: PCI || CPU_PXA168 || MV64X60 || PPC32 || PLAT_ORION || INET (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/marvell/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Marvell devices. If you say Y, you will be
asked for your specific card in the following questions.
Symbol NET_VENDOR_MELLANOX
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Mellanox devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
NETDEVICES && ETHERNET && PCI && INFINIBAND && MLX4_INFINIBAND (value: "n")
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/mellanox/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Mellanox cards. If you say Y, you will be asked
for your specific card in the following questions.
Symbol MLX4_EN
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Mellanox Technologies 10Gbit Ethernet support" if PCI (value: "y")
Default values:
(no default values)
Selects:
MLX4_CORE if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_MELLANOX (value: "y")
Locations: ../drivers/net/ethernet/mellanox/mlx4/Kconfig:5
This driver supports Mellanox Technologies ConnectX Ethernet
devices.
Symbol NET_VENDOR_MICREL
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Micrel devices" if HAS_IOMEM && DMA_ENGINE || SPI || PCI || HAS_IOMEM || ARM && ARCH_KS8695 (value: "y")
Default values:
y (value: "y")
Condition: HAS_IOMEM && DMA_ENGINE || SPI || PCI || HAS_IOMEM || ARM && ARCH_KS8695 (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/micrel/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Micrel devices. If you say Y, you will be asked
for your specific card in the following questions.
Symbol NET_VENDOR_MYRI
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Myricom devices" if PCI && INET (value: "y")
Default values:
y (value: "y")
Condition: PCI && INET (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/myricom/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say
Y and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Myricom cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol FEALNX
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Myson MTD-8xx PCI Ethernet support" if PCI (value: "y")
Default values:
(no default values)
Selects:
CRC32 if PCI (value: "y")
NET_CORE if PCI (value: "y")
MII if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/Kconfig:94
Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
cards. <http://www.myson.com.tw/>
Symbol NET_VENDOR_NATSEMI
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semi-conductor devices"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/natsemi/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about National Semi-conductor devices. If you say Y,
you will be asked for your specific card in the following questions.
Symbol NET_VENDOR_NVIDIA
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"NVIDIA devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/nvidia/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about NVIDIA cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_OKI
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"OKI Semiconductor devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/oki-semi/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about OKI Semiconductor cards. If you say Y, you will
be asked for your specific card in the following questions.
Symbol ETHOC
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"OpenCores 10/100 Mbps Ethernet MAC support" if HAS_IOMEM && HAS_DMA (value: "y")
Default values:
(no default values)
Selects:
NET_CORE if HAS_IOMEM && HAS_DMA (value: "y")
MII if HAS_IOMEM && HAS_DMA (value: "y")
PHYLIB if HAS_IOMEM && HAS_DMA (value: "y")
CRC32 if HAS_IOMEM && HAS_DMA (value: "y")
BITREVERSE if HAS_IOMEM && HAS_DMA (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/Kconfig:124
Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
Symbol NET_PACKET_ENGINE
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Packet Engine devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/packetengines/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about packet engine devices. If you say Y, you will
be asked for your specific card in the following questions.
Symbol NET_VENDOR_QLOGIC
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"QLogic devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/qlogic/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about QLogic cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_REALTEK
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Realtek devices" if PCI || PARPORT && X86 (value: "y")
Default values:
y (value: "y")
Condition: PCI || PARPORT && X86 (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/realtek/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Realtek devices. If you say Y, you will be asked for
your specific card in the following questions.
Symbol ATP
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AT-LAN-TEC/RealTek pocket adapter support" if PARPORT && X86 (value: "m")
Default values:
(no default values)
Selects:
CRC32 if PARPORT && X86 (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_REALTEK (value: "y")
Locations: ../drivers/net/ethernet/realtek/Kconfig:21
This is a network (Ethernet) device which attaches to your parallel
port. Read <file:drivers/net/ethernet/realtek/atp.c> as well as the
Ethernet-HOWTO, available from <http://www.tldp.org/docs.html#howto>,
if you want to use this. If you intend to use this driver, you
should have said N to the "Parallel printer support", because the two
drivers don't like each other.
To compile this driver as a module, choose M here: the module
will be called atp.
Symbol 8139CP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support" if PCI (value: "y")
Default values:
(no default values)
Selects:
CRC32 if PCI (value: "y")
NET_CORE if PCI (value: "y")
MII if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_REALTEK (value: "y")
Locations: ../drivers/net/ethernet/realtek/Kconfig:36
This is a driver for the Fast Ethernet PCI network cards based on
the RTL8139C+ chips. If you have one of those, say Y and read
the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose M here: the module
will be called 8139cp. This is recommended.
Symbol 8139TOO
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support" if PCI (value: "y")
Default values:
(no default values)
Selects:
CRC32 if PCI (value: "y")
NET_CORE if PCI (value: "y")
MII if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_REALTEK (value: "y")
Locations: ../drivers/net/ethernet/realtek/Kconfig:51
This is a driver for the Fast Ethernet PCI network cards based on
the RTL 8129/8130/8139 chips. If you have one of those, say Y and
read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose M here: the module
will be called 8139too. This is recommended.
Symbol 8139TOO_PIO
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Use PIO instead of MMIO" if 8139TOO (value: "m")
Default values:
y (value: "y")
Condition: 8139TOO (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_REALTEK (value: "y")
Locations: ../drivers/net/ethernet/realtek/Kconfig:65
This instructs the driver to use programmed I/O ports (PIO) instead
of PCI shared memory (MMIO). This can possibly solve some problems
in case your mainboard has memory consistency issues. If unsure,
say N.
Symbol R8169
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Realtek 8169 gigabit ethernet support" if PCI (value: "y")
Default values:
(no default values)
Selects:
FW_LOADER if PCI (value: "y")
CRC32 if PCI (value: "y")
NET_CORE if PCI (value: "y")
MII if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_REALTEK (value: "y")
Locations: ../drivers/net/ethernet/realtek/Kconfig:105
Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
To compile this driver as a module, choose M here: the module
will be called r8169. This is recommended.
Symbol NET_VENDOR_RDC
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RDC devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/rdc/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about RDC cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_SEEQ
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SEEQ devices" if HAS_IOMEM (value: "y")
Default values:
y (value: "y")
Condition: HAS_IOMEM (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/seeq/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about SEEQ devices. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_SILAN
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Silan devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/silan/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Silan devices. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_SIS
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Silicon Integrated Systems (SiS) devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/sis/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about SiS devices. If you say Y, you will be asked for
your specific card in the following questions.
Symbol SFC
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Solarflare SFC4000/SFC9000-family support" if PCI (value: "y")
Default values:
(no default values)
Selects:
MDIO if PCI (value: "y")
CRC32 if PCI (value: "y")
I2C if PCI (value: "y")
I2C_ALGOBIT if PCI (value: "y")
PTP_1588_CLOCK if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/sfc/Kconfig:1
This driver supports 10-gigabit Ethernet cards based on
the Solarflare SFC4000 and SFC9000-family controllers.
To compile this driver as a module, choose M here. The module
will be called sfc.
Symbol NET_VENDOR_SMSC
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SMC (SMSC)/Western Digital devices" if ARM || ISA || MAC || ARM || MIPS || M32R || SUPERH || BLACKFIN || MN10300 || COLDFIRE || PCI || PCMCIA (value: "y")
Default values:
y (value: "y")
Condition: ARM || ISA || MAC || ARM || MIPS || M32R || SUPERH || BLACKFIN || MN10300 || COLDFIRE || PCI || PCMCIA (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/smsc/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about SMC/Western Digital cards. If you say Y, you will
be asked for your specific card in the following questions.
Symbol NET_VENDOR_STMICRO
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"STMicroelectronics devices" if HAS_IOMEM (value: "y")
Default values:
y (value: "y")
Condition: HAS_IOMEM (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/stmicro/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about STMicroelectronics cards. If you say Y, you will
be asked for your specific card in the following questions.
Symbol NET_VENDOR_SUN
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Sun devices" if SUN3 || SBUS || PCI || SUN_LDOMS (value: "y")
Default values:
y (value: "y")
Condition: SUN3 || SBUS || PCI || SUN_LDOMS (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/sun/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say
Y and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Sun network interfaces. If you say Y, you will be
asked for your specific card in the following questions.
Symbol NET_VENDOR_TEHUTI
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Tehuti devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/tehuti/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about Tehuti cards. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_TI
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Texas Instruments (TI) devices" if PCI || EISA || AR7 || ARM && (ARCH_DAVINCI || ARCH_OMAP3 || SOC_AM33XX) (value: "y")
Default values:
y (value: "y")
Condition: PCI || EISA || AR7 || ARM && (ARCH_DAVINCI || ARCH_OMAP3 || SOC_AM33XX) (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/ti/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about TI devices. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_VIA
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VIA devices" if PCI (value: "y")
Default values:
y (value: "y")
Condition: PCI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/via/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about VIA devices. If you say Y, you will be asked for
your specific card in the following questions.
Symbol NET_VENDOR_WIZNET
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"WIZnet devices" if HAS_IOMEM (value: "y")
Default values:
y (value: "y")
Condition: HAS_IOMEM (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES (value: "y")
Locations: ../drivers/net/ethernet/wiznet/Kconfig:5
If you have a network (Ethernet) card belonging to this class, say Y
and read the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about WIZnet devices. If you say Y, you will be asked
for your specific card in the following questions.
Symbol WIZNET_W5100
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"WIZnet W5100 Ethernet support" if HAS_IOMEM (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_WIZNET (value: "y")
Locations: ../drivers/net/ethernet/wiznet/Kconfig:21
Support for WIZnet W5100 chips.
W5100 is a single chip with integrated 10/100 Ethernet MAC,
PHY and hardware TCP/IP stack, but this driver is limited to
the MAC and PHY functions only, onchip TCP/IP is unused.
To compile this driver as a module, choose M here: the module
will be called w5100.
Symbol WIZNET_W5300
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"WIZnet W5300 Ethernet support" if HAS_IOMEM (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ETHERNET && NETDEVICES && NET_VENDOR_WIZNET (value: "y")
Locations: ../drivers/net/ethernet/wiznet/Kconfig:34
Support for WIZnet W5300 chips.
W5300 is a single chip with integrated 10/100 Ethernet MAC,
PHY and hardware TCP/IP stack, but this driver is limited to
the MAC and PHY functions only, onchip TCP/IP is unused.
To compile this driver as a module, choose M here: the module
will be called w5300.
Symbol FDDI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"FDDI driver support" if PCI || EISA || TC (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/fddi/Kconfig:5
Fiber Distributed Data Interface is a high speed local area network
design; essentially a replacement for high speed Ethernet. FDDI can
run over copper or fiber. If you are connected to such a network and
want a driver for the FDDI card in your computer, say Y here (and
then also Y to the driver for your FDDI card, below). Most people
will say N.
Symbol HIPPI
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"HIPPI driver support" if INET && PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/hippi/Kconfig:5
HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
can run over copper (25m) or fiber (300m on multi-mode or 10km on
single-mode). HIPPI networks are commonly used for clusters and to
connect to super computers. If you are connected to a HIPPI network
and have a HIPPI network card in your computer that you want to use
under Linux, say Y here (you must also remember to enable the driver
for your HIPPI card below). Most people will say N here.
Symbol NET_SB1000
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"General Instruments Surfboard 1000" if PNP (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/Kconfig:264
This is a driver for the General Instrument (also known as
NextLevel) SURFboard 1000 internal
cable modem. This is an ISA card which is used by a number of cable
TV companies to provide cable modem access. It's a one-way
downstream-only cable modem, meaning that your upstream net link is
provided by your regular phone modem.
At present this driver only compiles as a module, so say M here if
you have this card. The module will be called sb1000. Then read
<file:Documentation/networking/README.sb1000> for information on how
to use this module, as it needs special ppp scripts for establishing
a connection. Further documentation and the necessary scripts can be
found at:
<http://www.jacksonville.net/~fventuri/>
<http://home.adelphia.net/~siglercm/sb1000.html>
<http://linuxpower.cx/~cable/>
If you don't have this card, of course say N.
Symbol PHYLIB
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PHY Device support and infrastructure" if NETDEVICES (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
HAVE_NET_DSA && NET && NET_DSA || ETHERNET && NETDEVICES && SPARC && GRETH || ETHERNET && NETDEVICES && NET_VENDOR_AMD && MIPS_ALCHEMY && MIPS_AU1X00_ENET || ETHERNET && NETDEVICES && NET_CADENCE && MACB || ETHERNET && NETDEVICES && NET_BFIN && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537) && BFIN_MAC || ETHERNET && NETDEVICES && NET_VENDOR_BROADCOM && BCM63XX && BCM63XX_ENET || ETHERNET && NETDEVICES && NET_VENDOR_BROADCOM && SIBYTE_SB1xxx_SOC && SB1250_MAC || ETHERNET && NETDEVICES && NET_VENDOR_BROADCOM && PCI && TIGON3 || ETHERNET && NETDEVICES && HAS_IOMEM && DNET || ETHERNET && NETDEVICES && NET_VENDOR_FARADAY && ARM && FTGMAC100 || ETHERNET && NETDEVICES && NET_VENDOR_FREESCALE && (M523x || M527x || M5272 || M528x || M520x || M532x || ARCH_MXC || SOC_IMX28) && FEC || PPC_MPC52xx && PPC_BESTCOMM && ETHERNET && NETDEVICES && NET_VENDOR_FREESCALE && FEC_MPC52xx || NET_VENDOR_FREESCALE && (CPM1 || CPM2 || PPC_MPC512x) && ETHERNET && NETDEVICES && NET_VENDOR_FREESCALE && FS_ENET || ETHERNET && NETDEVICES && NET_VENDOR_FREESCALE && FSL_SOC && FSL_PQ_MDIO || ETHERNET && NETDEVICES && NET_VENDOR_FREESCALE && FSL_SOC && FSL_XGMAC_MDIO || ETHERNET && NETDEVICES && NET_VENDOR_FREESCALE && QUICC_ENGINE && UCC_GETH || ETHERNET && NETDEVICES && NET_VENDOR_FREESCALE && FSL_SOC && GIANFAR || ARM && ARCH_IXP4XX && IXP4XX_NPE && IXP4XX_QMGR && ETHERNET && NETDEVICES && NET_VENDOR_XSCALE && IXP4XX_ETH || (MV64X60 || PPC32 || PLAT_ORION) && INET && ETHERNET && NETDEVICES && NET_VENDOR_MARVELL && MV643XX_ETH || ETHERNET && NETDEVICES && NET_VENDOR_MARVELL && MVMDIO || ETHERNET && NETDEVICES && NET_VENDOR_MARVELL && CPU_PXA168 && PXA168_ETH || ETHERNET && NETDEVICES && NET_VENDOR_8390 && (ARM || MIPS || SUPERH) && AX88796 || ARM && ARCH_W90X900 && ETHERNET && NETDEVICES && NET_VENDOR_NUVOTON && W90P910_ETH || ETHERNET && NETDEVICES && ARCH_LPC32XX && LPC_ENET || ETHERNET && NETDEVICES && CPU_CAVIUM_OCTEON && OCTEON_MGMT_ETHERNET || HAS_IOMEM && HAS_DMA && ETHERNET && NETDEVICES && ETHOC || PPC_PASEMI && PCI && INET && ETHERNET && NETDEVICES && NET_VENDOR_PASEMI && PASEMI_MAC || (SUPERH || ARCH_SHMOBILE) && (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7734 || CPU_SUBTYPE_SH7757 || ARCH_R8A7740 || ARCH_R8A7779) && ETHERNET && NETDEVICES && SH_ETH || ETHERNET && NETDEVICES && NET_VENDOR_RDC && PCI && R6040 || ETHERNET && NETDEVICES && XTENSA_VARIANT_S6000 && S6GMAC || ETHERNET && NETDEVICES && NET_VENDOR_SMSC && (ARM || SUPERH || BLACKFIN || MIPS || MN10300) && SMSC911X || ETHERNET && NETDEVICES && NET_VENDOR_SMSC && PCI && SMSC9420 || ETHERNET && NETDEVICES && NET_VENDOR_STMICRO && HAS_IOMEM && STMMAC_ETH || ARM && (ARCH_DAVINCI || ARCH_OMAP3) && ETHERNET && NETDEVICES && NET_VENDOR_TI && TI_DAVINCI_EMAC || ARM && (ARCH_DAVINCI || ARCH_OMAP3 || SOC_AM33XX) && ETHERNET && NETDEVICES && NET_VENDOR_TI && TI_DAVINCI_MDIO || ETHERNET && NETDEVICES && NET_VENDOR_TI && AR7 && CPMAC || PCI && MIPS && ETHERNET && NETDEVICES && NET_VENDOR_TOSHIBA && TC35815 || ETHERNET && NETDEVICES && NET_VENDOR_XILINX && (PPC32 || MICROBLAZE) && XILINX_EMACLITE || ETHERNET && NETDEVICES && NET_VENDOR_XILINX && MICROBLAZE && XILINX_AXI_EMAC || ETHERNET && NETDEVICES && NET_VENDOR_XILINX && (PPC || MICROBLAZE) && XILINX_LL_TEMAC || USB && NET && NETDEVICES && USB_USBNET && USB_NET_AX8817X || USB && NET && NETDEVICES && USB_USBNET && USB_NET_AX88179_178A || PCI && NET && NETDEVICES && STAGING && ET131X || CPU_CAVIUM_OCTEON && NETDEVICES && STAGING && OCTEON_ETHERNET (value: "n")
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/phy/Kconfig:5
Ethernet controllers are usually attached to PHY
devices. This option provides infrastructure for
managing PHY devices.
Symbol AMD_PHY
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Drivers for the AMD PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:22
Currently supports the am79c874
Symbol MARVELL_PHY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Drivers for Marvell PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:27
Currently has a driver for the 88E1011S
Symbol DAVICOM_PHY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Drivers for Davicom PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:32
Currently supports dm9161e and dm9131
Symbol QSEMI_PHY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Drivers for Quality Semiconductor PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:37
Currently supports the qs6612
Symbol LXT_PHY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Drivers for the Intel LXT PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:42
Currently supports the lxt970, lxt971
Symbol CICADA_PHY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Drivers for the Cicada PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:47
Currently supports the cis8204
Symbol VITESSE_PHY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Drivers for the Vitesse PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:52
Currently supports the vsc8244
Symbol SMSC_PHY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Drivers for SMSC PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
ETHERNET && NETDEVICES && NET_VENDOR_SMSC && PCI && SMSC9420 (value: "n")
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:57
Currently supports the LAN83C185, LAN8187 and LAN8700 PHYs
Symbol BROADCOM_PHY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Drivers for Broadcom PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:62
Currently supports the BCM5411, BCM5421, BCM5461, BCM5464, BCM5481
and BCM5482 PHYs.
Symbol BCM87XX_PHY
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Driver for Broadcom BCM8706 and BCM8727 PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:74
Currently supports the BCM8706 and BCM8727 10G Ethernet PHYs.
Symbol ICPLUS_PHY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Drivers for ICPlus PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:79
Currently supports the IP175C and IP1001 PHYs.
Symbol REALTEK_PHY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Drivers for Realtek PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:84
Supports the Realtek 821x PHY.
Symbol NATIONAL_PHY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Drivers for National Semiconductor PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:89
Currently supports the DP83865 PHY.
Symbol STE10XP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Driver for STMicroelectronics STe10Xp PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:94
This is the driver for the STe100p and STe101p PHYs.
Symbol LSI_ET1011C_PHY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Driver for LSI ET1011C PHY"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:99
Supports the LSI ET1011C PHY.
Symbol MICREL_PHY
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Driver for Micrel PHYs"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:104
Supports the KSZ9021, VSC8201, KS8001 PHYs.
Symbol MDIO_BITBANG
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support for bitbanged MDIO buses"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
FS_ENET && CPM2 && ETHERNET && NETDEVICES && NET_VENDOR_FREESCALE && FS_ENET_MDIO_FCC || ETHERNET && NETDEVICES && NET_VENDOR_8390 && (ARM || MIPS || SUPERH) && AX88796 || (SUPERH || ARCH_SHMOBILE) && (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7734 || CPU_SUBTYPE_SH7757 || ARCH_R8A7740 || ARCH_R8A7779) && ETHERNET && NETDEVICES && SH_ETH (value: "n")
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:118
This module implements the MDIO bus protocol in software,
for use by low level drivers that export the ability to
drive the relevant pins.
If in doubt, say N.
Symbol MDIO_GPIO
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support for GPIO lib-based bitbanged MDIO buses" if MDIO_BITBANG && GENERIC_GPIO (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
PHYLIB && NETDEVICES (value: "m")
Locations: ../drivers/net/phy/Kconfig:127
Supports GPIO lib-based MDIO busses.
To compile this driver as a module, choose M here: the module
will be called mdio-gpio.
Symbol PLIP
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PLIP (parallel port) support" if PARPORT (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/plip/Kconfig:5
PLIP (Parallel Line Internet Protocol) is used to create a
reasonably fast mini network consisting of two (or, rarely, more)
local machines. A PLIP link from a Linux box is a popular means to
install a Linux distribution on a machine which doesn't have a
CD-ROM drive (a minimal system has to be transferred with floppies
first). The kernels on both machines need to have this PLIP option
enabled for this to work.
The PLIP driver has two modes, mode 0 and mode 1. The parallel
ports (the connectors at the computers with 25 holes) are connected
with "null printer" or "Turbo Laplink" cables which can transmit 4
bits at a time (mode 0) or with special PLIP cables, to be used on
bidirectional parallel ports only, which can transmit 8 bits at a
time (mode 1); you can find the wiring of these cables in
<file:Documentation/networking/PLIP.txt>. The cables can be up to
15m long. Mode 0 works also if one of the machines runs DOS/Windows
and has some PLIP software installed, e.g. the Crynwr PLIP packet
driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
and winsock or NCSA's telnet.
If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
as the NET-3-HOWTO, both available from
<http://www.tldp.org/docs.html#howto>. Note that the PLIP
protocol has been changed and this PLIP driver won't work together
with the PLIP support in Linux versions 1.0.x. This option enlarges
your kernel by about 8 KB.
To compile this driver as a module, choose M here. The module
will be called plip. If unsure, say Y or M, in case you buy
a laptop later.
Symbol PPP
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PPP (point-to-point protocol) support"
Default values:
(no default values)
Selects:
SLHC
Reverse dependencies:
PCMCIA && NETDEVICES && TTY && HOTPLUG && PCMCIA != n && IPWIRELESS (value: "n")
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/ppp/Kconfig:5
PPP (Point to Point Protocol) is a newer and better SLIP. It serves
the same purpose: sending Internet traffic over telephone (and other
serial) lines. Ask your access provider if they support it, because
otherwise you can't use it; most Internet access providers these
days support PPP rather than SLIP.
To use PPP, you need an additional program called pppd as described
in the PPP-HOWTO, available at
<http://www.tldp.org/docs.html#howto>. Make sure that you have
the version of pppd recommended in <file:Documentation/Changes>.
The PPP option enlarges your kernel by about 16 KB.
There are actually two versions of PPP: the traditional PPP for
asynchronous lines, such as regular analog phone lines, and
synchronous PPP which can be used over digital ISDN lines for
example. If you want to use PPP over phone lines or other
asynchronous serial lines, you need to say Y (or M) here and also to
the next option, "PPP support for async serial ports". For PPP over
synchronous lines, you should say Y (or M) here and to "Support
synchronous PPP", below.
If you said Y to "Version information on all symbols" above, then
you cannot compile the PPP driver into the kernel; you can then only
compile it as a module. To compile this driver as a module, choose M
here. The module will be called ppp_generic.
Symbol SLIP
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SLIP (serial line) support" if TTY (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/slip/Kconfig:5
Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
connect to your Internet service provider or to connect to some
other local Unix box or if you want to configure your Linux box as a
Slip/CSlip server for other people to dial in. SLIP (Serial Line
Internet Protocol) is a protocol used to send Internet traffic over
serial connections such as telephone lines or null modem cables;
nowadays, the protocol PPP is more commonly used for this same
purpose.
Normally, your access provider has to support SLIP in order for you
to be able to use it, but there is now a SLIP emulator called SLiRP
around (available from
<ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
allows you to use SLIP over a regular dial up shell connection. If
you plan to use SLiRP, make sure to say Y to CSLIP, below. The
NET-3-HOWTO, available from
<http://www.tldp.org/docs.html#howto>, explains how to
configure SLIP. Note that you don't need this option if you just
want to run term (term is a program which gives you almost full
Internet connectivity if you have a regular dial up shell account on
some Internet connected Unix computer. Read
<http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
support will enlarge your kernel by about 4 KB. If unsure, say N.
To compile this driver as a module, choose M here. The module
will be called slip.
Symbol USB_CATC
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
USB Network Adapters
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"USB CATC NetMate-based Ethernet device support"
Default values:
(no default values)
Selects:
CRC32
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
USB && NET && NETDEVICES (value: "m")
Locations: ../drivers/net/usb/Kconfig:10
Say Y if you want to use one of the following 10Mbps USB Ethernet
device based on the EL1210A chip. Supported devices are:
Belkin F5U011
Belkin F5U111
CATC NetMate
CATC NetMate II
smartBridges smartNIC
This driver makes the adapter appear as a normal Ethernet interface,
typically on eth0, if it is the only ethernet device, or perhaps on
eth1, if you have a PCI or ISA ethernet card installed.
To compile this driver as a module, choose M here: the
module will be called catc.
Symbol USB_KAWETH
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
USB Network Adapters
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"USB KLSI KL5USB101-based ethernet device support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
USB && NET && NETDEVICES (value: "m")
Locations: ../drivers/net/usb/Kconfig:29
Say Y here if you want to use one of the following 10Mbps only
USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
3Com 3C19250
ADS USB-10BT
ATEN USB Ethernet
ASANTE USB To Ethernet Adapter
AOX Endpoints USB Ethernet
Correga K.K.
D-Link DSB-650C and DU-E10
Entrega / Portgear E45
I-O DATA USB-ET/T
Jaton USB Ethernet Device Adapter
Kingston Technology USB Ethernet Adapter
Linksys USB10T
Mobility USB-Ethernet Adapter
NetGear EA-101
Peracom Enet and Enet2
Portsmith Express Ethernet Adapter
Shark Pocket Adapter
SMC 2202USB
Sony Vaio port extender
This driver is likely to work with most 10Mbps only USB Ethernet
adapters, including some "no brand" devices. It does NOT work on
SmartBridges smartNIC or on Belkin F5U111 devices - you should use
the CATC NetMate driver for those. If you are not sure which one
you need, select both, and the correct one should be selected for
you.
This driver makes the adapter appear as a normal Ethernet interface,
typically on eth0, if it is the only ethernet device, or perhaps on
eth1, if you have a PCI or ISA ethernet card installed.
To compile this driver as a module, choose M here: the
module will be called kaweth.
Symbol USB_PEGASUS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
USB Network Adapters
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"USB Pegasus/Pegasus-II based ethernet device support"
Default values:
(no default values)
Selects:
NET_CORE
MII
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
USB && NET && NETDEVICES (value: "m")
Locations: ../drivers/net/usb/Kconfig:68
Say Y here if you know you have Pegasus or Pegasus-II based adapter.
If in doubt then look at <file:drivers/net/usb/pegasus.h> for the
complete list of supported devices.
If your particular adapter is not in the list and you are _sure_ it
is Pegasus or Pegasus II based then send me
<petkan@users.sourceforge.net> vendor and device IDs.
To compile this driver as a module, choose M here: the
module will be called pegasus.
Symbol USB_RTL8150
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
USB Network Adapters
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"USB RTL8150 based ethernet device support"
Default values:
(no default values)
Selects:
NET_CORE
MII
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
USB && NET && NETDEVICES (value: "m")
Locations: ../drivers/net/usb/Kconfig:84
Say Y here if you have RTL8150 based usb-ethernet adapter.
Send me <petkan@users.sourceforge.net> any comments you may have.
You can also check for updates at <http://pegasus2.sourceforge.net/>.
To compile this driver as a module, choose M here: the
module will be called rtl8150.
Symbol USB_USBNET
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
USB Network Adapters
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Multi-purpose USB Networking Framework"
Default values:
(no default values)
Selects:
NET_CORE
MII
Reverse dependencies:
USB && CFG80211 && WLAN && NETDEVICES && USB_NET_RNDIS_WLAN (value: "n")
Additional dependencies from enclosing menus and if's:
USB && NET && NETDEVICES (value: "m")
Locations: ../drivers/net/usb/Kconfig:96
This driver supports several kinds of network links over USB,
with "minidrivers" built around a common network driver core
that supports deep queues for efficient transfers. (This gives
better performance with small packets and at high speeds).
The USB host runs "usbnet", and the other end of the link might be:
- Another USB host, when using USB "network" or "data transfer"
cables. These are often used to network laptops to PCs, like
"Laplink" parallel cables or some motherboards. These rely
on specialized chips from many suppliers.
- An intelligent USB gadget, perhaps embedding a Linux system.
These include PDAs running Linux (iPaq, Yopy, Zaurus, and
others), and devices that interoperate using the standard
CDC-Ethernet specification (including many cable modems).
- Network adapter hardware (like those for 10/100 Ethernet) which
uses this driver framework.
The link will appear with a name like "usb0", when the link is
a two-node link, or "eth0" for most CDC-Ethernet devices. Those
two-node links are most easily managed with Ethernet Bridging
(CONFIG_BRIDGE) instead of routing.
For more information see <http://www.linux-usb.org/usbnet/>.
To compile this driver as a module, choose M here: the
module will be called usbnet.
Symbol USB_CDC_PHONET
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
USB Network Adapters
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"CDC Phonet support" if PHONET (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
USB && NET && NETDEVICES (value: "m")
Locations: ../drivers/net/usb/Kconfig:481
Choose this option to support the Phonet interface to a Nokia
cellular modem, as found on most Nokia handsets with the
"PC suite" USB profile.
Symbol USB_IPHETH
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
USB Network Adapters
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Apple iPhone USB Ethernet driver"
Default values:
n (value: "n")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
USB && NET && NETDEVICES (value: "m")
Locations: ../drivers/net/usb/Kconfig:489
Module used to share Internet connection (tethering) from your
iPhone (Original, 3G and 3GS) to your system.
Note that you need userspace libraries and programs that are needed
to pair your device with your system and that understand the iPhone
protocol.
For more information: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
Symbol WLAN
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Wireless LAN" if !S390 && NET (value: "y")
Default values:
y (value: "y")
Condition: !S390 && NET (value: "y")
Selects:
WIRELESS if !S390 && NET (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/wireless/Kconfig:5
This section contains all the pre 802.11 and 802.11 wireless
device drivers. For a complete list of drivers and documentation
on them refer to the wireless wiki:
http://wireless.kernel.org/en/users/Drivers
Symbol WAN
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Wan interfaces support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/wan/Kconfig:5
Wide Area Networks (WANs), such as X.25, Frame Relay and leased
lines, are used to interconnect Local Area Networks (LANs) over vast
distances with data transfer rates significantly higher than those
achievable with commonly used asynchronous modem connections.
Usually, a quite expensive external device called a `WAN router' is
needed to connect to a WAN. As an alternative, a relatively
inexpensive WAN interface card can allow your Linux box to directly
connect to a WAN.
If you have one of those cards and wish to use it under Linux,
say Y here and also to the WAN driver for your card.
If unsure, say N.
Symbol IEEE802154_DRIVERS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IEEE 802.15.4 drivers" if NETDEVICES && IEEE802154 (value: "m")
Default values:
y (value: "y")
Condition: NETDEVICES && IEEE802154 (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/ieee802154/Kconfig:1
Say Y here to get to see options for IEEE 802.15.4 Low-Rate
Wireless Personal Area Network device drivers. This option alone
does not add any kernel code.
If you say N, all options in this submenu will be skipped and
disabled.
Symbol XEN_NETDEV_FRONTEND
Type : tristate
Value : "y"
User value : "y"
Xen config : 'y'
Main config : 'n'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Xen network device frontend driver" if XEN (value: "y")
Default values:
y (value: "y")
Condition: XEN (value: "y")
Selects:
XEN_XENBUS_FRONTEND if XEN (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/Kconfig:308
This driver provides support for Xen paravirtual network
devices exported by a Xen network driver domain (often
domain 0).
The corresponding Linux backend driver is enabled by the
CONFIG_XEN_NETDEV_BACKEND option.
If you are compiling a kernel for use as Xen guest, you
should say Y here. To compile this driver as a module, chose
M here: the module will be called xen-netfront.
Symbol XEN_NETDEV_BACKEND
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'n'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Xen backend network device" if XEN_BACKEND (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/Kconfig:325
This driver allows the kernel to act as a Xen network driver
domain which exports paravirtual network devices to other
Xen domains. These devices can be accessed by any operating
system that implements a compatible front end.
The corresponding Linux frontend driver is enabled by the
CONFIG_XEN_NETDEV_FRONTEND configuration option.
The backend driver presents a standard network device
endpoint for each paravirtual network device to the driver
domain network stack. These can then be bridged or routed
etc in order to provide full network connectivity.
If you are compiling a kernel to run in a Xen network driver
domain (often this is domain 0) you should say Y here. To
compile this driver as a module, chose M here: the module
will be called xen-netback.
Symbol VMXNET3
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VMware VMXNET3 ethernet driver" if PCI && INET (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/Kconfig:347
This driver supports VMware's vmxnet3 virtual ethernet NIC.
To compile this driver as a module, choose M here: the
module will be called vmxnet3.
Symbol HYPERV_NET
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Microsoft Hyper-V virtual network driver" if HYPERV (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
NETDEVICES (value: "y")
Locations: ../drivers/net/hyperv/Kconfig:1
Select this option to enable the Hyper-V virtual network driver.
Symbol ISDN
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ISDN support" if NET && NETDEVICES && !S390 && !UML (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/isdn/Kconfig:5
ISDN ("Integrated Services Digital Network", called RNIS in France)
is a fully digital telephone service that can be used for voice and
data connections. If your computer is equipped with an ISDN
adapter you can use it to connect to your Internet service provider
(with SLIP or PPP) faster than via a conventional telephone modem
(though still much slower than with DSL) or to make and accept
voice calls (eg. turning your PC into a software answering machine
or PABX).
Select this option if you want your kernel to support ISDN.
Symbol INPUT_FF_MEMLESS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support for memoryless force-feedback devices"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
INPUT && !UML && INPUT_JOYSTICK && PARPORT && JOYSTICK_GAMECON || JOYSTICK_XPAD && INPUT && INPUT && !UML && INPUT_JOYSTICK && JOYSTICK_XPAD_FF || MFD_ARIZONA && SND_SOC && INPUT && !UML && INPUT_MISC && INPUT_ARIZONA_HAPTICS || INPUT && !UML && INPUT_MISC && MFD_PM8XXX && INPUT_PM8XXX_VIBRATOR || HAVE_PWM && MFD_MAX8997 && INPUT && !UML && INPUT_MISC && INPUT_MAX8997_HAPTIC || INPUT && !UML && INPUT_MISC && TWL4030_CORE && INPUT_TWL4030_VIBRA || INPUT && !UML && INPUT_MISC && TWL6040_CORE && INPUT_TWL6040_VIBRA || HID && INPUT && HID && HID_ACRUX && HID_ACRUX_FF || HID && INPUT && HID && HID_DRAGONRISE && DRAGONRISE_FF || HID && INPUT && HID && USB_HID && HID_EMS_FF || HID && INPUT && HID && HID_HOLTEK && HOLTEK_FF || HID && INPUT && HID && HID_LOGITECH && LOGITECH_FF || HID && INPUT && HID && HID_LOGITECH && LOGIRUMBLEPAD2_FF || HID && INPUT && HID && HID_LOGITECH && LOGIG940_FF || HID && INPUT && HID && HID_LOGITECH && LOGIWHEELS_FF || HID && INPUT && HID && HID_PANTHERLORD && PANTHERLORD_FF || HID && INPUT && HID && HID_GREENASIA && GREENASIA_FF || HID && INPUT && HID && HID_SMARTJOYPLUS && SMARTJOYPLUS_FF || HID && INPUT && HID && HID_THRUSTMASTER && THRUSTMASTER_FF || BT_HIDP && LEDS_CLASS && HID && INPUT && HID && HID_WIIMOTE || HID && INPUT && HID && HID_ZEROPLUS && ZEROPLUS_FF (value: "n")
Additional dependencies from enclosing menus and if's:
INPUT && !UML (value: "y")
Locations: ../drivers/input/Kconfig:28
Say Y here if you have memoryless force-feedback input device
such as Logitech WingMan Force 3D, ThrustMaster FireStorm Dual
Power 2, or similar. You will also need to enable hardware-specific
driver.
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called ff-memless.
Symbol INPUT_SPARSEKMAP
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Sparse keymap support library"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
X86 && !X86_64 && INPUT && !UML && INPUT_MISC && INPUT_WISTRON_BTNS || INPUT && !UML && INPUT_MISC && MFD_DM355EVM_MSP && INPUT_DM355EVM || ACPI && BACKLIGHT_CLASS_DEVICE && SERIO_I8042 && INPUT && (RFKILL || RFKILL = n) && ACPI_WMI && X86_PLATFORM_DEVICES && X86 && ACER_WMI || ACPI && INPUT && (RFKILL || RFKILL = n) && X86_PLATFORM_DEVICES && X86 && ASUS_LAPTOP || ACPI_WMI && INPUT && X86_PLATFORM_DEVICES && X86 && DELL_WMI || ACPI_WMI && INPUT && X86_PLATFORM_DEVICES && X86 && DELL_WMI_AIO || ACPI_WMI && INPUT && (RFKILL || RFKILL = n) && X86_PLATFORM_DEVICES && X86 && HP_WMI || ACPI && BACKLIGHT_CLASS_DEVICE && RFKILL && INPUT && SERIO_I8042 && X86_PLATFORM_DEVICES && X86 && MSI_LAPTOP || INPUT && ACPI && BACKLIGHT_CLASS_DEVICE && X86_PLATFORM_DEVICES && X86 && PANASONIC_LAPTOP || RFKILL && INPUT && ACPI && SERIO_I8042 && BACKLIGHT_CLASS_DEVICE && X86_PLATFORM_DEVICES && X86 && IDEAPAD_LAPTOP || ACPI && INPUT && (RFKILL || RFKILL = n) && HOTPLUG_PCI && X86_PLATFORM_DEVICES && X86 && EEEPC_LAPTOP || ACPI_WMI && INPUT && HWMON && BACKLIGHT_CLASS_DEVICE && (RFKILL || RFKILL = n) && HOTPLUG_PCI && X86_PLATFORM_DEVICES && X86 && ASUS_WMI || ACPI_WMI && INPUT && BACKLIGHT_CLASS_DEVICE && X86_PLATFORM_DEVICES && X86 && MSI_WMI || ACPI && INPUT && X86_PLATFORM_DEVICES && X86 && TOPSTAR_LAPTOP || ACPI && ACPI_WMI && BACKLIGHT_CLASS_DEVICE && INPUT && (RFKILL || RFKILL = n) && X86_PLATFORM_DEVICES && X86 && ACPI_TOSHIBA (value: "n")
Additional dependencies from enclosing menus and if's:
INPUT && !UML (value: "y")
Locations: ../drivers/input/Kconfig:54
Say Y here if you are using a driver for an input
device that uses sparse keymap. This option is only
useful for out-of-tree drivers since in-tree drivers
select it automatically.
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called sparse-keymap.
Symbol INPUT_MOUSEDEV
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Mouse interface" if EXPERT (value: "y")
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML (value: "y")
Locations: ../drivers/input/Kconfig:82
Say Y here if you want your mouse to be accessible as char devices
13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
programs (including SVGAlib, GPM and X) will be able to use your
mouse.
If unsure, say Y.
To compile this driver as a module, choose M here: the
module will be called mousedev.
Symbol INPUT_MOUSEDEV_PSAUX
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Provide legacy /dev/psaux device" if INPUT_MOUSEDEV (value: "m")
Default values:
y (value: "y")
Condition: INPUT_MOUSEDEV (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML (value: "y")
Locations: ../drivers/input/Kconfig:97
Say Y here if you want your mouse also be accessible as char device
10:1 - /dev/psaux. The data available through /dev/psaux is exactly
the same as the data from /dev/input/mice.
If unsure, say Y.
Symbol INPUT_MOUSEDEV_SCREEN_X
Type : int
Value : "1024"
User value : "1024"
Xen config : ''
Main config : '1024'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Horizontal screen resolution" if INPUT_MOUSEDEV (value: "m")
Default values:
"1024" (value: "n")
Condition: INPUT_MOUSEDEV (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML (value: "y")
Locations: ../drivers/input/Kconfig:109
If you're using a digitizer, or a graphic tablet, and want to use
it as a mouse then the mousedev driver needs to know the X window
screen resolution you are using to correctly scale the data. If
you're not using a digitizer, this value is ignored.
Symbol INPUT_MOUSEDEV_SCREEN_Y
Type : int
Value : "768"
User value : "768"
Xen config : ''
Main config : '768'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Vertical screen resolution" if INPUT_MOUSEDEV (value: "m")
Default values:
"768" (value: "n")
Condition: INPUT_MOUSEDEV (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML (value: "y")
Locations: ../drivers/input/Kconfig:119
If you're using a digitizer, or a graphic tablet, and want to use
it as a mouse then the mousedev driver needs to know the X window
screen resolution you are using to correctly scale the data. If
you're not using a digitizer, this value is ignored.
Symbol INPUT_JOYDEV
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Joystick interface"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML (value: "y")
Locations: ../drivers/input/Kconfig:129
Say Y here if you want your joystick or gamepad to be
accessible as char device 13:0+ - /dev/input/jsX device.
If unsure, say Y.
More information is available: <file:Documentation/input/joystick.txt>
To compile this driver as a module, choose M here: the
module will be called joydev.
Symbol INPUT_EVDEV
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Event interface"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML (value: "y")
Locations: ../drivers/input/Kconfig:142
Say Y here if you want your input device events be accessible
under char device 13:64+ - /dev/input/eventX in a generic way.
To compile this driver as a module, choose M here: the
module will be called evdev.
Symbol INPUT_EVBUG
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Event debugging"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML (value: "y")
Locations: ../drivers/input/Kconfig:151
Say Y here if you have a problem with the input subsystem and
want all events (keypresses, mouse movements), to be output to
the system log. While this is useful for debugging, it's also
a security threat - your keypresses include your passwords, of
course.
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called evbug.
Symbol INPUT_KEYBOARD
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Keyboards" if EXPERT || !X86 (value: "y")
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML (value: "y")
Locations: ../drivers/input/keyboard/Kconfig:4
Say Y here, and a list of supported keyboards will be displayed.
This option doesn't affect the kernel.
If unsure, say Y.
Symbol KEYBOARD_ATKBD
Type : tristate
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AT keyboard" if EXPERT || !X86 (value: "y")
Default values:
y (value: "y")
Condition: (none)
Selects:
SERIO
SERIO_LIBPS2
SERIO_I8042 if X86 (value: "y")
SERIO_GSCPS2 if GSC (value: "n")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_KEYBOARD (value: "y")
Locations: ../drivers/input/keyboard/Kconfig:69
Say Y here if you want to use a standard AT or PS/2 keyboard. Usually
you'll need this, unless you have a different type keyboard (USB, ADB
or other). This also works for AT and PS/2 keyboards connected over a
PS/2 to serial converter.
If unsure, say Y.
To compile this driver as a module, choose M here: the
module will be called atkbd.
Symbol INPUT_MOUSE
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Mice"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML (value: "y")
Locations: ../drivers/input/mouse/Kconfig:4
Say Y here, and a list of supported mice will be displayed.
This option doesn't affect the kernel.
If unsure, say Y.
Symbol MOUSE_PS2
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PS/2 mouse"
Default values:
y (value: "y")
Condition: (none)
Selects:
SERIO
SERIO_LIBPS2
SERIO_I8042 if X86 (value: "y")
SERIO_GSCPS2 if GSC (value: "n")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:15
Say Y here if you have a PS/2 mouse connected to your system. This
includes the standard 2 or 3-button PS/2 mouse, as well as PS/2
mice with wheels and extra buttons, Microsoft, Logitech or Genius
compatible.
Synaptics, ALPS or Elantech TouchPad users might be interested
in a specialized Xorg/XFree86 driver at:
<http://w1.894.telia.com/~u89404340/touchpad/index.html>
and a new version of GPM at:
<http://www.geocities.com/dt_or/gpm/gpm.html>
<http://xorg.freedesktop.org/archive/individual/driver/>
to take advantage of the advanced features of the touchpad.
If unsure, say Y.
To compile this driver as a module, choose M here: the
module will be called psmouse.
Symbol MOUSE_PS2_ALPS
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ALPS PS/2 mouse protocol extension" if EXPERT && MOUSE_PS2 (value: "m")
Default values:
y (value: "y")
Condition: MOUSE_PS2 (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:41
Say Y here if you have an ALPS PS/2 touchpad connected to
your system.
If unsure, say Y.
Symbol MOUSE_PS2_LOGIPS2PP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Logitech PS/2++ mouse protocol extension" if EXPERT && MOUSE_PS2 (value: "m")
Default values:
y (value: "y")
Condition: MOUSE_PS2 (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:51
Say Y here if you have a Logictech PS/2++ mouse connected to
your system.
If unsure, say Y.
Symbol MOUSE_PS2_SYNAPTICS
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Synaptics PS/2 mouse protocol extension" if EXPERT && MOUSE_PS2 (value: "m")
Default values:
y (value: "y")
Condition: MOUSE_PS2 (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:61
Say Y here if you have a Synaptics PS/2 TouchPad connected to
your system.
If unsure, say Y.
Symbol MOUSE_PS2_CYPRESS
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Cypress PS/2 mouse protocol extension" if EXPERT && MOUSE_PS2 (value: "m")
Default values:
y (value: "y")
Condition: MOUSE_PS2 (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:71
Say Y here if you have a Cypress PS/2 Trackpad connected to
your system.
If unsure, say Y.
Symbol MOUSE_PS2_LIFEBOOK
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fujitsu Lifebook PS/2 mouse protocol extension" if MOUSE_PS2 && X86 && DMI && EXPERT (value: "m")
Default values:
y (value: "y")
Condition: MOUSE_PS2 && X86 && DMI (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:81
Say Y here if you have a Fujitsu B-series Lifebook PS/2
TouchScreen connected to your system.
If unsure, say Y.
Symbol MOUSE_PS2_TRACKPOINT
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IBM Trackpoint PS/2 mouse protocol extension" if EXPERT && MOUSE_PS2 (value: "m")
Default values:
y (value: "y")
Condition: MOUSE_PS2 (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:91
Say Y here if you have an IBM Trackpoint PS/2 mouse connected
to your system.
If unsure, say Y.
Symbol MOUSE_PS2_ELANTECH
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Elantech PS/2 protocol extension" if MOUSE_PS2 (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:101
Say Y here if you have an Elantech PS/2 touchpad connected
to your system.
Note that if you enable this driver you will need an updated
X.org Synaptics driver that does not require ABS_PRESSURE
reports from the touchpad (i.e. post 1.5.0 version). You can
grab a patch for the driver here:
http://userweb.kernel.org/~dtor/synaptics-no-abspressure.patch
If unsure, say N.
This driver exposes some configuration registers via sysfs
entries. For further information,
see <file:Documentation/input/elantech.txt>.
Symbol MOUSE_SERIAL
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Serial mouse"
Default values:
(no default values)
Selects:
SERIO
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:149
Say Y here if you have a serial (RS-232, COM port) mouse connected
to your system. This includes Sun, MouseSystems, Microsoft,
Logitech and all other compatible serial mice.
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called sermouse.
Symbol MOUSE_APPLETOUCH
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Apple USB Touchpad support" if USB_ARCH_HAS_HCD (value: "y")
Default values:
(no default values)
Selects:
USB if USB_ARCH_HAS_HCD (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:162
Say Y here if you want to use an Apple USB Touchpad.
These are the touchpads that can be found on post-February 2005
Apple Powerbooks (prior models have a Synaptics touchpad connected
to the ADB bus).
This driver provides a basic mouse driver but can be interfaced
with the synaptics X11 driver to provide acceleration and
scrolling in X11.
For further information, see
<file:Documentation/input/appletouch.txt>.
To compile this driver as a module, choose M here: the
module will be called appletouch.
Symbol MOUSE_BCM5974
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Apple USB BCM5974 Multitouch trackpad support" if USB_ARCH_HAS_HCD (value: "y")
Default values:
(no default values)
Selects:
USB if USB_ARCH_HAS_HCD (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:183
Say Y here if you have an Apple USB BCM5974 Multitouch
trackpad.
The BCM5974 is the multitouch trackpad found in the Macbook
Air (JAN2008) and Macbook Pro Penryn (FEB2008) laptops.
It is also found in the IPhone (2007) and Ipod Touch (2008).
This driver provides multitouch functionality together with
the synaptics X11 driver.
The interface is currently identical to the appletouch interface,
for further information, see
<file:Documentation/input/appletouch.txt>.
To compile this driver as a module, choose M here: the
module will be called bcm5974.
Symbol MOUSE_CYAPA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Cypress APA I2C Trackpad support" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:206
This driver adds support for Cypress All Points Addressable (APA)
I2C Trackpads, including the ones used in 2012 Samsung Chromebooks.
Say Y here if you have a Cypress APA I2C Trackpad.
To compile this driver as a module, choose M here: the module will be
called cyapa.
Symbol MOUSE_VSXXXAA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"DEC VSXXX-AA/GA mouse and VSXXX-AB tablet"
Default values:
(no default values)
Selects:
SERIO
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:285
Say Y (or M) if you want to use a DEC VSXXX-AA (hockey
puck) or a VSXXX-GA (rectangular) mouse. Theses mice are
typically used on DECstations or VAXstations, but can also
be used on any box capable of RS232 (with some adaptor
described in the source file). This driver also works with the
digitizer (VSXXX-AB) DEC produced.
Symbol MOUSE_GPIO
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"GPIO mouse" if GENERIC_GPIO (value: "y")
Default values:
(no default values)
Selects:
INPUT_POLLDEV if GENERIC_GPIO (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:296
This driver simulates a mouse on GPIO lines of various CPUs (and some
other chips).
Say Y here if your device has buttons or a simple joystick connected
directly to GPIO lines. Your board-specific setup logic must also
provide a platform device and platform data saying which GPIOs are
used.
To compile this driver as a module, choose M here: the
module will be called gpio_mouse.
Symbol MOUSE_SYNAPTICS_I2C
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Synaptics I2C Touchpad support" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:329
This driver supports Synaptics I2C touchpad controller on eXeda
mobile device.
The device will not work the synaptics X11 driver because
(i) it reports only relative coordinates and has no capabilities
to report absolute coordinates
(ii) the eXeda device itself uses Xfbdev as X Server and it does
not allow using xf86-input-* drivers.
Say y here if you have eXeda device and want to use a Synaptics
I2C Touchpad.
To compile this driver as a module, choose M here: the
module will be called synaptics_i2c.
Symbol MOUSE_SYNAPTICS_USB
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Synaptics USB device support" if USB_ARCH_HAS_HCD (value: "y")
Default values:
(no default values)
Selects:
USB if USB_ARCH_HAS_HCD (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MOUSE (value: "y")
Locations: ../drivers/input/mouse/Kconfig:347
Say Y here if you want to use a Synaptics USB touchpad or pointing
stick.
While these devices emulate an USB mouse by default and can be used
with standard usbhid driver, this driver, together with its X.Org
counterpart, allows you to fully utilize capabilities of the device.
More information can be found at:
<http://jan-steinhoff.de/linux/synaptics-usb.html>
To compile this driver as a module, choose M here: the
module will be called synaptics_usb.
Symbol INPUT_TOUCHSCREEN
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Touchscreens"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML (value: "y")
Locations: ../drivers/input/touchscreen/Kconfig:4
Say Y here, and a list of supported touchscreens will be displayed.
This option doesn't affect the kernel.
If unsure, say Y.
Symbol INPUT_AD714X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices AD714x Capacitance Touch Sensor"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:45
Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
You should select a bus connection too.
To compile this driver as a module, choose M here: the
module will be called ad714x.
Symbol INPUT_PCSPKR
Type : tristate
Value : "n"
User value : (no user value)
Xen config : 'n'
Main config : 'm'
Visibility : "n"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PC Speaker support" if PCSPKR_PLATFORM (value: "n")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:96
Say Y here if you want the standard PC Speaker to be used for
bells and whistles.
If unsure, say Y.
To compile this driver as a module, choose M here: the
module will be called pcspkr.
Symbol INPUT_MMA8450
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer" if I2C (value: "m")
Default values:
(no default values)
Selects:
INPUT_POLLDEV if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:179
Say Y here if you want to support Freescale's MMA8450 Accelerometer
through I2C interface.
To compile this driver as a module, choose M here: the
module will be called mma8450.
Symbol INPUT_MPU3050
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"MPU3050 Triaxial gyroscope sensor" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:190
Say Y here if you want to support InvenSense MPU3050
connected via an I2C bus.
To compile this driver as a module, choose M here: the
module will be called mpu3050.
Symbol INPUT_APANEL
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fujitsu Lifebook Application Panel buttons" if X86 && I2C && LEDS_CLASS (value: "m")
Default values:
(no default values)
Selects:
INPUT_POLLDEV if X86 && I2C && LEDS_CLASS (value: "m")
CHECK_SIGNATURE if X86 && I2C && LEDS_CLASS (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:200
Say Y here for support of the Application Panel buttons, used on
Fujitsu Lifebook. These are attached to the mainboard through
an SMBus interface managed by the I2C Intel ICH (i801) driver,
which you should also build for this kernel.
To compile this driver as a module, choose M here: the module will
be called apanel.
Symbol INPUT_ATLAS_BTNS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"x86 Atlas button interface" if X86 && ACPI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:277
Say Y here for support of Atlas wallmount touchscreen buttons.
The events will show up as scancodes F1 through F9 via evdev.
To compile this driver as a module, choose M here: the module will
be called atlas_btns.
Symbol INPUT_ATI_REMOTE2
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ATI / Philips USB RF remote control" if USB_ARCH_HAS_HCD (value: "y")
Default values:
(no default values)
Selects:
USB if USB_ARCH_HAS_HCD (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:287
Say Y here if you want to use an ATI or Philips USB RF remote control.
These are RF remotes with USB receivers.
ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
and is also available as a separate product.
This driver provides mouse pointer, left and right mouse buttons,
and maps all the other remote buttons to keypress events.
To compile this driver as a module, choose M here: the module will be
called ati_remote2.
Symbol INPUT_KEYSPAN_REMOTE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Keyspan DMR USB remote control" if USB_ARCH_HAS_HCD (value: "y")
Default values:
(no default values)
Selects:
USB if USB_ARCH_HAS_HCD (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:302
Say Y here if you want to use a Keyspan DMR USB remote control.
Currently only the UIA-11 type of receiver has been tested. The tag
on the receiver that connects to the USB port should have a P/N that
will tell you what type of DMR you have. The UIA-10 type is not
supported at this time. This driver maps all buttons to keypress
events.
To compile this driver as a module, choose M here: the module will
be called keyspan_remote.
Symbol INPUT_KXTJ9
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Kionix KXTJ9 tri-axis digital accelerometer" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:317
Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
accelerometer.
To compile this driver as a module, choose M here: the module will
be called kxtj9.
Symbol INPUT_POWERMATE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Griffin PowerMate and Contour Jog support" if USB_ARCH_HAS_HCD (value: "y")
Default values:
(no default values)
Selects:
USB if USB_ARCH_HAS_HCD (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:334
Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
These are aluminum dials which can measure clockwise and anticlockwise
rotation. The dial also acts as a pushbutton. The base contains an LED
which can be instructed to pulse or to switch to a particular intensity.
You can download userspace tools from
<http://sowerbutts.com/powermate/>.
To compile this driver as a module, choose M here: the
module will be called powermate.
Symbol INPUT_YEALINK
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Yealink usb-p1k voip phone" if USB_ARCH_HAS_HCD (value: "y")
Default values:
(no default values)
Selects:
USB if USB_ARCH_HAS_HCD (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:350
Say Y here if you want to enable keyboard and LCD functions of the
Yealink usb-p1k usb phones. The audio part is enabled by the generic
usb sound driver, so you might want to enable that as well.
For information about how to use these additional functions, see
<file:Documentation/input/yealink.txt>.
To compile this driver as a module, choose M here: the module will be
called yealink.
Symbol INPUT_CM109
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"C-Media CM109 USB I/O Controller" if USB_ARCH_HAS_HCD (value: "y")
Default values:
(no default values)
Selects:
USB if USB_ARCH_HAS_HCD (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:365
Say Y here if you want to enable keyboard and buzzer functions of the
C-Media CM109 usb phones. The audio part is enabled by the generic
usb sound driver, so you might want to enable that as well.
To compile this driver as a module, choose M here: the module will be
called cm109.
Symbol INPUT_UINPUT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"User level driver support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:418
Say Y here if you want to support user level drivers for input
subsystem accessible under char device 10:223 - /dev/input/uinput.
To compile this driver as a module, choose M here: the
module will be called uinput.
Symbol INPUT_PCF8574
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PCF8574 Keypad input device" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:452
Say Y here if you want to support a keypad connected via I2C
with a PCF8574.
To compile this driver as a module, choose M here: the
module will be called pcf8574_keypad.
Symbol INPUT_GPIO_ROTARY_ENCODER
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Rotary encoders connected to GPIO pins" if GPIOLIB && GENERIC_GPIO (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:473
Say Y here to add support for rotary encoders connected to GPIO lines.
Check file:Documentation/input/rotary-encoder.txt for more
information.
To compile this driver as a module, choose M here: the
module will be called rotary_encoder.
Symbol INPUT_ADXL34X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices ADXL34x Three-Axis Digital Accelerometer"
Default values:
n (value: "n")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:556
Say Y here if you have a Accelerometer interface using the
ADXL345/6 controller, and your board-specific initialization
code includes that in its table of devices.
This driver can use either I2C or SPI communication to the
ADXL345/6 controller. Select the appropriate method for
your system.
If unsure, say N (but it's safe to say "Y").
To compile this driver as a module, choose M here: the
module will be called adxl34x.
Symbol INPUT_CMA3000
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VTI CMA3000 Tri-axis accelerometer"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:593
Say Y here if you want to use VTI CMA3000_D0x Accelerometer
driver
This driver currently only supports I2C interface to the
controller. Also select the I2C method.
If unsure, say N
To compile this driver as a module, choose M here: the
module will be called cma3000_d0x.
Symbol INPUT_XEN_KBDDEV_FRONTEND
Type : tristate
Value : "y"
User value : "y"
Xen config : 'm'
Main config : 'n'
Visibility : "y"
Device Drivers
Input device support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Xen virtual keyboard and mouse support" if XEN (value: "y")
Default values:
y (value: "y")
Condition: XEN (value: "y")
Selects:
XEN_XENBUS_FRONTEND if XEN (value: "y")
Reverse dependencies:
FB && XEN && HAS_IOMEM && XEN_FBDEV_FRONTEND (value: "m")
Additional dependencies from enclosing menus and if's:
INPUT && !UML && INPUT_MISC (value: "y")
Locations: ../drivers/input/misc/Kconfig:617
This driver implements the front-end of the Xen virtual
keyboard and mouse device driver. It communicates with a back-end
in another domain.
To compile this driver as a module, choose M here: the
module will be called xen-kbdfront.
Symbol SERIO
Type : tristate
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Input device support
Hardware I/O ports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Serial I/O support" if EXPERT || !X86 (value: "y")
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
INPUT && !UML && INPUT_KEYBOARD && KEYBOARD_ATKBD || INPUT && !UML && INPUT_KEYBOARD && KEYBOARD_LKKBD || INPUT && !UML && INPUT_KEYBOARD && (GSC || HP300) && KEYBOARD_HIL || INPUT && !UML && INPUT_KEYBOARD && KEYBOARD_NEWTON || INPUT && !UML && INPUT_KEYBOARD && KEYBOARD_STOWAWAY || INPUT && !UML && INPUT_KEYBOARD && KEYBOARD_SUNKBD || INPUT && !UML && INPUT_KEYBOARD && KEYBOARD_XTKBD || INPUT && !UML && INPUT_MOUSE && MOUSE_PS2 || INPUT && !UML && INPUT_MOUSE && MOUSE_SERIAL || INPUT && !UML && INPUT_MOUSE && MOUSE_VSXXXAA || INPUT && !UML && INPUT_JOYSTICK && JOYSTICK_WARRIOR || INPUT && !UML && INPUT_JOYSTICK && JOYSTICK_MAGELLAN || INPUT && !UML && INPUT_JOYSTICK && JOYSTICK_SPACEORB || INPUT && !UML && INPUT_JOYSTICK && JOYSTICK_SPACEBALL || INPUT && !UML && INPUT_JOYSTICK && JOYSTICK_STINGER || INPUT && !UML && INPUT_JOYSTICK && JOYSTICK_TWIDJOY || INPUT && !UML && INPUT_JOYSTICK && JOYSTICK_ZHENHUA || INPUT && !UML && INPUT_TOUCHSCREEN && TOUCHSCREEN_DYNAPRO || INPUT && !UML && INPUT_TOUCHSCREEN && TOUCHSCREEN_HAMPSHIRE || INPUT && !UML && INPUT_TOUCHSCREEN && TOUCHSCREEN_FUJITSU || INPUT && !UML && INPUT_TOUCHSCREEN && TOUCHSCREEN_GUNZE || INPUT && !UML && INPUT_TOUCHSCREEN && TOUCHSCREEN_ELO || INPUT && !UML && INPUT_TOUCHSCREEN && TOUCHSCREEN_WACOM_W8001 || INPUT && !UML && INPUT_TOUCHSCREEN && TOUCHSCREEN_MTOUCH || INPUT && !UML && INPUT_TOUCHSCREEN && TOUCHSCREEN_INEXIO || INPUT && !UML && INPUT_TOUCHSCREEN && TOUCHSCREEN_PENMOUNT || INPUT && !UML && INPUT_TOUCHSCREEN && TOUCHSCREEN_TOUCHRIGHT || INPUT && !UML && INPUT_TOUCHSCREEN && TOUCHSCREEN_TOUCHWIN || INPUT && !UML && INPUT_TOUCHSCREEN && TOUCHSCREEN_TOUCHIT213 || INPUT && !UML && INPUT_TOUCHSCREEN && TOUCHSCREEN_TSC_SERIO || HAS_IOMEM && I2C && TTY && I2C_TAOS_EVM (value: "y")
Additional dependencies from enclosing menus and if's:
!UML (value: "y")
Locations: ../drivers/input/serio/Kconfig:4
Say Yes here if you have any input device that uses serial I/O to
communicate with the system. This includes the
* standard AT keyboard and PS/2 mouse *
as well as serial mice, Sun keyboards, some joysticks and 6dof
devices and more.
If unsure, say Y.
To compile this driver as a module, choose M here: the
module will be called serio.
Symbol SERIO_SERPORT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Hardware I/O ports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Serial port line discipline" if TTY (value: "y")
Default values:
y (value: "y")
Condition: TTY (value: "y")
Selects:
(no selects)
Reverse dependencies:
HAS_IOMEM && I2C && TTY && I2C_TAOS_EVM (value: "n")
Additional dependencies from enclosing menus and if's:
SERIO && !UML (value: "y")
Locations: ../drivers/input/serio/Kconfig:35
Say Y here if you plan to use an input device (mouse, joystick,
tablet, 6dof) that communicates over the RS232 serial (COM) port.
More information is available: <file:Documentation/input/input.txt>
If unsure, say Y.
To compile this driver as a module, choose M here: the
module will be called serport.
Symbol SERIO_CT82C710
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Hardware I/O ports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ct82c710 Aux port controller" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SERIO && !UML (value: "y")
Locations: ../drivers/input/serio/Kconfig:50
Say Y here if you have a Texas Instruments TravelMate notebook
equipped with the ct82c710 chip and want to use a mouse connected
to the "QuickPort".
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called ct82c710.
Symbol SERIO_PARKBD
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Input device support
Hardware I/O ports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Parallel port keyboard adapter" if PARPORT (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SERIO && !UML (value: "y")
Locations: ../drivers/input/serio/Kconfig:67
Say Y here if you built a simple parallel port adapter to attach
an additional AT keyboard, XT keyboard or PS/2 mouse.
More information is available: <file:Documentation/input/input.txt>
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called parkbd.
Symbol SERIO_PCIPS2
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Hardware I/O ports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PCI PS/2 keyboard and PS/2 mouse controller" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SERIO && !UML (value: "y")
Locations: ../drivers/input/serio/Kconfig:150
Say Y here if you have a Mobility Docking station with PS/2
keyboard and mice ports.
To compile this driver as a module, choose M here: the
module will be called pcips2.
Symbol SERIO_RAW
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Hardware I/O ports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Raw access to serio ports"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SERIO && !UML (value: "y")
Locations: ../drivers/input/serio/Kconfig:180
Say Y here if you want to have raw access to serio ports, such as
AUX ports on i8042 keyboard controller. Each serio port that is
bound to this driver will be accessible via a char device with
major 10 and dynamically allocated minor. The driver will try
allocating minor 1 (that historically corresponds to /dev/psaux)
first. To bind this driver to a serio port use sysfs interface:
echo -n "serio_raw" > /sys/bus/serio/devices/serioX/drvctl
To compile this driver as a module, choose M here: the
module will be called serio_raw.
Symbol SERIO_ALTERA_PS2
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Hardware I/O ports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Altera UP PS/2 controller"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SERIO && !UML (value: "y")
Locations: ../drivers/input/serio/Kconfig:205
Say Y here if you have Altera University Program PS/2 ports.
To compile this driver as a module, choose M here: the
module will be called altera_ps2.
Symbol SERIO_PS2MULT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Input device support
Hardware I/O ports
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"TQC PS/2 multiplexer"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
SERIO && !UML (value: "y")
Locations: ../drivers/input/serio/Kconfig:228
Say Y here if you have the PS/2 line multiplexer like the one
present on TQC boards.
To compile this driver as a module, choose M here: the
module will be called ps2mult.
Symbol SERIAL_NONSTANDARD
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Non-standard serial port support" if HAS_IOMEM (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
METAG_DA && TTY && DA_TTY (value: "n")
Additional dependencies from enclosing menus and if's:
TTY (value: "y")
Locations: ../drivers/tty/Kconfig:178
Say Y here if you have any non-standard serial boards -- boards
which aren't supported using the standard "dumb" serial driver.
This includes intelligent serial boards such as Cyclades,
Digiboards, etc. These are usually used for systems that need many
serial ports because they serve many terminals or dial-in
connections.
Note that the answer to this question won't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about non-standard serial boards.
Most people can say N here.
Symbol NOZOMI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"HSDPA Broadband Wireless Data Card - Globe Trotter" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
TTY (value: "y")
Locations: ../drivers/tty/Kconfig:297
If you have a HSDPA driver Broadband Wireless Data Card -
Globe Trotter PCMCIA card, say Y here.
To compile this driver as a module, choose M here, the module
will be called nozomi.
Symbol SERIAL_8250_DEPRECATED_OPTIONS
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'n'
Visibility : "y"
Device Drivers
Character devices
Serial drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support 8250_core.* kernel options (DEPRECATED)" if SERIAL_8250 (value: "y")
Default values:
y (value: "y")
Condition: SERIAL_8250 (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && GENERIC_HARDIRQS && TTY (value: "y")
Locations: ../drivers/tty/serial/8250/Kconfig:36
In 3.7 we renamed 8250 to 8250_core by mistake, so now we have to
accept kernel parameters in both forms like 8250_core.nr_uarts=4 and
8250.nr_uarts=4. We now renamed the module back to 8250, but if
anybody noticed in 3.7 and changed their userspace we still have to
keep the 8350_core.* options around until they revert the changes
they already did.
If 8250 is built as a module, this adds 8250_core alias instead.
If you did not notice yet and/or you have userspace from pre-3.7, it
is safe (and recommended) to say N here.
Symbol SERIAL_8250_PNP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Character devices
Serial drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"8250/16550 PNP device support" if SERIAL_8250 && PNP && EXPERT (value: "y")
Default values:
y (value: "y")
Condition: SERIAL_8250 && PNP (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && GENERIC_HARDIRQS && TTY (value: "y")
Locations: ../drivers/tty/serial/8250/Kconfig:53
This builds standard PNP serial support. You may be able to
disable this feature if you only need legacy serial support.
Symbol SERIAL_ARC
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Character devices
Serial drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ARC UART driver support"
Default values:
(no default values)
Selects:
SERIAL_CORE
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && GENERIC_HARDIRQS && TTY (value: "y")
Locations: ../drivers/tty/serial/Kconfig:1440
Driver for on-chip UART for ARC(Synopsys) for the legacy
FPGA Boards (ML50x/ARCAngel4)
Symbol PRINTER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Parallel printer support" if PARPORT (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/Kconfig:98
If you intend to attach a printer to the parallel port of your Linux
box (as opposed to using a serial printer; if the connector at the
printer has 9 or 25 holes ["female"], then it's serial), say Y.
Also read the Printing-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
It is possible to share one parallel port among several devices
(e.g. printer and ZIP drive) and it is safe to compile the
corresponding drivers into the kernel.
To compile this driver as a module, choose M here and read
<file:Documentation/parport.txt>. The module will be called lp.
If you have several parallel ports, you can specify which ports to
use with the "lp" kernel command line option. (Try "man bootparam"
or see the documentation of your boot loader (lilo or loadlin) about
how to pass options to the kernel at boot time.) The syntax of the
"lp" command line option can be found in <file:drivers/char/lp.c>.
If you have more than 8 printers, you need to increase the LP_NO
macro in lp.c and the PARPORT_MAX macro in parport.h.
Symbol PPDEV
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Support for user-space parallel port device drivers" if PARPORT (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/Kconfig:141
Saying Y to this adds support for /dev/parport device nodes. This
is needed for programs that want portable access to the parallel
port, for instance deviceid (which displays Plug-and-Play device
IDs).
This is the parallel port equivalent of SCSI generic support (sg).
It is safe to say N to this -- it is not needed for normal printing
or parallel port CD-ROM/disk support.
To compile this driver as a module, choose M here: the
module will be called ppdev.
If unsure, say N.
Symbol HVC_XEN
Type : bool
Value : "y"
User value : "y"
Xen config : 'y'
Main config : 'n'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Xen Hypervisor Console support" if XEN (value: "y")
Default values:
y (value: "y")
Condition: XEN (value: "y")
Selects:
HVC_DRIVER if XEN (value: "y")
HVC_IRQ if XEN (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
TTY (value: "y")
Locations: ../drivers/tty/hvc/Kconfig:62
Xen virtual console device driver
Symbol HVC_XEN_FRONTEND
Type : bool
Value : "y"
User value : "y"
Xen config : 'y'
Main config : 'n'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Xen Hypervisor Multiple Consoles support" if HVC_XEN (value: "y")
Default values:
y (value: "y")
Condition: HVC_XEN (value: "y")
Selects:
XEN_XENBUS_FRONTEND if HVC_XEN (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
TTY (value: "y")
Locations: ../drivers/tty/hvc/Kconfig:71
Xen driver for secondary virtual consoles
Symbol VIRTIO_CONSOLE
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Virtio console" if VIRTIO && TTY (value: "m")
Default values:
(no default values)
Selects:
HVC_DRIVER if VIRTIO && TTY (value: "m")
Reverse dependencies:
X86_32 && PARAVIRT_GUEST && LGUEST_GUEST (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/Kconfig:161
Virtio console for use with lguest and other hypervisors.
Also serves as a general-purpose serial device for data
transfer between the guest and host. Character devices at
/dev/vportNpn will be created when corresponding ports are
found, where N is the device number and n is the port number
within that device. If specified by the host, a sysfs
attribute called 'name' will be populated with a name for
the port which can be used by udev scripts to create a
symlink to the device.
Symbol IPMI_HANDLER
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IPMI top-level message handler" if HAS_IOMEM (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/ipmi/Kconfig:5
This enables the central IPMI message handler, required for IPMI
to work.
IPMI is a standard for managing sensors (temperature,
voltage, etc.) in a system.
See <file:Documentation/IPMI.txt> for more details on the driver.
If unsure, say N.
Symbol HW_RANDOM_TIMERIOMEM
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "m"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Timer IOMEM HW Random Number Generator support" if HW_RANDOM && HAS_IOMEM (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/hw_random/Kconfig:23
This driver provides kernel-side support for a generic Random
Number Generator used by reading a 'dumb' iomem address that
is to be read no faster than, for example, once a second;
the default FPGA bitstream on the TS-7800 has such functionality.
To compile this driver as a module, choose M here: the
module will be called timeriomem-rng.
If unsure, say Y.
Symbol HW_RANDOM_INTEL
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "m"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel HW Random Number Generator support" if HW_RANDOM && (X86 || IA64) && PCI (value: "m")
Default values:
HW_RANDOM (value: "m")
Condition: HW_RANDOM && (X86 || IA64) && PCI (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/hw_random/Kconfig:37
This driver provides kernel-side support for the Random Number
Generator hardware found on Intel i8xx-based motherboards.
To compile this driver as a module, choose M here: the
module will be called intel-rng.
If unsure, say Y.
Symbol HW_RANDOM_AMD
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "m"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD HW Random Number Generator support" if HW_RANDOM && (X86 || PPC_MAPLE) && PCI (value: "m")
Default values:
HW_RANDOM (value: "m")
Condition: HW_RANDOM && (X86 || PPC_MAPLE) && PCI (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/hw_random/Kconfig:50
This driver provides kernel-side support for the Random Number
Generator hardware found on AMD 76x-based motherboards.
To compile this driver as a module, choose M here: the
module will be called amd-rng.
If unsure, say Y.
Symbol HW_RANDOM_GEODE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "m"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD Geode HW Random Number Generator support" if HW_RANDOM && X86_32 && PCI (value: "m")
Default values:
HW_RANDOM (value: "m")
Condition: HW_RANDOM && X86_32 && PCI (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/hw_random/Kconfig:90
This driver provides kernel-side support for the Random Number
Generator hardware found on the AMD Geode LX.
To compile this driver as a module, choose M here: the
module will be called geode-rng.
If unsure, say Y.
Symbol HW_RANDOM_VIA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "m"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VIA HW Random Number Generator support" if HW_RANDOM && X86 (value: "m")
Default values:
HW_RANDOM (value: "m")
Condition: HW_RANDOM && X86 (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/hw_random/Kconfig:116
This driver provides kernel-side support for the Random Number
Generator hardware found on VIA based motherboards.
To compile this driver as a module, choose M here: the
module will be called via-rng.
If unsure, say Y.
Symbol NVRAM
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"/dev/nvram support" if ATARI || X86 || ARM && RTC_DRV_CMOS || GENERIC_NVRAM (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
ATARI && SCSI && SCSI_LOWLEVEL && SCSI && ATARI_SCSI || ACPI && INPUT && (RFKILL || RFKILL = n) && X86_PLATFORM_DEVICES && X86 && THINKPAD_ACPI (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/Kconfig:252
If you say Y here and create a character special file /dev/nvram
with major number 10 and minor number 144 using mknod ("man mknod"),
you get read and write access to the extra bytes of non-volatile
memory in the real time clock (RTC), which is contained in every PC
and most Ataris. The actual number of bytes varies, depending on the
nvram in the system, but is usually 114 (128-14 for the RTC).
This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
on Ataris. /dev/nvram may be used to view settings there, or to
change them (with some utility). It could also be used to frequently
save a few bits of very important data that may not be lost over
power-off and for which writing to disk is too insecure. Note
however that most NVRAM space in a PC belongs to the BIOS and you
should NEVER idly tamper with it. See Ralf Brown's interrupt list
for a guide to the use of CMOS bytes by your BIOS.
On Atari machines, /dev/nvram is always configured and does not need
to be selected.
To compile this driver as a module, choose M here: the
module will be called nvram.
Symbol R3964
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Siemens R3964 line discipline" if TTY (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/Kconfig:393
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.
Symbol APPLICOM
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Applicom intelligent fieldbus card support" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/Kconfig:406
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.
Symbol MWAVE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ACP Modem (Mwave) support" if X86 && TTY (value: "y")
Default values:
(no default values)
Selects:
SERIAL_8250 if X86 && TTY (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/Kconfig:441
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.
Symbol RAW_DRIVER
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RAW driver (/dev/raw/rawN)" if BLOCK (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/Kconfig:500
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.
Applications should preferably open the device (eg /dev/hda1)
with the O_DIRECT flag.
Symbol HPET
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"HPET - High Precision Event Timer" if (X86 || IA64) && ACPI (value: "y")
Default values:
n (value: "n")
Condition: ACPI (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/Kconfig:520
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-periodic and/or periodic.
Symbol HPET_MMAP
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Allow mmap of HPET" if HPET (value: "y")
Default values:
y (value: "y")
Condition: HPET (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/Kconfig:529
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.
Symbol TCG_TPM
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"TPM Hardware Support" if HAS_IOMEM (value: "y")
Default values:
(no default values)
Selects:
SECURITYFS if HAS_IOMEM (value: "y")
Reverse dependencies:
HAS_IOMEM && !UML && SECURITY && IMA (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/tpm/Kconfig:5
If you have a TPM security chip in your system, which
implements the Trusted Computing Group's specification,
say Yes and it will be accessible from within Linux. For
more information see <http://www.trustedcomputinggroup.org>.
An implementation of the Trusted Software Stack (TSS), the
userspace enablement piece of the specification, can be
obtained at: <http://sourceforge.net/projects/trousers>. To
compile this driver as a module, choose M here; the module
will be called tpm. If unsure, say N.
Notes:
1) For more TPM drivers enable CONFIG_PNP, CONFIG_ACPI
and CONFIG_PNPACPI.
2) Without ACPI enabled, the BIOS event log won't be accessible,
which is required to validate the PCR 0-7 values.
Symbol TELCLOCK
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Character devices
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Telecom clock driver for ATCA SBC" if X86 (value: "y")
Default values:
n (value: "n")
Condition: X86 (value: "y")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/char/Kconfig:568
The telecom clock device is specific to the MPCBL0010 and MPCBL0050
ATCA computers and allows direct userspace access to the
configuration of the telecom clock configuration settings. This
device is used for hardware synchronization across the ATCA backplane
fabric. Upon loading, the driver exports a sysfs directory,
/sys/devices/platform/telco_clock, with a number of files for
controlling the behavior of this hardware.
Symbol I2C
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"I2C support"
Default values:
(no default values)
Selects:
RT_MUTEXES
Reverse dependencies:
PCI && PCI_GOANY && X86_IO_APIC && X86_WANT_INTEL_MID && X86_MDFLD || CAN && NET && CAN_DEV && CAN_SJA1000 && CAN_PEAK_PCI && CAN_PEAK_PCIEC || ETHERNET && NETDEVICES && NET_VENDOR_INTEL && PCI && IGB || ETHERNET && NETDEVICES && PCI && SFC || (AGP || AGP = n) && !EMULATED_CMPXCHG && MMU && HAS_IOMEM && DRM || FB && HAS_IOMEM && FB_DDC || FB && BLACKFIN && HAS_IOMEM && FB_BFIN_7393 || FB && PCI && X86 && HAS_IOMEM && FB_VIA || !M68K && !UML && SOUND && SND && SND_AOA && SND_AOA_ONYX || !M68K && !UML && SOUND && SND && SND_AOA && SND_AOA_TAS || !M68K && !UML && SOUND && SND && SND_SOC && SND_BF5XX_I2S && SND_SOC_BFIN_EVAL_ADAU1701 || OLPC && FB && STAGING && FB_OLPC_DCON (value: "m")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/i2c/Kconfig:5
I2C (pronounce: I-squared-C) is a slow serial bus protocol used in
many micro controller applications and developed by Philips. SMBus,
or System Management Bus is a subset of the I2C protocol. More
information is contained in the directory <file:Documentation/i2c/>,
especially in the file called "summary" there.
Both I2C and SMBus are supported here. You will need this for
hardware sensors support, and also for Video For Linux support.
If you want I2C support, you should say Y here and also to the
specific driver for your bus adapter(s) below.
This I2C support can also be built as a module. If so, the module
will be called i2c-core.
Symbol I2C_COMPAT
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Enable compatibility bits for old user-space"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2C (value: "m")
Locations: ../drivers/i2c/Kconfig:30
Say Y here if you intend to run lm-sensors 3.1.1 or older, or any
other user-space package which expects i2c adapters to be class
devices. If you don't know, say Y.
Symbol I2C_CHARDEV
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"I2C device interface"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2C (value: "m")
Locations: ../drivers/i2c/Kconfig:38
Say Y here to use i2c-* device files, usually found in the /dev
directory on your system. They make it possible to have user-space
programs use the I2C bus. Information on how to do this is
contained in the file <file:Documentation/i2c/dev-interface>.
This support is also available as a module. If so, the module
will be called i2c-dev.
Symbol I2C_MUX
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"I2C bus multiplexing support" if HAS_IOMEM (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2C (value: "m")
Locations: ../drivers/i2c/Kconfig:49
Say Y here if you want the I2C core to support the ability to
handle multiplexed I2C bus topologies, by presenting each
multiplexed segment as a I2C adapter.
This support is also available as a module. If so, the module
will be called i2c-mux.
Symbol I2C_MUX_GPIO
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Multiplexer I2C Chip support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"GPIO-based I2C multiplexer" if GENERIC_GPIO (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2C_MUX && I2C (value: "m")
Locations: ../drivers/i2c/muxes/Kconfig:8
If you say yes to this option, support will be included for a
GPIO based I2C multiplexer. This driver provides access to
I2C busses connected through a MUX, which is controlled
through GPIO pins.
This driver can also be built as a module. If so, the module
will be called i2c-mux-gpio.
Symbol I2C_MUX_PCA9541
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Multiplexer I2C Chip support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"NXP PCA9541 I2C Master Selector"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2C_MUX && I2C (value: "m")
Locations: ../drivers/i2c/muxes/Kconfig:20
If you say yes here you get support for the NXP PCA9541
I2C Master Selector.
This driver can also be built as a module. If so, the module
will be called i2c-mux-pca9541.
Symbol I2C_MUX_PCA954x
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Multiplexer I2C Chip support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Philips PCA954x I2C Mux/switches"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2C_MUX && I2C (value: "m")
Locations: ../drivers/i2c/muxes/Kconfig:29
If you say yes here you get support for the Philips PCA954x
I2C mux/switch devices.
This driver can also be built as a module. If so, the module
will be called i2c-mux-pca954x.
Symbol I2C_HELPER_AUTO
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Autoselect pertinent helper modules"
Default values:
y (value: "y")
Condition: (none)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2C (value: "m")
Locations: ../drivers/i2c/Kconfig:62
Some I2C bus drivers require so-called "I2C algorithm" modules
to work. These are basically software-only abstractions of generic
I2C interfaces. This option will autoselect them so that you don't
have to care.
Unselect this only if you need to enable additional helper
modules, for example for use with external I2C bus drivers.
In doubt, say Y.
Symbol I2C_ALI1535
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ALI 1535" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:11
If you say yes to this option, support will be included for the SMB
Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
controller is part of the 7101 device, which is an ACPI-compliant
Power Management Unit (PMU).
This driver can also be built as a module. If so, the module
will be called i2c-ali1535.
Symbol I2C_ALI1563
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ALI 1563" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:23
If you say yes to this option, support will be included for the SMB
Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
controller is part of the 7101 device, which is an ACPI-compliant
Power Management Unit (PMU).
This driver can also be built as a module. If so, the module
will be called i2c-ali1563.
Symbol I2C_ALI15X3
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ALI 15x3" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:35
If you say yes to this option, support will be included for the
Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
This driver can also be built as a module. If so, the module
will be called i2c-ali15x3.
Symbol I2C_AMD756
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD 756/766/768/8111 and nVidia nForce" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:45
If you say yes to this option, support will be included for the AMD
756/766/768 mainboard I2C interfaces. The driver also includes
support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
the nVidia nForce I2C interface.
This driver can also be built as a module. If so, the module
will be called i2c-amd756.
Symbol I2C_AMD8111
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD 8111" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:70
If you say yes to this option, support will be included for the
second (SMBus 2.0) AMD 8111 mainboard I2C interface.
This driver can also be built as a module. If so, the module
will be called i2c-amd8111.
Symbol I2C_I801
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel 82801 (ICH/PCH)" if PCI (value: "y")
Default values:
(no default values)
Selects:
CHECK_SIGNATURE if X86 && DMI && PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:80
If you say yes to this option, support will be included for the Intel
801 family of mainboard I2C interfaces. Specifically, the following
versions of the chipset are supported:
82801AA
82801AB
82801BA
82801CA/CAM
82801DB
82801EB/ER (ICH5/ICH5R)
6300ESB
ICH6
ICH7
ESB2
ICH8
ICH9
EP80579 (Tolapai)
ICH10
5/3400 Series (PCH)
6 Series (PCH)
Patsburg (PCH)
DH89xxCC (PCH)
Panther Point (PCH)
Lynx Point (PCH)
Lynx Point-LP (PCH)
Avoton (SOC)
Wellsburg (PCH)
This driver can also be built as a module. If so, the module
will be called i2c-i801.
Symbol I2C_ISCH
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel SCH SMBus 1.0" if PCI && GENERIC_HARDIRQS (value: "y")
Default values:
(no default values)
Selects:
LPC_SCH if PCI && GENERIC_HARDIRQS (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:115
Say Y here if you want to use SMBus controller on the Intel SCH
based systems.
This driver can also be built as a module. If so, the module
will be called i2c-isch.
Symbol I2C_ISMT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel iSMT SMBus Controller" if PCI && X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:126
If you say yes to this option, support will be included for the Intel
iSMT SMBus host controller interface.
This driver can also be built as a module. If so, the module will be
called i2c-ismt.
Symbol I2C_PIIX4
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:136
If you say yes to this option, support will be included for the Intel
PIIX4 family of mainboard I2C interfaces. Specifically, the following
versions of the chipset are supported (note that Serverworks is part
of Broadcom):
Intel PIIX4
Intel 440MX
ATI IXP200
ATI IXP300
ATI IXP400
ATI SB600
ATI SB700/SP5100
ATI SB800
AMD Hudson-2
Serverworks OSB4
Serverworks CSB5
Serverworks CSB6
Serverworks HT-1000
Serverworks HT-1100
SMSC Victory66
Some AMD chipsets contain two PIIX4-compatible SMBus
controllers. This driver will attempt to use both controllers
on the SB700/SP5100, if they have been initialized by the BIOS.
This driver can also be built as a module. If so, the module
will be called i2c-piix4.
Symbol I2C_NFORCE2
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Nvidia nForce2, nForce3 and nForce4" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:167
If you say yes to this option, support will be included for the Nvidia
nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
This driver can also be built as a module. If so, the module
will be called i2c-nforce2.
Symbol I2C_SIS5595
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SiS 5595" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:190
If you say yes to this option, support will be included for the
SiS5595 SMBus (a subset of I2C) interface.
This driver can also be built as a module. If so, the module
will be called i2c-sis5595.
Symbol I2C_SIS630
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SiS 630/730/964" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:200
If you say yes to this option, support will be included for the
SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
This driver can also be built as a module. If so, the module
will be called i2c-sis630.
Symbol I2C_SIS96X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SiS 96x" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:210
If you say yes to this option, support will be included for the SiS
96x SMBus (a subset of I2C) interfaces. Specifically, the following
chipsets are supported:
645/961
645DX/961
645DX/962
648/961
650/961
735
745
This driver can also be built as a module. If so, the module
will be called i2c-sis96x.
Symbol I2C_VIA
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VIA VT82C586B" if PCI (value: "y")
Default values:
(no default values)
Selects:
I2C_ALGOBIT if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:228
If you say yes to this option, support will be included for the VIA
82C586B I2C interface
This driver can also be built as a module. If so, the module
will be called i2c-via.
Symbol I2C_VIAPRO
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:239
If you say yes to this option, support will be included for the VIA
VT82C596 and later SMBus interface. Specifically, the following
chipsets are supported:
VT82C596A/B
VT82C686A/B
VT8231
VT8233/A
VT8235
VT8237R/A/S
VT8251
CX700
VX800/VX820
VX855/VX875
VX900
This driver can also be built as a module. If so, the module
will be called i2c-viapro.
Symbol I2C_SCMI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SMBus Control Method Interface"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C && ACPI (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:265
This driver supports the SMBus Control Method Interface. It needs the
BIOS to declare ACPI control methods as described in the SMBus Control
Method Interface specification.
To compile this driver as a module, choose M here:
the module will be called i2c-scmi.
Symbol I2C_EG20T
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:422
This driver is for PCH(Platform controller Hub) I2C of EG20T which
is an IOH(Input/Output Hub) for x86 embedded processor.
This driver can access PCH I2C bus device.
This driver also can be used for LAPIS Semiconductor IOH(Input/
Output Hub), ML7213, ML7223 and ML7831.
ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
for MP(Media Phone) use and ML7831 IOH is for general purpose use.
ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
Symbol I2C_GPIO
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"GPIO-based bitbanging I2C" if GENERIC_GPIO (value: "y")
Default values:
(no default values)
Selects:
I2C_ALGOBIT if GENERIC_GPIO (value: "y")
Reverse dependencies:
ARCH_MMP && I2C && VIDEO_V4L2 && V4L_PLATFORM_DRIVERS && MEDIA_SUPPORT && VIDEO_MMP_CAMERA (value: "n")
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:437
This is a very simple bitbanging I2C driver utilizing the
arch-neutral GPIO API to control the SCL and SDA lines.
Symbol I2C_INTEL_MID
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel Moorestown/Medfield Platform I2C controller" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:477
Say Y here if you have an Intel Moorestown/Medfield platform I2C
controller.
This support is also available as a module. If so, the module
will be called i2c-intel-mid.
Symbol I2C_OCORES
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"OpenCores I2C Controller" if GENERIC_HARDIRQS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:544
If you say yes to this option, support will be included for the
OpenCores I2C controller. For details see
http://www.opencores.org/projects.cgi/web/i2c/overview
This driver can also be built as a module. If so, the module
will be called i2c-ocores.
Symbol I2C_PCA_PLATFORM
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PCA9564/PCA9665 as platform device"
Default values:
n (value: "n")
Condition: (none)
Selects:
I2C_ALGOPCA
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:571
This driver supports a memory mapped Philips PCA9564/PCA9665
parallel bus to I2C bus controller.
This driver can also be built as a module. If so, the module
will be called i2c-pca-platform.
Symbol I2C_SIMTEC
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Simtec Generic I2C interface"
Default values:
(no default values)
Selects:
I2C_ALGOBIT
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:674
If you say yes to this option, support will be included for
the Simtec Generic I2C interface. This driver is for the
simple I2C bus used on newer Simtec products for general
I2C, such as DDC on the Simtec BBD2016A.
This driver can also be built as a module. If so, the module
will be called i2c-simtec.
Symbol I2C_XILINX
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Xilinx I2C Controller" if HAS_IOMEM (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:737
If you say yes to this option, support will be included for the
Xilinx I2C controller.
This driver can also be built as a module. If so, the module
will be called xilinx_i2c.
Symbol I2C_DIOLAN_U2C
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Diolan U2C-12 USB adapter" if USB (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:769
If you say yes to this option, support will be included for Diolan
U2C-12, a USB to I2C interface.
This driver can also be built as a module. If so, the module
will be called i2c-diolan-u2c.
Symbol I2C_PARPORT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Parallel port adapter" if PARPORT && GENERIC_HARDIRQS (value: "m")
Default values:
(no default values)
Selects:
I2C_ALGOBIT if PARPORT && GENERIC_HARDIRQS (value: "m")
I2C_SMBUS if PARPORT && GENERIC_HARDIRQS (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:779
This supports parallel port I2C adapters such as the ones made by
Philips or Velleman, Analog Devices evaluation boards, and more.
Basically any adapter using the parallel port as an I2C bus with
no extra chipset is supported by this driver, or could be.
This driver is a replacement for (and was inspired by) an older
driver named i2c-philips-par. The new driver supports more devices,
and makes it easier to add support for new devices.
An adapter type parameter is now mandatory. Please read the file
Documentation/i2c/busses/i2c-parport for details.
Another driver exists, named i2c-parport-light, which doesn't depend
on the parport driver. This is meant for embedded systems. Don't say
Y here if you intend to say Y or M there.
This support is also available as a module. If so, the module
will be called i2c-parport.
Symbol I2C_PARPORT_LIGHT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Parallel port adapter (light)" if GENERIC_HARDIRQS (value: "y")
Default values:
(no default values)
Selects:
I2C_ALGOBIT if GENERIC_HARDIRQS (value: "y")
I2C_SMBUS if GENERIC_HARDIRQS (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:804
This supports parallel port I2C adapters such as the ones made by
Philips or Velleman, Analog Devices evaluation boards, and more.
Basically any adapter using the parallel port as an I2C bus with
no extra chipset is supported by this driver, or could be.
This driver is a light version of i2c-parport. It doesn't depend
on the parport driver, and uses direct I/O access instead. This
might be preferred on embedded systems where wasting memory for
the clean but heavy parport handling is not an option. The
drawback is a reduced portability and the impossibility to
daisy-chain other parallel port devices.
Don't say Y here if you said Y or M to i2c-parport. Saying M to
both is possible but both modules should not be loaded at the same
time.
This support is also available as a module. If so, the module
will be called i2c-parport-light.
Symbol I2C_TAOS_EVM
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"TAOS evaluation module" if TTY (value: "y")
Default values:
n (value: "n")
Condition: TTY (value: "y")
Selects:
SERIO if TTY (value: "y")
SERIO_SERPORT if TTY (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:829
This supports TAOS evaluation modules on serial port. In order to
use this driver, you will need the inputattach tool, which is part
of the input-utils package.
If unsure, say N.
This support is also available as a module. If so, the module
will be called i2c-taos-evm.
Symbol I2C_TINY_USB
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
I2C Hardware Bus support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Tiny-USB adapter" if USB (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HAS_IOMEM && I2C (value: "m")
Locations: ../drivers/i2c/busses/Kconfig:845
If you say yes to this option, support will be included for the
i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
This driver can also be built as a module. If so, the module
will be called i2c-tiny-usb.
Symbol I2C_STUB
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"I2C/SMBus Test Stub" if "m" && MODULES (value: "m")
Default values:
"n" (value: "n")
Condition: "m" && MODULES (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
I2C (value: "m")
Locations: ../drivers/i2c/Kconfig:90
This module may be useful to developers of SMBus client drivers,
especially for certain kinds of sensor chips.
If you do build this module, be sure to read the notes and warnings
in <file:Documentation/i2c/i2c-stub>.
If you don't know what to do here, definitely say N.
Symbol SPI
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SPI support" if HAS_IOMEM (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
PCI && PCI_GOANY && X86_IO_APIC && X86_WANT_INTEL_MID && X86_MDFLD (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/spi/Kconfig:8
The "Serial Peripheral Interface" is a low level synchronous
protocol. Chips that support SPI can have data transfer rates
up to several tens of Mbit/sec. Chips are addressed with a
controller and a chipselect. Most SPI slaves don't support
dynamic device discovery; some are even write-only or read-only.
SPI is widely used by microcontrollers to talk with sensors,
eeprom and flash memory, codecs and various other controller
chips, analog to digital (and d-to-a) converters, and more.
MMC and SD cards can be accessed using SPI protocol; and for
DataFlash cards used in MMC sockets, SPI must always be used.
SPI is one of a family of similar protocols using a four wire
interface (select, clock, data in, data out) including Microwire
(half duplex), SSP, SSI, and PSP. This driver framework should
work with most such devices and controllers.
Symbol PPS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
PPS support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PPS support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
PTP_1588_CLOCK (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/pps/Kconfig:7
PPS (Pulse Per Second) is a special pulse provided by some GPS
antennae. Userland can use it to get a high-precision time
reference.
Some antennae's PPS signals are connected with the CD (Carrier
Detect) pin of the serial line they use to communicate with the
host. In this case use the SERIAL_LINE client support.
Some antennae's PPS signals are connected with some special host
inputs so you have to enable the corresponding client support.
To compile this driver as a module, choose M here: the module
will be called pps_core.ko.
Symbol PTP_1588_CLOCK
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
PTP clock support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PTP clock support"
Default values:
(no default values)
Selects:
PPS
Reverse dependencies:
BFIN_MAC && BF518 && ETHERNET && NETDEVICES && NET_BFIN && BFIN_MAC_USE_HWSTAMP || ETHERNET && NETDEVICES && NET_VENDOR_BROADCOM && PCI && TIGON3 || ETHERNET && NETDEVICES && NET_VENDOR_FREESCALE && (M523x || M527x || M5272 || M528x || M520x || M532x || ARCH_MXC || SOC_IMX28) && FEC || PCI && (!SPARC32 || BROKEN) && ETHERNET && NETDEVICES && NET_VENDOR_INTEL && E1000E || ETHERNET && NETDEVICES && NET_VENDOR_INTEL && PCI && IGB || ETHERNET && NETDEVICES && NET_VENDOR_INTEL && PCI && IXGBE || ETHERNET && NETDEVICES && PCI && SFC || ETHERNET && NETDEVICES && NET_VENDOR_TI && TI_CPSW && TI_CPTS || PTP_1588_CLOCK_GIANFAR && GIANFAR || PTP_1588_CLOCK_IXP46X && IXP4XX_ETH || NETWORK_PHY_TIMESTAMPING && PHYLIB && DP83640_PHY || PTP_1588_CLOCK_PCH (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/ptp/Kconfig:7
The IEEE 1588 standard defines a method to precisely
synchronize distributed clocks over Ethernet networks. The
standard defines a Precision Time Protocol (PTP), which can
be used to achieve synchronization within a few dozen
microseconds. In addition, with the help of special hardware
time stamping units, it can be possible to achieve
synchronization to within a few hundred nanoseconds.
This driver adds support for PTP clocks as character
devices. If you want to use a PTP clock, then you should
also enable at least one clock driver as well.
To compile this driver as a module, choose M here: the module
will be called ptp.
Symbol PTP_1588_CLOCK_PCH
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
PTP clock support
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel PCH EG20T as PTP clock"
Default values:
(no default values)
Selects:
PTP_1588_CLOCK
Reverse dependencies:
ETHERNET && NETDEVICES && NET_VENDOR_OKI && PCI && PCH_GBE (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/ptp/Kconfig:73
This driver adds support for using the PCH EG20T as a PTP
clock. The hardware supports time stamping of PTP packets
when using the end-to-end delay (E2E) mechansim. The peer
delay mechansim (P2P) is not supported.
This clock is only useful if your PTP programs are getting
hardware time stamps on the PTP Ethernet packets using the
SO_TIMESTAMPING API.
To compile this driver as a module, choose M here: the module
will be called ptp_pch.
Symbol GPIOLIB
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"GPIO Support" if ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB (value: "y")
Default values:
(no default values)
Selects:
GENERIC_GPIO if ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB (value: "y")
Reverse dependencies:
!X86_PAE && X86_32 && OLPC || ALIX && X86_32 || NET5501 && X86_32 || DMI && X86_32 && GEOS || ARCH_REQUIRE_GPIOLIB || ARM && HAVE_CLK && HAS_IOMEM && MFD_TC6393XB || FB && PCI && X86 && HAS_IOMEM && FB_VIA (value: "n")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/gpio/Kconfig:38
This enables GPIO support through the generic GPIO library.
You only need to enable this, if you also want to enable
one or more of the GPIO drivers below.
If unsure, say N.
Symbol GPIO_SYSFS
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"/sys/class/gpio/... (sysfs interface)" if SYSFS (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:70
Say Y here to add a sysfs interface for GPIOs.
This is mostly useful to work around omissions in a system's
kernel support. Those are common in custom and semicustom
hardware assembled using standard kernels with a minimum of
custom patches. In those cases, userspace code may import
a given GPIO from the kernel, if no kernel driver requested it.
Kernel drivers may also request that a particular GPIO be
exported to userspace; this can be useful when debugging.
Symbol GPIO_IT8761E
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IT8761E GPIO support" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:122
Say yes here to support GPIO functionality of IT8761E super I/O chip.
Symbol GPIO_SCH
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel SCH/TunnelCreek/Centerton GPIO" if PCI && X86 (value: "y")
Default values:
(no default values)
Selects:
MFD_CORE if PCI && X86 (value: "y")
LPC_SCH if PCI && X86 (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:247
Say yes here to support GPIO interface on Intel Poulsbo SCH,
Intel Tunnel Creek processor or Intel Centerton processor.
The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
powered by the core power rail and are turned off during sleep
modes (S3 and higher). The remaining four GPIOs are powered by
the Intel SCH suspend power supply. These GPIOs remain
active during S3. The suspend powered GPIOs can be used to wake the
system from the Suspend-to-RAM state.
The Intel Tunnel Creek processor has 5 GPIOs powered by the
core power rail and 9 from suspend power supply.
The Intel Centerton processor has a total of 30 GPIO pins.
Twenty-one are powered by the core power rail and 9 from the
suspend power supply.
Symbol GPIO_ICH
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel ICH GPIO" if PCI && X86 (value: "y")
Default values:
(no default values)
Selects:
MFD_CORE if PCI && X86 (value: "y")
LPC_ICH if PCI && X86 (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:267
Say yes here to support the GPIO functionality of a number of Intel
ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
If unsure, say N.
Symbol GPIO_VX855
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VIA VX855/VX875 GPIO" if PCI && GENERIC_HARDIRQS (value: "y")
Default values:
(no default values)
Selects:
MFD_CORE if PCI && GENERIC_HARDIRQS (value: "y")
MFD_VX855 if PCI && GENERIC_HARDIRQS (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:280
Support access to the VX855/VX875 GPIO lines through the gpio library.
This driver provides common support for accessing the device,
additional drivers must be enabled in order to use the
functionality of the device.
Symbol GPIO_MAX7300
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Maxim MAX7300 GPIO expander" if I2C (value: "m")
Default values:
(no default values)
Selects:
GPIO_MAX730X if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:319
GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
Symbol GPIO_MAX732X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"MAX7319, MAX7320-7327 I2C Port Expanders" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:326
Say yes here to support the MAX7319, MAX7320-7327 series of I2C
Port Expanders. Each IO port on these chips has a fixed role of
Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
Input and Output (designed by 'P'). The combinations are listed
below:
8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
max7322 (4I4O), max7323 (4P4O)
16 bits: max7324 (8I8O), max7325 (8P8O),
max7326 (4I12O), max7327 (4P12O)
Board setup code must specify the model to use, and the start
number for these GPIOs.
Symbol GPIO_PCA953X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
SOC_CAMERA && I2C && MT9M001_PCA9536_SWITCH && VIDEO_V4L2 && MEDIA_SUPPORT && SOC_CAMERA && SOC_CAMERA_MT9M001 || SOC_CAMERA && I2C && MT9V022_PCA9536_SWITCH && VIDEO_V4L2 && MEDIA_SUPPORT && SOC_CAMERA && SOC_CAMERA_MT9V022 (value: "n")
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:358
Say yes here to provide access to several register-oriented
SMBus I/O expanders, made mostly by NXP or TI. Compatible
models include:
4 bits: pca9536, pca9537
8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
pca9556, pca9557, pca9574, tca6408
16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
tca6416
Symbol GPIO_PCF857X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders" if I2C (value: "m")
Default values:
(no default values)
Selects:
IRQ_DOMAIN if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:381
Say yes here to provide access to most "quasi-bidirectional" I2C
GPIO expanders used for additional digital outputs or inputs.
Most of these parts are from NXP, though TI is a second source for
some of them. Compatible models include:
8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
pca9670, pca9672, pca9674, pca9674a,
max7328, max7329
16 bits: pcf8575, pcf8575c, pca8575,
pca9671, pca9673, pca9675
Your board setup code will need to declare the expanders in
use, and assign numbers to the GPIOs they expose. Those GPIOs
can then be used from drivers and other kernel code, just like
other GPIOs, but only accessible from task contexts.
This driver provides an in-kernel interface to those GPIOs using
platform-neutral GPIO calls.
Symbol GPIO_ADP5588
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ADP5588 I2C GPIO expander" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:498
This option enables support for 18 GPIOs found
on Analog Devices ADP5588 GPIO Expanders.
Symbol GPIO_AMD8111
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD 8111 GPIO driver" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:551
The AMD 8111 south bridge contains 32 GPIO pins which can be used.
Note, that usually system firmware/ACPI handles GPIO pins on their
own and users might easily break their systems with uncarefull usage
of this driver!
If unsure, say N
Symbol GPIO_PCH
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO" if PCI && X86 (value: "y")
Default values:
(no default values)
Selects:
GENERIC_IRQ_CHIP if PCI && X86 (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:570
This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
which is an IOH(Input/Output Hub) for x86 embedded processor.
This driver can access PCH GPIO device.
This driver also can be used for LAPIS Semiconductor IOH(Input/
Output Hub), ML7223 and ML7831.
ML7223 IOH is for MP(Media Phone) use.
ML7831 IOH is for general purpose use.
ML7223/ML7831 is companion chip for Intel Atom E6xx series.
ML7223/ML7831 is completely compatible for Intel EG20T PCH.
Symbol GPIO_ML_IOH
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"OKI SEMICONDUCTOR ML7213 IOH GPIO support" if PCI (value: "y")
Default values:
(no default values)
Selects:
GENERIC_IRQ_CHIP if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:586
ML7213 is companion chip for Intel Atom E6xx series.
This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
Hub) which is for IVI(In-Vehicle Infotainment) use.
This driver can access the IOH's GPIO device.
Symbol GPIO_RDC321X
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"RDC R-321x GPIO support" if PCI && GENERIC_HARDIRQS (value: "y")
Default values:
(no default values)
Selects:
MFD_CORE if PCI && GENERIC_HARDIRQS (value: "y")
MFD_RDC321X if PCI && GENERIC_HARDIRQS (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:610
Support for the RDC R321x SoC GPIOs over southbridge
PCI configuration space.
Symbol GPIO_MCP23S08
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Microchip MCP23xxx I/O expander" if SPI_MASTER || I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
GPIOLIB (value: "y")
Locations: ../drivers/gpio/Kconfig:628
SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
I/O expanders.
This provides a GPIO interface supporting inputs and outputs.
Symbol POWER_SUPPLY
Type : bool
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Power supply class support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
X86 && ACPI && ACPI_AC || X86 && ACPI && ACPI_BATTERY || X86 && ACPI && ACPI_SBS || OLPC && OLPC_XO1_PM && INPUT = y && X86_32 && OLPC_XO1_SCI || OLPC && ACPI && X86_32 && OLPC_XO15_SCI || INPUT && !UML && INPUT_TABLET && USB_ARCH_HAS_HCD && TABLET_USB_WACOM || GENERIC_HARDIRQS && ABX500_CORE && MFD_DB8500_PRCMU && HAS_IOMEM && AB8500_CORE || DRM && PCI && HAS_IOMEM && DRM_RADEON || DRM && PCI && HAS_IOMEM && DRM_NOUVEAU || BT_HIDP && LEDS_CLASS && HID && INPUT && HID && HID_WACOM || BT_HIDP && LEDS_CLASS && HID && INPUT && HID && HID_WIIMOTE || X86 && DCDBAS && BACKLIGHT_CLASS_DEVICE && (RFKILL || RFKILL = n) && SERIO_I8042 && X86_PLATFORM_DEVICES && X86 && DELL_LAPTOP (value: "m")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/power/Kconfig:1
Say Y here to enable power supply class support. This allows
power supply (batteries, AC, USB) monitoring by userspace
via sysfs and uevent (if available) and/or APM kernel interface
(if selected below).
Symbol HWMON
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Hardware Monitoring support" if HAS_IOMEM (value: "y")
Default values:
y (value: "y")
Condition: HAS_IOMEM (value: "y")
Selects:
(no selects)
Reverse dependencies:
I8K || ETHERNET && NETDEVICES && NET_VENDOR_BROADCOM && PCI && TIGON3 || DRM && PCI && HAS_IOMEM && DRM_RADEON || ACPI && INPUT && (RFKILL || RFKILL = n) && X86_PLATFORM_DEVICES && X86 && THINKPAD_ACPI || ACPI && INPUT && (RFKILL || RFKILL = n) && HOTPLUG_PCI && X86_PLATFORM_DEVICES && X86 && EEEPC_LAPTOP (value: "m")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/hwmon/Kconfig:5
Hardware monitoring devices let you monitor the hardware health
of a system. Most modern motherboards include such a device. It
can include temperature sensors, voltage sensors, fan speed
sensors and various additional features such as the ability to
control the speed of the fans. If you want this support you
should say Y here and also to the specific driver(s) for your
sensors chip(s) below.
To find out which specific driver(s) you need, use the
sensors-detect script from the lm_sensors package. Read
<file:Documentation/hwmon/userspace-tools> for details.
This support can also be built as a module. If so, the module
will be called hwmon.
Symbol SENSORS_ABITUGURU
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Abit uGuru (rev 1 & 2)" if X86 && DMI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:42
If you say yes here you get support for the sensor part of the first
and second revision of the Abit uGuru chip. The voltage and frequency
control parts of the Abit uGuru are not supported. The Abit uGuru
chip can be found on Abit uGuru featuring motherboards (most modern
Abit motherboards from before end 2005). For more info and a list
of which motherboards have which revision see
Documentation/hwmon/abituguru
This driver can also be built as a module. If so, the module
will be called abituguru.
Symbol SENSORS_ABITUGURU3
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Abit uGuru (rev 3)" if X86 && DMI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:57
If you say yes here you get support for the sensor part of the
third revision of the Abit uGuru chip. Only reading the sensors
and their settings is supported. The third revision of the Abit
uGuru chip can be found on recent Abit motherboards (since end
2005). For more info and a list of which motherboards have which
revision see Documentation/hwmon/abituguru3
This driver can also be built as a module. If so, the module
will be called abituguru3.
Symbol SENSORS_AD7414
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices AD7414" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:81
If you say yes here you get support for the Analog Devices
AD7414 temperature monitoring chip.
This driver can also be built as a module. If so, the module
will be called ad7414.
Symbol SENSORS_AD7418
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices AD7416, AD7417 and AD7418" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:91
If you say yes here you get support for the Analog Devices
AD7416, AD7417 and AD7418 temperature monitoring chips.
This driver can also be built as a module. If so, the module
will be called ad7418.
Symbol SENSORS_ADM1021
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices ADM1021 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:117
If you say yes here you get support for Analog Devices ADM1021
and ADM1023 sensor chips and clones: Maxim MAX1617 and MAX1617A,
Genesys Logic GL523SM, National Semiconductor LM84 and TI THMC10.
This driver can also be built as a module. If so, the module
will be called adm1021.
Symbol SENSORS_ADM1025
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices ADM1025 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:128
If you say yes here you get support for Analog Devices ADM1025
and Philips NE1619 sensor chips.
This driver can also be built as a module. If so, the module
will be called adm1025.
Symbol SENSORS_ADM1026
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices ADM1026 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:139
If you say yes here you get support for Analog Devices ADM1026
sensor chip.
This driver can also be built as a module. If so, the module
will be called adm1026.
Symbol SENSORS_ADM1029
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices ADM1029" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:150
If you say yes here you get support for Analog Devices ADM1029
sensor chip.
Very rare chip, please let us know you use it.
This driver can also be built as a module. If so, the module
will be called adm1029.
Symbol SENSORS_ADM1031
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices ADM1031 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:161
If you say yes here you get support for Analog Devices ADM1031
and ADM1030 sensor chips.
This driver can also be built as a module. If so, the module
will be called adm1031.
Symbol SENSORS_ADM9240
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices ADM9240 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:171
If you say yes here you get support for Analog Devices ADM9240,
Dallas DS1780, National Semiconductor LM81 sensor chips.
This driver can also be built as a module. If so, the module
will be called adm9240.
Symbol SENSORS_ADT7411
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices ADT7411" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:192
If you say yes here you get support for the Analog Devices
ADT7411 voltage and temperature monitoring chip.
This driver can also be built as a module. If so, the module
will be called adt7411.
Symbol SENSORS_ADT7462
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices ADT7462" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:202
If you say yes here you get support for the Analog Devices
ADT7462 temperature monitoring chips.
This driver can also be built as a module. If so, the module
will be called adt7462.
Symbol SENSORS_ADT7470
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices ADT7470" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:212
If you say yes here you get support for the Analog Devices
ADT7470 temperature monitoring chips.
This driver can also be built as a module. If so, the module
will be called adt7470.
Symbol SENSORS_ADT7475
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Analog Devices ADT7473, ADT7475, ADT7476 and ADT7490" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:222
If you say yes here you get support for the Analog Devices
ADT7473, ADT7475, ADT7476 and ADT7490 hardware monitoring
chips.
This driver can also be build as a module. If so, the module
will be called adt7475.
Symbol SENSORS_ASC7621
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Andigilog aSC7621" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:234
If you say yes here you get support for the aSC7621
family of SMBus sensors chip found on most Intel X38, X48, X58,
945, 965 and 975 desktop boards. Currently supported chips:
aSC7621
aSC7621a
This driver can also be built as a module. If so, the module
will be called asc7621.
Symbol SENSORS_K8TEMP
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD Athlon64/FX or Opteron temperature sensor" if X86 && PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:247
If you say yes here you get support for the temperature
sensor(s) inside your CPU. Supported is whole AMD K8
microarchitecture. Please note that you will need at least
lm-sensors 2.10.1 for proper userspace support.
This driver can also be built as a module. If so, the module
will be called k8temp.
Symbol SENSORS_K10TEMP
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD Family 10h+ temperature sensor" if X86 && PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:259
If you say yes here you get support for the temperature
sensor(s) inside your CPU. Supported are later revisions of
the AMD Family 10h and all revisions of the AMD Family 11h,
12h (Llano), 14h (Brazos) and 15h (Bulldozer/Trinity)
microarchitectures.
This driver can also be built as a module. If so, the module
will be called k10temp.
Symbol SENSORS_FAM15H_POWER
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD Family 15h processor power" if X86 && PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:272
If you say yes here you get support for processor power
information of your AMD family 15h CPU.
This driver can also be built as a module. If so, the module
will be called fam15h_power.
Symbol SENSORS_ASB100
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Asus ASB100 Bach" if X86 && I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if X86 && I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:282
If you say yes here you get support for the ASB100 Bach sensor
chip found on some Asus mainboards.
This driver can also be built as a module. If so, the module
will be called asb100.
Symbol SENSORS_ATXP1
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Attansic ATXP1 VID controller" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:293
If you say yes here you get support for the Attansic ATXP1 VID
controller.
If your board have such a chip, you are able to control your CPU
core and other voltages.
This driver can also be built as a module. If so, the module
will be called atxp1.
Symbol SENSORS_DS620
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Dallas Semiconductor DS620" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:307
If you say yes here you get support for Dallas Semiconductor
DS620 sensor chip.
This driver can also be built as a module. If so, the module
will be called ds620.
Symbol SENSORS_DS1621
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Dallas Semiconductor DS1621 and DS1625" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:317
If you say yes here you get support for Dallas Semiconductor
DS1621 and DS1625 sensor chips.
This driver can also be built as a module. If so, the module
will be called ds1621.
Symbol SENSORS_I5K_AMB
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"FB-DIMM AMB temperature sensor on Intel 5000 series chipsets" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:347
If you say yes here you get support for FB-DIMM AMB temperature
monitoring chips on systems with the Intel 5000 series chipset.
This driver can also be built as a module. If so, the module
will be called i5k_amb.
Symbol SENSORS_F71805F
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fintek F71805F/FG, F71806F/FG and F71872F/FG" if !PPC (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:357
If you say yes here you get support for hardware monitoring
features of the Fintek F71805F/FG, F71806F/FG and F71872F/FG
Super-I/O chips.
This driver can also be built as a module. If so, the module
will be called f71805f.
Symbol SENSORS_F71882FG
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fintek F71882FG and compatibles" if !PPC (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:368
If you say yes here you get support for hardware monitoring
features of many Fintek Super-I/O (LPC) chips. The currently
supported chips are:
F71808E/A
F71858FG
F71862FG
F71863FG
F71869F/E/A
F71882FG
F71883FG
F71889FG/ED/A
F8000
F81801U
F81865F
This driver can also be built as a module. If so, the module
will be called f71882fg.
Symbol SENSORS_F75375S
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fintek F75375S/SP, F75373 and F75387" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:390
If you say yes here you get support for hardware monitoring
features of the Fintek F75375S/SP, F75373 and F75387
This driver can also be built as a module. If so, the module
will be called f75375s.
Symbol SENSORS_FSCHMD
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fujitsu Siemens Computers sensor chips" if X86 && I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:400
If you say yes here you get support for the following Fujitsu
Siemens Computers (FSC) sensor chips: Poseidon, Scylla, Hermes,
Heimdall, Heracles, Hades and Syleus including support for the
integrated watchdog.
This is a merged driver for FSC sensor chips replacing the fscpos,
fscscy and fscher drivers and adding support for several other FSC
sensor chips.
This driver can also be built as a module. If so, the module
will be called fschmd.
Symbol SENSORS_G760A
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"GMT G760A" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:416
If you say yes here you get support for Global Mixed-mode
Technology Inc G760A fan speed PWM controller chips.
This driver can also be built as a module. If so, the module
will be called g760a.
Symbol SENSORS_GL518SM
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Genesys Logic GL518SM" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:426
If you say yes here you get support for Genesys Logic GL518SM
sensor chips.
This driver can also be built as a module. If so, the module
will be called gl518sm.
Symbol SENSORS_GL520SM
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Genesys Logic GL520SM" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:436
If you say yes here you get support for Genesys Logic GL520SM
sensor chips.
This driver can also be built as a module. If so, the module
will be called gl520sm.
Symbol SENSORS_GPIO_FAN
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"GPIO fan" if GPIOLIB (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:447
If you say yes here you get support for fans connected to GPIO lines.
This driver can also be built as a module. If so, the module
will be called gpio-fan.
Symbol SENSORS_CORETEMP
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel Core/Core2/Atom temperature sensor" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:466
If you say yes here you get support for the temperature
sensor inside your CPU. Most of the family 6 CPUs
are supported. Check Documentation/hwmon/coretemp for details.
Symbol SENSORS_IT87
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ITE IT87xx and compatibles" if !PPC (value: "y")
Default values:
(no default values)
Selects:
HWMON_VID if !PPC (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:502
If you say yes here you get support for ITE IT8705F, IT8712F,
IT8716F, IT8718F, IT8720F, IT8721F, IT8726F, IT8728F, IT8758E,
IT8771E, IT8772E, IT8782F, and IT8783E/F sensor chips, and the
SiS950 clone.
This driver can also be built as a module. If so, the module
will be called it87.
Symbol SENSORS_JC42
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"JEDEC JC42.4 compliant memory module temperature sensors" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:525
If you say yes here, you get support for JEDEC JC42.4 compliant
temperature sensors, which are used on many DDR3 memory modules for
mobile devices and servers. Support will include, but not be limited
to, ADT7408, AT30TS00, CAT34TS02, CAT6095, MAX6604, MCP9804, MCP9805,
MCP98242, MCP98243, MCP98244, MCP9843, SE97, SE98, STTS424(E),
STTS2002, STTS3000, TSE2002B3, TSE2002GB2, TS3000B3, and TS3000GB2.
This driver can also be built as a module. If so, the module
will be called jc42.
Symbol SENSORS_LINEAGE
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Lineage Compact Power Line Power Entry Module" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:539
If you say yes here you get support for the Lineage Compact Power Line
series of DC/DC and AC/DC converters such as CP1800, CP2000AC,
CP2000DC, CP2725, and others.
This driver can also be built as a module. If so, the module
will be called lineage-pem.
Symbol SENSORS_LM63
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM63 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:550
If you say yes here you get support for the National
Semiconductor LM63, LM64, and LM96163 remote diode digital temperature
sensors with integrated fan control. Such chips are found
on the Tyan S4882 (Thunder K8QS Pro) motherboard, among
others.
This driver can also be built as a module. If so, the module
will be called lm63.
Symbol SENSORS_LM73
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM73" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:574
If you say yes here you get support for National Semiconductor LM73
sensor chips.
This driver can also be built as a module. If so, the module
will be called lm73.
Symbol SENSORS_LM75
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM75 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:583
If you say yes here you get support for one common type of
temperature sensor chip, with models including:
- Analog Devices ADT75
- Dallas Semiconductor DS75 and DS1775
- Maxim MAX6625 and MAX6626
- Microchip MCP980x
- National Semiconductor LM75, LM75A
- NXP's LM75A
- ST Microelectronics STDS75
- TelCom (now Microchip) TCN75
- Texas Instruments TMP100, TMP101, TMP105, TMP75, TMP175,
TMP275
This driver supports driver model based binding through board
specific I2C device tables.
It also supports the "legacy" style of driver binding. To use
that with some chips which don't replicate LM75 quirks exactly,
you may need the "force" module parameter.
This driver can also be built as a module. If so, the module
will be called lm75.
Symbol SENSORS_LM77
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM77" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:611
If you say yes here you get support for National Semiconductor LM77
sensor chips.
This driver can also be built as a module. If so, the module
will be called lm77.
Symbol SENSORS_LM78
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM78 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:621
If you say yes here you get support for National Semiconductor LM78,
LM78-J and LM79.
This driver can also be built as a module. If so, the module
will be called lm78.
Symbol SENSORS_LM80
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM80 and LM96080" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:632
If you say yes here you get support for National Semiconductor
LM80 and LM96080 sensor chips.
This driver can also be built as a module. If so, the module
will be called lm80.
Symbol SENSORS_LM83
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM83 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:642
If you say yes here you get support for National Semiconductor
LM82 and LM83 sensor chips.
This driver can also be built as a module. If so, the module
will be called lm83.
Symbol SENSORS_LM85
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM85 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:652
If you say yes here you get support for National Semiconductor LM85
sensor chips and clones: ADM1027, ADT7463, ADT7468, EMC6D100,
EMC6D101, EMC6D102, and EMC6D103.
This driver can also be built as a module. If so, the module
will be called lm85.
Symbol SENSORS_LM87
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM87 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:664
If you say yes here you get support for National Semiconductor LM87
and Analog Devices ADM1024 sensor chips.
This driver can also be built as a module. If so, the module
will be called lm87.
Symbol SENSORS_LM90
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM90 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:675
If you say yes here you get support for National Semiconductor LM90,
LM86, LM89 and LM99, Analog Devices ADM1032, ADT7461, and ADT7461A,
Maxim MAX6646, MAX6647, MAX6648, MAX6649, MAX6657, MAX6658, MAX6659,
MAX6680, MAX6681, MAX6692, MAX6695, MAX6696, ON Semiconductor NCT1008,
Winbond/Nuvoton W83L771W/G/AWG/ASG, Philips SA56004, and GMT G781
sensor chips.
This driver can also be built as a module. If so, the module
will be called lm90.
Symbol SENSORS_LM92
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM92 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:689
If you say yes here you get support for National Semiconductor LM92
and Maxim MAX6635 sensor chips.
This driver can also be built as a module. If so, the module
will be called lm92.
Symbol SENSORS_LM93
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM93 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:699
If you say yes here you get support for National Semiconductor LM93,
LM94, and compatible sensor chips.
This driver can also be built as a module. If so, the module
will be called lm93.
Symbol SENSORS_LTC4151
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Linear Technology LTC4151" if I2C (value: "m")
Default values:
n (value: "n")
Condition: I2C (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:710
If you say yes here you get support for Linear Technology LTC4151
High Voltage I2C Current and Voltage Monitor interface.
This driver can also be built as a module. If so, the module will
be called ltc4151.
Symbol SENSORS_LTC4215
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Linear Technology LTC4215" if I2C (value: "m")
Default values:
n (value: "n")
Condition: I2C (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:721
If you say yes here you get support for Linear Technology LTC4215
Hot Swap Controller I2C interface.
This driver can also be built as a module. If so, the module will
be called ltc4215.
Symbol SENSORS_LTC4245
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Linear Technology LTC4245" if I2C (value: "m")
Default values:
n (value: "n")
Condition: I2C (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:732
If you say yes here you get support for Linear Technology LTC4245
Multiple Supply Hot Swap Controller I2C interface.
This driver can also be built as a module. If so, the module will
be called ltc4245.
Symbol SENSORS_LTC4261
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Linear Technology LTC4261" if I2C (value: "m")
Default values:
n (value: "n")
Condition: I2C (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:743
If you say yes here you get support for Linear Technology LTC4261
Negative Voltage Hot Swap Controller I2C interface.
This driver can also be built as a module. If so, the module will
be called ltc4261.
Symbol SENSORS_LM95241
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM95241 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:754
If you say yes here you get support for LM95231 and LM95241 sensor
chips.
This driver can also be built as a module. If so, the module
will be called lm95241.
Symbol SENSORS_LM95245
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor LM95245 sensor chip" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:764
If you say yes here you get support for LM95245 sensor chip.
This driver can also be built as a module. If so, the module
will be called lm95245.
Symbol SENSORS_MAX16065
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Maxim MAX16065 System Manager and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:783
If you say yes here you get support for hardware monitoring
capabilities of the following Maxim System Manager chips.
MAX16065
MAX16066
MAX16067
MAX16068
MAX16070
MAX16071
This driver can also be built as a module. If so, the module
will be called max16065.
Symbol SENSORS_MAX1619
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Maxim MAX1619 sensor chip" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:799
If you say yes here you get support for MAX1619 sensor chip.
This driver can also be built as a module. If so, the module
will be called max1619.
Symbol SENSORS_MAX1668
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Maxim MAX1668 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:808
If you say yes here you get support for MAX1668, MAX1989 and
MAX1805 chips.
This driver can also be built as a module. If so, the module
will be called max1668.
Symbol SENSORS_MAX6639
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Maxim MAX6639 sensor chip" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:827
If you say yes here you get support for the MAX6639
sensor chips.
This driver can also be built as a module. If so, the module
will be called max6639.
Symbol SENSORS_MAX6642
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Maxim MAX6642 sensor chip" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:837
If you say yes here you get support for MAX6642 sensor chip.
MAX6642 is a SMBus-Compatible Remote/Local Temperature Sensor
with Overtemperature Alarm from Maxim.
This driver can also be built as a module. If so, the module
will be called max6642.
Symbol SENSORS_MAX6650
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Maxim MAX6650 sensor chip" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:848
If you say yes here you get support for the MAX6650 / MAX6651
sensor chips.
This driver can also be built as a module. If so, the module
will be called max6650.
Symbol SENSORS_MAX6697
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Maxim MAX6697 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:858
If you say yes here you get support for MAX6581, MAX6602, MAX6622,
MAX6636, MAX6689, MAX6693, MAX6694, MAX6697, MAX6698, and MAX6699
temperature sensor chips.
This driver can also be built as a module. If so, the module
will be called max6697.
Symbol SENSORS_MCP3021
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Microchip MCP3021 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:869
If you say yes here you get support for MCP3021 and MCP3221.
The MCP3021 is a A/D converter (ADC) with 10-bit and the MCP3221
with 12-bit resolution.
This driver can also be built as a module. If so, the module
will be called mcp3021.
Symbol SENSORS_NTC_THERMISTOR
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"NTC thermistor support"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:880
This driver supports NTC thermistors sensor reading and its
interpretation. The driver can also monitor the temperature and
send notifications about the temperature.
Currently, this driver supports
NCP15WB473, NCP18WB473, NCP21WB473, NCP03WB473, and NCP15WL333.
This driver can also be built as a module. If so, the module
will be called ntc-thermistor.
Symbol SENSORS_PC87360
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor PC87360 family" if !PPC (value: "y")
Default values:
(no default values)
Selects:
HWMON_VID if !PPC (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:893
If you say yes here you get access to the hardware monitoring
functions of the National Semiconductor PC8736x Super-I/O chips.
The PC87360, PC87363 and PC87364 only have fan monitoring and
control. The PC87365 and PC87366 additionally have voltage and
temperature monitoring.
This driver can also be built as a module. If so, the module
will be called pc87360.
Symbol SENSORS_PC87427
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor PC87427" if !PPC (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:907
If you say yes here you get access to the hardware monitoring
functions of the National Semiconductor PC87427 Super-I/O chip.
The chip has two distinct logical devices, one for fan speed
monitoring and control, and one for voltage and temperature
monitoring. Fan speed monitoring and control are supported, as
well as temperature monitoring. Voltages aren't supported yet.
This driver can also be built as a module. If so, the module
will be called pc87427.
Symbol SENSORS_PCF8591
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Philips PCF8591 ADC/DAC" if I2C (value: "m")
Default values:
n (value: "n")
Condition: I2C (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:921
If you say yes here you get support for Philips PCF8591 4-channel
ADC, 1-channel DAC chips.
This driver can also be built as a module. If so, the module
will be called pcf8591.
These devices are hard to detect and rarely found on mainstream
hardware. If unsure, say N.
Symbol PMBUS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PMBus support" if I2C (value: "m")
Default values:
n (value: "n")
Condition: I2C (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/pmbus/Kconfig:5
Say yes here if you want to enable PMBus support.
This driver can also be built as a module. If so, the module will
be called pmbus_core.
Symbol SENSORS_SHT15
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Sensiron humidity and temperature sensors. SHT15 and compat." if GPIOLIB (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:937
If you say yes here you get support for the Sensiron SHT10, SHT11,
SHT15, SHT71, SHT75 humidity and temperature sensors.
This driver can also be built as a module. If so, the module
will be called sht15.
Symbol SENSORS_SHT21
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Sensiron humidity and temperature sensors. SHT21 and compat." if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:947
If you say yes here you get support for the Sensiron SHT21, SHT25
humidity and temperature sensors.
This driver can also be built as a module. If so, the module
will be called sht21.
Symbol SENSORS_SIS5595
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Silicon Integrated Systems Corp. SiS5595" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:974
If you say yes here you get support for the integrated sensors in
SiS5595 South Bridges.
This driver can also be built as a module. If so, the module
will be called sis5595.
Symbol SENSORS_SMM665
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Summit Microelectronics SMM665" if I2C (value: "m")
Default values:
n (value: "n")
Condition: I2C (value: "m")
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:984
If you say yes here you get support for the hardware monitoring
features of the Summit Microelectronics SMM665/SMM665B Six-Channel
Active DC Output Controller / Monitor.
Other supported chips are SMM465, SMM665C, SMM764, and SMM766.
Support for those chips is untested.
This driver can also be built as a module. If so, the module will
be called smm665.
Symbol SENSORS_DME1737
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SMSC DME1737, SCH311x and compatibles" if I2C && !PPC (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C && !PPC (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:999
If you say yes here you get support for the hardware monitoring
and fan control features of the SMSC DME1737, SCH311x, SCH5027, and
Asus A8000 Super-I/O chips.
This driver can also be built as a module. If so, the module
will be called dme1737.
Symbol SENSORS_EMC1403
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SMSC EMC1403/23 thermal sensor" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1011
If you say yes here you get support for the SMSC EMC1403/23
temperature monitoring chip.
Threshold values can be configured using sysfs.
Data from the different diodes are accessible via sysfs.
Symbol SENSORS_EMC2103
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SMSC EMC2103" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1021
If you say yes here you get support for the temperature
and fan sensors of the SMSC EMC2103 chips.
This driver can also be built as a module. If so, the module
will be called emc2103.
Symbol SENSORS_EMC6W201
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SMSC EMC6W201" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1031
If you say yes here you get support for the SMSC EMC6W201
hardware monitoring chip.
This driver can also be built as a module. If so, the module
will be called emc6w201.
Symbol SENSORS_SMSC47M1
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SMSC LPC47M10x and compatibles" if !PPC (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1041
If you say yes here you get support for the integrated fan
monitoring and control capabilities of the SMSC LPC47B27x,
LPC47M10x, LPC47M112, LPC47M13x, LPC47M14x, LPC47M15x,
LPC47M192, LPC47M292 and LPC47M997 chips.
The temperature and voltage sensor features of the LPC47M15x,
LPC47M192, LPC47M292 and LPC47M997 are supported by another
driver, select also "SMSC LPC47M192 and compatibles" below for
those.
This driver can also be built as a module. If so, the module
will be called smsc47m1.
Symbol SENSORS_SMSC47M192
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SMSC LPC47M192 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1058
If you say yes here you get support for the temperature and
voltage sensors of the SMSC LPC47M192, LPC47M15x, LPC47M292
and LPC47M997 chips.
The fan monitoring and control capabilities of these chips
are supported by another driver, select
"SMSC LPC47M10x and compatibles" above. You need both drivers
if you want fan control and voltage/temperature sensor support.
This driver can also be built as a module. If so, the module
will be called smsc47m192.
Symbol SENSORS_SMSC47B397
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SMSC LPC47B397-NC" if !PPC (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1075
If you say yes here you get support for the SMSC LPC47B397-NC
sensor chip.
This driver can also be built as a module. If so, the module
will be called smsc47b397.
Symbol SENSORS_SCH5627
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SMSC SCH5627" if !PPC && WATCHDOG (value: "y")
Default values:
(no default values)
Selects:
SENSORS_SCH56XX_COMMON if !PPC && WATCHDOG (value: "y")
WATCHDOG_CORE if !PPC && WATCHDOG (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1089
If you say yes here you get support for the hardware monitoring
features of the SMSC SCH5627 Super-I/O chip including support for
the integrated watchdog.
This driver can also be built as a module. If so, the module
will be called sch5627.
Symbol SENSORS_SCH5636
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SMSC SCH5636" if !PPC && WATCHDOG (value: "y")
Default values:
(no default values)
Selects:
SENSORS_SCH56XX_COMMON if !PPC && WATCHDOG (value: "y")
WATCHDOG_CORE if !PPC && WATCHDOG (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1102
SMSC SCH5636 Super I/O chips include an embedded microcontroller for
hardware monitoring solutions, allowing motherboard manufacturers to
create their own custom hwmon solution based upon the SCH5636.
Currently this driver only supports the Fujitsu Theseus SCH5636 based
hwmon solution. Say yes here if you want support for the Fujitsu
Theseus' hardware monitoring features including support for the
integrated watchdog.
This driver can also be built as a module. If so, the module
will be called sch5636.
Symbol SENSORS_ADS1015
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Texas Instruments ADS1015" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1120
If you say yes here you get support for Texas Instruments ADS1015
12-bit 4-input ADC device.
This driver can also be built as a module. If so, the module
will be called ads1015.
Symbol SENSORS_ADS7828
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Texas Instruments ADS7828 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1130
If you say yes here you get support for Texas Instruments ADS7828 and
ADS7830 8-channel A/D converters. ADS7828 resolution is 12-bit, while
it is 8-bit on ADS7830.
This driver can also be built as a module. If so, the module
will be called ads7828.
Symbol SENSORS_AMC6821
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Texas Instruments AMC6821" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1150
If you say yes here you get support for the Texas Instruments
AMC6821 hardware monitoring chips.
This driver can also be build as a module. If so, the module
will be called amc6821.
Symbol SENSORS_INA209
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"TI / Burr Brown INA209" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1160
If you say yes here you get support for the TI / Burr Brown INA209
voltage / current / power monitor I2C interface.
This driver can also be built as a module. If so, the module will
be called ina209.
Symbol SENSORS_THMC50
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Texas Instruments THMC50 / Analog Devices ADM1022" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1183
If you say yes here you get support for Texas Instruments THMC50
sensor chips and clones: the Analog Devices ADM1022.
This driver can also be built as a module. If so, the module
will be called thmc50.
Symbol SENSORS_TMP102
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Texas Instruments TMP102" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1193
If you say yes here you get support for Texas Instruments TMP102
sensor chips.
This driver can also be built as a module. If so, the module
will be called tmp102.
Symbol SENSORS_TMP401
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Texas Instruments TMP401 and compatibles" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1203
If you say yes here you get support for Texas Instruments TMP401 and
TMP411 temperature sensor chips.
This driver can also be built as a module. If so, the module
will be called tmp401.
Symbol SENSORS_TMP421
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Texas Instruments TMP421 and compatible" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1213
If you say yes here you get support for Texas Instruments TMP421,
TMP422 and TMP423 temperature sensor chips.
This driver can also be built as a module. If so, the module
will be called tmp421.
Symbol SENSORS_VIA_CPUTEMP
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VIA CPU temperature sensor" if X86 (value: "y")
Default values:
(no default values)
Selects:
HWMON_VID if X86 (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1241
If you say yes here you get support for the temperature
sensor inside your CPU. Supported are all known variants of
the VIA C7 and Nano.
Symbol SENSORS_VIA686A
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VIA686A" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1250
If you say yes here you get support for the integrated sensors in
Via 686A/B South Bridges.
This driver can also be built as a module. If so, the module
will be called via686a.
Symbol SENSORS_VT1211
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VIA VT1211" if !PPC (value: "y")
Default values:
(no default values)
Selects:
HWMON_VID if !PPC (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1260
If you say yes here then you get support for hardware monitoring
features of the VIA VT1211 Super-I/O chip.
This driver can also be built as a module. If so, the module
will be called vt1211.
Symbol SENSORS_VT8231
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VIA VT8231" if PCI (value: "y")
Default values:
(no default values)
Selects:
HWMON_VID if PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1271
If you say yes here then you get support for the integrated sensors
in the VIA VT8231 device.
This driver can also be built as a module. If so, the module
will be called vt8231.
Symbol SENSORS_W83781D
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Winbond W83781D, W83782D, W83783S, Asus AS99127F" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1282
If you say yes here you get support for the Winbond W8378x series
of sensor chips: the W83781D, W83782D and W83783S, and the similar
Asus AS99127F.
This driver can also be built as a module. If so, the module
will be called w83781d.
Symbol SENSORS_W83791D
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Winbond W83791D" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1294
If you say yes here you get support for the Winbond W83791D chip.
This driver can also be built as a module. If so, the module
will be called w83791d.
Symbol SENSORS_W83792D
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Winbond W83792D" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1304
If you say yes here you get support for the Winbond W83792D chip.
This driver can also be built as a module. If so, the module
will be called w83792d.
Symbol SENSORS_W83793
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Winbond W83793" if I2C (value: "m")
Default values:
(no default values)
Selects:
HWMON_VID if I2C (value: "m")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1313
If you say yes here you get support for the Winbond W83793
hardware monitoring chip, including support for the integrated
watchdog.
This driver can also be built as a module. If so, the module
will be called w83793.
Symbol SENSORS_W83795
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Winbond/Nuvoton W83795G/ADG" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1325
If you say yes here you get support for the Winbond W83795G and
W83795ADG hardware monitoring chip, including manual fan speed
control.
This driver can also be built as a module. If so, the module
will be called w83795.
Symbol SENSORS_W83L785TS
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Winbond W83L785TS-S" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1353
If you say yes here you get support for the Winbond W83L785TS-S
sensor chip, which is used on the Asus A7N8X, among other
motherboards.
This driver can also be built as a module. If so, the module
will be called w83l785ts.
Symbol SENSORS_W83L786NG
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Winbond W83L786NG, W83L786NR" if I2C (value: "m")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1364
If you say yes here you get support for the Winbond W83L786NG
and W83L786NR sensor chips.
This driver can also be built as a module. If so, the module
will be called w83l786ng.
Symbol SENSORS_W83627HF
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Winbond W83627HF, W83627THF, W83637HF, W83687THF, W83697HF" if !PPC (value: "y")
Default values:
(no default values)
Selects:
HWMON_VID if !PPC (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1374
If you say yes here you get support for the Winbond W836X7 series
of sensor chips: the W83627HF, W83627THF, W83637HF, W83687THF and
W83697HF.
This driver can also be built as a module. If so, the module
will be called w83627hf.
Symbol SENSORS_W83627EHF
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Winbond W83627EHF/EHG/DHG/UHG, W83667HG, NCT6775F, NCT6776F" if !PPC (value: "y")
Default values:
(no default values)
Selects:
HWMON_VID if !PPC (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1386
If you say yes here you get support for the hardware
monitoring functionality of the Winbond W83627EHF Super-I/O chip.
This driver also supports the W83627EHG, which is the lead-free
version of the W83627EHF, and the W83627DHG, which is a similar
chip suited for specific Intel processors that use PECI such as
the Core 2 Duo. And also the W83627UHG, which is a stripped down
version of the W83627DHG (as far as hardware monitoring goes.)
This driver also supports Nuvoton W83667HG, W83667HG-B, NCT6775F
(also known as W83667HG-I), and NCT6776F.
This driver can also be built as a module. If so, the module
will be called w83627ehf.
Symbol SENSORS_APPLESMC
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Apple SMC (Motion sensor, light sensor, keyboard backlight)" if INPUT && X86 (value: "y")
Default values:
n (value: "n")
Condition: INPUT && X86 (value: "y")
Selects:
NEW_LEDS if INPUT && X86 (value: "y")
LEDS_CLASS if INPUT && X86 (value: "y")
INPUT_POLLDEV if INPUT && X86 (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1434
This driver provides support for the Apple System Management
Controller, which provides an accelerometer (Apple Sudden Motion
Sensor), light sensors, temperature sensors, keyboard backlight
control and fan control.
Only Intel-based Apple's computers are supported (MacBook Pro,
MacBook, MacMini).
Data from the different sensors, keyboard backlight control and fan
control are accessible via sysfs.
This driver also provides an absolute input class device, allowing
the laptop to act as a pinball machine-esque joystick.
Say Y here if you have an applicable laptop and want to experience
the awesome power of applesmc.
Symbol SENSORS_ACPI_POWER
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ACPI 4.0 power meter"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI && HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1469
This driver exposes ACPI 4.0 power meters as hardware monitoring
devices. Say Y (or M) if you have a computer with ACPI 4.0 firmware
and a power meter.
To compile this driver as a module, choose M here:
the module will be called acpi_power_meter.
Symbol SENSORS_ATK0110
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "m"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ASUS ATK0110" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
ACPI && HWMON (value: "m")
Locations: ../drivers/hwmon/Kconfig:1479
If you say yes here you get support for the ACPI hardware
monitoring interface found in many ASUS motherboards. This
driver will provide readings of fans, voltages and temperatures
through the system firmware.
This driver can also be built as a module. If so, the module
will be called asus_atk0110.
Symbol THERMAL
Type : tristate
Value : "y"
User value : "y"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Generic Thermal sysfs driver"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
X86 && BACKLIGHT_CLASS_DEVICE && VIDEO_OUTPUT_CONTROL && INPUT && ACPI && ACPI_VIDEO || ACPI_FAN && ACPI || ACPI_PROCESSOR && ACPI || ACPI_PROCESSOR && ACPI && ACPI_THERMAL || X86_PLATFORM_DEVICES && X86 && ACPI_THERMAL && INTEL_MENLOW (value: "m")
Additional dependencies from enclosing menus and if's:
(no additional dependencies)
Locations: ../drivers/thermal/Kconfig:5
Generic Thermal Sysfs driver offers a generic mechanism for
thermal management. Usually it's made up of one or more thermal
zone and cooling device.
Each thermal zone contains its own temperature, trip points,
cooling devices.
All platforms with ACPI thermal support can use this driver.
If you want this support, you should say Y or M here.
Symbol THERMAL_GOV_FAIR_SHARE
Type : bool
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'y'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fair-share thermal governor"
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
THERMAL_DEFAULT_GOV_FAIR_SHARE (value: "n")
Additional dependencies from enclosing menus and if's:
THERMAL (value: "y")
Locations: ../drivers/thermal/Kconfig:54
Enable this to manage platform thermals using fair-share governor.
Symbol SOFT_WATCHDOG
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Software watchdog"
Default values:
(no default values)
Selects:
WATCHDOG_CORE
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:56
A software monitoring watchdog. This will fail to reboot your system
from some situations that the hardware watchdog will recover
from. Equally it's a lot cheaper to install.
To compile this driver as a module, choose M here: the
module will be called softdog.
Symbol ACQUIRE_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Acquire SBC Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:424
This is the driver for the hardware watchdog on Single Board
Computers produced by Acquire Inc (and others). This watchdog
simply watches your kernel to make sure it doesn't freeze, and if
it does, it reboots your computer after a certain amount of time.
To compile this driver as a module, choose M here: the
module will be called acquirewdt.
Most people will say N.
Symbol ADVANTECH_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Advantech SBC Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:438
If you are configuring a Linux kernel for the Advantech single-board
computer, say `Y' here to support its built-in watchdog timer
feature. More information can be found at
<http://www.advantech.com.tw/products/>
Symbol ALIM1535_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ALi M1535 PMU Watchdog Timer" if X86 && PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:447
This is the driver for the hardware watchdog on the ALi M1535 PMU.
To compile this driver as a module, choose M here: the
module will be called alim1535_wdt.
Most people will say N.
Symbol ALIM7101_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ALi M7101 PMU Computer Watchdog" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:458
This is the driver for the hardware watchdog on the ALi M7101 PMU
as used in the x86 Cobalt servers and also found in some
SPARC Netra servers too.
To compile this driver as a module, choose M here: the
module will be called alim7101_wdt.
Most people will say N.
Symbol F71808E_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:471
This is the driver for the hardware watchdog on the Fintek
F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
You can compile this driver directly into the kernel, or use
it as a module. The module will be called f71808e_wdt.
Symbol SP5100_TCO
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD/ATI SP5100 TCO Timer/Watchdog" if X86 && PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:481
Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
(Total Cost of Ownership) timer is a watchdog timer that will reboot
the machine after its expiration. The expiration time can be
configured with the "heartbeat" parameter.
To compile this driver as a module, choose M here: the
module will be called sp5100_tco.
Symbol SC520_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"AMD Elan SC520 processor Watchdog" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:506
This is the driver for the hardware watchdog built in to the
AMD "Elan" SC520 microcomputer commonly used in embedded systems.
This watchdog simply watches your kernel to make sure it doesn't
freeze, and if it does, it reboots your computer after a certain
amount of time.
You can compile this driver directly into the kernel, or use
it as a module. The module will be called sc520_wdt.
Symbol EUROTECH_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Eurotech CPU-1220/1410 Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:541
Enable support for the watchdog timer on the Eurotech CPU-1220 and
CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
information are at <http://www.eurotech.it/>.
Symbol IB700_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IB700 SBC Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:549
This is the driver for the hardware watchdog on the IB700 Single
Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
simply watches your kernel to make sure it doesn't freeze, and if
it does, it reboots your computer after a certain amount of time.
This driver is like the WDT501 driver but for slightly different hardware.
To compile this driver as a module, choose M here: the
module will be called ib700wdt.
Most people will say N.
Symbol IBMASR
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IBM Automatic Server Restart" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:565
This is the driver for the IBM Automatic Server Restart watchdog
timer built-in into some eServer xSeries machines.
To compile this driver as a module, choose M here: the
module will be called ibmasr.
Symbol WAFER_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ICP Single Board Computer Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:575
This is a driver for the hardware watchdog on the ICP Single
Board Computer. This driver is working on (at least) the following
IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
To compile this driver as a module, choose M here: the
module will be called wafer5823wdt.
Symbol I6300ESB_WDT
Type : tristate
Value : "m"
User value : "m"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel 6300ESB Timer/Watchdog" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:586
Hardware driver for the watchdog timer built into the Intel
6300ESB controller hub.
To compile this driver as a module, choose M here: the
module will be called i6300esb.
Symbol IE6XX_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel Atom E6xx Watchdog" if X86 && PCI (value: "y")
Default values:
(no default values)
Selects:
WATCHDOG_CORE if X86 && PCI (value: "y")
MFD_CORE if X86 && PCI (value: "y")
LPC_SCH if X86 && PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:596
Hardware driver for the watchdog timer built into the Intel
Atom E6XX (TunnelCreek) processor.
To compile this driver as a module, choose M here: the
module will be called ie6xx_wdt.
Symbol ITCO_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Intel TCO Timer/Watchdog" if (X86 || IA64) && PCI (value: "y")
Default values:
(no default values)
Selects:
WATCHDOG_CORE if (X86 || IA64) && PCI (value: "y")
LPC_ICH if (X86 || IA64) && PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:618
Hardware driver for the intel TCO timer based watchdog devices.
These drivers are included in the Intel 82801 I/O Controller
Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
controller hub.
The TCO (Total Cost of Ownership) timer is a watchdog timer
that will reboot the machine after its second expiration. The
expiration time can be configured with the "heartbeat" parameter.
On some motherboards the driver may fail to reset the chipset's
NO_REBOOT flag which prevents the watchdog from rebooting the
machine. If this is the case you will get a kernel message like
"failed to reset NO_REBOOT flag, reboot disabled by hardware".
To compile this driver as a module, choose M here: the
module will be called iTCO_wdt.
Symbol IT8712F_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IT8712F (Smart Guardian) Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:649
This is the driver for the built-in watchdog timer on the IT8712F
Super I/0 chipset used on many motherboards.
If the driver does not work, then make sure that the game port in
the BIOS is enabled.
To compile this driver as a module, choose M here: the
module will be called it8712f_wdt.
Symbol IT87_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"IT87 Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:662
This is the driver for the hardware watchdog on the ITE IT8702,
IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
Super I/O chips.
If the driver does not work, then make sure that the game port in
the BIOS is enabled.
This watchdog simply watches your kernel to make sure it doesn't
freeze, and if it does, it reboots your computer after a certain
amount of time.
To compile this driver as a module, choose M here: the module will
be called it87_wdt.
Symbol SC1200_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:698
This is a driver for National Semiconductor PC87307/PC97307 hardware
watchdog cards as found on the SC1200. This watchdog is mainly used
for power management purposes and can be used to power down the device
during inactivity periods (includes interrupt activity monitoring).
To compile this driver as a module, choose M here: the
module will be called sc1200wdt.
Most people will say N.
Symbol PC87413_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"NS PC87413 watchdog" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:721
This is the driver for the hardware watchdog on the PC87413 chipset
This watchdog simply watches your kernel to make sure it doesn't
freeze, and if it does, it reboots your computer after a certain
amount of time.
To compile this driver as a module, choose M here: the
module will be called pc87413_wdt.
Most people will say N.
Symbol NV_TCO
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"nVidia TCO Timer/Watchdog" if X86 && PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:735
Hardware driver for the TCO timer built into the nVidia Hub family
(such as the MCP51). The TCO (Total Cost of Ownership) timer is a
watchdog timer that will reboot the machine after its second
expiration. The expiration time can be configured with the
"heartbeat" parameter.
On some motherboards the driver may fail to reset the chipset's
NO_REBOOT flag which prevents the watchdog from rebooting the
machine. If this is the case you will get a kernel message like
"failed to reset NO_REBOOT flag, reboot disabled by hardware".
To compile this driver as a module, choose M here: the
module will be called nv_tco.
Symbol 60XX_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SBC-60XX Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:763
This driver can be used with the watchdog timer found on some
single board computers, namely the 6010 PII based computer.
It may well work with other cards. It reads port 0x443 to enable
and re-set the watchdog timer, and reads port 0x45 to disable
the watchdog. If you have a card that behave in similar ways,
you can probably make this driver work with your card as well.
You can compile this driver directly into the kernel, or use
it as a module. The module will be called sbc60xxwdt.
Symbol SBC8360_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SBC8360 Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:777
This is the driver for the hardware watchdog on the SBC8360 Single
Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
To compile this driver as a module, choose M here: the
module will be called sbc8360.
Most people will say N.
Symbol CPU5_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SMA CPU5 Watchdog" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:803
TBD.
To compile this driver as a module, choose M here: the
module will be called cpu5wdt.
Symbol SMSC_SCH311X_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"SMSC SCH311X Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:811
This is the driver for the hardware watchdog timer on the
SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
(LPC IO with 8042 KBC, Reset Generation, HWM and multiple
serial ports).
To compile this driver as a module, choose M here: the
module will be called sch311x_wdt.
Symbol SMSC37B787_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Winbond SMsC37B787 Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:823
This is the driver for the hardware watchdog component on the
Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
from Vision Systems and maybe others.
This watchdog simply watches your kernel to make sure it doesn't
freeze, and if it does, it reboots your computer after a certain
amount of time.
Usually a userspace daemon will notify the kernel WDT driver that
userspace is still alive, at regular intervals.
To compile this driver as a module, choose M here: the
module will be called smsc37b787_wdt.
Most people will say N.
Symbol VIA_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"VIA Watchdog Timer" if X86 && PCI (value: "y")
Default values:
(no default values)
Selects:
WATCHDOG_CORE if X86 && PCI (value: "y")
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:843
This is the driver for the hardware watchdog timer on VIA
southbridge chipset CX700, VX800/VX820 or VX855/VX875.
To compile this driver as a module, choose M here; the module
will be called via_wdt.
Most people will say N.
Symbol W83627HF_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"W83627HF/W83627DHG Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:856
This is the driver for the hardware watchdog on the W83627HF chipset
as used in Advantech PC-9578 and Tyan S2721-533 motherboards
(and likely others). The driver also supports the W83627DHG chip.
This watchdog simply watches your kernel to make sure it doesn't
freeze, and if it does, it reboots your computer after a certain
amount of time.
To compile this driver as a module, choose M here: the
module will be called w83627hf_wdt.
Most people will say N.
Symbol W83697HF_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"W83697HF/W83697HG Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:872
This is the driver for the hardware watchdog on the W83697HF/HG
chipset as used in Dedibox/VIA motherboards (and likely others).
This watchdog simply watches your kernel to make sure it doesn't
freeze, and if it does, it reboots your computer after a certain
amount of time.
To compile this driver as a module, choose M here: the
module will be called w83697hf_wdt.
Most people will say N.
Symbol W83697UG_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"W83697UG/W83697UF Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:887
This is the driver for the hardware watchdog on the W83697UG/UF
chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
This watchdog simply watches your kernel to make sure it doesn't
freeze, and if it does, it reboots your computer after a certain
amount of time.
To compile this driver as a module, choose M here: the
module will be called w83697ug_wdt.
Most people will say N.
Symbol W83877F_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"W83877F (EMACS) Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:902
This is the driver for the hardware watchdog on the W83877F chipset
as used in EMACS PC-104 motherboards (and likely others). This
watchdog simply watches your kernel to make sure it doesn't freeze,
and if it does, it reboots your computer after a certain amount of
time.
To compile this driver as a module, choose M here: the
module will be called w83877f_wdt.
Most people will say N.
Symbol W83977F_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"W83977F (PCM-5335) Watchdog Timer" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:917
This is the driver for the hardware watchdog on the W83977F I/O chip
as used in AAEON's PCM-5335 SBC (and likely others). This
watchdog simply watches your kernel to make sure it doesn't freeze,
and if it does, it reboots your computer after a certain amount of
time.
To compile this driver as a module, choose M here: the
module will be called w83977f_wdt.
Symbol MACHZ_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"ZF MachZ Watchdog" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:930
If you are using a ZF Micro MachZ processor, say Y here, otherwise
N. This is the driver for the watchdog timer built-in on that
processor using ZF-Logic interface. This watchdog simply watches
your kernel to make sure it doesn't freeze, and if it does, it
reboots your computer after a certain amount of time.
To compile this driver as a module, choose M here: the
module will be called machzwd.
Symbol SBC_EPX_C3_WATCHDOG
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Winsystems SBC EPX-C3 watchdog" if X86 (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:943
This is the driver for the built-in watchdog timer on the EPX-C3
Single-board computer made by Winsystems, Inc.
*Note*: This hardware watchdog is not probeable and thus there
is no way to know if writing to its IO address will corrupt
your system or have any real effect. The only way to be sure
that this driver does what you want is to make sure you
are running it on an EPX-C3 from Winsystems with the watchdog
timer at IO address 0x1ee and 0x1ef. It will write to both those
IO ports. Basically, the assumption is made that if you compile
this driver into your kernel and/or load it as a module, that you
know what you are doing and that you are in fact running on an
EPX-C3 board!
To compile this driver as a module, choose M here: the
module will be called sbc_epx_c3.
Symbol XEN_WDT
Type : tristate
Value : "n"
User value : "n"
Xen config : 'm'
Main config : 'n'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Xen Watchdog support" if XEN (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:1250
Say Y here to support the hypervisor watchdog capability provided
by Xen 4.0 and newer. The watchdog timeout period is normally one
minute but can be changed with a boot-time parameter.
Symbol PCIPCWATCHDOG
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"Berkshire Products PCI-PC Watchdog" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Locations: ../drivers/watchdog/Kconfig:1318
This is the driver for the Berkshire Products PCI-PC Watchdog card.
This card simply watches your kernel to make sure it doesn't freeze,
and if it does, it reboots your computer after a certain amount of
time. The card can also monitor the internal temperature of the PC.
More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
To compile this driver as a module, choose M here: the
module will be called pcwd_pci.
Most people will say N.
Symbol WDTPCI
Type : tristate
Value : "n"
User value : "n"
Xen config : 'n'
Main config : 'm'
Visibility : "y"
Device Drivers
Is choice item : false
Is defined : true
Is from env. : false
Is special : false
Prompts:
"PCI-WDT500/501 Watchdog timer" if PCI (value: "y")
Default values:
(no default values)
Selects:
(no selects)
Reverse dependencies:
(no reverse dependencies)
Additional dependencies from enclosing menus and if's:
WATCHDOG (value: "y")
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment