Pull more Kbuild updates from Masahiro Yamada: - fix build rules in binderfs sample - fix build errors when Kbuild recurses to the top Makefile - covert '---help---' in Kconfig to 'help' * tag 'kbuild-v5.8-2' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild: treewide: replace '---help---' in Kconfig files with 'help' kbuild: fix broken builds because of GZIP,BZIP2,LZOP variables samples: binderfs: really compile this sample and fix build issues
Unified · Split
| @@ -458,27 +458,13 @@ PYTHON = python · 457 unmodified lines | ||
| 458 | 458 | PYTHON3 = python3 |
| 459 | 459 | CHECK = sparse |
| 460 | 460 | BASH = bash |
| 461 | −GZIP = gzip | |
| 462 | −BZIP2 = bzip2 | |
| 463 | −LZOP = lzop | |
| 461 | +KGZIP = gzip | |
| 462 | +KBZIP2 = bzip2 | |
| 463 | +KLZOP = lzop | |
| 464 | 464 | LZMA = lzma |
| 465 | 465 | LZ4 = lz4c |
| 466 | 466 | XZ = xz |
| 467 | 467 | |
| 468 | −# GZIP, BZIP2, LZOP env vars are used by the tools. Support them as the command | |
| 469 | −# line interface, but use _GZIP, _BZIP2, _LZOP internally. | |
| 470 | −_GZIP := $(GZIP) | |
| 471 | −_BZIP2 := $(BZIP2) | |
| 472 | −_LZOP := $(LZOP) | |
| 473 | − | |
| 474 | −# Reset GZIP, BZIP2, LZOP in this Makefile | |
| 475 | −override GZIP= | |
| 476 | −override BZIP2= | |
| 477 | −override LZOP= | |
| 478 | − | |
| 479 | −# Reset GZIP, BZIP2, LZOP in recursive invocations | |
| 480 | −MAKEOVERRIDES += GZIP= BZIP2= LZOP= | |
| 481 | − | |
| 482 | 468 | CHECKFLAGS := -D__linux__ -Dlinux -D__STDC__ -Dunix -D__unix__ \ |
| 483 | 469 | -Wbitwise -Wno-return-void -Wno-unknown-attribute $(CF) |
| 484 | 470 | NOSTDINC_FLAGS := |
| @@ -526,7 +512,7 @@ CLANG_FLAGS := · 41 unmodified lines | ||
| 526 | 512 | export ARCH SRCARCH CONFIG_SHELL BASH HOSTCC KBUILD_HOSTCFLAGS CROSS_COMPILE LD CC |
| 527 | 513 | export CPP AR NM STRIP OBJCOPY OBJDUMP OBJSIZE READELF PAHOLE LEX YACC AWK INSTALLKERNEL |
| 528 | 514 | export PERL PYTHON PYTHON3 CHECK CHECKFLAGS MAKE UTS_MACHINE HOSTCXX |
| 529 | −export _GZIP _BZIP2 _LZOP LZMA LZ4 XZ | |
| 515 | +export KGZIP KBZIP2 KLZOP LZMA LZ4 XZ | |
| 530 | 516 | export KBUILD_HOSTCXXFLAGS KBUILD_HOSTLDFLAGS KBUILD_HOSTLDLIBS LDFLAGS_MODULE |
| 531 | 517 | |
| 532 | 518 | export KBUILD_CPPFLAGS NOSTDINC_FLAGS LINUXINCLUDE OBJCOPYFLAGS KBUILD_LDFLAGS |
| @@ -1048,7 +1034,7 @@ export mod_strip_cmd · 515 unmodified lines | ||
| 1048 | 1034 | mod_compress_cmd = true |
| 1049 | 1035 | ifdef CONFIG_MODULE_COMPRESS |
| 1050 | 1036 | ifdef CONFIG_MODULE_COMPRESS_GZIP |
| 1051 | − mod_compress_cmd = $(_GZIP) -n -f | |
| 1037 | + mod_compress_cmd = $(KGZIP) -n -f | |
| 1052 | 1038 | endif # CONFIG_MODULE_COMPRESS_GZIP |
| 1053 | 1039 | ifdef CONFIG_MODULE_COMPRESS_XZ |
| 1054 | 1040 | mod_compress_cmd = $(XZ) -f |
| @@ -876,7 +876,7 @@ config VMAP_STACK · 875 unmodified lines | ||
| 876 | 876 | bool "Use a virtually-mapped stack" |
| 877 | 877 | depends on HAVE_ARCH_VMAP_STACK |
| 878 | 878 | depends on !KASAN || KASAN_VMALLOC |
| 879 | − ---help--- | |
| 879 | + help | |
| 880 | 880 | Enable this if you want the use virtually-mapped kernel stacks |
| 881 | 881 | with guard pages. This causes kernel stack overflows to be |
| 882 | 882 | caught immediately rather than causing difficult-to-diagnose |
| @@ -948,7 +948,7 @@ config ARCH_USE_MEMREMAP_PROT · 65 unmodified lines | ||
| 948 | 948 | config LOCK_EVENT_COUNTS |
| 949 | 949 | bool "Locking event counts collection" |
| 950 | 950 | depends on DEBUG_FS |
| 951 | − ---help--- | |
| 951 | + help | |
| 952 | 952 | Enable light-weight counting of various locking related events |
| 953 | 953 | in the system with minimal performance impact. This reduces |
| 954 | 954 | the chance of application behavior change because of timing |
| @@ -83,7 +83,7 @@ menu "System setup" · 82 unmodified lines | ||
| 83 | 83 | choice |
| 84 | 84 | prompt "Alpha system type" |
| 85 | 85 | default ALPHA_GENERIC |
| 86 | − ---help--- | |
| 86 | + help | |
| 87 | 87 | This is the system type of your hardware. A "generic" kernel will |
| 88 | 88 | run on any supported Alpha system. However, if you configure a |
| 89 | 89 | kernel for your specific system, it will be faster and smaller. |
| @@ -480,7 +480,7 @@ config VGA_HOSE · 390 unmodified lines | ||
| 480 | 480 | config ALPHA_QEMU |
| 481 | 481 | bool "Run under QEMU emulation" |
| 482 | 482 | depends on !ALPHA_GENERIC |
| 483 | − ---help--- | |
| 483 | + help | |
| 484 | 484 | Assume the presence of special features supported by QEMU PALcode |
| 485 | 485 | that reduce the overhead of system emulation. |
| 486 | 486 | |
| @@ -495,7 +495,7 @@ config ALPHA_SRM · 8 unmodified lines | ||
| 495 | 495 | bool "Use SRM as bootloader" if ALPHA_CABRIOLET || ALPHA_AVANTI_CH || ALPHA_EB64P || ALPHA_PC164 || ALPHA_TAKARA || ALPHA_EB164 || ALPHA_ALCOR || ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_NAUTILUS || ALPHA_NONAME |
| 496 | 496 | depends on TTY |
| 497 | 497 | default y if ALPHA_JENSEN || ALPHA_MIKASA || ALPHA_SABLE || ALPHA_LYNX || ALPHA_NORITAKE || ALPHA_DP264 || ALPHA_RAWHIDE || ALPHA_EIGER || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_SHARK || ALPHA_MARVEL |
| 498 | − ---help--- | |
| 498 | + help | |
| 499 | 499 | There are two different types of booting firmware on Alphas: SRM, |
| 500 | 500 | which is command line driven, and ARC, which uses menus and arrow |
| 501 | 501 | keys. Details about the Linux/Alpha booting process are contained in |
| @@ -521,7 +521,7 @@ config ARCH_MAY_HAVE_PC_FDC · 19 unmodified lines | ||
| 521 | 521 | config SMP |
| 522 | 522 | bool "Symmetric multi-processing support" |
| 523 | 523 | depends on ALPHA_SABLE || ALPHA_LYNX || ALPHA_RAWHIDE || ALPHA_DP264 || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_GENERIC || ALPHA_SHARK || ALPHA_MARVEL |
| 524 | − ---help--- | |
| 524 | + help | |
| 525 | 525 | This enables support for systems with more than one CPU. If you have |
| 526 | 526 | a system with only one CPU, say N. If you have a system with more |
| 527 | 527 | than one CPU, say Y. |
| @@ -569,7 +569,7 @@ config ALPHA_WTINT · 41 unmodified lines | ||
| 569 | 569 | default n if ALPHA_EV5 || ALPHA_EV56 || (ALPHA_EV4 && !ALPHA_LCA) |
| 570 | 570 | default n if !ALPHA_SRM && !ALPHA_GENERIC |
| 571 | 571 | default y if SMP |
| 572 | − ---help--- | |
| 572 | + help | |
| 573 | 573 | The Wait for Interrupt (WTINT) PALcall attempts to place the CPU |
| 574 | 574 | to sleep until the next interrupt. This may reduce the power |
| 575 | 575 | consumed, and the heat produced by the computer. However, it has |
| @@ -595,7 +595,7 @@ config NODES_SHIFT · 19 unmodified lines | ||
| 595 | 595 | # LARGE_VMALLOC is racy, if you *really* need it then fix it first |
| 596 | 596 | config ALPHA_LARGE_VMALLOC |
| 597 | 597 | bool |
| 598 | − ---help--- | |
| 598 | + help | |
| 599 | 599 | Process creation and other aspects of virtual memory management can |
| 600 | 600 | be streamlined if we restrict the kernel to one PGD for all vmalloc |
| 601 | 601 | allocations. This equates to about 8GB. |
| @@ -614,7 +614,7 @@ config VERBOSE_MCHECK_ON · 12 unmodified lines | ||
| 614 | 614 | int "Verbose Printing Mode (0=off, 1=on, 2=all)" |
| 615 | 615 | depends on VERBOSE_MCHECK |
| 616 | 616 | default 1 |
| 617 | − ---help--- | |
| 617 | + help | |
| 618 | 618 | This option allows the default printing mode to be set, and then |
| 619 | 619 | possibly overridden by a boot command argument. |
| 620 | 620 | |
| @@ -633,7 +633,7 @@ choice · 12 unmodified lines | ||
| 633 | 633 | default HZ_128 if ALPHA_QEMU |
| 634 | 634 | default HZ_1200 if ALPHA_RAWHIDE |
| 635 | 635 | default HZ_1024 |
| 636 | − ---help--- | |
| 636 | + help | |
| 637 | 637 | The frequency at which timer interrupts occur. A high frequency |
| 638 | 638 | minimizes latency, whereas a low frequency minimizes overhead of |
| 639 | 639 | process accounting. The later effect is especially significant |
| @@ -668,7 +668,7 @@ config HZ · 28 unmodified lines | ||
| 668 | 668 | config SRM_ENV |
| 669 | 669 | tristate "SRM environment through procfs" |
| 670 | 670 | depends on PROC_FS |
| 671 | − ---help--- | |
| 671 | + help | |
| 672 | 672 | If you enable this option, a subdirectory inside /proc called |
| 673 | 673 | /proc/srm_environment will give you access to the all important |
| 674 | 674 | SRM environment variables (those which have a name) and also |
| @@ -9,7 +9,7 @@ config ALPHA_LEGACY_START_ADDRESS · 8 unmodified lines | ||
| 9 | 9 | bool "Legacy kernel start address" |
| 10 | 10 | depends on ALPHA_GENERIC |
| 11 | 11 | default n |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | The 2.4 kernel changed the kernel start address from 0x310000 |
| 14 | 14 | to 0x810000 to make room for the Wildfire's larger SRM console. |
| 15 | 15 | Recent consoles on Titan and Marvel machines also require the |
| @@ -348,7 +348,7 @@ config NODES_SHIFT · 347 unmodified lines | ||
| 348 | 348 | default "0" if !DISCONTIGMEM |
| 349 | 349 | default "1" if DISCONTIGMEM |
| 350 | 350 | depends on NEED_MULTIPLE_NODES |
| 351 | − ---help--- | |
| 351 | + help | |
| 352 | 352 | Accessing memory beyond 1GB (with or w/o PAE) requires 2 memory |
| 353 | 353 | zones. |
| 354 | 354 | |
| @@ -1655,7 +1655,7 @@ config UACCESS_WITH_MEMCPY · 1654 unmodified lines | ||
| 1655 | 1655 | config SECCOMP |
| 1656 | 1656 | bool |
| 1657 | 1657 | prompt "Enable seccomp to safely compute untrusted bytecode" |
| 1658 | − ---help--- | |
| 1658 | + help | |
| 1659 | 1659 | This kernel feature is useful for number crunching applications |
| 1660 | 1660 | that may need to compute untrusted bytecode during their |
| 1661 | 1661 | execution. By using pipes or other transports made available to |
| @@ -1963,7 +1963,7 @@ config EFI · 301 unmodified lines | ||
| 1963 | 1963 | select EFI_STUB |
| 1964 | 1964 | select EFI_GENERIC_STUB |
| 1965 | 1965 | select EFI_RUNTIME_WRAPPERS |
| 1966 | − ---help--- | |
| 1966 | + help | |
| 1967 | 1967 | This option provides support for runtime services provided |
| 1968 | 1968 | by UEFI firmware (such as non-volatile variables, realtime |
| 1969 | 1969 | clock, and platform reset). A UEFI stub is also provided to |
| @@ -2005,7 +2005,7 @@ comment "At least one emulation must be selected" · 35 unmodified lines | ||
| 2005 | 2005 | config FPE_NWFPE |
| 2006 | 2006 | bool "NWFPE math emulation" |
| 2007 | 2007 | depends on (!AEABI || OABI_COMPAT) && !THUMB2_KERNEL |
| 2008 | − ---help--- | |
| 2008 | + help | |
| 2009 | 2009 | Say Y to include the NWFPE floating point emulator in the kernel. |
| 2010 | 2010 | This is necessary to run most binaries. Linux does not currently |
| 2011 | 2011 | support floating point hardware so you need to say Y here even if |
| @@ -2029,7 +2029,7 @@ config FPE_NWFPE_XP · 17 unmodified lines | ||
| 2029 | 2029 | config FPE_FASTFPE |
| 2030 | 2030 | bool "FastFPE math emulation (EXPERIMENTAL)" |
| 2031 | 2031 | depends on (!AEABI || OABI_COMPAT) && !CPU_32v3 |
| 2032 | − ---help--- | |
| 2032 | + help | |
| 2033 | 2033 | Say Y here to include the FAST floating point emulator in the kernel. |
| 2034 | 2034 | This is an experimental much faster emulator which now also has full |
| 2035 | 2035 | precision for the mantissa. It does not support any exceptions. |
| @@ -9,7 +9,7 @@ config ARM_PTDUMP_DEBUGFS · 8 unmodified lines | ||
| 9 | 9 | depends on MMU |
| 10 | 10 | select ARM_PTDUMP_CORE |
| 11 | 11 | select DEBUG_FS |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | Say Y here if you want to show the kernel pagetable layout in a |
| 14 | 14 | debugfs file. This information is only useful for kernel developers |
| 15 | 15 | who are working in architecture specific areas of the kernel. |
| @@ -21,7 +21,7 @@ config DEBUG_WX · 5 unmodified lines | ||
| 21 | 21 | bool "Warn on W+X mappings at boot" |
| 22 | 22 | depends on MMU |
| 23 | 23 | select ARM_PTDUMP_CORE |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | Generate a warning if any W+X mappings are found at boot. |
| 26 | 26 | |
| 27 | 27 | This is useful for discovering cases where the kernel is leaving |
| @@ -56,7 +56,7 @@ trap 'rm -f "$XIPIMAGE.tmp"; exit 1' 1 2 3 · 55 unmodified lines | ||
| 56 | 56 | # substitute the data section by a compressed version |
| 57 | 57 | $DD if="$XIPIMAGE" count=$data_start iflag=count_bytes of="$XIPIMAGE.tmp" |
| 58 | 58 | $DD if="$XIPIMAGE" skip=$data_start iflag=skip_bytes | |
| 59 | −$_GZIP -9 >> "$XIPIMAGE.tmp" | |
| 59 | +$KGZIP -9 >> "$XIPIMAGE.tmp" | |
| 60 | 60 | |
| 61 | 61 | # replace kernel binary |
| 62 | 62 | mv -f "$XIPIMAGE.tmp" "$XIPIMAGE" |
| @@ -22,7 +22,7 @@ config ARCH_PERSONAL_SERVER · 21 unmodified lines | ||
| 22 | 22 | select ISA |
| 23 | 23 | select ISA_DMA |
| 24 | 24 | select FORCE_PCI |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | Say Y here if you intend to run this kernel on the Compaq |
| 27 | 27 | Personal Server. |
| 28 | 28 | |
| @@ -1035,7 +1035,7 @@ config CC_HAVE_SHADOW_CALL_STACK · 1034 unmodified lines | ||
| 1035 | 1035 | |
| 1036 | 1036 | config SECCOMP |
| 1037 | 1037 | bool "Enable seccomp to safely compute untrusted bytecode" |
| 1038 | − ---help--- | |
| 1038 | + help | |
| 1039 | 1039 | This kernel feature is useful for number crunching applications |
| 1040 | 1040 | that may need to compute untrusted bytecode during their |
| 1041 | 1041 | execution. By using pipes or other transports made available to |
| @@ -1068,7 +1068,7 @@ config KEXEC · 26 unmodified lines | ||
| 1068 | 1068 | depends on PM_SLEEP_SMP |
| 1069 | 1069 | select KEXEC_CORE |
| 1070 | 1070 | bool "kexec system call" |
| 1071 | − ---help--- | |
| 1071 | + help | |
| 1072 | 1072 | kexec is a system call that implements the ability to shutdown your |
| 1073 | 1073 | current kernel, and to start another kernel. It is like a reboot |
| 1074 | 1074 | but it is independent of the system firmware. And like a reboot |
| @@ -7,7 +7,7 @@ source "virt/lib/Kconfig" · 6 unmodified lines | ||
| 7 | 7 | |
| 8 | 8 | menuconfig VIRTUALIZATION |
| 9 | 9 | bool "Virtualization" |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Say Y here to get to see options for using your Linux host to run |
| 12 | 12 | other operating systems inside virtual machines (guests). |
| 13 | 13 | This option alone does not add any kernel code. |
| @@ -40,7 +40,7 @@ menuconfig KVM · 26 unmodified lines | ||
| 40 | 40 | select HAVE_KVM_VCPU_RUN_PID_CHANGE |
| 41 | 41 | select TASKSTATS |
| 42 | 42 | select TASK_DELAY_ACCT |
| 43 | − ---help--- | |
| 43 | + help | |
| 44 | 44 | Support hosting virtualized guest machines. |
| 45 | 45 | |
| 46 | 46 | If unsure, say N. |
| @@ -53,7 +53,7 @@ config KVM_ARM_PMU · 6 unmodified lines | ||
| 53 | 53 | bool "Virtual Performance Monitoring Unit (PMU) support" |
| 54 | 54 | depends on HW_PERF_EVENTS |
| 55 | 55 | default y |
| 56 | − ---help--- | |
| 56 | + help | |
| 57 | 57 | Adds support for a virtual Performance Monitoring Unit (PMU) in |
| 58 | 58 | virtual machines. |
| 59 | 59 | |
| @@ -31,13 +31,13 @@ config HEXAGON · 30 unmodified lines | ||
| 31 | 31 | select GENERIC_CLOCKEVENTS_BROADCAST |
| 32 | 32 | select MODULES_USE_ELF_RELA |
| 33 | 33 | select GENERIC_CPU_DEVICES |
| 34 | − ---help--- | |
| 34 | + help | |
| 35 | 35 | Qualcomm Hexagon is a processor architecture designed for high |
| 36 | 36 | performance and low power across a wide variety of applications. |
| 37 | 37 | |
| 38 | 38 | config HEXAGON_PHYS_OFFSET |
| 39 | 39 | def_bool y |
| 40 | − ---help--- | |
| 40 | + help | |
| 41 | 41 | Platforms that don't load the kernel at zero set this. |
| 42 | 42 | |
| 43 | 43 | config FRAME_POINTER |
| @@ -83,7 +83,7 @@ choice · 39 unmodified lines | ||
| 83 | 83 | |
| 84 | 84 | config HEXAGON_COMET |
| 85 | 85 | bool "Comet Board" |
| 86 | − ---help--- | |
| 86 | + help | |
| 87 | 87 | Support for the Comet platform. |
| 88 | 88 | |
| 89 | 89 | endchoice |
| @@ -104,7 +104,7 @@ config CMDLINE · 14 unmodified lines | ||
| 104 | 104 | |
| 105 | 105 | config SMP |
| 106 | 106 | bool "Multi-Processing support" |
| 107 | − ---help--- | |
| 107 | + help | |
| 108 | 108 | Enables SMP support in the kernel. If unsure, say "Y" |
| 109 | 109 | |
| 110 | 110 | config NR_CPUS |
| @@ -112,7 +112,7 @@ config NR_CPUS · 1 unmodified line | ||
| 112 | 112 | range 2 6 if SMP |
| 113 | 113 | default "1" if !SMP |
| 114 | 114 | default "6" if SMP |
| 115 | − ---help--- | |
| 115 | + help | |
| 116 | 116 | This allows you to specify the maximum number of CPUs which this |
| 117 | 117 | kernel will support. The maximum supported value is 6 and the |
| 118 | 118 | minimum value which makes sense is 2. |
| @@ -123,7 +123,7 @@ config NR_CPUS · 4 unmodified lines | ||
| 123 | 123 | choice |
| 124 | 124 | prompt "Kernel page size" |
| 125 | 125 | default PAGE_SIZE_4KB |
| 126 | − ---help--- | |
| 126 | + help | |
| 127 | 127 | Changes the default page size; use with caution. |
| 128 | 128 | |
| 129 | 129 | config PAGE_SIZE_4KB |
| @@ -243,7 +243,7 @@ config HOTPLUG_CPU · 242 unmodified lines | ||
| 243 | 243 | bool "Support for hot-pluggable CPUs" |
| 244 | 244 | depends on SMP |
| 245 | 245 | default n |
| 246 | − ---help--- | |
| 246 | + help | |
| 247 | 247 | Say Y here to experiment with turning CPUs off and on. CPUs |
| 248 | 248 | can be controlled through /sys/devices/system/cpu/cpu#. |
| 249 | 249 | Say N if you want to disable CPU hotplug. |
| @@ -266,7 +266,7 @@ config PERMIT_BSP_REMOVE · 16 unmodified lines | ||
| 266 | 266 | bool "Support removal of Bootstrap Processor" |
| 267 | 267 | depends on HOTPLUG_CPU |
| 268 | 268 | default n |
| 269 | − ---help--- | |
| 269 | + help | |
| 270 | 270 | Say Y here if your platform SAL will support removal of BSP with HOTPLUG_CPU |
| 271 | 271 | support. |
| 272 | 272 | |
| @@ -274,7 +274,7 @@ config FORCE_CPEI_RETARGET · 1 unmodified line | ||
| 274 | 274 | bool "Force assumption that CPEI can be re-targeted" |
| 275 | 275 | depends on PERMIT_BSP_REMOVE |
| 276 | 276 | default n |
| 277 | − ---help--- | |
| 277 | + help | |
| 278 | 278 | Say Y if you need to force the assumption that CPEI can be re-targeted to |
| 279 | 279 | any cpu in the system. This hint is available via ACPI 3.0 specifications. |
| 280 | 280 | Tiger4 systems are capable of re-directing CPEI to any CPU other than BSP. |
| @@ -40,7 +40,7 @@ $(error Sorry, you need a newer version of the assember, one that is built from · 39 unmodified lines | ||
| 40 | 40 | endif |
| 41 | 41 | |
| 42 | 42 | quiet_cmd_gzip = GZIP $@ |
| 43 | −cmd_gzip = cat $(real-prereqs) | $(_GZIP) -n -f -9 > $@ | |
| 43 | +cmd_gzip = cat $(real-prereqs) | $(KGZIP) -n -f -9 > $@ | |
| 44 | 44 | |
| 45 | 45 | quiet_cmd_objcopy = OBJCOPY $@ |
| 46 | 46 | cmd_objcopy = $(OBJCOPY) $(OBJCOPYFLAGS) $(OBJCOPYFLAGS_$(@F)) $< $@ |
| @@ -343,7 +343,7 @@ config M68KFPU_EMU_ONLY · 342 unmodified lines | ||
| 343 | 343 | config ADVANCED |
| 344 | 344 | bool "Advanced configuration options" |
| 345 | 345 | depends on MMU |
| 346 | − ---help--- | |
| 346 | + help | |
| 347 | 347 | This gives you access to some advanced options for the CPU. The |
| 348 | 348 | defaults should be fine for most users, but these options may make |
| 349 | 349 | it possible for you to improve performance somewhat if you know what |
| @@ -358,7 +358,7 @@ config ADVANCED · 8 unmodified lines | ||
| 358 | 358 | config RMW_INSNS |
| 359 | 359 | bool "Use read-modify-write instructions" |
| 360 | 360 | depends on ADVANCED |
| 361 | − ---help--- | |
| 361 | + help | |
| 362 | 362 | This allows to use certain instructions that work with indivisible |
| 363 | 363 | read-modify-write bus cycles. While this is faster than the |
| 364 | 364 | workaround of disabling interrupts, it can conflict with DMA |
| @@ -386,7 +386,7 @@ config ARCH_DISCONTIGMEM_ENABLE · 21 unmodified lines | ||
| 386 | 386 | config 060_WRITETHROUGH |
| 387 | 387 | bool "Use write-through caching for 68060 supervisor accesses" |
| 388 | 388 | depends on ADVANCED && M68060 |
| 389 | − ---help--- | |
| 389 | + help | |
| 390 | 390 | The 68060 generally uses copyback caching of recently accessed data. |
| 391 | 391 | Copyback caching means that memory writes will be held in an on-chip |
| 392 | 392 | cache and only written back to memory some time later. Saying Y |
| @@ -59,7 +59,7 @@ config NFETH · 58 unmodified lines | ||
| 59 | 59 | config ATARI_ETHERNAT |
| 60 | 60 | bool "Atari EtherNAT Ethernet support" |
| 61 | 61 | depends on ATARI |
| 62 | − ---help--- | |
| 62 | + help | |
| 63 | 63 | Say Y to include support for the EtherNAT network adapter for the |
| 64 | 64 | CT/60 extension port. |
| 65 | 65 | |
| @@ -69,7 +69,7 @@ config ATARI_ETHERNAT · 3 unmodified lines | ||
| 69 | 69 | config ATARI_ETHERNEC |
| 70 | 70 | bool "Atari EtherNEC Ethernet support" |
| 71 | 71 | depends on ATARI_ROM_ISA |
| 72 | − ---help--- | |
| 72 | + help | |
| 73 | 73 | Say Y to include support for the EtherNEC network adapter for the |
| 74 | 74 | ROM port. The driver works by polling instead of interrupts, so it |
| 75 | 75 | is quite slow. |
| @@ -120,7 +120,7 @@ config HPAPCI · 44 unmodified lines | ||
| 120 | 120 | config SERIAL_CONSOLE |
| 121 | 121 | bool "Support for serial port console" |
| 122 | 122 | depends on AMIGA_BUILTIN_SERIAL=y |
| 123 | − ---help--- | |
| 123 | + help | |
| 124 | 124 | If you say Y here, it will be possible to use a serial port as the |
| 125 | 125 | system console (the system console is the device which receives all |
| 126 | 126 | kernel messages and warnings and which allows logins in single user |
| @@ -437,7 +437,7 @@ config ROMSIZE · 436 unmodified lines | ||
| 437 | 437 | |
| 438 | 438 | choice |
| 439 | 439 | prompt "Kernel executes from" |
| 440 | − ---help--- | |
| 440 | + help | |
| 441 | 441 | Choose the memory type that the kernel will be running in. |
| 442 | 442 | |
| 443 | 443 | config RAMKERNEL |
| @@ -135,10 +135,10 @@ vmlinux.gz: vmlinux · 134 unmodified lines | ||
| 135 | 135 | ifndef CONFIG_KGDB |
| 136 | 136 | cp vmlinux vmlinux.tmp |
| 137 | 137 | $(STRIP) vmlinux.tmp |
| 138 | − $(_GZIP) -9c vmlinux.tmp >vmlinux.gz | |
| 138 | + $(KGZIP) -9c vmlinux.tmp >vmlinux.gz | |
| 139 | 139 | rm vmlinux.tmp |
| 140 | 140 | else |
| 141 | − $(_GZIP) -9c vmlinux >vmlinux.gz | |
| 141 | + $(KGZIP) -9c vmlinux >vmlinux.gz | |
| 142 | 142 | endif |
| 143 | 143 | |
| 144 | 144 | bzImage: vmlinux.bz2 |
| @@ -148,10 +148,10 @@ vmlinux.bz2: vmlinux · 3 unmodified lines | ||
| 148 | 148 | ifndef CONFIG_KGDB |
| 149 | 149 | cp vmlinux vmlinux.tmp |
| 150 | 150 | $(STRIP) vmlinux.tmp |
| 151 | − $(_BZIP2) -1c vmlinux.tmp >vmlinux.bz2 | |
| 151 | + $(KBZIP2) -1c vmlinux.tmp >vmlinux.bz2 | |
| 152 | 152 | rm vmlinux.tmp |
| 153 | 153 | else |
| 154 | − $(_BZIP2) -1c vmlinux >vmlinux.bz2 | |
| 154 | + $(KBZIP2) -1c vmlinux >vmlinux.bz2 | |
| 155 | 155 | endif |
| 156 | 156 | |
| 157 | 157 | archclean: |
| @@ -2742,7 +2742,7 @@ config RELOCATION_TABLE_SIZE · 2741 unmodified lines | ||
| 2742 | 2742 | depends on RELOCATABLE |
| 2743 | 2743 | range 0x0 0x01000000 |
| 2744 | 2744 | default "0x00100000" |
| 2745 | − ---help--- | |
| 2745 | + help | |
| 2746 | 2746 | A table of relocation data will be appended to the kernel binary |
| 2747 | 2747 | and parsed at boot to fix up the relocated kernel. |
| 2748 | 2748 | |
| @@ -2756,7 +2756,7 @@ config RELOCATION_TABLE_SIZE · 7 unmodified lines | ||
| 2756 | 2756 | config RANDOMIZE_BASE |
| 2757 | 2757 | bool "Randomize the address of the kernel image" |
| 2758 | 2758 | depends on RELOCATABLE |
| 2759 | − ---help--- | |
| 2759 | + help | |
| 2760 | 2760 | Randomizes the physical and virtual address at which the |
| 2761 | 2761 | kernel image is loaded, as a security feature that |
| 2762 | 2762 | deters exploit attempts relying on knowledge of the location |
| @@ -2774,7 +2774,7 @@ config RANDOMIZE_BASE_MAX_OFFSET · 11 unmodified lines | ||
| 2774 | 2774 | range 0x0 0x40000000 if EVA || 64BIT |
| 2775 | 2775 | range 0x0 0x08000000 |
| 2776 | 2776 | default "0x01000000" |
| 2777 | − ---help--- | |
| 2777 | + help | |
| 2778 | 2778 | When kASLR is active, this provides the maximum offset that will |
| 2779 | 2779 | be applied to the kernel image. It should be set according to the |
| 2780 | 2780 | amount of physical RAM available in the target system minus |
| @@ -6,7 +6,7 @@ source "virt/kvm/Kconfig" · 5 unmodified lines | ||
| 6 | 6 | |
| 7 | 7 | menuconfig VIRTUALIZATION |
| 8 | 8 | bool "Virtualization" |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Say Y here to get to see options for using your Linux host to run |
| 11 | 11 | other operating systems inside virtual machines (guests). |
| 12 | 12 | This option alone does not add any kernel code. |
| @@ -27,7 +27,7 @@ config KVM · 14 unmodified lines | ||
| 27 | 27 | select KVM_MMIO |
| 28 | 28 | select MMU_NOTIFIER |
| 29 | 29 | select SRCU |
| 30 | − ---help--- | |
| 30 | + help | |
| 31 | 31 | Support for hosting Guest kernels. |
| 32 | 32 | |
| 33 | 33 | choice |
| @@ -37,7 +37,7 @@ choice · 3 unmodified lines | ||
| 37 | 37 | |
| 38 | 38 | config KVM_MIPS_TE |
| 39 | 39 | bool "Trap & Emulate" |
| 40 | − ---help--- | |
| 40 | + help | |
| 41 | 41 | Use trap and emulate to virtualize 32-bit guests in user mode. This |
| 42 | 42 | does not require any special hardware Virtualization support beyond |
| 43 | 43 | standard MIPS32/64 r2 or later, but it does require the guest kernel |
| @@ -46,7 +46,7 @@ config KVM_MIPS_TE · 2 unmodified lines | ||
| 46 | 46 | |
| 47 | 47 | config KVM_MIPS_VZ |
| 48 | 48 | bool "MIPS Virtualization (VZ) ASE" |
| 49 | − ---help--- | |
| 49 | + help | |
| 50 | 50 | Use the MIPS Virtualization (VZ) ASE to virtualize guests. This |
| 51 | 51 | supports running unmodified guest kernels (with CONFIG_KVM_GUEST=n), |
| 52 | 52 | but requires hardware support. |
| @@ -57,7 +57,7 @@ config KVM_MIPS_DYN_TRANS · 4 unmodified lines | ||
| 57 | 57 | bool "KVM/MIPS: Dynamic binary translation to reduce traps" |
| 58 | 58 | depends on KVM_MIPS_TE |
| 59 | 59 | default y |
| 60 | − ---help--- | |
| 60 | + help | |
| 61 | 61 | When running in Trap & Emulate mode patch privileged |
| 62 | 62 | instructions to reduce the number of traps. |
| 63 | 63 | |
| @@ -66,7 +66,7 @@ config KVM_MIPS_DYN_TRANS · 2 unmodified lines | ||
| 66 | 66 | config KVM_MIPS_DEBUG_COP0_COUNTERS |
| 67 | 67 | bool "Maintain counters for COP0 accesses" |
| 68 | 68 | depends on KVM |
| 69 | − ---help--- | |
| 69 | + help | |
| 70 | 70 | Maintain statistics for Guest COP0 accesses. |
| 71 | 71 | A histogram of COP0 accesses is printed when the VM is |
| 72 | 72 | shutdown. |
| @@ -147,7 +147,7 @@ choice · 146 unmodified lines | ||
| 147 | 147 | |
| 148 | 148 | config PA7000 |
| 149 | 149 | bool "PA7000/PA7100" |
| 150 | − ---help--- | |
| 150 | + help | |
| 151 | 151 | This is the processor type of your CPU. This information is |
| 152 | 152 | used for optimizing purposes. In order to compile a kernel |
| 153 | 153 | that can run on all 32-bit PA CPUs (albeit not optimally fast), |
| @@ -275,7 +275,7 @@ config PARISC_SELF_EXTRACT · 121 unmodified lines | ||
| 275 | 275 | |
| 276 | 276 | config SMP |
| 277 | 277 | bool "Symmetric multi-processing support" |
| 278 | − ---help--- | |
| 278 | + help | |
| 279 | 279 | This enables support for systems with more than one CPU. If you have |
| 280 | 280 | a system with only one CPU, say N. If you have a system with more |
| 281 | 281 | than one CPU, say Y. |
| @@ -382,7 +382,7 @@ source "drivers/parisc/Kconfig" · 100 unmodified lines | ||
| 382 | 382 | config SECCOMP |
| 383 | 383 | def_bool y |
| 384 | 384 | prompt "Enable seccomp to safely compute untrusted bytecode" |
| 385 | − ---help--- | |
| 385 | + help | |
| 386 | 386 | This kernel feature is useful for number crunching applications |
| 387 | 387 | that may need to compute untrusted bytecode during their |
| 388 | 388 | execution. By using pipes or other transports made available to |
| @@ -162,7 +162,7 @@ vmlinuz: bzImage · 161 unmodified lines | ||
| 162 | 162 | $(OBJCOPY) $(boot)/bzImage $@ |
| 163 | 163 | else |
| 164 | 164 | vmlinuz: vmlinux |
| 165 | − @$(_GZIP) -cf -9 $< > $@ | |
| 165 | + @$(KGZIP) -cf -9 $< > $@ | |
| 166 | 166 | endif |
| 167 | 167 | |
| 168 | 168 | install: |
| @@ -7,7 +7,7 @@ source "virt/kvm/Kconfig" · 6 unmodified lines | ||
| 7 | 7 | |
| 8 | 8 | menuconfig VIRTUALIZATION |
| 9 | 9 | bool "Virtualization" |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Say Y here to get to see options for using your Linux host to run |
| 12 | 12 | other operating systems inside virtual machines (guests). |
| 13 | 13 | This option alone does not add any kernel code. |
| @@ -54,7 +54,7 @@ config KVM_BOOK3S_32 · 40 unmodified lines | ||
| 54 | 54 | select KVM |
| 55 | 55 | select KVM_BOOK3S_32_HANDLER |
| 56 | 56 | select KVM_BOOK3S_PR_POSSIBLE |
| 57 | − ---help--- | |
| 57 | + help | |
| 58 | 58 | Support running unmodified book3s_32 guest kernels |
| 59 | 59 | in virtual machines on book3s_32 host processors. |
| 60 | 60 | |
| @@ -70,7 +70,7 @@ config KVM_BOOK3S_64 · 9 unmodified lines | ||
| 70 | 70 | select KVM |
| 71 | 71 | select KVM_BOOK3S_PR_POSSIBLE if !KVM_BOOK3S_HV_POSSIBLE |
| 72 | 72 | select SPAPR_TCE_IOMMU if IOMMU_SUPPORT && (PPC_PSERIES || PPC_POWERNV) |
| 73 | − ---help--- | |
| 73 | + help | |
| 74 | 74 | Support running unmodified book3s_64 and book3s_32 guest kernels |
| 75 | 75 | in virtual machines on book3s_64 host processors. |
| 76 | 76 | |
| @@ -85,7 +85,7 @@ config KVM_BOOK3S_64_HV · 8 unmodified lines | ||
| 85 | 85 | select KVM_BOOK3S_HV_POSSIBLE |
| 86 | 86 | select MMU_NOTIFIER |
| 87 | 87 | select CMA |
| 88 | − ---help--- | |
| 88 | + help | |
| 89 | 89 | Support running unmodified book3s_64 guest kernels in |
| 90 | 90 | virtual machines on POWER7 and newer processors that have |
| 91 | 91 | hypervisor mode available to the host. |
| @@ -104,7 +104,7 @@ config KVM_BOOK3S_64_PR · 12 unmodified lines | ||
| 104 | 104 | tristate "KVM support without using hypervisor mode in host" |
| 105 | 105 | depends on KVM_BOOK3S_64 |
| 106 | 106 | select KVM_BOOK3S_PR_POSSIBLE |
| 107 | − ---help--- | |
| 107 | + help | |
| 108 | 108 | Support running guest kernels in virtual machines on processors |
| 109 | 109 | without using hypervisor mode in the host, by running the |
| 110 | 110 | guest in user mode (problem state) and emulating all |
| @@ -119,7 +119,7 @@ config KVM_BOOK3S_64_PR · 8 unmodified lines | ||
| 119 | 119 | config KVM_BOOK3S_HV_EXIT_TIMING |
| 120 | 120 | bool "Detailed timing for hypervisor real-mode code" |
| 121 | 121 | depends on KVM_BOOK3S_HV_POSSIBLE && DEBUG_FS |
| 122 | − ---help--- | |
| 122 | + help | |
| 123 | 123 | Calculate time taken for each vcpu in the real-mode guest entry, |
| 124 | 124 | exit, and interrupt handling code, plus time spent in the guest |
| 125 | 125 | and in nap mode due to idle (cede) while other threads are still |
| @@ -136,7 +136,7 @@ config KVM_BOOKE_HV · 10 unmodified lines | ||
| 136 | 136 | config KVM_EXIT_TIMING |
| 137 | 137 | bool "Detailed exit timing" |
| 138 | 138 | depends on KVM_E500V2 || KVM_E500MC |
| 139 | − ---help--- | |
| 139 | + help | |
| 140 | 140 | Calculate elapsed time for every exit/enter cycle. A per-vcpu |
| 141 | 141 | report is available in debugfs kvm/vm#_vcpu#_timing. |
| 142 | 142 | The overhead is relatively small, however it is not recommended for |
| @@ -150,7 +150,7 @@ config KVM_E500V2 · 7 unmodified lines | ||
| 150 | 150 | select KVM |
| 151 | 151 | select KVM_MMIO |
| 152 | 152 | select MMU_NOTIFIER |
| 153 | − ---help--- | |
| 153 | + help | |
| 154 | 154 | Support running unmodified E500 guest kernels in virtual machines on |
| 155 | 155 | E500v2 host processors. |
| 156 | 156 | |
| @@ -166,7 +166,7 @@ config KVM_E500MC · 9 unmodified lines | ||
| 166 | 166 | select KVM_MMIO |
| 167 | 167 | select KVM_BOOKE_HV |
| 168 | 168 | select MMU_NOTIFIER |
| 169 | − ---help--- | |
| 169 | + help | |
| 170 | 170 | Support running unmodified E500MC/E5500/E6500 guest kernels in |
| 171 | 171 | virtual machines on E500MC/E5500/E6500 host processors. |
| 172 | 172 | |
| @@ -194,7 +194,7 @@ config KVM_XICS · 21 unmodified lines | ||
| 194 | 194 | select HAVE_KVM_IRQCHIP |
| 195 | 195 | select HAVE_KVM_IRQFD |
| 196 | 196 | default y |
| 197 | − ---help--- | |
| 197 | + help | |
| 198 | 198 | Include support for the XICS (eXternal Interrupt Controller |
| 199 | 199 | Specification) interrupt controller architecture used on |
| 200 | 200 | IBM POWER (pSeries) servers. |
| @@ -24,7 +24,7 @@ source "arch/powerpc/platforms/amigaone/Kconfig" · 23 unmodified lines | ||
| 24 | 24 | config KVM_GUEST |
| 25 | 25 | bool "KVM Guest support" |
| 26 | 26 | select EPAPR_PARAVIRT |
| 27 | − ---help--- | |
| 27 | + help | |
| 28 | 28 | This option enables various optimizations for running under the KVM |
| 29 | 29 | hypervisor. Overhead for the kernel when not running inside KVM should |
| 30 | 30 | be minimal. |
| @@ -230,7 +230,7 @@ config TAU · 199 unmodified lines | ||
| 230 | 230 | config TAU_INT |
| 231 | 231 | bool "Interrupt driven TAU driver (DANGEROUS)" |
| 232 | 232 | depends on TAU |
| 233 | − ---help--- | |
| 233 | + help | |
| 234 | 234 | The TAU supports an interrupt driven mode which causes an interrupt |
| 235 | 235 | whenever the temperature goes out of range. This is the fastest way |
| 236 | 236 | to get notified the temp has exceeded a range. With this option off, |
| @@ -246,7 +246,7 @@ config TAU_INT · 9 unmodified lines | ||
| 246 | 246 | config TAU_AVERAGE |
| 247 | 247 | bool "Average high and low temp" |
| 248 | 248 | depends on TAU |
| 249 | − ---help--- | |
| 249 | + help | |
| 250 | 250 | The TAU hardware can compare the temperature to an upper and lower |
| 251 | 251 | bound. The default behavior is to show both the upper and lower |
| 252 | 252 | bound in /proc/cpuinfo. If the range is large, the temperature is |
| @@ -280,7 +280,7 @@ config PHYS_64BIT · 279 unmodified lines | ||
| 280 | 280 | bool 'Large physical address support' if E500 || PPC_86xx |
| 281 | 281 | depends on (44x || E500 || PPC_86xx) && !PPC_83xx && !PPC_82xx |
| 282 | 282 | select PHYS_ADDR_T_64BIT |
| 283 | − ---help--- | |
| 283 | + help | |
| 284 | 284 | This option enables kernel support for larger than 32-bit physical |
| 285 | 285 | addresses. This feature may not be available on all cores. |
| 286 | 286 | |
| @@ -293,7 +293,7 @@ config PHYS_64BIT · 6 unmodified lines | ||
| 293 | 293 | config ALTIVEC |
| 294 | 294 | bool "AltiVec Support" |
| 295 | 295 | depends on PPC_BOOK3S_32 || PPC_BOOK3S_64 || (PPC_E500MC && PPC64) |
| 296 | − ---help--- | |
| 296 | + help | |
| 297 | 297 | This option enables kernel support for the Altivec extensions to the |
| 298 | 298 | PowerPC processor. The kernel currently supports saving and restoring |
| 299 | 299 | altivec registers, and turning on the 'altivec enable' bit so user |
| @@ -309,7 +309,7 @@ config ALTIVEC · 9 unmodified lines | ||
| 309 | 309 | config VSX |
| 310 | 310 | bool "VSX Support" |
| 311 | 311 | depends on PPC_BOOK3S_64 && ALTIVEC && PPC_FPU |
| 312 | − ---help--- | |
| 312 | + help | |
| 313 | 313 | |
| 314 | 314 | This option enables kernel support for the Vector Scaler extensions |
| 315 | 315 | to the PowerPC processor. The kernel currently supports saving and |
| @@ -330,7 +330,7 @@ config SPE · 14 unmodified lines | ||
| 330 | 330 | bool "SPE Support" |
| 331 | 331 | depends on SPE_POSSIBLE |
| 332 | 332 | default y |
| 333 | − ---help--- | |
| 333 | + help | |
| 334 | 334 | This option enables kernel support for the Signal Processing |
| 335 | 335 | Extensions (SPE) to the PowerPC processor. The kernel currently |
| 336 | 336 | supports saving and restoring SPE registers, and turning on the |
| @@ -446,7 +446,7 @@ config SMP · 109 unmodified lines | ||
| 446 | 446 | depends on PPC_BOOK3S || PPC_BOOK3E || FSL_BOOKE || PPC_47x |
| 447 | 447 | select GENERIC_IRQ_MIGRATION |
| 448 | 448 | bool "Symmetric multi-processing support" if !FORCE_SMP |
| 449 | − ---help--- | |
| 449 | + help | |
| 450 | 450 | This enables support for systems with more than one CPU. If you have |
| 451 | 451 | a system with only one CPU, say N. If you have a system with more |
| 452 | 452 | than one CPU, say Y. Note that the kernel does not currently |
| @@ -696,7 +696,7 @@ menu "I/O subsystem" · 695 unmodified lines | ||
| 696 | 696 | config QDIO |
| 697 | 697 | def_tristate y |
| 698 | 698 | prompt "QDIO support" |
| 699 | − ---help--- | |
| 699 | + help | |
| 700 | 700 | This driver provides the Queued Direct I/O base support for |
| 701 | 701 | IBM System z. |
| 702 | 702 | |
| @@ -7,7 +7,7 @@ config S390_PTDUMP · 6 unmodified lines | ||
| 7 | 7 | bool "Export kernel pagetable layout to userspace via debugfs" |
| 8 | 8 | depends on DEBUG_KERNEL |
| 9 | 9 | select DEBUG_FS |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Say Y here if you want to show the kernel pagetable layout in a |
| 12 | 12 | debugfs file. This information is only useful for kernel developers |
| 13 | 13 | who are working in architecture specific areas of the kernel. |
| @@ -7,7 +7,7 @@ source "virt/kvm/Kconfig" · 6 unmodified lines | ||
| 7 | 7 | menuconfig VIRTUALIZATION |
| 8 | 8 | def_bool y |
| 9 | 9 | prompt "KVM" |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Say Y here to get to see options for using your Linux host to run other |
| 12 | 12 | operating systems inside virtual machines (guests). |
| 13 | 13 | This option alone does not add any kernel code. |
| @@ -33,7 +33,7 @@ config KVM · 19 unmodified lines | ||
| 33 | 33 | select HAVE_KVM_NO_POLL |
| 34 | 34 | select SRCU |
| 35 | 35 | select KVM_VFIO |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | Support hosting paravirtualized guest machines using the SIE |
| 38 | 38 | virtualization capability on the mainframe. This should work |
| 39 | 39 | on any 64bit machine. |
| @@ -49,7 +49,7 @@ config KVM · 9 unmodified lines | ||
| 49 | 49 | config KVM_S390_UCONTROL |
| 50 | 50 | bool "Userspace controlled virtual machines" |
| 51 | 51 | depends on KVM |
| 52 | − ---help--- | |
| 52 | + help | |
| 53 | 53 | Allow CAP_SYS_ADMIN users to create KVM virtual machines that are |
| 54 | 54 | controlled by userspace. |
| 55 | 55 | |
| @@ -588,7 +588,7 @@ config KEXEC_JUMP · 587 unmodified lines | ||
| 588 | 588 | config PHYSICAL_START |
| 589 | 589 | hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP) |
| 590 | 590 | default MEMORY_START |
| 591 | − ---help--- | |
| 591 | + help | |
| 592 | 592 | This gives the physical address where the kernel is loaded |
| 593 | 593 | and is ordinarily the same as MEMORY_START. |
| 594 | 594 | |
| @@ -615,7 +615,7 @@ config SECCOMP · 20 unmodified lines | ||
| 615 | 615 | config SMP |
| 616 | 616 | bool "Symmetric multi-processing support" |
| 617 | 617 | depends on SYS_SUPPORTS_SMP |
| 618 | − ---help--- | |
| 618 | + help | |
| 619 | 619 | This enables support for systems with more than one CPU. If you have |
| 620 | 620 | a system with only one CPU, say N. If you have a system with more |
| 621 | 621 | than one CPU, say Y. |
| @@ -11,7 +11,7 @@ choice · 10 unmodified lines | ||
| 11 | 11 | |
| 12 | 12 | config HD64461 |
| 13 | 13 | bool "Hitachi HD64461 companion chip support" |
| 14 | − ---help--- | |
| 14 | + help | |
| 15 | 15 | The Hitachi HD64461 provides an interface for |
| 16 | 16 | the SH7709 CPU, supporting a LCD controller, |
| 17 | 17 | CRT color controller, IrDA up to 4 Mbps, and a |
| @@ -44,7 +44,7 @@ config FORCE_MAX_ZONEORDER · 43 unmodified lines | ||
| 44 | 44 | config MEMORY_START |
| 45 | 45 | hex "Physical memory start address" |
| 46 | 46 | default "0x08000000" |
| 47 | − ---help--- | |
| 47 | + help | |
| 48 | 48 | Computers built with Hitachi SuperH processors always |
| 49 | 49 | map the ROM starting at address zero. But the processor |
| 50 | 50 | does not specify the range that RAM takes. |
| @@ -159,7 +159,7 @@ menu "Processor type and features" · 158 unmodified lines | ||
| 159 | 159 | |
| 160 | 160 | config SMP |
| 161 | 161 | bool "Symmetric multi-processing support" |
| 162 | − ---help--- | |
| 162 | + help | |
| 163 | 163 | This enables support for systems with more than one CPU. If you have |
| 164 | 164 | a system with only one CPU, say N. If you have a system with more |
| 165 | 165 | than one CPU, say Y. |
| @@ -366,7 +366,7 @@ config SERIAL_CONSOLE · 200 unmodified lines | ||
| 366 | 366 | bool |
| 367 | 367 | depends on SPARC32 |
| 368 | 368 | default y |
| 369 | − ---help--- | |
| 369 | + help | |
| 370 | 370 | If you say Y here, it will be possible to use a serial port as the |
| 371 | 371 | system console (the system console is the device which receives all |
| 372 | 372 | kernel messages and warnings and which allows logins in single user |
| @@ -393,7 +393,7 @@ config SPARC_LEON · 20 unmodified lines | ||
| 393 | 393 | select USB_EHCI_BIG_ENDIAN_DESC |
| 394 | 394 | select USB_UHCI_BIG_ENDIAN_MMIO |
| 395 | 395 | select USB_UHCI_BIG_ENDIAN_DESC |
| 396 | − ---help--- | |
| 396 | + help | |
| 397 | 397 | If you say Y here if you are running on a SPARC-LEON processor. |
| 398 | 398 | The LEON processor is a synthesizable VHDL model of the |
| 399 | 399 | SPARC-v8 standard. LEON is part of the GRLIB collection of |
| @@ -407,7 +407,7 @@ menu "U-Boot options" · 7 unmodified lines | ||
| 407 | 407 | config UBOOT_LOAD_ADDR |
| 408 | 408 | hex "uImage Load Address" |
| 409 | 409 | default 0x40004000 |
| 410 | − ---help--- | |
| 410 | + help | |
| 411 | 411 | U-Boot kernel load address, the address in physical address space |
| 412 | 412 | where u-boot will place the Linux kernel before booting it. |
| 413 | 413 | This address is normally the base address of main memory + 0x4000. |
| @@ -415,7 +415,7 @@ config UBOOT_LOAD_ADDR · 1 unmodified line | ||
| 415 | 415 | config UBOOT_FLASH_ADDR |
| 416 | 416 | hex "uImage.o Load Address" |
| 417 | 417 | default 0x00080000 |
| 418 | − ---help--- | |
| 418 | + help | |
| 419 | 419 | Optional setting only affecting the uImage.o ELF-image used to |
| 420 | 420 | download the uImage file to the target using a ELF-loader other than |
| 421 | 421 | U-Boot. It may for example be used to download an uImage to FLASH with |
| @@ -424,7 +424,7 @@ config UBOOT_FLASH_ADDR · 2 unmodified lines | ||
| 424 | 424 | config UBOOT_ENTRY_ADDR |
| 425 | 425 | hex "uImage Entry Address" |
| 426 | 426 | default 0xf0004000 |
| 427 | − ---help--- | |
| 427 | + help | |
| 428 | 428 | Do not change this unless you know what you're doing. This is |
| 429 | 429 | hardcoded by the SPARC32 and LEON port. |
| 430 | 430 | |
| @@ -179,7 +179,7 @@ config PGTABLE_LEVELS · 178 unmodified lines | ||
| 179 | 179 | config SECCOMP |
| 180 | 180 | def_bool y |
| 181 | 181 | prompt "Enable seccomp to safely compute untrusted bytecode" |
| 182 | − ---help--- | |
| 182 | + help | |
| 183 | 183 | This kernel feature is useful for number crunching applications |
| 184 | 184 | that may need to compute untrusted bytecode during their |
| 185 | 185 | execution. By using pipes or other transports made available to |
| @@ -30,7 +30,7 @@ config GCOV · 29 unmodified lines | ||
| 30 | 30 | config EARLY_PRINTK |
| 31 | 31 | bool "Early printk" |
| 32 | 32 | default y |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | Write kernel log output directly to stdout. |
| 35 | 35 | |
| 36 | 36 | This is useful for kernel debugging when your machine crashes very |
| @@ -3,7 +3,7 @@ · 2 unmodified lines | ||
| 3 | 3 | config 64BIT |
| 4 | 4 | bool "64-bit kernel" if "$(ARCH)" = "x86" |
| 5 | 5 | default "$(ARCH)" != "i386" |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | Say yes to build a 64-bit kernel - formerly known as x86_64 |
| 8 | 8 | Say no to build a 32-bit kernel - formerly known as i386 |
| 9 | 9 | |
| @@ -386,7 +386,7 @@ config ZONE_DMA · 376 unmodified lines | ||
| 386 | 386 | |
| 387 | 387 | config SMP |
| 388 | 388 | bool "Symmetric multi-processing support" |
| 389 | − ---help--- | |
| 389 | + help | |
| 390 | 390 | This enables support for systems with more than one CPU. If you have |
| 391 | 391 | a system with only one CPU, say N. If you have a system with more |
| 392 | 392 | than one CPU, say Y. |
| @@ -415,7 +415,7 @@ config SMP · 22 unmodified lines | ||
| 415 | 415 | config X86_FEATURE_NAMES |
| 416 | 416 | bool "Processor feature human-readable names" if EMBEDDED |
| 417 | 417 | default y |
| 418 | − ---help--- | |
| 418 | + help | |
| 419 | 419 | This option compiles in a table of x86 feature bits and corresponding |
| 420 | 420 | names. This is required to support /proc/cpuinfo and a few kernel |
| 421 | 421 | messages. You can disable this to save space, at the expense of |
| @@ -426,7 +426,7 @@ config X86_FEATURE_NAMES · 4 unmodified lines | ||
| 426 | 426 | config X86_X2APIC |
| 427 | 427 | bool "Support x2apic" |
| 428 | 428 | depends on X86_LOCAL_APIC && X86_64 && (IRQ_REMAP || HYPERVISOR_GUEST) |
| 429 | − ---help--- | |
| 429 | + help | |
| 430 | 430 | This enables x2apic support on CPUs that have this feature. |
| 431 | 431 | |
| 432 | 432 | This allows 32-bit apic IDs (so it can support very large systems), |
| @@ -438,7 +438,7 @@ config X86_MPPARSE · 5 unmodified lines | ||
| 438 | 438 | bool "Enable MPS table" if ACPI || SFI |
| 439 | 439 | default y |
| 440 | 440 | depends on X86_LOCAL_APIC |
| 441 | − ---help--- | |
| 441 | + help | |
| 442 | 442 | For old smp systems that do not have proper acpi support. Newer systems |
| 443 | 443 | (esp with 64bit cpus) with acpi support, MADT and DSDT will override it |
| 444 | 444 | |
| @@ -481,13 +481,13 @@ if X86_32 · 36 unmodified lines | ||
| 481 | 481 | config X86_BIGSMP |
| 482 | 482 | bool "Support for big SMP systems with more than 8 CPUs" |
| 483 | 483 | depends on SMP |
| 484 | − ---help--- | |
| 484 | + help | |
| 485 | 485 | This option is needed for the systems that have more than 8 CPUs. |
| 486 | 486 | |
| 487 | 487 | config X86_EXTENDED_PLATFORM |
| 488 | 488 | bool "Support for extended (non-PC) x86 platforms" |
| 489 | 489 | default y |
| 490 | − ---help--- | |
| 490 | + help | |
| 491 | 491 | If you disable this option then the kernel will only support |
| 492 | 492 | standard PC platforms. (which covers the vast majority of |
| 493 | 493 | systems out there.) |
| @@ -509,7 +509,7 @@ if X86_64 · 15 unmodified lines | ||
| 509 | 509 | config X86_EXTENDED_PLATFORM |
| 510 | 510 | bool "Support for extended (non-PC) x86 platforms" |
| 511 | 511 | default y |
| 512 | − ---help--- | |
| 512 | + help | |
| 513 | 513 | If you disable this option then the kernel will only support |
| 514 | 514 | standard PC platforms. (which covers the vast majority of |
| 515 | 515 | systems out there.) |
| @@ -533,7 +533,7 @@ config X86_NUMACHIP · 17 unmodified lines | ||
| 533 | 533 | depends on SMP |
| 534 | 534 | depends on X86_X2APIC |
| 535 | 535 | depends on PCI_MMCONFIG |
| 536 | − ---help--- | |
| 536 | + help | |
| 537 | 537 | Adds support for Numascale NumaChip large-SMP systems. Needed to |
| 538 | 538 | enable more than ~168 cores. |
| 539 | 539 | If you don't have one of these, you should say N here. |
| @@ -545,7 +545,7 @@ config X86_VSMP · 5 unmodified lines | ||
| 545 | 545 | depends on X86_64 && PCI |
| 546 | 546 | depends on X86_EXTENDED_PLATFORM |
| 547 | 547 | depends on SMP |
| 548 | − ---help--- | |
| 548 | + help | |
| 549 | 549 | Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is |
| 550 | 550 | supposed to run on these EM64T-based machines. Only choose this option |
| 551 | 551 | if you have one of these machines. |
| @@ -558,7 +558,7 @@ config X86_UV · 6 unmodified lines | ||
| 558 | 558 | depends on EFI |
| 559 | 559 | depends on X86_X2APIC |
| 560 | 560 | depends on PCI |
| 561 | − ---help--- | |
| 561 | + help | |
| 562 | 562 | This option is needed in order to support SGI Ultraviolet systems. |
| 563 | 563 | If you don't have one of these, you should say N here. |
| 564 | 564 | |
| @@ -568,7 +568,7 @@ config X86_UV · 3 unmodified lines | ||
| 568 | 568 | config X86_GOLDFISH |
| 569 | 569 | bool "Goldfish (Virtual Platform)" |
| 570 | 570 | depends on X86_EXTENDED_PLATFORM |
| 571 | − ---help--- | |
| 571 | + help | |
| 572 | 572 | Enable support for the Goldfish virtual platform used primarily |
| 573 | 573 | for Android development. Unless you are building for the Android |
| 574 | 574 | Goldfish emulator say N here. |
| @@ -583,7 +583,7 @@ config X86_INTEL_CE · 8 unmodified lines | ||
| 583 | 583 | select X86_REBOOTFIXUPS |
| 584 | 584 | select OF |
| 585 | 585 | select OF_EARLY_FLATTREE |
| 586 | − ---help--- | |
| 586 | + help | |
| 587 | 587 | Select for the Intel CE media processor (CE4100) SOC. |
| 588 | 588 | This option compiles in support for the CE4100 SOC for settop |
| 589 | 589 | boxes and media devices. |
| @@ -601,7 +601,7 @@ config X86_INTEL_MID · 11 unmodified lines | ||
| 601 | 601 | select APB_TIMER |
| 602 | 602 | select INTEL_SCU_PCI |
| 603 | 603 | select MFD_INTEL_MSIC |
| 604 | − ---help--- | |
| 604 | + help | |
| 605 | 605 | Select to build a kernel capable of supporting Intel MID (Mobile |
| 606 | 606 | Internet Device) platform systems which do not have the PCI legacy |
| 607 | 607 | interfaces. If you are building for a PC class system say N here. |
| @@ -621,7 +621,7 @@ config X86_INTEL_QUARK · 13 unmodified lines | ||
| 621 | 621 | select IOSF_MBI |
| 622 | 622 | select INTEL_IMR |
| 623 | 623 | select COMMON_CLK |
| 624 | − ---help--- | |
| 624 | + help | |
| 625 | 625 | Select to include support for Quark X1000 SoC. |
| 626 | 626 | Say Y here if you have a Quark based system such as the Arduino |
| 627 | 627 | compatible Intel Galileo. |
| @@ -632,7 +632,7 @@ config X86_INTEL_LPSS · 4 unmodified lines | ||
| 632 | 632 | select COMMON_CLK |
| 633 | 633 | select PINCTRL |
| 634 | 634 | select IOSF_MBI |
| 635 | − ---help--- | |
| 635 | + help | |
| 636 | 636 | Select to build support for Intel Low Power Subsystem such as |
| 637 | 637 | found on Intel Lynxpoint PCH. Selecting this option enables |
| 638 | 638 | things like clock tree (common clock framework) and pincontrol |
| @@ -643,7 +643,7 @@ config X86_AMD_PLATFORM_DEVICE · 4 unmodified lines | ||
| 643 | 643 | depends on ACPI |
| 644 | 644 | select COMMON_CLK |
| 645 | 645 | select PINCTRL |
| 646 | − ---help--- | |
| 646 | + help | |
| 647 | 647 | Select to interpret AMD specific ACPI device to platform device |
| 648 | 648 | such as I2C, UART, GPIO found on AMD Carrizo and later chipsets. |
| 649 | 649 | I2C and UART depend on COMMON_CLK to set clock. GPIO driver is |
| @@ -652,7 +652,7 @@ config X86_AMD_PLATFORM_DEVICE · 2 unmodified lines | ||
| 652 | 652 | config IOSF_MBI |
| 653 | 653 | tristate "Intel SoC IOSF Sideband support for SoC platforms" |
| 654 | 654 | depends on PCI |
| 655 | − ---help--- | |
| 655 | + help | |
| 656 | 656 | This option enables sideband register access support for Intel SoC |
| 657 | 657 | platforms. On these platforms the IOSF sideband is used in lieu of |
| 658 | 658 | MSR's for some register accesses, mostly but not limited to thermal |
| @@ -669,7 +669,7 @@ config IOSF_MBI · 10 unmodified lines | ||
| 669 | 669 | config IOSF_MBI_DEBUG |
| 670 | 670 | bool "Enable IOSF sideband access through debugfs" |
| 671 | 671 | depends on IOSF_MBI && DEBUG_FS |
| 672 | − ---help--- | |
| 672 | + help | |
| 673 | 673 | Select this option to expose the IOSF sideband access registers (MCR, |
| 674 | 674 | MDR, MCRX) through debugfs to write and read register information from |
| 675 | 675 | different units on the SoC. This is most useful for obtaining device |
| @@ -685,7 +685,7 @@ config X86_RDC321X · 9 unmodified lines | ||
| 685 | 685 | depends on X86_EXTENDED_PLATFORM |
| 686 | 686 | select M486 |
| 687 | 687 | select X86_REBOOTFIXUPS |
| 688 | − ---help--- | |
| 688 | + help | |
| 689 | 689 | This option is needed for RDC R-321x system-on-chip, also known |
| 690 | 690 | as R-8610-(G). |
| 691 | 691 | If you don't have one of these chips, you should say N here. |
| @@ -694,7 +694,7 @@ config X86_32_NON_STANDARD · 2 unmodified lines | ||
| 694 | 694 | bool "Support non-standard 32-bit SMP architectures" |
| 695 | 695 | depends on X86_32 && SMP |
| 696 | 696 | depends on X86_EXTENDED_PLATFORM |
| 697 | − ---help--- | |
| 697 | + help | |
| 698 | 698 | This option compiles in the bigsmp and STA2X11 default |
| 699 | 699 | subarchitectures. It is intended for a generic binary |
| 700 | 700 | kernel. If you select them all, kernel will probe it one by |
| @@ -717,7 +717,7 @@ config STA2X11 · 16 unmodified lines | ||
| 717 | 717 | select SWIOTLB |
| 718 | 718 | select MFD_STA2X11 |
| 719 | 719 | select GPIOLIB |
| 720 | − ---help--- | |
| 720 | + help | |
| 721 | 721 | This adds support for boards based on the STA2X11 IO-Hub, |
| 722 | 722 | a.k.a. "ConneXt". The chip is used in place of the standard |
| 723 | 723 | PC chipset, so all "standard" peripherals are missing. If this |
| @@ -727,7 +727,7 @@ config STA2X11 · 3 unmodified lines | ||
| 727 | 727 | config X86_32_IRIS |
| 728 | 728 | tristate "Eurobraille/Iris poweroff module" |
| 729 | 729 | depends on X86_32 |
| 730 | − ---help--- | |
| 730 | + help | |
| 731 | 731 | The Iris machines from EuroBraille do not have APM or ACPI support |
| 732 | 732 | to shut themselves down properly. A special I/O sequence is |
| 733 | 733 | needed to do so, which is what this module does at |
| @@ -741,7 +741,7 @@ config SCHED_OMIT_FRAME_POINTER · 7 unmodified lines | ||
| 741 | 741 | def_bool y |
| 742 | 742 | prompt "Single-depth WCHAN output" |
| 743 | 743 | depends on X86 |
| 744 | − ---help--- | |
| 744 | + help | |
| 745 | 745 | Calculate simpler /proc/<PID>/wchan values. If this option |
| 746 | 746 | is disabled then wchan values will recurse back to the |
| 747 | 747 | caller function. This provides more accurate wchan values, |
| @@ -751,7 +751,7 @@ config SCHED_OMIT_FRAME_POINTER · 3 unmodified lines | ||
| 751 | 751 | |
| 752 | 752 | menuconfig HYPERVISOR_GUEST |
| 753 | 753 | bool "Linux guest support" |
| 754 | − ---help--- | |
| 754 | + help | |
| 755 | 755 | Say Y here to enable options for running Linux under various hyper- |
| 756 | 756 | visors. This option enables basic hypervisor detection and platform |
| 757 | 757 | setup. |
| @@ -763,7 +763,7 @@ if HYPERVISOR_GUEST · 5 unmodified lines | ||
| 763 | 763 | |
| 764 | 764 | config PARAVIRT |
| 765 | 765 | bool "Enable paravirtualization code" |
| 766 | − ---help--- | |
| 766 | + help | |
| 767 | 767 | This changes the kernel so it can modify itself when it is run |
| 768 | 768 | under a hypervisor, potentially improving performance significantly |
| 769 | 769 | over full virtualization. However, when run without a hypervisor |
| @@ -775,14 +775,14 @@ config PARAVIRT_XXL · 5 unmodified lines | ||
| 775 | 775 | config PARAVIRT_DEBUG |
| 776 | 776 | bool "paravirt-ops debugging" |
| 777 | 777 | depends on PARAVIRT && DEBUG_KERNEL |
| 778 | − ---help--- | |
| 778 | + help | |
| 779 | 779 | Enable to debug paravirt_ops internals. Specifically, BUG if |
| 780 | 780 | a paravirt_op is missing when it is called. |
| 781 | 781 | |
| 782 | 782 | config PARAVIRT_SPINLOCKS |
| 783 | 783 | bool "Paravirtualization layer for spinlocks" |
| 784 | 784 | depends on PARAVIRT && SMP |
| 785 | − ---help--- | |
| 785 | + help | |
| 786 | 786 | Paravirtualized spinlocks allow a pvops backend to replace the |
| 787 | 787 | spinlock implementation with something virtualization-friendly |
| 788 | 788 | (for example, block the virtual CPU rather than spinning). |
| @@ -803,7 +803,7 @@ config KVM_GUEST · 14 unmodified lines | ||
| 803 | 803 | select PARAVIRT_CLOCK |
| 804 | 804 | select ARCH_CPUIDLE_HALTPOLL |
| 805 | 805 | default y |
| 806 | − ---help--- | |
| 806 | + help | |
| 807 | 807 | This option enables various optimizations for running under the KVM |
| 808 | 808 | hypervisor. It includes a paravirtualized clock, so that instead |
| 809 | 809 | of relying on a PIT (or probably other) emulation by the |
| @@ -818,14 +818,14 @@ config ARCH_CPUIDLE_HALTPOLL · 8 unmodified lines | ||
| 818 | 818 | |
| 819 | 819 | config PVH |
| 820 | 820 | bool "Support for running PVH guests" |
| 821 | − ---help--- | |
| 821 | + help | |
| 822 | 822 | This option enables the PVH entry point for guest virtual machines |
| 823 | 823 | as specified in the x86/HVM direct boot ABI. |
| 824 | 824 | |
| 825 | 825 | config PARAVIRT_TIME_ACCOUNTING |
| 826 | 826 | bool "Paravirtual steal time accounting" |
| 827 | 827 | depends on PARAVIRT |
| 828 | − ---help--- | |
| 828 | + help | |
| 829 | 829 | Select this option to enable fine granularity task steal time |
| 830 | 830 | accounting. Time spent executing other tasks in parallel with |
| 831 | 831 | the current vCPU is discounted from the vCPU power. To account for |
| @@ -840,7 +840,7 @@ config JAILHOUSE_GUEST · 8 unmodified lines | ||
| 840 | 840 | bool "Jailhouse non-root cell support" |
| 841 | 841 | depends on X86_64 && PCI |
| 842 | 842 | select X86_PM_TIMER |
| 843 | − ---help--- | |
| 843 | + help | |
| 844 | 844 | This option allows to run Linux as guest in a Jailhouse non-root |
| 845 | 845 | cell. You can leave this option disabled if you only want to start |
| 846 | 846 | Jailhouse and run Linux afterwards in the root cell. |
| @@ -863,7 +863,7 @@ source "arch/x86/Kconfig.cpu" · 16 unmodified lines | ||
| 863 | 863 | config HPET_TIMER |
| 864 | 864 | def_bool X86_64 |
| 865 | 865 | prompt "HPET Timer Support" if X86_32 |
| 866 | − ---help--- | |
| 866 | + help | |
| 867 | 867 | Use the IA-PC HPET (High Precision Event Timer) to manage |
| 868 | 868 | time in preference to the PIT and RTC, if a HPET is |
| 869 | 869 | present. |
| @@ -901,7 +901,7 @@ config DMI · 31 unmodified lines | ||
| 901 | 901 | default y |
| 902 | 902 | select DMI_SCAN_MACHINE_NON_EFI_FALLBACK |
| 903 | 903 | bool "Enable DMI scanning" if EXPERT |
| 904 | − ---help--- | |
| 904 | + help | |
| 905 | 905 | Enabled scanning of DMI to identify machine quirks. Say Y |
| 906 | 906 | here unless you have verified that your setup is not |
| 907 | 907 | affected by entries in the DMI blacklist. Required by PNP |
| @@ -912,7 +912,7 @@ config GART_IOMMU · 4 unmodified lines | ||
| 912 | 912 | select IOMMU_HELPER |
| 913 | 913 | select SWIOTLB |
| 914 | 914 | depends on X86_64 && PCI && AMD_NB |
| 915 | − ---help--- | |
| 915 | + help | |
| 916 | 916 | Provides a driver for older AMD Athlon64/Opteron/Turion/Sempron |
| 917 | 917 | GART based hardware IOMMUs. |
| 918 | 918 | |
| @@ -933,7 +933,7 @@ config MAXSMP · 14 unmodified lines | ||
| 933 | 933 | bool "Enable Maximum number of SMP Processors and NUMA Nodes" |
| 934 | 934 | depends on X86_64 && SMP && DEBUG_KERNEL |
| 935 | 935 | select CPUMASK_OFFSTACK |
| 936 | − ---help--- | |
| 936 | + help | |
| 937 | 937 | Enable maximum number of CPUS and NUMA Nodes for this architecture. |
| 938 | 938 | If unsure, say N. |
| 939 | 939 | |
| @@ -989,7 +989,7 @@ config NR_CPUS · 49 unmodified lines | ||
| 989 | 989 | int "Maximum number of CPUs" if SMP && !MAXSMP |
| 990 | 990 | range NR_CPUS_RANGE_BEGIN NR_CPUS_RANGE_END |
| 991 | 991 | default NR_CPUS_DEFAULT |
| 992 | − ---help--- | |
| 992 | + help | |
| 993 | 993 | This allows you to specify the maximum number of CPUs which this |
| 994 | 994 | kernel will support. If CPUMASK_OFFSTACK is enabled, the maximum |
| 995 | 995 | supported value is 8192, otherwise the maximum value is 512. The |
| @@ -1005,7 +1005,7 @@ config SCHED_MC · 9 unmodified lines | ||
| 1005 | 1005 | def_bool y |
| 1006 | 1006 | prompt "Multi-core scheduler support" |
| 1007 | 1007 | depends on SMP |
| 1008 | − ---help--- | |
| 1008 | + help | |
| 1009 | 1009 | Multi-core scheduler support improves the CPU scheduler's decision |
| 1010 | 1010 | making when dealing with multi-core CPU chips at a cost of slightly |
| 1011 | 1011 | increased overhead in some places. If unsure say N here. |
| @@ -1016,7 +1016,7 @@ config SCHED_MC_PRIO · 4 unmodified lines | ||
| 1016 | 1016 | select X86_INTEL_PSTATE |
| 1017 | 1017 | select CPU_FREQ |
| 1018 | 1018 | default y |
| 1019 | − ---help--- | |
| 1019 | + help | |
| 1020 | 1020 | Intel Turbo Boost Max Technology 3.0 enabled CPUs have a |
| 1021 | 1021 | core ordering determined at manufacturing time, which allows |
| 1022 | 1022 | certain cores to reach higher turbo frequencies (when running |
| @@ -1039,7 +1039,7 @@ config X86_UP_APIC · 16 unmodified lines | ||
| 1039 | 1039 | bool "Local APIC support on uniprocessors" if !PCI_MSI |
| 1040 | 1040 | default PCI_MSI |
| 1041 | 1041 | depends on X86_32 && !SMP && !X86_32_NON_STANDARD |
| 1042 | − ---help--- | |
| 1042 | + help | |
| 1043 | 1043 | A local APIC (Advanced Programmable Interrupt Controller) is an |
| 1044 | 1044 | integrated interrupt controller in the CPU. If you have a single-CPU |
| 1045 | 1045 | system which has a processor with a local APIC, you can say Y here to |
| @@ -1052,7 +1052,7 @@ config X86_UP_APIC · 6 unmodified lines | ||
| 1052 | 1052 | config X86_UP_IOAPIC |
| 1053 | 1053 | bool "IO-APIC support on uniprocessors" |
| 1054 | 1054 | depends on X86_UP_APIC |
| 1055 | − ---help--- | |
| 1055 | + help | |
| 1056 | 1056 | An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an |
| 1057 | 1057 | SMP-capable replacement for PC-style interrupt controllers. Most |
| 1058 | 1058 | SMP systems and many recent uniprocessor systems have one. |
| @@ -1074,7 +1074,7 @@ config X86_IO_APIC · 15 unmodified lines | ||
| 1074 | 1074 | config X86_REROUTE_FOR_BROKEN_BOOT_IRQS |
| 1075 | 1075 | bool "Reroute for broken boot IRQs" |
| 1076 | 1076 | depends on X86_IO_APIC |
| 1077 | − ---help--- | |
| 1077 | + help | |
| 1078 | 1078 | This option enables a workaround that fixes a source of |
| 1079 | 1079 | spurious interrupts. This is recommended when threaded |
| 1080 | 1080 | interrupt handling is used on systems where the generation of |
| @@ -1098,7 +1098,7 @@ config X86_MCE · 17 unmodified lines | ||
| 1098 | 1098 | bool "Machine Check / overheating reporting" |
| 1099 | 1099 | select GENERIC_ALLOCATOR |
| 1100 | 1100 | default y |
| 1101 | − ---help--- | |
| 1101 | + help | |
| 1102 | 1102 | Machine Check support allows the processor to notify the |
| 1103 | 1103 | kernel if it detects a problem (e.g. overheating, data corruption). |
| 1104 | 1104 | The action the kernel takes depends on the severity of the problem, |
| @@ -1107,7 +1107,7 @@ config X86_MCE · 2 unmodified lines | ||
| 1107 | 1107 | config X86_MCELOG_LEGACY |
| 1108 | 1108 | bool "Support for deprecated /dev/mcelog character device" |
| 1109 | 1109 | depends on X86_MCE |
| 1110 | − ---help--- | |
| 1110 | + help | |
| 1111 | 1111 | Enable support for /dev/mcelog which is needed by the old mcelog |
| 1112 | 1112 | userspace logging daemon. Consider switching to the new generation |
| 1113 | 1113 | rasdaemon solution. |
| @@ -1116,7 +1116,7 @@ config X86_MCE_INTEL · 2 unmodified lines | ||
| 1116 | 1116 | def_bool y |
| 1117 | 1117 | prompt "Intel MCE features" |
| 1118 | 1118 | depends on X86_MCE && X86_LOCAL_APIC |
| 1119 | − ---help--- | |
| 1119 | + help | |
| 1120 | 1120 | Additional support for intel specific MCE features such as |
| 1121 | 1121 | the thermal monitor. |
| 1122 | 1122 | |
| @@ -1124,14 +1124,14 @@ config X86_MCE_AMD · 1 unmodified line | ||
| 1124 | 1124 | def_bool y |
| 1125 | 1125 | prompt "AMD MCE features" |
| 1126 | 1126 | depends on X86_MCE && X86_LOCAL_APIC && AMD_NB |
| 1127 | − ---help--- | |
| 1127 | + help | |
| 1128 | 1128 | Additional support for AMD specific MCE features such as |
| 1129 | 1129 | the DRAM Error Threshold. |
| 1130 | 1130 | |
| 1131 | 1131 | config X86_ANCIENT_MCE |
| 1132 | 1132 | bool "Support for old Pentium 5 / WinChip machine checks" |
| 1133 | 1133 | depends on X86_32 && X86_MCE |
| 1134 | − ---help--- | |
| 1134 | + help | |
| 1135 | 1135 | Include support for machine check handling on old Pentium 5 or WinChip |
| 1136 | 1136 | systems. These typically need to be enabled explicitly on the command |
| 1137 | 1137 | line. |
| @@ -1143,7 +1143,7 @@ config X86_MCE_THRESHOLD · 5 unmodified lines | ||
| 1143 | 1143 | config X86_MCE_INJECT |
| 1144 | 1144 | depends on X86_MCE && X86_LOCAL_APIC && DEBUG_FS |
| 1145 | 1145 | tristate "Machine check injector support" |
| 1146 | − ---help--- | |
| 1146 | + help | |
| 1147 | 1147 | Provide support for injecting machine checks for testing purposes. |
| 1148 | 1148 | If you don't know what a machine check is and you don't do kernel |
| 1149 | 1149 | QA it is safe to say n. |
| @@ -1157,7 +1157,7 @@ source "arch/x86/events/Kconfig" · 7 unmodified lines | ||
| 1157 | 1157 | config X86_LEGACY_VM86 |
| 1158 | 1158 | bool "Legacy VM86 support" |
| 1159 | 1159 | depends on X86_32 |
| 1160 | − ---help--- | |
| 1160 | + help | |
| 1161 | 1161 | This option allows user programs to put the CPU into V8086 |
| 1162 | 1162 | mode, which is an 80286-era approximation of 16-bit real mode. |
| 1163 | 1163 | |
| @@ -1189,7 +1189,7 @@ config X86_16BIT · 25 unmodified lines | ||
| 1189 | 1189 | bool "Enable support for 16-bit segments" if EXPERT |
| 1190 | 1190 | default y |
| 1191 | 1191 | depends on MODIFY_LDT_SYSCALL |
| 1192 | − ---help--- | |
| 1192 | + help | |
| 1193 | 1193 | This option is required by programs like Wine to run 16-bit |
| 1194 | 1194 | protected mode legacy code on x86 processors. Disabling |
| 1195 | 1195 | this option saves about 300 bytes on i386, or around 6K text |
| @@ -1207,7 +1207,7 @@ config X86_VSYSCALL_EMULATION · 11 unmodified lines | ||
| 1207 | 1207 | bool "Enable vsyscall emulation" if EXPERT |
| 1208 | 1208 | default y |
| 1209 | 1209 | depends on X86_64 |
| 1210 | − ---help--- | |
| 1210 | + help | |
| 1211 | 1211 | This enables emulation of the legacy vsyscall page. Disabling |
| 1212 | 1212 | it is roughly equivalent to booting with vsyscall=none, except |
| 1213 | 1213 | that it will also disable the helpful warning if a program |
| @@ -1224,7 +1224,7 @@ config X86_VSYSCALL_EMULATION · 10 unmodified lines | ||
| 1224 | 1224 | config X86_IOPL_IOPERM |
| 1225 | 1225 | bool "IOPERM and IOPL Emulation" |
| 1226 | 1226 | default y |
| 1227 | − ---help--- | |
| 1227 | + help | |
| 1228 | 1228 | This enables the ioperm() and iopl() syscalls which are necessary |
| 1229 | 1229 | for legacy applications. |
| 1230 | 1230 | |
| @@ -1242,7 +1242,7 @@ config X86_IOPL_IOPERM · 11 unmodified lines | ||
| 1242 | 1242 | config TOSHIBA |
| 1243 | 1243 | tristate "Toshiba Laptop support" |
| 1244 | 1244 | depends on X86_32 |
| 1245 | − ---help--- | |
| 1245 | + help | |
| 1246 | 1246 | This adds a driver to safely access the System Management Mode of |
| 1247 | 1247 | the CPU on Toshiba portables with a genuine Toshiba BIOS. It does |
| 1248 | 1248 | not work on models with a Phoenix BIOS. The System Management Mode |
| @@ -1259,7 +1259,7 @@ config I8K · 10 unmodified lines | ||
| 1259 | 1259 | tristate "Dell i8k legacy laptop support" |
| 1260 | 1260 | select HWMON |
| 1261 | 1261 | select SENSORS_DELL_SMM |
| 1262 | − ---help--- | |
| 1262 | + help | |
| 1263 | 1263 | This option enables legacy /proc/i8k userspace interface in hwmon |
| 1264 | 1264 | dell-smm-hwmon driver. Character file /proc/i8k reports bios version, |
| 1265 | 1265 | temperature and allows controlling fan speeds of Dell laptops via |
| @@ -1274,7 +1274,7 @@ config I8K · 8 unmodified lines | ||
| 1274 | 1274 | config X86_REBOOTFIXUPS |
| 1275 | 1275 | bool "Enable X86 board specific fixups for reboot" |
| 1276 | 1276 | depends on X86_32 |
| 1277 | − ---help--- | |
| 1277 | + help | |
| 1278 | 1278 | This enables chipset and/or board specific fixups to be done |
| 1279 | 1279 | in order to get reboot to work correctly. This is only needed on |
| 1280 | 1280 | some combinations of hardware and BIOS. The symptom, for which |
| @@ -1293,7 +1293,7 @@ config MICROCODE · 12 unmodified lines | ||
| 1293 | 1293 | default y |
| 1294 | 1294 | depends on CPU_SUP_AMD || CPU_SUP_INTEL |
| 1295 | 1295 | select FW_LOADER |
| 1296 | − ---help--- | |
| 1296 | + help | |
| 1297 | 1297 | If you say Y here, you will be able to update the microcode on |
| 1298 | 1298 | Intel and AMD processors. The Intel support is for the IA32 family, |
| 1299 | 1299 | e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4, Xeon etc. The |
| @@ -1315,7 +1315,7 @@ config MICROCODE_INTEL · 15 unmodified lines | ||
| 1315 | 1315 | depends on MICROCODE |
| 1316 | 1316 | default MICROCODE |
| 1317 | 1317 | select FW_LOADER |
| 1318 | − ---help--- | |
| 1318 | + help | |
| 1319 | 1319 | This options enables microcode patch loading support for Intel |
| 1320 | 1320 | processors. |
| 1321 | 1321 | |
| @@ -1327,7 +1327,7 @@ config MICROCODE_AMD · 5 unmodified lines | ||
| 1327 | 1327 | bool "AMD microcode loading support" |
| 1328 | 1328 | depends on MICROCODE |
| 1329 | 1329 | select FW_LOADER |
| 1330 | − ---help--- | |
| 1330 | + help | |
| 1331 | 1331 | If you select this option, microcode patch loading support for AMD |
| 1332 | 1332 | processors will be enabled. |
| 1333 | 1333 | |
| @@ -1335,7 +1335,7 @@ config MICROCODE_OLD_INTERFACE · 1 unmodified line | ||
| 1335 | 1335 | bool "Ancient loading interface (DEPRECATED)" |
| 1336 | 1336 | default n |
| 1337 | 1337 | depends on MICROCODE |
| 1338 | − ---help--- | |
| 1338 | + help | |
| 1339 | 1339 | DO NOT USE THIS! This is the ancient /dev/cpu/microcode interface |
| 1340 | 1340 | which was used by userspace tools like iucode_tool and microcode.ctl. |
| 1341 | 1341 | It is inadequate because it runs too late to be able to properly |
| @@ -1345,7 +1345,7 @@ config MICROCODE_OLD_INTERFACE · 3 unmodified lines | ||
| 1345 | 1345 | |
| 1346 | 1346 | config X86_MSR |
| 1347 | 1347 | tristate "/dev/cpu/*/msr - Model-specific register support" |
| 1348 | − ---help--- | |
| 1348 | + help | |
| 1349 | 1349 | This device gives privileged processes access to the x86 |
| 1350 | 1350 | Model-Specific Registers (MSRs). It is a character device with |
| 1351 | 1351 | major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr. |
| @@ -1354,7 +1354,7 @@ config X86_MSR · 2 unmodified lines | ||
| 1354 | 1354 | |
| 1355 | 1355 | config X86_CPUID |
| 1356 | 1356 | tristate "/dev/cpu/*/cpuid - CPU information support" |
| 1357 | − ---help--- | |
| 1357 | + help | |
| 1358 | 1358 | This device gives processes access to the x86 CPUID instruction to |
| 1359 | 1359 | be executed on a specific processor. It is a character device |
| 1360 | 1360 | with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to |
| @@ -1367,7 +1367,7 @@ choice · 6 unmodified lines | ||
| 1367 | 1367 | |
| 1368 | 1368 | config NOHIGHMEM |
| 1369 | 1369 | bool "off" |
| 1370 | − ---help--- | |
| 1370 | + help | |
| 1371 | 1371 | Linux can use up to 64 Gigabytes of physical memory on x86 systems. |
| 1372 | 1372 | However, the address space of 32-bit x86 processors is only 4 |
| 1373 | 1373 | Gigabytes large. That means that, if you have a large amount of |
| @@ -1403,7 +1403,7 @@ config NOHIGHMEM · 29 unmodified lines | ||
| 1403 | 1403 | |
| 1404 | 1404 | config HIGHMEM4G |
| 1405 | 1405 | bool "4GB" |
| 1406 | − ---help--- | |
| 1406 | + help | |
| 1407 | 1407 | Select this if you have a 32-bit processor and between 1 and 4 |
| 1408 | 1408 | gigabytes of physical RAM. |
| 1409 | 1409 | |
| @@ -1411,7 +1411,7 @@ config HIGHMEM64G · 1 unmodified line | ||
| 1411 | 1411 | bool "64GB" |
| 1412 | 1412 | depends on !M486 && !M586 && !M586TSC && !M586MMX && !MGEODE_LX && !MGEODEGX1 && !MCYRIXIII && !MELAN && !MWINCHIPC6 && !WINCHIP3D && !MK6 |
| 1413 | 1413 | select X86_PAE |
| 1414 | − ---help--- | |
| 1414 | + help | |
| 1415 | 1415 | Select this if you have a 32-bit processor and more than 4 |
| 1416 | 1416 | gigabytes of physical RAM. |
| 1417 | 1417 | |
| @@ -1421,7 +1421,7 @@ choice · 3 unmodified lines | ||
| 1421 | 1421 | prompt "Memory split" if EXPERT |
| 1422 | 1422 | default VMSPLIT_3G |
| 1423 | 1423 | depends on X86_32 |
| 1424 | − ---help--- | |
| 1424 | + help | |
| 1425 | 1425 | Select the desired split between kernel and user memory. |
| 1426 | 1426 | |
| 1427 | 1427 | If the address range available to the kernel is less than the |
| @@ -1469,7 +1469,7 @@ config X86_PAE · 41 unmodified lines | ||
| 1469 | 1469 | depends on X86_32 && !HIGHMEM4G |
| 1470 | 1470 | select PHYS_ADDR_T_64BIT |
| 1471 | 1471 | select SWIOTLB |
| 1472 | − ---help--- | |
| 1472 | + help | |
| 1473 | 1473 | PAE is required for NX support, and furthermore enables |
| 1474 | 1474 | larger swapspace support for non-overcommit purposes. It |
| 1475 | 1475 | has the cost of more pagetable lookup overhead, and also |
| @@ -1481,7 +1481,7 @@ config X86_5LEVEL · 5 unmodified lines | ||
| 1481 | 1481 | select DYNAMIC_MEMORY_LAYOUT |
| 1482 | 1482 | select SPARSEMEM_VMEMMAP |
| 1483 | 1483 | depends on X86_64 |
| 1484 | − ---help--- | |
| 1484 | + help | |
| 1485 | 1485 | 5-level paging enables access to larger address space: |
| 1486 | 1486 | upto 128 PiB of virtual address space and 4 PiB of |
| 1487 | 1487 | physical address space. |
| @@ -1499,7 +1499,7 @@ config X86_5LEVEL · 11 unmodified lines | ||
| 1499 | 1499 | config X86_DIRECT_GBPAGES |
| 1500 | 1500 | def_bool y |
| 1501 | 1501 | depends on X86_64 |
| 1502 | − ---help--- | |
| 1502 | + help | |
| 1503 | 1503 | Certain kernel features effectively disable kernel |
| 1504 | 1504 | linear 1 GB mappings (even if the CPU otherwise |
| 1505 | 1505 | supports them), so don't confuse the user by printing |
| @@ -1508,7 +1508,7 @@ config X86_DIRECT_GBPAGES · 2 unmodified lines | ||
| 1508 | 1508 | config X86_CPA_STATISTICS |
| 1509 | 1509 | bool "Enable statistic for Change Page Attribute" |
| 1510 | 1510 | depends on DEBUG_FS |
| 1511 | − ---help--- | |
| 1511 | + help | |
| 1512 | 1512 | Expose statistics about the Change Page Attribute mechanism, which |
| 1513 | 1513 | helps to determine the effectiveness of preserving large and huge |
| 1514 | 1514 | page mappings when mapping protections are changed. |
| @@ -1520,7 +1520,7 @@ config AMD_MEM_ENCRYPT · 5 unmodified lines | ||
| 1520 | 1520 | select DYNAMIC_PHYSICAL_MASK |
| 1521 | 1521 | select ARCH_USE_MEMREMAP_PROT |
| 1522 | 1522 | select ARCH_HAS_FORCE_DMA_UNENCRYPTED |
| 1523 | − ---help--- | |
| 1523 | + help | |
| 1524 | 1524 | Say yes to enable support for the encryption of system memory. |
| 1525 | 1525 | This requires an AMD processor that supports Secure Memory |
| 1526 | 1526 | Encryption (SME). |
| @@ -1529,7 +1529,7 @@ config AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT · 2 unmodified lines | ||
| 1529 | 1529 | bool "Activate AMD Secure Memory Encryption (SME) by default" |
| 1530 | 1530 | default y |
| 1531 | 1531 | depends on AMD_MEM_ENCRYPT |
| 1532 | − ---help--- | |
| 1532 | + help | |
| 1533 | 1533 | Say yes to have system memory encrypted by default if running on |
| 1534 | 1534 | an AMD processor that supports Secure Memory Encryption (SME). |
| 1535 | 1535 | |
| @@ -1545,7 +1545,7 @@ config NUMA · 9 unmodified lines | ||
| 1545 | 1545 | depends on SMP |
| 1546 | 1546 | depends on X86_64 || (X86_32 && HIGHMEM64G && X86_BIGSMP) |
| 1547 | 1547 | default y if X86_BIGSMP |
| 1548 | − ---help--- | |
| 1548 | + help | |
| 1549 | 1549 | Enable NUMA (Non-Uniform Memory Access) support. |
| 1550 | 1550 | |
| 1551 | 1551 | The kernel will try to allocate memory used by a CPU on the |
| @@ -1564,7 +1564,7 @@ config AMD_NUMA · 12 unmodified lines | ||
| 1564 | 1564 | def_bool y |
| 1565 | 1565 | prompt "Old style AMD Opteron NUMA detection" |
| 1566 | 1566 | depends on X86_64 && NUMA && PCI |
| 1567 | − ---help--- | |
| 1567 | + help | |
| 1568 | 1568 | Enable AMD NUMA node topology detection. You should say Y here if |
| 1569 | 1569 | you have a multi processor AMD system. This uses an old method to |
| 1570 | 1570 | read the NUMA configuration directly from the builtin Northbridge |
| @@ -1576,13 +1576,13 @@ config X86_64_ACPI_NUMA · 5 unmodified lines | ||
| 1576 | 1576 | prompt "ACPI NUMA detection" |
| 1577 | 1577 | depends on X86_64 && NUMA && ACPI && PCI |
| 1578 | 1578 | select ACPI_NUMA |
| 1579 | − ---help--- | |
| 1579 | + help | |
| 1580 | 1580 | Enable ACPI SRAT based node topology detection. |
| 1581 | 1581 | |
| 1582 | 1582 | config NUMA_EMU |
| 1583 | 1583 | bool "NUMA emulation" |
| 1584 | 1584 | depends on NUMA |
| 1585 | − ---help--- | |
| 1585 | + help | |
| 1586 | 1586 | Enable NUMA emulation. A flat machine will be split |
| 1587 | 1587 | into virtual nodes when booted with "numa=fake=N", where N is the |
| 1588 | 1588 | number of nodes. This is only useful for debugging. |
| @@ -1594,7 +1594,7 @@ config NODES_SHIFT · 5 unmodified lines | ||
| 1594 | 1594 | default "6" if X86_64 |
| 1595 | 1595 | default "3" |
| 1596 | 1596 | depends on NEED_MULTIPLE_NODES |
| 1597 | − ---help--- | |
| 1597 | + help | |
| 1598 | 1598 | Specify the maximum number of NUMA Nodes available on the target |
| 1599 | 1599 | system. Increases memory reserved to accommodate various tables. |
| 1600 | 1600 | |
| @@ -1653,7 +1653,7 @@ config X86_PMEM_LEGACY · 52 unmodified lines | ||
| 1653 | 1653 | config HIGHPTE |
| 1654 | 1654 | bool "Allocate 3rd-level pagetables from highmem" |
| 1655 | 1655 | depends on HIGHMEM |
| 1656 | − ---help--- | |
| 1656 | + help | |
| 1657 | 1657 | The VM uses one page table entry for each page of physical memory. |
| 1658 | 1658 | For systems with a lot of RAM, this can be wasteful of precious |
| 1659 | 1659 | low memory. Setting this option will put user-space page table |
| @@ -1661,7 +1661,7 @@ config HIGHPTE · 1 unmodified line | ||
| 1661 | 1661 | |
| 1662 | 1662 | config X86_CHECK_BIOS_CORRUPTION |
| 1663 | 1663 | bool "Check for low memory corruption" |
| 1664 | − ---help--- | |
| 1664 | + help | |
| 1665 | 1665 | Periodically check for memory corruption in low memory, which |
| 1666 | 1666 | is suspected to be caused by BIOS. Even when enabled in the |
| 1667 | 1667 | configuration, it is disabled at runtime. Enable it by |
| @@ -1685,7 +1685,7 @@ config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK · 17 unmodified lines | ||
| 1685 | 1685 | bool "Set the default setting of memory_corruption_check" |
| 1686 | 1686 | depends on X86_CHECK_BIOS_CORRUPTION |
| 1687 | 1687 | default y |
| 1688 | − ---help--- | |
| 1688 | + help | |
| 1689 | 1689 | Set whether the default state of memory_corruption_check is |
| 1690 | 1690 | on or off. |
| 1691 | 1691 | |
| @@ -1693,7 +1693,7 @@ config X86_RESERVE_LOW · 1 unmodified line | ||
| 1693 | 1693 | int "Amount of low memory, in kilobytes, to reserve for the BIOS" |
| 1694 | 1694 | default 64 |
| 1695 | 1695 | range 4 640 |
| 1696 | − ---help--- | |
| 1696 | + help | |
| 1697 | 1697 | Specify the amount of low memory to reserve for the BIOS. |
| 1698 | 1698 | |
| 1699 | 1699 | The first page contains BIOS data structures that the kernel |
| @@ -1722,7 +1722,7 @@ config MATH_EMULATION · 22 unmodified lines | ||
| 1722 | 1722 | bool |
| 1723 | 1723 | depends on MODIFY_LDT_SYSCALL |
| 1724 | 1724 | prompt "Math emulation" if X86_32 && (M486SX || MELAN) |
| 1725 | − ---help--- | |
| 1725 | + help | |
| 1726 | 1726 | Linux can emulate a math coprocessor (used for floating point |
| 1727 | 1727 | operations) if you don't have one. 486DX and Pentium processors have |
| 1728 | 1728 | a math coprocessor built in, 486SX and 386 do not, unless you added |
| @@ -1748,7 +1748,7 @@ config MATH_EMULATION · 19 unmodified lines | ||
| 1748 | 1748 | config MTRR |
| 1749 | 1749 | def_bool y |
| 1750 | 1750 | prompt "MTRR (Memory Type Range Register) support" if EXPERT |
| 1751 | − ---help--- | |
| 1751 | + help | |
| 1752 | 1752 | On Intel P6 family processors (Pentium Pro, Pentium II and later) |
| 1753 | 1753 | the Memory Type Range Registers (MTRRs) may be used to control |
| 1754 | 1754 | processor access to memory ranges. This is most useful if you have |
| @@ -1784,7 +1784,7 @@ config MTRR_SANITIZER · 29 unmodified lines | ||
| 1784 | 1784 | def_bool y |
| 1785 | 1785 | prompt "MTRR cleanup support" |
| 1786 | 1786 | depends on MTRR |
| 1787 | − ---help--- | |
| 1787 | + help | |
| 1788 | 1788 | Convert MTRR layout from continuous to discrete, so X drivers can |
| 1789 | 1789 | add writeback entries. |
| 1790 | 1790 | |
| @@ -1799,7 +1799,7 @@ config MTRR_SANITIZER_ENABLE_DEFAULT · 8 unmodified lines | ||
| 1799 | 1799 | range 0 1 |
| 1800 | 1800 | default "0" |
| 1801 | 1801 | depends on MTRR_SANITIZER |
| 1802 | − ---help--- | |
| 1802 | + help | |
| 1803 | 1803 | Enable mtrr cleanup default value |
| 1804 | 1804 | |
| 1805 | 1805 | config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT |
| @@ -1807,7 +1807,7 @@ config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT · 1 unmodified line | ||
| 1807 | 1807 | range 0 7 |
| 1808 | 1808 | default "1" |
| 1809 | 1809 | depends on MTRR_SANITIZER |
| 1810 | − ---help--- | |
| 1810 | + help | |
| 1811 | 1811 | mtrr cleanup spare entries default, it can be changed via |
| 1812 | 1812 | mtrr_spare_reg_nr=N on the kernel command line. |
| 1813 | 1813 | |
| @@ -1815,7 +1815,7 @@ config X86_PAT · 1 unmodified line | ||
| 1815 | 1815 | def_bool y |
| 1816 | 1816 | prompt "x86 PAT support" if EXPERT |
| 1817 | 1817 | depends on MTRR |
| 1818 | − ---help--- | |
| 1818 | + help | |
| 1819 | 1819 | Use PAT attributes to setup page level cache control. |
| 1820 | 1820 | |
| 1821 | 1821 | PATs are the modern equivalents of MTRRs and are much more |
| @@ -1833,7 +1833,7 @@ config ARCH_USES_PG_UNCACHED · 11 unmodified lines | ||
| 1833 | 1833 | config ARCH_RANDOM |
| 1834 | 1834 | def_bool y |
| 1835 | 1835 | prompt "x86 architectural random number generator" if EXPERT |
| 1836 | − ---help--- | |
| 1836 | + help | |
| 1837 | 1837 | Enable the x86 architectural RDRAND instruction |
| 1838 | 1838 | (Intel Bull Mountain technology) to generate random numbers. |
| 1839 | 1839 | If supported, this is a high bandwidth, cryptographically |
| @@ -1842,7 +1842,7 @@ config ARCH_RANDOM · 2 unmodified lines | ||
| 1842 | 1842 | config X86_SMAP |
| 1843 | 1843 | def_bool y |
| 1844 | 1844 | prompt "Supervisor Mode Access Prevention" if EXPERT |
| 1845 | − ---help--- | |
| 1845 | + help | |
| 1846 | 1846 | Supervisor Mode Access Prevention (SMAP) is a security |
| 1847 | 1847 | feature in newer Intel processors. There is a small |
| 1848 | 1848 | performance cost if this enabled and turned on; there is |
| @@ -1853,7 +1853,7 @@ config X86_SMAP · 4 unmodified lines | ||
| 1853 | 1853 | config X86_UMIP |
| 1854 | 1854 | def_bool y |
| 1855 | 1855 | prompt "User Mode Instruction Prevention" if EXPERT |
| 1856 | − ---help--- | |
| 1856 | + help | |
| 1857 | 1857 | User Mode Instruction Prevention (UMIP) is a security feature in |
| 1858 | 1858 | some x86 processors. If enabled, a general protection fault is |
| 1859 | 1859 | issued if the SGDT, SLDT, SIDT, SMSW or STR instructions are |
| @@ -1872,7 +1872,7 @@ config X86_INTEL_MEMORY_PROTECTION_KEYS · 12 unmodified lines | ||
| 1872 | 1872 | depends on X86_64 && (CPU_SUP_INTEL || CPU_SUP_AMD) |
| 1873 | 1873 | select ARCH_USES_HIGH_VMA_FLAGS |
| 1874 | 1874 | select ARCH_HAS_PKEYS |
| 1875 | − ---help--- | |
| 1875 | + help | |
| 1876 | 1876 | Memory Protection Keys provides a mechanism for enforcing |
| 1877 | 1877 | page-based protections, but without requiring modification of the |
| 1878 | 1878 | page tables when an application changes protection domains. |
| @@ -1931,7 +1931,7 @@ config EFI · 52 unmodified lines | ||
| 1931 | 1931 | depends on ACPI |
| 1932 | 1932 | select UCS2_STRING |
| 1933 | 1933 | select EFI_RUNTIME_WRAPPERS |
| 1934 | − ---help--- | |
| 1934 | + help | |
| 1935 | 1935 | This enables the kernel to use EFI runtime services that are |
| 1936 | 1936 | available (such as the EFI variable services). |
| 1937 | 1937 | |
| @@ -1947,7 +1947,7 @@ config EFI_STUB · 9 unmodified lines | ||
| 1947 | 1947 | depends on EFI && !X86_USE_3DNOW |
| 1948 | 1948 | depends on $(cc-option,-mabi=ms) || X86_32 |
| 1949 | 1949 | select RELOCATABLE |
| 1950 | − ---help--- | |
| 1950 | + help | |
| 1951 | 1951 | This kernel feature allows a bzImage to be loaded directly |
| 1952 | 1952 | by EFI firmware without the use of a bootloader. |
| 1953 | 1953 | |
| @@ -1956,7 +1956,7 @@ config EFI_STUB · 2 unmodified lines | ||
| 1956 | 1956 | config EFI_MIXED |
| 1957 | 1957 | bool "EFI mixed-mode support" |
| 1958 | 1958 | depends on EFI_STUB && X86_64 |
| 1959 | − ---help--- | |
| 1959 | + help | |
| 1960 | 1960 | Enabling this feature allows a 64-bit kernel to be booted |
| 1961 | 1961 | on a 32-bit firmware, provided that your CPU supports 64-bit |
| 1962 | 1962 | mode. |
| @@ -1970,7 +1970,7 @@ config EFI_MIXED · 7 unmodified lines | ||
| 1970 | 1970 | config SECCOMP |
| 1971 | 1971 | def_bool y |
| 1972 | 1972 | prompt "Enable seccomp to safely compute untrusted bytecode" |
| 1973 | − ---help--- | |
| 1973 | + help | |
| 1974 | 1974 | This kernel feature is useful for number crunching applications |
| 1975 | 1975 | that may need to compute untrusted bytecode during their |
| 1976 | 1976 | execution. By using pipes or other transports made available to |
| @@ -1988,7 +1988,7 @@ source "kernel/Kconfig.hz" · 11 unmodified lines | ||
| 1988 | 1988 | config KEXEC |
| 1989 | 1989 | bool "kexec system call" |
| 1990 | 1990 | select KEXEC_CORE |
| 1991 | − ---help--- | |
| 1991 | + help | |
| 1992 | 1992 | kexec is a system call that implements the ability to shutdown your |
| 1993 | 1993 | current kernel, and to start another kernel. It is like a reboot |
| 1994 | 1994 | but it is independent of the system firmware. And like a reboot |
| @@ -2009,7 +2009,7 @@ config KEXEC_FILE · 14 unmodified lines | ||
| 2009 | 2009 | depends on X86_64 |
| 2010 | 2010 | depends on CRYPTO=y |
| 2011 | 2011 | depends on CRYPTO_SHA256=y |
| 2012 | − ---help--- | |
| 2012 | + help | |
| 2013 | 2013 | This is new version of kexec system call. This system call is |
| 2014 | 2014 | file based and takes file descriptors as system call argument |
| 2015 | 2015 | for kernel and initramfs as opposed to list of segments as |
| @@ -2021,7 +2021,7 @@ config ARCH_HAS_KEXEC_PURGATORY · 5 unmodified lines | ||
| 2021 | 2021 | config KEXEC_SIG |
| 2022 | 2022 | bool "Verify kernel signature during kexec_file_load() syscall" |
| 2023 | 2023 | depends on KEXEC_FILE |
| 2024 | − ---help--- | |
| 2024 | + help | |
| 2025 | 2025 | |
| 2026 | 2026 | This option makes the kexec_file_load() syscall check for a valid |
| 2027 | 2027 | signature of the kernel image. The image can still be loaded without |
| @@ -2035,7 +2035,7 @@ config KEXEC_SIG · 7 unmodified lines | ||
| 2035 | 2035 | config KEXEC_SIG_FORCE |
| 2036 | 2036 | bool "Require a valid signature in kexec_file_load() syscall" |
| 2037 | 2037 | depends on KEXEC_SIG |
| 2038 | − ---help--- | |
| 2038 | + help | |
| 2039 | 2039 | This option makes kernel signature verification mandatory for |
| 2040 | 2040 | the kexec_file_load() syscall. |
| 2041 | 2041 | |
| @@ -2044,13 +2044,13 @@ config KEXEC_BZIMAGE_VERIFY_SIG · 2 unmodified lines | ||
| 2044 | 2044 | depends on KEXEC_SIG |
| 2045 | 2045 | depends on SIGNED_PE_FILE_VERIFICATION |
| 2046 | 2046 | select SYSTEM_TRUSTED_KEYRING |
| 2047 | − ---help--- | |
| 2047 | + help | |
| 2048 | 2048 | Enable bzImage signature verification support. |
| 2049 | 2049 | |
| 2050 | 2050 | config CRASH_DUMP |
| 2051 | 2051 | bool "kernel crash dumps" |
| 2052 | 2052 | depends on X86_64 || (X86_32 && HIGHMEM) |
| 2053 | − ---help--- | |
| 2053 | + help | |
| 2054 | 2054 | Generate crash dump after being started by kexec. |
| 2055 | 2055 | This should be normally only set in special crash dump kernels |
| 2056 | 2056 | which are loaded in the main kernel with kexec-tools into |
| @@ -2064,14 +2064,14 @@ config CRASH_DUMP · 7 unmodified lines | ||
| 2064 | 2064 | config KEXEC_JUMP |
| 2065 | 2065 | bool "kexec jump" |
| 2066 | 2066 | depends on KEXEC && HIBERNATION |
| 2067 | − ---help--- | |
| 2067 | + help | |
| 2068 | 2068 | Jump between original kernel and kexeced kernel and invoke |
| 2069 | 2069 | code in physical address mode via KEXEC |
| 2070 | 2070 | |
| 2071 | 2071 | config PHYSICAL_START |
| 2072 | 2072 | hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP) |
| 2073 | 2073 | default "0x1000000" |
| 2074 | − ---help--- | |
| 2074 | + help | |
| 2075 | 2075 | This gives the physical address where the kernel is loaded. |
| 2076 | 2076 | |
| 2077 | 2077 | If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then |
| @@ -2112,7 +2112,7 @@ config PHYSICAL_START · 34 unmodified lines | ||
| 2112 | 2112 | config RELOCATABLE |
| 2113 | 2113 | bool "Build a relocatable kernel" |
| 2114 | 2114 | default y |
| 2115 | − ---help--- | |
| 2115 | + help | |
| 2116 | 2116 | This builds a kernel image that retains relocation information |
| 2117 | 2117 | so it can be loaded someplace besides the default 1MB. |
| 2118 | 2118 | The relocations tend to make the kernel binary about 10% larger, |
| @@ -2130,7 +2130,7 @@ config RANDOMIZE_BASE · 11 unmodified lines | ||
| 2130 | 2130 | bool "Randomize the address of the kernel image (KASLR)" |
| 2131 | 2131 | depends on RELOCATABLE |
| 2132 | 2132 | default y |
| 2133 | − ---help--- | |
| 2133 | + help | |
| 2134 | 2134 | In support of Kernel Address Space Layout Randomization (KASLR), |
| 2135 | 2135 | this randomizes the physical address at which the kernel image |
| 2136 | 2136 | is decompressed and the virtual address where the kernel |
| @@ -2171,7 +2171,7 @@ config PHYSICAL_ALIGN · 34 unmodified lines | ||
| 2171 | 2171 | default "0x200000" |
| 2172 | 2172 | range 0x2000 0x1000000 if X86_32 |
| 2173 | 2173 | range 0x200000 0x1000000 if X86_64 |
| 2174 | − ---help--- | |
| 2174 | + help | |
| 2175 | 2175 | This value puts the alignment restrictions on physical address |
| 2176 | 2176 | where kernel is loaded and run from. Kernel is compiled for an |
| 2177 | 2177 | address which meets above alignment restriction. |
| @@ -2195,7 +2195,7 @@ config PHYSICAL_ALIGN · 17 unmodified lines | ||
| 2195 | 2195 | |
| 2196 | 2196 | config DYNAMIC_MEMORY_LAYOUT |
| 2197 | 2197 | bool |
| 2198 | − ---help--- | |
| 2198 | + help | |
| 2199 | 2199 | This option makes base addresses of vmalloc and vmemmap as well as |
| 2200 | 2200 | __PAGE_OFFSET movable during boot. |
| 2201 | 2201 | |
| @@ -2205,7 +2205,7 @@ config RANDOMIZE_MEMORY · 3 unmodified lines | ||
| 2205 | 2205 | depends on RANDOMIZE_BASE |
| 2206 | 2206 | select DYNAMIC_MEMORY_LAYOUT |
| 2207 | 2207 | default RANDOMIZE_BASE |
| 2208 | − ---help--- | |
| 2208 | + help | |
| 2209 | 2209 | Randomizes the base virtual address of kernel memory sections |
| 2210 | 2210 | (physical memory mapping, vmalloc & vmemmap). This security feature |
| 2211 | 2211 | makes exploits relying on predictable memory locations less reliable. |
| @@ -2224,7 +2224,7 @@ config RANDOMIZE_MEMORY_PHYSICAL_PADDING · 12 unmodified lines | ||
| 2224 | 2224 | default "0x0" |
| 2225 | 2225 | range 0x1 0x40 if MEMORY_HOTPLUG |
| 2226 | 2226 | range 0x0 0x40 |
| 2227 | − ---help--- | |
| 2227 | + help | |
| 2228 | 2228 | Define the padding in terabytes added to the existing physical |
| 2229 | 2229 | memory size during kernel memory randomization. It is useful |
| 2230 | 2230 | for memory hotplug support but reduces the entropy available for |
| @@ -2239,7 +2239,7 @@ config HOTPLUG_CPU · 8 unmodified lines | ||
| 2239 | 2239 | config BOOTPARAM_HOTPLUG_CPU0 |
| 2240 | 2240 | bool "Set default setting of cpu0_hotpluggable" |
| 2241 | 2241 | depends on HOTPLUG_CPU |
| 2242 | − ---help--- | |
| 2242 | + help | |
| 2243 | 2243 | Set whether default state of cpu0_hotpluggable is on or off. |
| 2244 | 2244 | |
| 2245 | 2245 | Say Y here to enable CPU0 hotplug by default. If this switch |
| @@ -2268,7 +2268,7 @@ config DEBUG_HOTPLUG_CPU0 · 22 unmodified lines | ||
| 2268 | 2268 | def_bool n |
| 2269 | 2269 | prompt "Debug CPU0 hotplug" |
| 2270 | 2270 | depends on HOTPLUG_CPU |
| 2271 | − ---help--- | |
| 2271 | + help | |
| 2272 | 2272 | Enabling this option offlines CPU0 (if CPU0 can be offlined) as |
| 2273 | 2273 | soon as possible and boots up userspace with CPU0 offlined. User |
| 2274 | 2274 | can online CPU0 back after boot time. |
| @@ -2283,7 +2283,7 @@ config COMPAT_VDSO · 8 unmodified lines | ||
| 2283 | 2283 | def_bool n |
| 2284 | 2284 | prompt "Disable the 32-bit vDSO (needed for glibc 2.3.3)" |
| 2285 | 2285 | depends on COMPAT_32 |
| 2286 | − ---help--- | |
| 2286 | + help | |
| 2287 | 2287 | Certain buggy versions of glibc will crash if they are |
| 2288 | 2288 | presented with a 32-bit vDSO that is not mapped at the address |
| 2289 | 2289 | indicated in its segment table. |
| @@ -2361,7 +2361,7 @@ endchoice · 71 unmodified lines | ||
| 2361 | 2361 | |
| 2362 | 2362 | config CMDLINE_BOOL |
| 2363 | 2363 | bool "Built-in kernel command line" |
| 2364 | − ---help--- | |
| 2364 | + help | |
| 2365 | 2365 | Allow for specifying boot arguments to the kernel at |
| 2366 | 2366 | build time. On some systems (e.g. embedded ones), it is |
| 2367 | 2367 | necessary or convenient to provide some or all of the |
| @@ -2379,7 +2379,7 @@ config CMDLINE · 11 unmodified lines | ||
| 2379 | 2379 | string "Built-in kernel command string" |
| 2380 | 2380 | depends on CMDLINE_BOOL |
| 2381 | 2381 | default "" |
| 2382 | − ---help--- | |
| 2382 | + help | |
| 2383 | 2383 | Enter arguments here that should be compiled into the kernel |
| 2384 | 2384 | image and used at boot time. If the boot loader provides a |
| 2385 | 2385 | command line at boot time, it is appended to this string to |
| @@ -2395,7 +2395,7 @@ config CMDLINE · 9 unmodified lines | ||
| 2395 | 2395 | config CMDLINE_OVERRIDE |
| 2396 | 2396 | bool "Built-in command line overrides boot loader arguments" |
| 2397 | 2397 | depends on CMDLINE_BOOL && CMDLINE != "" |
| 2398 | − ---help--- | |
| 2398 | + help | |
| 2399 | 2399 | Set this option to 'Y' to have the kernel ignore the boot loader |
| 2400 | 2400 | command line, and use ONLY the built-in command line. |
| 2401 | 2401 | |
| @@ -2405,7 +2405,7 @@ config CMDLINE_OVERRIDE · 3 unmodified lines | ||
| 2405 | 2405 | config MODIFY_LDT_SYSCALL |
| 2406 | 2406 | bool "Enable the LDT (local descriptor table)" if EXPERT |
| 2407 | 2407 | default y |
| 2408 | − ---help--- | |
| 2408 | + help | |
| 2409 | 2409 | Linux can allow user programs to install a per-process x86 |
| 2410 | 2410 | Local Descriptor Table (LDT) using the modify_ldt(2) system |
| 2411 | 2411 | call. This is required to run 16-bit or segmented code such as |
| @@ -2469,7 +2469,7 @@ config X86_APM_BOOT · 57 unmodified lines | ||
| 2469 | 2469 | menuconfig APM |
| 2470 | 2470 | tristate "APM (Advanced Power Management) BIOS support" |
| 2471 | 2471 | depends on X86_32 && PM_SLEEP |
| 2472 | − ---help--- | |
| 2472 | + help | |
| 2473 | 2473 | APM is a BIOS specification for saving power using several different |
| 2474 | 2474 | techniques. This is mostly useful for battery powered laptops with |
| 2475 | 2475 | APM compliant BIOSes. If you say Y here, the system time will be |
| @@ -2529,14 +2529,14 @@ if APM · 53 unmodified lines | ||
| 2529 | 2529 | |
| 2530 | 2530 | config APM_IGNORE_USER_SUSPEND |
| 2531 | 2531 | bool "Ignore USER SUSPEND" |
| 2532 | − ---help--- | |
| 2532 | + help | |
| 2533 | 2533 | This option will ignore USER SUSPEND requests. On machines with a |
| 2534 | 2534 | compliant APM BIOS, you want to say N. However, on the NEC Versa M |
| 2535 | 2535 | series notebooks, it is necessary to say Y because of a BIOS bug. |
| 2536 | 2536 | |
| 2537 | 2537 | config APM_DO_ENABLE |
| 2538 | 2538 | bool "Enable PM at boot time" |
| 2539 | − ---help--- | |
| 2539 | + help | |
| 2540 | 2540 | Enable APM features at boot time. From page 36 of the APM BIOS |
| 2541 | 2541 | specification: "When disabled, the APM BIOS does not automatically |
| 2542 | 2542 | power manage devices, enter the Standby State, enter the Suspend |
| @@ -2554,7 +2554,7 @@ config APM_DO_ENABLE · 11 unmodified lines | ||
| 2554 | 2554 | config APM_CPU_IDLE |
| 2555 | 2555 | depends on CPU_IDLE |
| 2556 | 2556 | bool "Make CPU Idle calls when idle" |
| 2557 | − ---help--- | |
| 2557 | + help | |
| 2558 | 2558 | Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop. |
| 2559 | 2559 | On some machines, this can activate improved power savings, such as |
| 2560 | 2560 | a slowed CPU clock rate, when the machine is idle. These idle calls |
| @@ -2565,7 +2565,7 @@ config APM_CPU_IDLE · 4 unmodified lines | ||
| 2565 | 2565 | |
| 2566 | 2566 | config APM_DISPLAY_BLANK |
| 2567 | 2567 | bool "Enable console blanking using APM" |
| 2568 | − ---help--- | |
| 2568 | + help | |
| 2569 | 2569 | Enable console blanking using the APM. Some laptops can use this to |
| 2570 | 2570 | turn off the LCD backlight when the screen blanker of the Linux |
| 2571 | 2571 | virtual console blanks the screen. Note that this is only used by |
| @@ -2578,7 +2578,7 @@ config APM_DISPLAY_BLANK · 6 unmodified lines | ||
| 2578 | 2578 | |
| 2579 | 2579 | config APM_ALLOW_INTS |
| 2580 | 2580 | bool "Allow interrupts during APM BIOS calls" |
| 2581 | − ---help--- | |
| 2581 | + help | |
| 2582 | 2582 | Normally we disable external interrupts while we are making calls to |
| 2583 | 2583 | the APM BIOS as a measure to lessen the effects of a badly behaving |
| 2584 | 2584 | BIOS implementation. The BIOS should reenable interrupts if it |
| @@ -2603,7 +2603,7 @@ choice · 18 unmodified lines | ||
| 2603 | 2603 | prompt "PCI access mode" |
| 2604 | 2604 | depends on X86_32 && PCI |
| 2605 | 2605 | default PCI_GOANY |
| 2606 | − ---help--- | |
| 2606 | + help | |
| 2607 | 2607 | On PCI systems, the BIOS can be used to detect the PCI devices and |
| 2608 | 2608 | determine their configuration. However, some old PCI motherboards |
| 2609 | 2609 | have BIOS bugs and may crash if this is done. Also, some embedded |
| @@ -2700,7 +2700,7 @@ if X86_32 · 90 unmodified lines | ||
| 2700 | 2700 | |
| 2701 | 2701 | config ISA |
| 2702 | 2702 | bool "ISA support" |
| 2703 | − ---help--- | |
| 2703 | + help | |
| 2704 | 2704 | Find out whether you have ISA slots on your motherboard. ISA is the |
| 2705 | 2705 | name of a bus system, i.e. the way the CPU talks to the other stuff |
| 2706 | 2706 | inside your box. Other bus systems are PCI, EISA, MicroChannel |
| @@ -2709,7 +2709,7 @@ config ISA · 2 unmodified lines | ||
| 2709 | 2709 | |
| 2710 | 2710 | config SCx200 |
| 2711 | 2711 | tristate "NatSemi SCx200 support" |
| 2712 | − ---help--- | |
| 2712 | + help | |
| 2713 | 2713 | This provides basic support for National Semiconductor's |
| 2714 | 2714 | (now AMD's) Geode processors. The driver probes for the |
| 2715 | 2715 | PCI-IDs of several on-chip devices, so its a good dependency |
| @@ -2721,7 +2721,7 @@ config SCx200HR_TIMER · 5 unmodified lines | ||
| 2721 | 2721 | tristate "NatSemi SCx200 27MHz High-Resolution Timer Support" |
| 2722 | 2722 | depends on SCx200 |
| 2723 | 2723 | default y |
| 2724 | − ---help--- | |
| 2724 | + help | |
| 2725 | 2725 | This driver provides a clocksource built upon the on-chip |
| 2726 | 2726 | 27MHz high-resolution timer. Its also a workaround for |
| 2727 | 2727 | NSC Geode SC-1100's buggy TSC, which loses time when the |
| @@ -2736,20 +2736,20 @@ config OLPC · 8 unmodified lines | ||
| 2736 | 2736 | select OF_PROMTREE |
| 2737 | 2737 | select IRQ_DOMAIN |
| 2738 | 2738 | select OLPC_EC |
| 2739 | − ---help--- | |
| 2739 | + help | |
| 2740 | 2740 | Add support for detecting the unique features of the OLPC |
| 2741 | 2741 | XO hardware. |
| 2742 | 2742 | |
| 2743 | 2743 | config OLPC_XO1_PM |
| 2744 | 2744 | bool "OLPC XO-1 Power Management" |
| 2745 | 2745 | depends on OLPC && MFD_CS5535=y && PM_SLEEP |
| 2746 | − ---help--- | |
| 2746 | + help | |
| 2747 | 2747 | Add support for poweroff and suspend of the OLPC XO-1 laptop. |
| 2748 | 2748 | |
| 2749 | 2749 | config OLPC_XO1_RTC |
| 2750 | 2750 | bool "OLPC XO-1 Real Time Clock" |
| 2751 | 2751 | depends on OLPC_XO1_PM && RTC_DRV_CMOS |
| 2752 | − ---help--- | |
| 2752 | + help | |
| 2753 | 2753 | Add support for the XO-1 real time clock, which can be used as a |
| 2754 | 2754 | programmable wakeup source. |
| 2755 | 2755 | |
| @@ -2758,7 +2758,7 @@ config OLPC_XO1_SCI · 2 unmodified lines | ||
| 2758 | 2758 | depends on OLPC && OLPC_XO1_PM && GPIO_CS5535=y |
| 2759 | 2759 | depends on INPUT=y |
| 2760 | 2760 | select POWER_SUPPLY |
| 2761 | − ---help--- | |
| 2761 | + help | |
| 2762 | 2762 | Add support for SCI-based features of the OLPC XO-1 laptop: |
| 2763 | 2763 | - EC-driven system wakeups |
| 2764 | 2764 | - Power button |
| @@ -2771,7 +2771,7 @@ config OLPC_XO15_SCI · 6 unmodified lines | ||
| 2771 | 2771 | bool "OLPC XO-1.5 SCI extras" |
| 2772 | 2772 | depends on OLPC && ACPI |
| 2773 | 2773 | select POWER_SUPPLY |
| 2774 | − ---help--- | |
| 2774 | + help | |
| 2775 | 2775 | Add support for SCI-based features of the OLPC XO-1.5 laptop: |
| 2776 | 2776 | - EC-driven system wakeups |
| 2777 | 2777 | - AC adapter status updates |
| @@ -2780,7 +2780,7 @@ config OLPC_XO15_SCI · 2 unmodified lines | ||
| 2780 | 2780 | config ALIX |
| 2781 | 2781 | bool "PCEngines ALIX System Support (LED setup)" |
| 2782 | 2782 | select GPIOLIB |
| 2783 | − ---help--- | |
| 2783 | + help | |
| 2784 | 2784 | This option enables system support for the PCEngines ALIX. |
| 2785 | 2785 | At present this just sets up LEDs for GPIO control on |
| 2786 | 2786 | ALIX2/3/6 boards. However, other system specific setup should |
| @@ -2794,14 +2794,14 @@ config ALIX · 7 unmodified lines | ||
| 2794 | 2794 | config NET5501 |
| 2795 | 2795 | bool "Soekris Engineering net5501 System Support (LEDS, GPIO, etc)" |
| 2796 | 2796 | select GPIOLIB |
| 2797 | − ---help--- | |
| 2797 | + help | |
| 2798 | 2798 | This option enables system support for the Soekris Engineering net5501. |
| 2799 | 2799 | |
| 2800 | 2800 | config GEOS |
| 2801 | 2801 | bool "Traverse Technologies GEOS System Support (LEDS, GPIO, etc)" |
| 2802 | 2802 | select GPIOLIB |
| 2803 | 2803 | depends on DMI |
| 2804 | − ---help--- | |
| 2804 | + help | |
| 2805 | 2805 | This option enables system support for the Traverse Technologies GEOS. |
| 2806 | 2806 | |
| 2807 | 2807 | config TS5500 |
| @@ -2810,7 +2810,7 @@ config TS5500 · 2 unmodified lines | ||
| 2810 | 2810 | select CHECK_SIGNATURE |
| 2811 | 2811 | select NEW_LEDS |
| 2812 | 2812 | select LEDS_CLASS |
| 2813 | − ---help--- | |
| 2813 | + help | |
| 2814 | 2814 | This option enables system support for the Technologic Systems TS-5500. |
| 2815 | 2815 | |
| 2816 | 2816 | endif # X86_32 |
| @@ -2857,7 +2857,7 @@ config IA32_EMULATION · 40 unmodified lines | ||
| 2857 | 2857 | select BINFMT_ELF |
| 2858 | 2858 | select COMPAT_BINFMT_ELF |
| 2859 | 2859 | select COMPAT_OLD_SIGACTION |
| 2860 | − ---help--- | |
| 2860 | + help | |
| 2861 | 2861 | Include code to run legacy 32-bit programs under a |
| 2862 | 2862 | 64-bit kernel. You should likely turn this on, unless you're |
| 2863 | 2863 | 100% sure that you don't have any 32-bit programs left. |
| @@ -2866,13 +2866,13 @@ config IA32_AOUT · 2 unmodified lines | ||
| 2866 | 2866 | tristate "IA32 a.out support" |
| 2867 | 2867 | depends on IA32_EMULATION |
| 2868 | 2868 | depends on BROKEN |
| 2869 | − ---help--- | |
| 2869 | + help | |
| 2870 | 2870 | Support old a.out binaries in the 32bit emulation. |
| 2871 | 2871 | |
| 2872 | 2872 | config X86_X32 |
| 2873 | 2873 | bool "x32 ABI for 64-bit mode" |
| 2874 | 2874 | depends on X86_64 |
| 2875 | − ---help--- | |
| 2875 | + help | |
| 2876 | 2876 | Include code to run binaries for the x32 native 32-bit ABI |
| 2877 | 2877 | for 64-bit processors. An x32 process gets access to the |
| 2878 | 2878 | full 64-bit register file and wide data path while leaving |
| @@ -4,7 +4,7 @@ choice · 3 unmodified lines | ||
| 4 | 4 | prompt "Processor family" |
| 5 | 5 | default M686 if X86_32 |
| 6 | 6 | default GENERIC_CPU if X86_64 |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | This is the processor type of your CPU. This information is |
| 9 | 9 | used for optimizing purposes. In order to compile a kernel |
| 10 | 10 | that can run on all supported x86 CPU types (albeit not |
| @@ -53,21 +53,21 @@ choice · 42 unmodified lines | ||
| 53 | 53 | config M486SX |
| 54 | 54 | bool "486SX" |
| 55 | 55 | depends on X86_32 |
| 56 | − ---help--- | |
| 56 | + help | |
| 57 | 57 | Select this for an 486-class CPU without an FPU such as |
| 58 | 58 | AMD/Cyrix/IBM/Intel SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5S. |
| 59 | 59 | |
| 60 | 60 | config M486 |
| 61 | 61 | bool "486DX" |
| 62 | 62 | depends on X86_32 |
| 63 | − ---help--- | |
| 63 | + help | |
| 64 | 64 | Select this for an 486-class CPU such as AMD/Cyrix/IBM/Intel |
| 65 | 65 | 486DX/DX2/DX4 and UMC U5D. |
| 66 | 66 | |
| 67 | 67 | config M586 |
| 68 | 68 | bool "586/K5/5x86/6x86/6x86MX" |
| 69 | 69 | depends on X86_32 |
| 70 | − ---help--- | |
| 70 | + help | |
| 71 | 71 | Select this for an 586 or 686 series processor such as the AMD K5, |
| 72 | 72 | the Cyrix 5x86, 6x86 and 6x86MX. This choice does not |
| 73 | 73 | assume the RDTSC (Read Time Stamp Counter) instruction. |
| @@ -75,21 +75,21 @@ config M586 · 1 unmodified line | ||
| 75 | 75 | config M586TSC |
| 76 | 76 | bool "Pentium-Classic" |
| 77 | 77 | depends on X86_32 |
| 78 | − ---help--- | |
| 78 | + help | |
| 79 | 79 | Select this for a Pentium Classic processor with the RDTSC (Read |
| 80 | 80 | Time Stamp Counter) instruction for benchmarking. |
| 81 | 81 | |
| 82 | 82 | config M586MMX |
| 83 | 83 | bool "Pentium-MMX" |
| 84 | 84 | depends on X86_32 |
| 85 | − ---help--- | |
| 85 | + help | |
| 86 | 86 | Select this for a Pentium with the MMX graphics/multimedia |
| 87 | 87 | extended instructions. |
| 88 | 88 | |
| 89 | 89 | config M686 |
| 90 | 90 | bool "Pentium-Pro" |
| 91 | 91 | depends on X86_32 |
| 92 | − ---help--- | |
| 92 | + help | |
| 93 | 93 | Select this for Intel Pentium Pro chips. This enables the use of |
| 94 | 94 | Pentium Pro extended instructions, and disables the init-time guard |
| 95 | 95 | against the f00f bug found in earlier Pentiums. |
| @@ -97,7 +97,7 @@ config M686 · 1 unmodified line | ||
| 97 | 97 | config MPENTIUMII |
| 98 | 98 | bool "Pentium-II/Celeron(pre-Coppermine)" |
| 99 | 99 | depends on X86_32 |
| 100 | − ---help--- | |
| 100 | + help | |
| 101 | 101 | Select this for Intel chips based on the Pentium-II and |
| 102 | 102 | pre-Coppermine Celeron core. This option enables an unaligned |
| 103 | 103 | copy optimization, compiles the kernel with optimization flags |
| @@ -107,7 +107,7 @@ config MPENTIUMII · 3 unmodified lines | ||
| 107 | 107 | config MPENTIUMIII |
| 108 | 108 | bool "Pentium-III/Celeron(Coppermine)/Pentium-III Xeon" |
| 109 | 109 | depends on X86_32 |
| 110 | − ---help--- | |
| 110 | + help | |
| 111 | 111 | Select this for Intel chips based on the Pentium-III and |
| 112 | 112 | Celeron-Coppermine core. This option enables use of some |
| 113 | 113 | extended prefetch instructions in addition to the Pentium II |
| @@ -116,14 +116,14 @@ config MPENTIUMIII · 2 unmodified lines | ||
| 116 | 116 | config MPENTIUMM |
| 117 | 117 | bool "Pentium M" |
| 118 | 118 | depends on X86_32 |
| 119 | − ---help--- | |
| 119 | + help | |
| 120 | 120 | Select this for Intel Pentium M (not Pentium-4 M) |
| 121 | 121 | notebook chips. |
| 122 | 122 | |
| 123 | 123 | config MPENTIUM4 |
| 124 | 124 | bool "Pentium-4/Celeron(P4-based)/Pentium-4 M/older Xeon" |
| 125 | 125 | depends on X86_32 |
| 126 | − ---help--- | |
| 126 | + help | |
| 127 | 127 | Select this for Intel Pentium 4 chips. This includes the |
| 128 | 128 | Pentium 4, Pentium D, P4-based Celeron and Xeon, and |
| 129 | 129 | Pentium-4 M (not Pentium M) chips. This option enables compile |
| @@ -159,7 +159,7 @@ config MPENTIUM4 · 29 unmodified lines | ||
| 159 | 159 | config MK6 |
| 160 | 160 | bool "K6/K6-II/K6-III" |
| 161 | 161 | depends on X86_32 |
| 162 | − ---help--- | |
| 162 | + help | |
| 163 | 163 | Select this for an AMD K6-family processor. Enables use of |
| 164 | 164 | some extended instructions, and passes appropriate optimization |
| 165 | 165 | flags to GCC. |
| @@ -167,14 +167,14 @@ config MK6 · 1 unmodified line | ||
| 167 | 167 | config MK7 |
| 168 | 168 | bool "Athlon/Duron/K7" |
| 169 | 169 | depends on X86_32 |
| 170 | − ---help--- | |
| 170 | + help | |
| 171 | 171 | Select this for an AMD Athlon K7-family processor. Enables use of |
| 172 | 172 | some extended instructions, and passes appropriate optimization |
| 173 | 173 | flags to GCC. |
| 174 | 174 | |
| 175 | 175 | config MK8 |
| 176 | 176 | bool "Opteron/Athlon64/Hammer/K8" |
| 177 | − ---help--- | |
| 177 | + help | |
| 178 | 178 | Select this for an AMD Opteron or Athlon64 Hammer-family processor. |
| 179 | 179 | Enables use of some extended instructions, and passes appropriate |
| 180 | 180 | optimization flags to GCC. |
| @@ -182,7 +182,7 @@ config MK8 · 1 unmodified line | ||
| 182 | 182 | config MCRUSOE |
| 183 | 183 | bool "Crusoe" |
| 184 | 184 | depends on X86_32 |
| 185 | − ---help--- | |
| 185 | + help | |
| 186 | 186 | Select this for a Transmeta Crusoe processor. Treats the processor |
| 187 | 187 | like a 586 with TSC, and sets some GCC optimization flags (like a |
| 188 | 188 | Pentium Pro with no alignment requirements). |
| @@ -190,13 +190,13 @@ config MCRUSOE · 1 unmodified line | ||
| 190 | 190 | config MEFFICEON |
| 191 | 191 | bool "Efficeon" |
| 192 | 192 | depends on X86_32 |
| 193 | − ---help--- | |
| 193 | + help | |
| 194 | 194 | Select this for a Transmeta Efficeon processor. |
| 195 | 195 | |
| 196 | 196 | config MWINCHIPC6 |
| 197 | 197 | bool "Winchip-C6" |
| 198 | 198 | depends on X86_32 |
| 199 | − ---help--- | |
| 199 | + help | |
| 200 | 200 | Select this for an IDT Winchip C6 chip. Linux and GCC |
| 201 | 201 | treat this chip as a 586TSC with some extended instructions |
| 202 | 202 | and alignment requirements. |
| @@ -204,7 +204,7 @@ config MWINCHIPC6 · 1 unmodified line | ||
| 204 | 204 | config MWINCHIP3D |
| 205 | 205 | bool "Winchip-2/Winchip-2A/Winchip-3" |
| 206 | 206 | depends on X86_32 |
| 207 | − ---help--- | |
| 207 | + help | |
| 208 | 208 | Select this for an IDT Winchip-2, 2A or 3. Linux and GCC |
| 209 | 209 | treat this chip as a 586TSC with some extended instructions |
| 210 | 210 | and alignment requirements. Also enable out of order memory |
| @@ -214,7 +214,7 @@ config MWINCHIP3D · 3 unmodified lines | ||
| 214 | 214 | config MELAN |
| 215 | 215 | bool "AMD Elan" |
| 216 | 216 | depends on X86_32 |
| 217 | − ---help--- | |
| 217 | + help | |
| 218 | 218 | Select this for an AMD Elan processor. |
| 219 | 219 | |
| 220 | 220 | Do not use this option for K6/Athlon/Opteron processors! |
| @@ -222,19 +222,19 @@ config MELAN · 1 unmodified line | ||
| 222 | 222 | config MGEODEGX1 |
| 223 | 223 | bool "GeodeGX1" |
| 224 | 224 | depends on X86_32 |
| 225 | − ---help--- | |
| 225 | + help | |
| 226 | 226 | Select this for a Geode GX1 (Cyrix MediaGX) chip. |
| 227 | 227 | |
| 228 | 228 | config MGEODE_LX |
| 229 | 229 | bool "Geode GX/LX" |
| 230 | 230 | depends on X86_32 |
| 231 | − ---help--- | |
| 231 | + help | |
| 232 | 232 | Select this for AMD Geode GX and LX processors. |
| 233 | 233 | |
| 234 | 234 | config MCYRIXIII |
| 235 | 235 | bool "CyrixIII/VIA-C3" |
| 236 | 236 | depends on X86_32 |
| 237 | − ---help--- | |
| 237 | + help | |
| 238 | 238 | Select this for a Cyrix III or C3 chip. Presently Linux and GCC |
| 239 | 239 | treat this chip as a generic 586. Whilst the CPU is 686 class, |
| 240 | 240 | it lacks the cmov extension which gcc assumes is present when |
| @@ -246,7 +246,7 @@ config MCYRIXIII · 5 unmodified lines | ||
| 246 | 246 | config MVIAC3_2 |
| 247 | 247 | bool "VIA C3-2 (Nehemiah)" |
| 248 | 248 | depends on X86_32 |
| 249 | − ---help--- | |
| 249 | + help | |
| 250 | 250 | Select this for a VIA C3 "Nehemiah". Selecting this enables usage |
| 251 | 251 | of SSE and tells gcc to treat the CPU as a 686. |
| 252 | 252 | Note, this kernel will not boot on older (pre model 9) C3s. |
| @@ -254,14 +254,14 @@ config MVIAC3_2 · 1 unmodified line | ||
| 254 | 254 | config MVIAC7 |
| 255 | 255 | bool "VIA C7" |
| 256 | 256 | depends on X86_32 |
| 257 | − ---help--- | |
| 257 | + help | |
| 258 | 258 | Select this for a VIA C7. Selecting this uses the correct cache |
| 259 | 259 | shift and tells gcc to treat the CPU as a 686. |
| 260 | 260 | |
| 261 | 261 | config MPSC |
| 262 | 262 | bool "Intel P4 / older Netburst based Xeon" |
| 263 | 263 | depends on X86_64 |
| 264 | − ---help--- | |
| 264 | + help | |
| 265 | 265 | Optimize for Intel Pentium 4, Pentium D and older Nocona/Dempsey |
| 266 | 266 | Xeon CPUs with Intel 64bit which is compatible with x86-64. |
| 267 | 267 | Note that the latest Xeons (Xeon 51xx and 53xx) are not based on the |
| @@ -271,7 +271,7 @@ config MPSC · 3 unmodified lines | ||
| 271 | 271 | |
| 272 | 272 | config MCORE2 |
| 273 | 273 | bool "Core 2/newer Xeon" |
| 274 | − ---help--- | |
| 274 | + help | |
| 275 | 275 | |
| 276 | 276 | Select this for Intel Core 2 and newer Core 2 Xeons (Xeon 51xx and |
| 277 | 277 | 53xx) CPUs. You can distinguish newer from older Xeons by the CPU |
| @@ -280,7 +280,7 @@ config MCORE2 · 2 unmodified lines | ||
| 280 | 280 | |
| 281 | 281 | config MATOM |
| 282 | 282 | bool "Intel Atom" |
| 283 | − ---help--- | |
| 283 | + help | |
| 284 | 284 | |
| 285 | 285 | Select this for the Intel Atom platform. Intel Atom CPUs have an |
| 286 | 286 | in-order pipelining architecture and thus can benefit from |
| @@ -290,7 +290,7 @@ config MATOM · 3 unmodified lines | ||
| 290 | 290 | config GENERIC_CPU |
| 291 | 291 | bool "Generic-x86-64" |
| 292 | 292 | depends on X86_64 |
| 293 | − ---help--- | |
| 293 | + help | |
| 294 | 294 | Generic x86-64 CPU. |
| 295 | 295 | Run equally well on all x86-64 CPUs. |
| 296 | 296 | |
| @@ -299,7 +299,7 @@ endchoice · 2 unmodified lines | ||
| 299 | 299 | config X86_GENERIC |
| 300 | 300 | bool "Generic x86 support" |
| 301 | 301 | depends on X86_32 |
| 302 | − ---help--- | |
| 302 | + help | |
| 303 | 303 | Instead of just including optimizations for the selected |
| 304 | 304 | x86 variant (e.g. PII, Crusoe or Athlon), include some more |
| 305 | 305 | generic optimizations as well. This will make the kernel |
| @@ -397,14 +397,14 @@ config X86_VMX_FEATURE_NAMES · 91 unmodified lines | ||
| 397 | 397 | |
| 398 | 398 | menuconfig PROCESSOR_SELECT |
| 399 | 399 | bool "Supported processor vendors" if EXPERT |
| 400 | − ---help--- | |
| 400 | + help | |
| 401 | 401 | This lets you choose what x86 vendor support code your kernel |
| 402 | 402 | will include. |
| 403 | 403 | |
| 404 | 404 | config CPU_SUP_INTEL |
| 405 | 405 | default y |
| 406 | 406 | bool "Support Intel processors" if PROCESSOR_SELECT |
| 407 | − ---help--- | |
| 407 | + help | |
| 408 | 408 | This enables detection, tunings and quirks for Intel processors |
| 409 | 409 | |
| 410 | 410 | You need this enabled if you want your kernel to run on an |
| @@ -418,7 +418,7 @@ config CPU_SUP_CYRIX_32 · 7 unmodified lines | ||
| 418 | 418 | default y |
| 419 | 419 | bool "Support Cyrix processors" if PROCESSOR_SELECT |
| 420 | 420 | depends on M486SX || M486 || M586 || M586TSC || M586MMX || (EXPERT && !64BIT) |
| 421 | − ---help--- | |
| 421 | + help | |
| 422 | 422 | This enables detection, tunings and quirks for Cyrix processors |
| 423 | 423 | |
| 424 | 424 | You need this enabled if you want your kernel to run on a |
| @@ -431,7 +431,7 @@ config CPU_SUP_CYRIX_32 · 6 unmodified lines | ||
| 431 | 431 | config CPU_SUP_AMD |
| 432 | 432 | default y |
| 433 | 433 | bool "Support AMD processors" if PROCESSOR_SELECT |
| 434 | − ---help--- | |
| 434 | + help | |
| 435 | 435 | This enables detection, tunings and quirks for AMD processors |
| 436 | 436 | |
| 437 | 437 | You need this enabled if you want your kernel to run on an |
| @@ -458,7 +458,7 @@ config CPU_SUP_HYGON · 20 unmodified lines | ||
| 458 | 458 | config CPU_SUP_CENTAUR |
| 459 | 459 | default y |
| 460 | 460 | bool "Support Centaur processors" if PROCESSOR_SELECT |
| 461 | − ---help--- | |
| 461 | + help | |
| 462 | 462 | This enables detection, tunings and quirks for Centaur processors |
| 463 | 463 | |
| 464 | 464 | You need this enabled if you want your kernel to run on a |
| @@ -472,7 +472,7 @@ config CPU_SUP_TRANSMETA_32 · 7 unmodified lines | ||
| 472 | 472 | default y |
| 473 | 473 | bool "Support Transmeta processors" if PROCESSOR_SELECT |
| 474 | 474 | depends on !64BIT |
| 475 | − ---help--- | |
| 475 | + help | |
| 476 | 476 | This enables detection, tunings and quirks for Transmeta processors |
| 477 | 477 | |
| 478 | 478 | You need this enabled if you want your kernel to run on a |
| @@ -486,7 +486,7 @@ config CPU_SUP_UMC_32 · 7 unmodified lines | ||
| 486 | 486 | default y |
| 487 | 487 | bool "Support UMC processors" if PROCESSOR_SELECT |
| 488 | 488 | depends on M486SX || M486 || (EXPERT && !64BIT) |
| 489 | − ---help--- | |
| 489 | + help | |
| 490 | 490 | This enables detection, tunings and quirks for UMC processors |
| 491 | 491 | |
| 492 | 492 | You need this enabled if you want your kernel to run on a |
| @@ -9,7 +9,7 @@ config EARLY_PRINTK_USB · 8 unmodified lines | ||
| 9 | 9 | config X86_VERBOSE_BOOTUP |
| 10 | 10 | bool "Enable verbose x86 bootup info messages" |
| 11 | 11 | default y |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | Enables the informational output from the decompression stage |
| 14 | 14 | (e.g. bzImage) of the boot. If you disable this you will still |
| 15 | 15 | see errors. Disable this if you want silent bootup. |
| @@ -17,7 +17,7 @@ config X86_VERBOSE_BOOTUP · 1 unmodified line | ||
| 17 | 17 | config EARLY_PRINTK |
| 18 | 18 | bool "Early printk" if EXPERT |
| 19 | 19 | default y |
| 20 | − ---help--- | |
| 20 | + help | |
| 21 | 21 | Write kernel log output directly into the VGA buffer or to a serial |
| 22 | 22 | port. |
| 23 | 23 | |
| @@ -31,7 +31,7 @@ config EARLY_PRINTK_DBGP · 7 unmodified lines | ||
| 31 | 31 | bool "Early printk via EHCI debug port" |
| 32 | 32 | depends on EARLY_PRINTK && PCI |
| 33 | 33 | select EARLY_PRINTK_USB |
| 34 | − ---help--- | |
| 34 | + help | |
| 35 | 35 | Write kernel log output directly into the EHCI debug port. |
| 36 | 36 | |
| 37 | 37 | This is useful for kernel debugging when your machine crashes very |
| @@ -44,7 +44,7 @@ config EARLY_PRINTK_USB_XDBC · 6 unmodified lines | ||
| 44 | 44 | bool "Early printk via the xHCI debug port" |
| 45 | 45 | depends on EARLY_PRINTK && PCI |
| 46 | 46 | select EARLY_PRINTK_USB |
| 47 | − ---help--- | |
| 47 | + help | |
| 48 | 48 | Write kernel log output directly into the xHCI debug port. |
| 49 | 49 | |
| 50 | 50 | One use for this feature is kernel debugging, for example when your |
| @@ -66,7 +66,7 @@ config EFI_PGT_DUMP · 15 unmodified lines | ||
| 66 | 66 | bool "Dump the EFI pagetable" |
| 67 | 67 | depends on EFI |
| 68 | 68 | select PTDUMP_CORE |
| 69 | − ---help--- | |
| 69 | + help | |
| 70 | 70 | Enable this if you want to dump the EFI page table before |
| 71 | 71 | enabling virtual mode. This can be used to debug miscellaneous |
| 72 | 72 | issues with the mapping of the EFI runtime regions into that |
| @@ -75,7 +75,7 @@ config EFI_PGT_DUMP · 2 unmodified lines | ||
| 75 | 75 | config DEBUG_TLBFLUSH |
| 76 | 76 | bool "Set upper limit of TLB entries to flush one-by-one" |
| 77 | 77 | depends on DEBUG_KERNEL |
| 78 | − ---help--- | |
| 78 | + help | |
| 79 | 79 | |
| 80 | 80 | X86-only for now. |
| 81 | 81 | |
| @@ -95,7 +95,7 @@ config IOMMU_DEBUG · 13 unmodified lines | ||
| 95 | 95 | bool "Enable IOMMU debugging" |
| 96 | 96 | depends on GART_IOMMU && DEBUG_KERNEL |
| 97 | 97 | depends on X86_64 |
| 98 | − ---help--- | |
| 98 | + help | |
| 99 | 99 | Force the IOMMU to on even when you have less than 4GB of |
| 100 | 100 | memory and add debugging code. On overflow always panic. And |
| 101 | 101 | allow to enable IOMMU leak tracing. Can be disabled at boot |
| @@ -110,7 +110,7 @@ config IOMMU_DEBUG · 8 unmodified lines | ||
| 110 | 110 | config IOMMU_LEAK |
| 111 | 111 | bool "IOMMU leak tracing" |
| 112 | 112 | depends on IOMMU_DEBUG && DMA_API_DEBUG |
| 113 | − ---help--- | |
| 113 | + help | |
| 114 | 114 | Add a simple leak tracer to the IOMMU code. This is useful when you |
| 115 | 115 | are debugging a buggy device driver that leaks IOMMU mappings. |
| 116 | 116 | |
| @@ -121,7 +121,7 @@ config X86_DECODER_SELFTEST · 4 unmodified lines | ||
| 121 | 121 | bool "x86 instruction decoder selftest" |
| 122 | 122 | depends on DEBUG_KERNEL && INSTRUCTION_DECODER |
| 123 | 123 | depends on !COMPILE_TEST |
| 124 | − ---help--- | |
| 124 | + help | |
| 125 | 125 | Perform x86 instruction decoder selftests at build time. |
| 126 | 126 | This option is useful for checking the sanity of x86 instruction |
| 127 | 127 | decoder code. |
| @@ -133,25 +133,25 @@ choice · 5 unmodified lines | ||
| 133 | 133 | |
| 134 | 134 | config IO_DELAY_0X80 |
| 135 | 135 | bool "port 0x80 based port-IO delay [recommended]" |
| 136 | − ---help--- | |
| 136 | + help | |
| 137 | 137 | This is the traditional Linux IO delay used for in/out_p. |
| 138 | 138 | It is the most tested hence safest selection here. |
| 139 | 139 | |
| 140 | 140 | config IO_DELAY_0XED |
| 141 | 141 | bool "port 0xed based port-IO delay" |
| 142 | − ---help--- | |
| 142 | + help | |
| 143 | 143 | Use port 0xed as the IO delay. This frees up port 0x80 which is |
| 144 | 144 | often used as a hardware-debug port. |
| 145 | 145 | |
| 146 | 146 | config IO_DELAY_UDELAY |
| 147 | 147 | bool "udelay based port-IO delay" |
| 148 | − ---help--- | |
| 148 | + help | |
| 149 | 149 | Use udelay(2) as the IO delay method. This provides the delay |
| 150 | 150 | while not having any side-effect on the IO port space. |
| 151 | 151 | |
| 152 | 152 | config IO_DELAY_NONE |
| 153 | 153 | bool "no port-IO delay" |
| 154 | − ---help--- | |
| 154 | + help | |
| 155 | 155 | No port-IO delay. Will break on old boxes that require port-IO |
| 156 | 156 | delay for certain operations. Should work on most new machines. |
| 157 | 157 | |
| @@ -161,19 +161,19 @@ config DEBUG_BOOT_PARAMS · 3 unmodified lines | ||
| 161 | 161 | bool "Debug boot parameters" |
| 162 | 162 | depends on DEBUG_KERNEL |
| 163 | 163 | depends on DEBUG_FS |
| 164 | − ---help--- | |
| 164 | + help | |
| 165 | 165 | This option will cause struct boot_params to be exported via debugfs. |
| 166 | 166 | |
| 167 | 167 | config CPA_DEBUG |
| 168 | 168 | bool "CPA self-test code" |
| 169 | 169 | depends on DEBUG_KERNEL |
| 170 | − ---help--- | |
| 170 | + help | |
| 171 | 171 | Do change_page_attr() self-tests every 30 seconds. |
| 172 | 172 | |
| 173 | 173 | config DEBUG_ENTRY |
| 174 | 174 | bool "Debug low-level entry code" |
| 175 | 175 | depends on DEBUG_KERNEL |
| 176 | − ---help--- | |
| 176 | + help | |
| 177 | 177 | This option enables sanity checks in x86's low-level entry code. |
| 178 | 178 | Some of these sanity checks may slow down kernel entries and |
| 179 | 179 | exits or otherwise impact performance. |
| @@ -183,7 +183,7 @@ config DEBUG_ENTRY · 3 unmodified lines | ||
| 183 | 183 | config DEBUG_NMI_SELFTEST |
| 184 | 184 | bool "NMI Selftest" |
| 185 | 185 | depends on DEBUG_KERNEL && X86_LOCAL_APIC |
| 186 | − ---help--- | |
| 186 | + help | |
| 187 | 187 | Enabling this option turns on a quick NMI selftest to verify |
| 188 | 188 | that the NMI behaves correctly. |
| 189 | 189 | |
| @@ -195,7 +195,7 @@ config DEBUG_NMI_SELFTEST · 5 unmodified lines | ||
| 195 | 195 | config DEBUG_IMR_SELFTEST |
| 196 | 196 | bool "Isolated Memory Region self test" |
| 197 | 197 | depends on INTEL_IMR |
| 198 | − ---help--- | |
| 198 | + help | |
| 199 | 199 | This option enables automated sanity testing of the IMR code. |
| 200 | 200 | Some simple tests are run to verify IMR bounds checking, alignment |
| 201 | 201 | and overlapping. This option is really only useful if you are |
| @@ -208,7 +208,7 @@ config X86_DEBUG_FPU · 6 unmodified lines | ||
| 208 | 208 | bool "Debug the x86 FPU code" |
| 209 | 209 | depends on DEBUG_KERNEL |
| 210 | 210 | default y |
| 211 | − ---help--- | |
| 211 | + help | |
| 212 | 212 | If this option is enabled then there will be extra sanity |
| 213 | 213 | checks and (boot time) debug printouts added to the kernel. |
| 214 | 214 | This debugging adds some small amount of runtime overhead |
| @@ -221,7 +221,7 @@ config PUNIT_ATOM_DEBUG · 6 unmodified lines | ||
| 221 | 221 | depends on PCI |
| 222 | 222 | select DEBUG_FS |
| 223 | 223 | select IOSF_MBI |
| 224 | − ---help--- | |
| 224 | + help | |
| 225 | 225 | This is a debug driver, which gets the power states |
| 226 | 226 | of all Punit North Complex devices. The power states of |
| 227 | 227 | each device is exposed as part of the debugfs interface. |
| @@ -232,7 +232,7 @@ choice · 4 unmodified lines | ||
| 232 | 232 | prompt "Choose kernel unwinder" |
| 233 | 233 | default UNWINDER_ORC if X86_64 |
| 234 | 234 | default UNWINDER_FRAME_POINTER if X86_32 |
| 235 | − ---help--- | |
| 235 | + help | |
| 236 | 236 | This determines which method will be used for unwinding kernel stack |
| 237 | 237 | traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack, |
| 238 | 238 | livepatch, lockdep, and more. |
| @@ -241,7 +241,7 @@ config UNWINDER_ORC · 2 unmodified lines | ||
| 241 | 241 | bool "ORC unwinder" |
| 242 | 242 | depends on X86_64 |
| 243 | 243 | select STACK_VALIDATION |
| 244 | − ---help--- | |
| 244 | + help | |
| 245 | 245 | This option enables the ORC (Oops Rewind Capability) unwinder for |
| 246 | 246 | unwinding kernel stack traces. It uses a custom data format which is |
| 247 | 247 | a simplified version of the DWARF Call Frame Information standard. |
| @@ -256,7 +256,7 @@ config UNWINDER_ORC · 8 unmodified lines | ||
| 256 | 256 | config UNWINDER_FRAME_POINTER |
| 257 | 257 | bool "Frame pointer unwinder" |
| 258 | 258 | select FRAME_POINTER |
| 259 | − ---help--- | |
| 259 | + help | |
| 260 | 260 | This option enables the frame pointer unwinder for unwinding kernel |
| 261 | 261 | stack traces. |
| 262 | 262 | |
| @@ -268,7 +268,7 @@ config UNWINDER_GUESS · 5 unmodified lines | ||
| 268 | 268 | bool "Guess unwinder" |
| 269 | 269 | depends on EXPERT |
| 270 | 270 | depends on !STACKDEPOT |
| 271 | − ---help--- | |
| 271 | + help | |
| 272 | 272 | This option enables the "guess" unwinder for unwinding kernel stack |
| 273 | 273 | traces. It scans the stack and reports every kernel text address it |
| 274 | 274 | finds. Some of the addresses it reports may be incorrect. |
| @@ -5,7 +5,7 @@ config PERF_EVENTS_INTEL_UNCORE · 4 unmodified lines | ||
| 5 | 5 | tristate "Intel uncore performance events" |
| 6 | 6 | depends on PERF_EVENTS && CPU_SUP_INTEL && PCI |
| 7 | 7 | default y |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | Include support for Intel uncore performance events. These are |
| 10 | 10 | available on NehalemEX and more modern processors. |
| 11 | 11 | |
| @@ -13,7 +13,7 @@ config PERF_EVENTS_INTEL_RAPL · 1 unmodified line | ||
| 13 | 13 | tristate "Intel/AMD rapl performance events" |
| 14 | 14 | depends on PERF_EVENTS && (CPU_SUP_INTEL || CPU_SUP_AMD) && PCI |
| 15 | 15 | default y |
| 16 | − ---help--- | |
| 16 | + help | |
| 17 | 17 | Include support for Intel and AMD rapl performance events for power |
| 18 | 18 | monitoring on modern processors. |
| 19 | 19 | |
| @@ -21,14 +21,14 @@ config PERF_EVENTS_INTEL_CSTATE · 1 unmodified line | ||
| 21 | 21 | tristate "Intel cstate performance events" |
| 22 | 22 | depends on PERF_EVENTS && CPU_SUP_INTEL && PCI |
| 23 | 23 | default y |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | Include support for Intel cstate performance events for power |
| 26 | 26 | monitoring on modern processors. |
| 27 | 27 | |
| 28 | 28 | config PERF_EVENTS_AMD_POWER |
| 29 | 29 | depends on PERF_EVENTS && CPU_SUP_AMD |
| 30 | 30 | tristate "AMD Processor Power Reporting Mechanism" |
| 31 | − ---help--- | |
| 31 | + help | |
| 32 | 32 | Provide power reporting mechanism support for AMD processors. |
| 33 | 33 | Currently, it leverages X86_FEATURE_ACC_POWER |
| 34 | 34 | (CPUID Fn8000_0007_EDX[12]) interface to calculate the |
| @@ -9,7 +9,7 @@ menuconfig VIRTUALIZATION · 8 unmodified lines | ||
| 9 | 9 | bool "Virtualization" |
| 10 | 10 | depends on HAVE_KVM || X86 |
| 11 | 11 | default y |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | Say Y here to get to see options for using your Linux host to run other |
| 14 | 14 | operating systems inside virtual machines (guests). |
| 15 | 15 | This option alone does not add any kernel code. |
| @@ -45,7 +45,7 @@ config KVM · 29 unmodified lines | ||
| 45 | 45 | select KVM_GENERIC_DIRTYLOG_READ_PROTECT |
| 46 | 46 | select KVM_VFIO |
| 47 | 47 | select SRCU |
| 48 | − ---help--- | |
| 48 | + help | |
| 49 | 49 | Support hosting fully virtualized guest machines using hardware |
| 50 | 50 | virtualization extensions. You will need a fairly recent |
| 51 | 51 | processor equipped with virtualization extensions. You will also |
| @@ -75,7 +75,7 @@ config KVM_WERROR · 23 unmodified lines | ||
| 75 | 75 | config KVM_INTEL |
| 76 | 76 | tristate "KVM for Intel (and compatible) processors support" |
| 77 | 77 | depends on KVM && IA32_FEAT_CTL |
| 78 | − ---help--- | |
| 78 | + help | |
| 79 | 79 | Provides support for KVM on processors equipped with Intel's VT |
| 80 | 80 | extensions, a.k.a. Virtual Machine Extensions (VMX). |
| 81 | 81 | |
| @@ -85,7 +85,7 @@ config KVM_INTEL · 3 unmodified lines | ||
| 85 | 85 | config KVM_AMD |
| 86 | 86 | tristate "KVM for AMD processors support" |
| 87 | 87 | depends on KVM |
| 88 | − ---help--- | |
| 88 | + help | |
| 89 | 89 | Provides support for KVM on AMD processors equipped with the AMD-V |
| 90 | 90 | (SVM) extensions. |
| 91 | 91 | |
| @@ -97,13 +97,13 @@ config KVM_AMD_SEV · 5 unmodified lines | ||
| 97 | 97 | bool "AMD Secure Encrypted Virtualization (SEV) support" |
| 98 | 98 | depends on KVM_AMD && X86_64 |
| 99 | 99 | depends on CRYPTO_DEV_SP_PSP && !(KVM_AMD=y && CRYPTO_DEV_CCP_DD=m) |
| 100 | − ---help--- | |
| 100 | + help | |
| 101 | 101 | Provides support for launching Encrypted VMs on AMD processors. |
| 102 | 102 | |
| 103 | 103 | config KVM_MMU_AUDIT |
| 104 | 104 | bool "Audit KVM MMU" |
| 105 | 105 | depends on KVM && TRACEPOINTS |
| 106 | − ---help--- | |
| 106 | + help | |
| 107 | 107 | This option adds a R/W kVM module parameter 'mmu_audit', which allows |
| 108 | 108 | auditing of KVM MMU events at runtime. |
| 109 | 109 | |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config RAS_CEC |
| 3 | 3 | bool "Correctable Errors Collector" |
| 4 | 4 | depends on X86_MCE && MEMORY_FAILURE && DEBUG_FS |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This is a small cache which collects correctable memory errors per 4K |
| 7 | 7 | page PFN and counts their repeated occurrence. Once the counter for a |
| 8 | 8 | PFN overflows, we try to soft-offline that page as we take it to mean |
| @@ -66,7 +66,7 @@ config BLK_DEV_BSGLIB · 65 unmodified lines | ||
| 66 | 66 | |
| 67 | 67 | config BLK_DEV_INTEGRITY |
| 68 | 68 | bool "Block layer data integrity support" |
| 69 | − ---help--- | |
| 69 | + help | |
| 70 | 70 | Some storage devices allow extra information to be |
| 71 | 71 | stored/retrieved to help protect the data. The block layer |
| 72 | 72 | data integrity option provides hooks which can be used by |
| @@ -84,7 +84,7 @@ config BLK_DEV_INTEGRITY_T10 · 11 unmodified lines | ||
| 84 | 84 | config BLK_DEV_ZONED |
| 85 | 85 | bool "Zoned block device support" |
| 86 | 86 | select MQ_IOSCHED_DEADLINE |
| 87 | − ---help--- | |
| 87 | + help | |
| 88 | 88 | Block layer zoned block device support. This option enables |
| 89 | 89 | support for ZAC/ZBC host-managed and host-aware zoned block devices. |
| 90 | 90 | |
| @@ -94,7 +94,7 @@ config BLK_DEV_THROTTLING · 3 unmodified lines | ||
| 94 | 94 | bool "Block layer bio throttling support" |
| 95 | 95 | depends on BLK_CGROUP=y |
| 96 | 96 | select BLK_CGROUP_RWSTAT |
| 97 | − ---help--- | |
| 97 | + help | |
| 98 | 98 | Block layer bio throttling support. It can be used to limit |
| 99 | 99 | the IO rate to a device. IO rate policies are per cgroup and |
| 100 | 100 | one needs to mount and use blkio cgroup controller for creating |
| @@ -105,7 +105,7 @@ config BLK_DEV_THROTTLING · 4 unmodified lines | ||
| 105 | 105 | config BLK_DEV_THROTTLING_LOW |
| 106 | 106 | bool "Block throttling .low limit interface support (EXPERIMENTAL)" |
| 107 | 107 | depends on BLK_DEV_THROTTLING |
| 108 | − ---help--- | |
| 108 | + help | |
| 109 | 109 | Add .low limit interface for block throttling. The low limit is a best |
| 110 | 110 | effort limit to prioritize cgroups. Depending on the setting, the limit |
| 111 | 111 | can be used to protect cgroups in terms of bandwidth/iops and better |
| @@ -115,7 +115,7 @@ config BLK_DEV_THROTTLING_LOW · 3 unmodified lines | ||
| 115 | 115 | |
| 116 | 116 | config BLK_CMDLINE_PARSER |
| 117 | 117 | bool "Block device command line partition parser" |
| 118 | − ---help--- | |
| 118 | + help | |
| 119 | 119 | Enabling this option allows you to specify the partition layout from |
| 120 | 120 | the kernel boot args. This is typically of use for embedded devices |
| 121 | 121 | which don't otherwise have any standardized method for listing the |
| @@ -125,7 +125,7 @@ config BLK_CMDLINE_PARSER · 3 unmodified lines | ||
| 125 | 125 | |
| 126 | 126 | config BLK_WBT |
| 127 | 127 | bool "Enable support for block device writeback throttling" |
| 128 | − ---help--- | |
| 128 | + help | |
| 129 | 129 | Enabling this option enables the block layer to throttle buffered |
| 130 | 130 | background writeback from the VM, making it more smooth and having |
| 131 | 131 | less impact on foreground operations. The throttling is done |
| @@ -135,7 +135,7 @@ config BLK_WBT · 3 unmodified lines | ||
| 135 | 135 | config BLK_CGROUP_IOLATENCY |
| 136 | 136 | bool "Enable support for latency based cgroup IO protection" |
| 137 | 137 | depends on BLK_CGROUP=y |
| 138 | − ---help--- | |
| 138 | + help | |
| 139 | 139 | Enabling this option enables the .latency interface for IO throttling. |
| 140 | 140 | The IO controller will attempt to maintain average IO latencies below |
| 141 | 141 | the configured latency target, throttling anybody with a higher latency |
| @@ -148,7 +148,7 @@ config BLK_CGROUP_IOCOST · 6 unmodified lines | ||
| 148 | 148 | depends on BLK_CGROUP=y |
| 149 | 149 | select BLK_RQ_IO_DATA_LEN |
| 150 | 150 | select BLK_RQ_ALLOC_TIME |
| 151 | − ---help--- | |
| 151 | + help | |
| 152 | 152 | Enabling this option enables the .weight interface for cost |
| 153 | 153 | model based proportional IO control. The IO controller |
| 154 | 154 | distributes IO capacity between different groups based on |
| @@ -158,7 +158,7 @@ config BLK_WBT_MQ · 3 unmodified lines | ||
| 158 | 158 | bool "Multiqueue writeback throttling" |
| 159 | 159 | default y |
| 160 | 160 | depends on BLK_WBT |
| 161 | − ---help--- | |
| 161 | + help | |
| 162 | 162 | Enable writeback throttling by default on multiqueue devices. |
| 163 | 163 | Multiqueue currently doesn't have support for IO scheduling, |
| 164 | 164 | enabling this option is recommended. |
| @@ -167,7 +167,7 @@ config BLK_DEBUG_FS · 2 unmodified lines | ||
| 167 | 167 | bool "Block layer debugging information in debugfs" |
| 168 | 168 | default y |
| 169 | 169 | depends on DEBUG_FS |
| 170 | − ---help--- | |
| 170 | + help | |
| 171 | 171 | Include block layer debugging information in debugfs. This information |
| 172 | 172 | is mostly useful for kernel developers, but it doesn't incur any cost |
| 173 | 173 | at runtime. |
| @@ -181,7 +181,7 @@ config BLK_DEBUG_FS_ZONED · 7 unmodified lines | ||
| 181 | 181 | |
| 182 | 182 | config BLK_SED_OPAL |
| 183 | 183 | bool "Logic for interfacing with Opal enabled SEDs" |
| 184 | − ---help--- | |
| 184 | + help | |
| 185 | 185 | Builds Logic for interfacing with Opal enabled controllers. |
| 186 | 186 | Enabling this option enables users to setup/unlock/lock |
| 187 | 187 | Locking ranges for SED devices using the Opal protocol. |
| @@ -6,13 +6,13 @@ menu "IO Schedulers" · 5 unmodified lines | ||
| 6 | 6 | config MQ_IOSCHED_DEADLINE |
| 7 | 7 | tristate "MQ deadline I/O scheduler" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | MQ version of the deadline IO scheduler. |
| 11 | 11 | |
| 12 | 12 | config MQ_IOSCHED_KYBER |
| 13 | 13 | tristate "Kyber I/O scheduler" |
| 14 | 14 | default y |
| 15 | − ---help--- | |
| 15 | + help | |
| 16 | 16 | The Kyber I/O scheduler is a low-overhead scheduler suitable for |
| 17 | 17 | multiqueue and other fast devices. Given target latencies for reads and |
| 18 | 18 | synchronous writes, it will self-tune queue depths to achieve that |
| @@ -20,7 +20,7 @@ config MQ_IOSCHED_KYBER · 1 unmodified line | ||
| 20 | 20 | |
| 21 | 21 | config IOSCHED_BFQ |
| 22 | 22 | tristate "BFQ I/O scheduler" |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | BFQ I/O scheduler for BLK-MQ. BFQ distributes the bandwidth of |
| 25 | 25 | of the device among all processes according to their weights, |
| 26 | 26 | regardless of the device parameters and with any workload. It |
| @@ -32,7 +32,7 @@ config BFQ_GROUP_IOSCHED · 5 unmodified lines | ||
| 32 | 32 | bool "BFQ hierarchical scheduling support" |
| 33 | 33 | depends on IOSCHED_BFQ && BLK_CGROUP |
| 34 | 34 | select BLK_CGROUP_RWSTAT |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | |
| 37 | 37 | Enable hierarchical scheduling in BFQ, using the blkio |
| 38 | 38 | (cgroups-v1) or io (cgroups-v2) controller. |
| @@ -40,7 +40,7 @@ config BFQ_GROUP_IOSCHED · 1 unmodified line | ||
| 40 | 40 | config BFQ_CGROUP_DEBUG |
| 41 | 41 | bool "BFQ IO controller debugging" |
| 42 | 42 | depends on BFQ_GROUP_IOSCHED |
| 43 | − ---help--- | |
| 43 | + help | |
| 44 | 44 | Enable some debugging help. Currently it exports additional stat |
| 45 | 45 | files in a cgroup which can be useful for debugging. |
| 46 | 46 | |
| @@ -156,7 +156,7 @@ config SOLARIS_X86_PARTITION · 155 unmodified lines | ||
| 156 | 156 | config UNIXWARE_DISKLABEL |
| 157 | 157 | bool "Unixware slices support" |
| 158 | 158 | depends on PARTITION_ADVANCED && MSDOS_PARTITION |
| 159 | − ---help--- | |
| 159 | + help | |
| 160 | 160 | Like some systems, UnixWare uses its own slice table inside a |
| 161 | 161 | partition (VTOC - Virtual Table of Contents). Its format is |
| 162 | 162 | incompatible with all other OSes. Saying Y here allows you to read |
| @@ -176,7 +176,7 @@ config UNIXWARE_DISKLABEL · 13 unmodified lines | ||
| 176 | 176 | config LDM_PARTITION |
| 177 | 177 | bool "Windows Logical Disk Manager (Dynamic Disk) support" |
| 178 | 178 | depends on PARTITION_ADVANCED |
| 179 | − ---help--- | |
| 179 | + help | |
| 180 | 180 | Say Y here if you would like to use hard disks under Linux which |
| 181 | 181 | were partitioned using Windows 2000's/XP's or Vista's Logical Disk |
| 182 | 182 | Manager. They are also known as "Dynamic Disks". |
| @@ -226,7 +226,7 @@ config ULTRIX_PARTITION · 43 unmodified lines | ||
| 226 | 226 | config SUN_PARTITION |
| 227 | 227 | bool "Sun partition tables support" if PARTITION_ADVANCED |
| 228 | 228 | default y if (SPARC || SUN3 || SUN3X) |
| 229 | − ---help--- | |
| 229 | + help | |
| 230 | 230 | Like most systems, SunOS uses its own hard disk partition table |
| 231 | 231 | format, incompatible with all others. Saying Y here allows you to |
| 232 | 232 | read these partition tables and further mount SunOS partitions from |
| @@ -1,7 +1,7 @@ | ||
| 1 | 1 | # SPDX-License-Identifier: GPL-2.0 |
| 2 | 2 | menuconfig ACCESSIBILITY |
| 3 | 3 | bool "Accessibility support" |
| 4 | − ---help--- | |
| 4 | + help | |
| 5 | 5 | Accessibility handles all special kinds of hardware devices or |
| 6 | 6 | software adapters which help people with disabilities (e.g. |
| 7 | 7 | blindness) to use computers. |
| @@ -21,7 +21,7 @@ config A11Y_BRAILLE_CONSOLE · 13 unmodified lines | ||
| 21 | 21 | bool "Console on braille device" |
| 22 | 22 | depends on VT |
| 23 | 23 | depends on SERIAL_CORE_CONSOLE |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | Enables console output on a braille device connected to a 8250 |
| 26 | 26 | serial port. For now only the VisioBraille device is supported. |
| 27 | 27 | |
| @@ -3,7 +3,7 @@ menu "Android" · 2 unmodified lines | ||
| 3 | 3 | |
| 4 | 4 | config ANDROID |
| 5 | 5 | bool "Android Drivers" |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | Enable support for various drivers needed on the Android platform |
| 8 | 8 | |
| 9 | 9 | if ANDROID |
| @@ -12,7 +12,7 @@ config ANDROID_BINDER_IPC · 2 unmodified lines | ||
| 12 | 12 | bool "Android Binder IPC Driver" |
| 13 | 13 | depends on MMU |
| 14 | 14 | default n |
| 15 | − ---help--- | |
| 15 | + help | |
| 16 | 16 | Binder is used in Android for both communication between processes, |
| 17 | 17 | and remote method invocation. |
| 18 | 18 | |
| @@ -24,7 +24,7 @@ config ANDROID_BINDERFS · 5 unmodified lines | ||
| 24 | 24 | bool "Android Binderfs filesystem" |
| 25 | 25 | depends on ANDROID_BINDER_IPC |
| 26 | 26 | default n |
| 27 | − ---help--- | |
| 27 | + help | |
| 28 | 28 | Binderfs is a pseudo-filesystem for the Android Binder IPC driver |
| 29 | 29 | which can be mounted per-ipc namespace allowing to run multiple |
| 30 | 30 | instances of Android. |
| @@ -36,7 +36,7 @@ config ANDROID_BINDER_DEVICES · 5 unmodified lines | ||
| 36 | 36 | string "Android Binder devices" |
| 37 | 37 | depends on ANDROID_BINDER_IPC |
| 38 | 38 | default "binder,hwbinder,vndbinder" |
| 39 | − ---help--- | |
| 39 | + help | |
| 40 | 40 | Default value for the binder.devices parameter. |
| 41 | 41 | |
| 42 | 42 | The binder.devices parameter is a comma-separated list of strings |
| @@ -47,7 +47,7 @@ config ANDROID_BINDER_DEVICES · 4 unmodified lines | ||
| 47 | 47 | config ANDROID_BINDER_IPC_SELFTEST |
| 48 | 48 | bool "Android Binder IPC Driver Selftest" |
| 49 | 49 | depends on ANDROID_BINDER_IPC |
| 50 | − ---help--- | |
| 50 | + help | |
| 51 | 51 | This feature allows binder selftest to run. |
| 52 | 52 | |
| 53 | 53 | Binder selftest checks the allocation and free of binder buffers |
| @@ -17,7 +17,7 @@ menuconfig ATA · 16 unmodified lines | ||
| 17 | 17 | depends on BLOCK |
| 18 | 18 | select SCSI |
| 19 | 19 | select GLOB |
| 20 | − ---help--- | |
| 20 | + help | |
| 21 | 21 | If you want to use an ATA hard disk, ATA tape drive, ATA CD-ROM or |
| 22 | 22 | any other ATA device under Linux, say Y and make sure that you know |
| 23 | 23 | the name of your ATA host adapter (the card inside your computer |
| @@ -7,7 +7,7 @@ menuconfig ATM_DRIVERS · 6 unmodified lines | ||
| 7 | 7 | bool "ATM drivers" |
| 8 | 8 | depends on NETDEVICES && ATM |
| 9 | 9 | default y |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Say Y here to get to see options for Asynchronous Transfer Mode |
| 12 | 12 | device drivers. This option alone does not add any kernel code. |
| 13 | 13 | |
| @@ -40,7 +40,7 @@ config ATM_LANAI · 26 unmodified lines | ||
| 40 | 40 | config ATM_ENI |
| 41 | 41 | tristate "Efficient Networks ENI155P" |
| 42 | 42 | depends on PCI |
| 43 | − ---help--- | |
| 43 | + help | |
| 44 | 44 | Driver for the Efficient Networks ENI155p series and SMC ATM |
| 45 | 45 | Power155 155 Mbps ATM adapters. Both, the versions with 512KB and |
| 46 | 46 | 2MB on-board RAM (Efficient calls them "C" and "S", respectively), |
| @@ -64,7 +64,7 @@ config ATM_ENI_DEBUG · 17 unmodified lines | ||
| 64 | 64 | config ATM_ENI_TUNE_BURST |
| 65 | 65 | bool "Fine-tune burst settings" |
| 66 | 66 | depends on ATM_ENI |
| 67 | − ---help--- | |
| 67 | + help | |
| 68 | 68 | In order to obtain good throughput, the ENI NIC can transfer |
| 69 | 69 | multiple words of data per PCI bus access cycle. Such a multi-word |
| 70 | 70 | transfer is called a burst. |
| @@ -256,7 +256,7 @@ config ATM_AMBASSADOR · 185 unmodified lines | ||
| 256 | 256 | config ATM_AMBASSADOR_DEBUG |
| 257 | 257 | bool "Enable debugging messages" |
| 258 | 258 | depends on ATM_AMBASSADOR |
| 259 | − ---help--- | |
| 259 | + help | |
| 260 | 260 | Somewhat useful debugging messages are available. The choice of |
| 261 | 261 | messages is controlled by a bitmap. This may be specified as a |
| 262 | 262 | module argument (kernel command line argument as well?), changed |
| @@ -280,7 +280,7 @@ config ATM_HORIZON · 17 unmodified lines | ||
| 280 | 280 | config ATM_HORIZON_DEBUG |
| 281 | 281 | bool "Enable debugging messages" |
| 282 | 282 | depends on ATM_HORIZON |
| 283 | − ---help--- | |
| 283 | + help | |
| 284 | 284 | Somewhat useful debugging messages are available. The choice of |
| 285 | 285 | messages is controlled by a bitmap. This may be specified as a |
| 286 | 286 | module argument (kernel command line argument as well?), changed |
| @@ -296,7 +296,7 @@ config ATM_HORIZON_DEBUG · 9 unmodified lines | ||
| 296 | 296 | config ATM_IA |
| 297 | 297 | tristate "Interphase ATM PCI x575/x525/x531" |
| 298 | 298 | depends on PCI |
| 299 | − ---help--- | |
| 299 | + help | |
| 300 | 300 | This is a driver for the Interphase (i)ChipSAR adapter cards |
| 301 | 301 | which include a variety of variants in term of the size of the |
| 302 | 302 | control memory (128K-1KVC, 512K-4KVC), the size of the packet |
| @@ -312,7 +312,7 @@ config ATM_IA · 9 unmodified lines | ||
| 312 | 312 | config ATM_IA_DEBUG |
| 313 | 313 | bool "Enable debugging messages" |
| 314 | 314 | depends on ATM_IA |
| 315 | − ---help--- | |
| 315 | + help | |
| 316 | 316 | Somewhat useful debugging messages are available. The choice of |
| 317 | 317 | messages is controlled by a bitmap. This may be specified as a |
| 318 | 318 | module argument (kernel command line argument as well?), changed |
| @@ -330,7 +330,7 @@ config ATM_FORE200E · 11 unmodified lines | ||
| 330 | 330 | tristate "FORE Systems 200E-series" |
| 331 | 331 | depends on (PCI || SBUS) |
| 332 | 332 | select FW_LOADER |
| 333 | − ---help--- | |
| 333 | + help | |
| 334 | 334 | This is a driver for the FORE Systems 200E-series ATM adapter |
| 335 | 335 | cards. It simultaneously supports PCA-200E and SBA-200E models |
| 336 | 336 | on PCI and SBUS hosts. Say Y (or M to compile as a module |
| @@ -352,7 +352,7 @@ config ATM_FORE200E_TX_RETRY · 15 unmodified lines | ||
| 352 | 352 | int "Maximum number of tx retries" |
| 353 | 353 | depends on ATM_FORE200E |
| 354 | 354 | default "16" |
| 355 | − ---help--- | |
| 355 | + help | |
| 356 | 356 | Specifies the number of times the driver attempts to transmit |
| 357 | 357 | a message before giving up, if the transmit queue of the ATM card |
| 358 | 358 | is transiently saturated. |
| @@ -8,7 +8,7 @@ · 7 unmodified lines | ||
| 8 | 8 | |
| 9 | 9 | menuconfig AUXDISPLAY |
| 10 | 10 | bool "Auxiliary Display support" |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | Say Y here to get to see options for auxiliary display drivers. |
| 13 | 13 | This option alone does not add any kernel code. |
| 14 | 14 | |
| @@ -20,7 +20,7 @@ config HD44780 · 5 unmodified lines | ||
| 20 | 20 | tristate "HD44780 Character LCD support" |
| 21 | 21 | depends on GPIOLIB || COMPILE_TEST |
| 22 | 22 | select CHARLCD |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | Enable support for Character LCDs using a HD44780 controller. |
| 25 | 25 | The LCD is accessible through the /dev/lcd char device (10, 156). |
| 26 | 26 | This code can either be compiled as a module, or linked into the |
| @@ -31,7 +31,7 @@ config KS0108 · 4 unmodified lines | ||
| 31 | 31 | tristate "KS0108 LCD Controller" |
| 32 | 32 | depends on PARPORT_PC |
| 33 | 33 | default n |
| 34 | − ---help--- | |
| 34 | + help | |
| 35 | 35 | If you have a LCD controlled by one or more KS0108 |
| 36 | 36 | controllers, say Y. You will need also another more specific |
| 37 | 37 | driver for your LCD. |
| @@ -49,7 +49,7 @@ config KS0108_PORT · 11 unmodified lines | ||
| 49 | 49 | hex "Parallel port where the LCD is connected" |
| 50 | 50 | depends on KS0108 |
| 51 | 51 | default 0x378 |
| 52 | − ---help--- | |
| 52 | + help | |
| 53 | 53 | The address of the parallel port where the LCD is connected. |
| 54 | 54 | |
| 55 | 55 | The first standard parallel port address is 0x378. |
| @@ -71,7 +71,7 @@ config KS0108_DELAY · 15 unmodified lines | ||
| 71 | 71 | int "Delay between each control writing (microseconds)" |
| 72 | 72 | depends on KS0108 |
| 73 | 73 | default "2" |
| 74 | − ---help--- | |
| 74 | + help | |
| 75 | 75 | Amount of time the ks0108 should wait between each control write |
| 76 | 76 | to the parallel port. |
| 77 | 77 | |
| @@ -92,7 +92,7 @@ config CFAG12864B · 14 unmodified lines | ||
| 92 | 92 | select FB_SYS_IMAGEBLIT |
| 93 | 93 | select FB_SYS_FOPS |
| 94 | 94 | default n |
| 95 | − ---help--- | |
| 95 | + help | |
| 96 | 96 | If you have a Crystalfontz 128x64 2-color LCD, cfag12864b Series, |
| 97 | 97 | say Y. You also need the ks0108 LCD Controller driver. |
| 98 | 98 | |
| @@ -114,7 +114,7 @@ config CFAG12864B_RATE · 15 unmodified lines | ||
| 114 | 114 | int "Refresh rate (hertz)" |
| 115 | 115 | depends on CFAG12864B |
| 116 | 116 | default "20" |
| 117 | − ---help--- | |
| 117 | + help | |
| 118 | 118 | Refresh rate of the LCD. |
| 119 | 119 | |
| 120 | 120 | As the LCD is not memory mapped, the driver has to make the work by |
| @@ -168,7 +168,7 @@ menuconfig PARPORT_PANEL · 47 unmodified lines | ||
| 168 | 168 | tristate "Parallel port LCD/Keypad Panel support" |
| 169 | 169 | depends on PARPORT |
| 170 | 170 | select CHARLCD |
| 171 | − ---help--- | |
| 171 | + help | |
| 172 | 172 | Say Y here if you have an HD44780 or KS-0074 LCD connected to your |
| 173 | 173 | parallel port. This driver also features 4 and 6-key keypads. The LCD |
| 174 | 174 | is accessible through the /dev/lcd char device (10, 156), and the |
| @@ -182,7 +182,7 @@ config PANEL_PARPORT · 7 unmodified lines | ||
| 182 | 182 | int "Default parallel port number (0=LPT1)" |
| 183 | 183 | range 0 255 |
| 184 | 184 | default "0" |
| 185 | − ---help--- | |
| 185 | + help | |
| 186 | 186 | This is the index of the parallel port the panel is connected to. One |
| 187 | 187 | driver instance only supports one parallel port, so if your keypad |
| 188 | 188 | and LCD are connected to two separate ports, you have to start two |
| @@ -193,7 +193,7 @@ config PANEL_PROFILE · 4 unmodified lines | ||
| 193 | 193 | int "Default panel profile (0-5, 0=custom)" |
| 194 | 194 | range 0 5 |
| 195 | 195 | default "5" |
| 196 | − ---help--- | |
| 196 | + help | |
| 197 | 197 | To ease configuration, the driver supports different configuration |
| 198 | 198 | profiles for past and recent wirings. These profiles can also be |
| 199 | 199 | used to define an approximative configuration, completed by a few |
| @@ -215,7 +215,7 @@ config PANEL_KEYPAD · 15 unmodified lines | ||
| 215 | 215 | int "Keypad type (0=none, 1=old 6 keys, 2=new 6 keys, 3=Nexcom 4 keys)" |
| 216 | 216 | range 0 3 |
| 217 | 217 | default 0 |
| 218 | − ---help--- | |
| 218 | + help | |
| 219 | 219 | This enables and configures a keypad connected to the parallel port. |
| 220 | 220 | The keys will be read from character device 10,185. Valid values are : |
| 221 | 221 | |
| @@ -232,7 +232,7 @@ config PANEL_LCD · 10 unmodified lines | ||
| 232 | 232 | int "LCD type (0=none, 1=custom, 2=old //, 3=ks0074, 4=hantronix, 5=Nexcom)" |
| 233 | 233 | range 0 5 |
| 234 | 234 | default 0 |
| 235 | − ---help--- | |
| 235 | + help | |
| 236 | 236 | This enables and configures an LCD connected to the parallel port. |
| 237 | 237 | The driver includes an interpreter for escape codes starting with |
| 238 | 238 | '\e[L' which are specific to the LCD, and a few ANSI codes. The |
| @@ -255,7 +255,7 @@ config PANEL_LCD_HEIGHT · 16 unmodified lines | ||
| 255 | 255 | int "Number of lines on the LCD (1-2)" |
| 256 | 256 | range 1 2 |
| 257 | 257 | default 2 |
| 258 | − ---help--- | |
| 258 | + help | |
| 259 | 259 | This is the number of visible character lines on the LCD in custom profile. |
| 260 | 260 | It can either be 1 or 2. |
| 261 | 261 | |
| @@ -264,7 +264,7 @@ config PANEL_LCD_WIDTH · 2 unmodified lines | ||
| 264 | 264 | int "Number of characters per line on the LCD (1-40)" |
| 265 | 265 | range 1 40 |
| 266 | 266 | default 40 |
| 267 | − ---help--- | |
| 267 | + help | |
| 268 | 268 | This is the number of characters per line on the LCD in custom profile. |
| 269 | 269 | Common values are 16,20,24,40. |
| 270 | 270 | |
| @@ -273,7 +273,7 @@ config PANEL_LCD_BWIDTH · 2 unmodified lines | ||
| 273 | 273 | int "Internal LCD line width (1-40, 40 by default)" |
| 274 | 274 | range 1 40 |
| 275 | 275 | default 40 |
| 276 | − ---help--- | |
| 276 | + help | |
| 277 | 277 | Most LCDs use a standard controller which supports hardware lines of 40 |
| 278 | 278 | characters, although sometimes only 16, 20 or 24 of them are really wired |
| 279 | 279 | to the terminal. This results in some non-visible but addressable characters, |
| @@ -289,7 +289,7 @@ config PANEL_LCD_HWIDTH · 9 unmodified lines | ||
| 289 | 289 | int "Hardware LCD line width (1-64, 64 by default)" |
| 290 | 290 | range 1 64 |
| 291 | 291 | default 64 |
| 292 | − ---help--- | |
| 292 | + help | |
| 293 | 293 | Most LCDs use a single address bit to differentiate line 0 and line 1. Since |
| 294 | 294 | some of them need to be able to address 40 chars with the lower bits, they |
| 295 | 295 | often use the immediately superior power of 2, which is 64, to address the |
| @@ -303,7 +303,7 @@ config PANEL_LCD_CHARSET · 7 unmodified lines | ||
| 303 | 303 | int "LCD character set (0=normal, 1=KS0074)" |
| 304 | 304 | range 0 1 |
| 305 | 305 | default 0 |
| 306 | − ---help--- | |
| 306 | + help | |
| 307 | 307 | Some controllers such as the KS0074 use a somewhat strange character set |
| 308 | 308 | where many symbols are at unusual places. The driver knows how to map |
| 309 | 309 | 'standard' ASCII characters to the character sets used by these controllers. |
| @@ -319,7 +319,7 @@ config PANEL_LCD_PROTO · 9 unmodified lines | ||
| 319 | 319 | int "LCD communication mode (0=parallel 8 bits, 1=serial)" |
| 320 | 320 | range 0 1 |
| 321 | 321 | default 0 |
| 322 | − ---help--- | |
| 322 | + help | |
| 323 | 323 | This driver now supports any serial or parallel LCD wired to a parallel |
| 324 | 324 | port. But before assigning signals, the driver needs to know if it will |
| 325 | 325 | be driving a serial LCD or a parallel one. Serial LCDs only use 2 wires |
| @@ -332,7 +332,7 @@ config PANEL_LCD_PIN_E · 6 unmodified lines | ||
| 332 | 332 | int "Parallel port pin number & polarity connected to the LCD E signal (-17...17) " |
| 333 | 333 | range -17 17 |
| 334 | 334 | default 14 |
| 335 | − ---help--- | |
| 335 | + help | |
| 336 | 336 | This describes the number of the parallel port pin to which the LCD 'E' |
| 337 | 337 | signal has been connected. It can be : |
| 338 | 338 | |
| @@ -347,7 +347,7 @@ config PANEL_LCD_PIN_RS · 8 unmodified lines | ||
| 347 | 347 | int "Parallel port pin number & polarity connected to the LCD RS signal (-17...17) " |
| 348 | 348 | range -17 17 |
| 349 | 349 | default 17 |
| 350 | − ---help--- | |
| 350 | + help | |
| 351 | 351 | This describes the number of the parallel port pin to which the LCD 'RS' |
| 352 | 352 | signal has been connected. It can be : |
| 353 | 353 | |
| @@ -362,7 +362,7 @@ config PANEL_LCD_PIN_RW · 8 unmodified lines | ||
| 362 | 362 | int "Parallel port pin number & polarity connected to the LCD RW signal (-17...17) " |
| 363 | 363 | range -17 17 |
| 364 | 364 | default 16 |
| 365 | − ---help--- | |
| 365 | + help | |
| 366 | 366 | This describes the number of the parallel port pin to which the LCD 'RW' |
| 367 | 367 | signal has been connected. It can be : |
| 368 | 368 | |
| @@ -377,7 +377,7 @@ config PANEL_LCD_PIN_SCL · 8 unmodified lines | ||
| 377 | 377 | int "Parallel port pin number & polarity connected to the LCD SCL signal (-17...17) " |
| 378 | 378 | range -17 17 |
| 379 | 379 | default 1 |
| 380 | − ---help--- | |
| 380 | + help | |
| 381 | 381 | This describes the number of the parallel port pin to which the serial |
| 382 | 382 | LCD 'SCL' signal has been connected. It can be : |
| 383 | 383 | |
| @@ -392,7 +392,7 @@ config PANEL_LCD_PIN_SDA · 8 unmodified lines | ||
| 392 | 392 | int "Parallel port pin number & polarity connected to the LCD SDA signal (-17...17) " |
| 393 | 393 | range -17 17 |
| 394 | 394 | default 2 |
| 395 | − ---help--- | |
| 395 | + help | |
| 396 | 396 | This describes the number of the parallel port pin to which the serial |
| 397 | 397 | LCD 'SDA' signal has been connected. It can be : |
| 398 | 398 | |
| @@ -407,7 +407,7 @@ config PANEL_LCD_PIN_BL · 8 unmodified lines | ||
| 407 | 407 | int "Parallel port pin number & polarity connected to the LCD backlight signal (-17...17) " |
| 408 | 408 | range -17 17 |
| 409 | 409 | default 0 |
| 410 | − ---help--- | |
| 410 | + help | |
| 411 | 411 | This describes the number of the parallel port pin to which the LCD 'BL' signal |
| 412 | 412 | has been connected. It can be : |
| 413 | 413 | |
| @@ -423,7 +423,7 @@ config PANEL_CHANGE_MESSAGE · 9 unmodified lines | ||
| 423 | 423 | bool "Change LCD initialization message ?" |
| 424 | 424 | depends on CHARLCD |
| 425 | 425 | default "n" |
| 426 | − ---help--- | |
| 426 | + help | |
| 427 | 427 | This allows you to replace the boot message indicating the kernel version |
| 428 | 428 | and the driver version with a custom message. This is useful on appliances |
| 429 | 429 | where a simple 'Starting system' message can be enough to stop a customer |
| @@ -436,7 +436,7 @@ config PANEL_BOOT_MESSAGE · 6 unmodified lines | ||
| 436 | 436 | depends on PANEL_CHANGE_MESSAGE="y" |
| 437 | 437 | string "New initialization message" |
| 438 | 438 | default "" |
| 439 | − ---help--- | |
| 439 | + help | |
| 440 | 440 | This allows you to replace the boot message indicating the kernel version |
| 441 | 441 | and the driver version with a custom message. This is useful on appliances |
| 442 | 442 | where a simple 'Starting system' message can be enough to stop a customer |
| @@ -448,7 +448,7 @@ config PANEL_BOOT_MESSAGE · 5 unmodified lines | ||
| 448 | 448 | choice |
| 449 | 449 | prompt "Backlight initial state" |
| 450 | 450 | default CHARLCD_BL_FLASH |
| 451 | − ---help--- | |
| 451 | + help | |
| 452 | 452 | Select the initial backlight state on boot or module load. |
| 453 | 453 | |
| 454 | 454 | Previously, there was no option for this: the backlight flashed |
| @@ -7,7 +7,7 @@ menuconfig BLK_DEV · 6 unmodified lines | ||
| 7 | 7 | bool "Block devices" |
| 8 | 8 | depends on BLOCK |
| 9 | 9 | default y |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Say Y here to get to see options for various different block device |
| 12 | 12 | drivers. This option alone does not add any kernel code. |
| 13 | 13 | |
| @@ -27,7 +27,7 @@ config BLK_DEV_NULL_BLK_FAULT_INJECTION · 13 unmodified lines | ||
| 27 | 27 | config BLK_DEV_FD |
| 28 | 28 | tristate "Normal floppy disk support" |
| 29 | 29 | depends on ARCH_MAY_HAVE_PC_FDC |
| 30 | − ---help--- | |
| 30 | + help | |
| 31 | 31 | If you want to use the floppy disk drive(s) of your PC under Linux, |
| 32 | 32 | say Y. Information about this driver, especially important for IBM |
| 33 | 33 | Thinkpad users, is contained in |
| @@ -91,7 +91,7 @@ config GDROM · 57 unmodified lines | ||
| 91 | 91 | config PARIDE |
| 92 | 92 | tristate "Parallel port IDE device support" |
| 93 | 93 | depends on PARPORT_PC |
| 94 | − ---help--- | |
| 94 | + help | |
| 95 | 95 | There are many external CD-ROM and disk devices that connect through |
| 96 | 96 | your computer's parallel port. Most of them are actually IDE devices |
| 97 | 97 | using a parallel port IDE adapter. This option enables the PARIDE |
| @@ -124,7 +124,7 @@ source "drivers/block/zram/Kconfig" · 26 unmodified lines | ||
| 124 | 124 | config BLK_DEV_UMEM |
| 125 | 125 | tristate "Micro Memory MM5415 Battery Backed RAM support" |
| 126 | 126 | depends on PCI |
| 127 | − ---help--- | |
| 127 | + help | |
| 128 | 128 | Saying Y here will include support for the MM5415 family of |
| 129 | 129 | battery backed (Non-volatile) RAM cards. |
| 130 | 130 | <http://www.umem.com/> |
| @@ -141,7 +141,7 @@ config BLK_DEV_UMEM · 10 unmodified lines | ||
| 141 | 141 | config BLK_DEV_UBD |
| 142 | 142 | bool "Virtual block device" |
| 143 | 143 | depends on UML |
| 144 | − ---help--- | |
| 144 | + help | |
| 145 | 145 | The User-Mode Linux port includes a driver called UBD which will let |
| 146 | 146 | you access arbitrary files on the host computer as block devices. |
| 147 | 147 | Unless you know that you do not need such virtual block devices say |
| @@ -150,7 +150,7 @@ config BLK_DEV_UBD · 2 unmodified lines | ||
| 150 | 150 | config BLK_DEV_UBD_SYNC |
| 151 | 151 | bool "Always do synchronous disk IO for UBD" |
| 152 | 152 | depends on BLK_DEV_UBD |
| 153 | − ---help--- | |
| 153 | + help | |
| 154 | 154 | Writes to the virtual block device are not immediately written to the |
| 155 | 155 | host's disk; this may cause problems if, for example, the User-Mode |
| 156 | 156 | Linux 'Virtual Machine' uses a journalling filesystem and the host |
| @@ -173,7 +173,7 @@ config BLK_DEV_COW_COMMON · 16 unmodified lines | ||
| 173 | 173 | |
| 174 | 174 | config BLK_DEV_LOOP |
| 175 | 175 | tristate "Loopback device support" |
| 176 | − ---help--- | |
| 176 | + help | |
| 177 | 177 | Saying Y here will allow you to use a regular file as a block |
| 178 | 178 | device; you can then create a file system on that block device and |
| 179 | 179 | mount it just as you would mount other block devices such as hard |
| @@ -234,7 +234,7 @@ config BLK_DEV_CRYPTOLOOP · 54 unmodified lines | ||
| 234 | 234 | select CRYPTO |
| 235 | 235 | select CRYPTO_CBC |
| 236 | 236 | depends on BLK_DEV_LOOP |
| 237 | − ---help--- | |
| 237 | + help | |
| 238 | 238 | Say Y here if you want to be able to use the ciphers that are |
| 239 | 239 | provided by the CryptoAPI as loop transformation. This might be |
| 240 | 240 | used as hard disk encryption. |
| @@ -249,7 +249,7 @@ source "drivers/block/drbd/Kconfig" · 8 unmodified lines | ||
| 249 | 249 | config BLK_DEV_NBD |
| 250 | 250 | tristate "Network block device support" |
| 251 | 251 | depends on NET |
| 252 | − ---help--- | |
| 252 | + help | |
| 253 | 253 | Saying Y here will allow your computer to be a client for network |
| 254 | 254 | block devices, i.e. it will be able to use block devices exported by |
| 255 | 255 | servers (mount file systems on them etc.). Communication between |
| @@ -277,7 +277,7 @@ config BLK_DEV_SKD · 21 unmodified lines | ||
| 277 | 277 | tristate "STEC S1120 Block Driver" |
| 278 | 278 | depends on PCI |
| 279 | 279 | depends on 64BIT |
| 280 | − ---help--- | |
| 280 | + help | |
| 281 | 281 | Saying Y or M here will enable support for the |
| 282 | 282 | STEC, Inc. S1120 PCIe SSD. |
| 283 | 283 | |
| @@ -286,7 +286,7 @@ config BLK_DEV_SKD · 2 unmodified lines | ||
| 286 | 286 | config BLK_DEV_SX8 |
| 287 | 287 | tristate "Promise SATA SX8 support" |
| 288 | 288 | depends on PCI |
| 289 | − ---help--- | |
| 289 | + help | |
| 290 | 290 | Saying Y or M here will enable support for the |
| 291 | 291 | Promise SATA SX8 controllers. |
| 292 | 292 | |
| @@ -294,7 +294,7 @@ config BLK_DEV_SX8 · 1 unmodified line | ||
| 294 | 294 | |
| 295 | 295 | config BLK_DEV_RAM |
| 296 | 296 | tristate "RAM block device support" |
| 297 | − ---help--- | |
| 297 | + help | |
| 298 | 298 | Saying Y here will allow you to use a portion of your RAM memory as |
| 299 | 299 | a block device, so that you can make file systems on it, read and |
| 300 | 300 | write to it and do all the other things that you can do with normal |
| @@ -428,7 +428,7 @@ config XEN_BLKDEV_BACKEND · 127 unmodified lines | ||
| 428 | 428 | config VIRTIO_BLK |
| 429 | 429 | tristate "Virtio block driver" |
| 430 | 430 | depends on VIRTIO |
| 431 | − ---help--- | |
| 431 | + help | |
| 432 | 432 | This is the virtual block driver for virtio. It can be used with |
| 433 | 433 | QEMU based VMMs (like KVM or Xen). Say Y or M. |
| 434 | 434 | |
| @@ -28,7 +28,7 @@ config PARIDE_PCD · 27 unmodified lines | ||
| 28 | 28 | depends on PARIDE |
| 29 | 29 | select CDROM |
| 30 | 30 | select BLK_SCSI_REQUEST # only for the generic cdrom code |
| 31 | − ---help--- | |
| 31 | + help | |
| 32 | 32 | This option enables the high-level driver for ATAPI CD-ROM devices |
| 33 | 33 | connected through a parallel port. If you chose to build PARIDE |
| 34 | 34 | support into your kernel, you may answer Y here to build in the |
| @@ -71,7 +71,7 @@ config PARIDE_PT · 36 unmodified lines | ||
| 71 | 71 | config PARIDE_PG |
| 72 | 72 | tristate "Parallel port generic ATAPI devices" |
| 73 | 73 | depends on PARIDE |
| 74 | − ---help--- | |
| 74 | + help | |
| 75 | 75 | This option enables a special high-level driver for generic ATAPI |
| 76 | 76 | devices connected through a parallel port. The driver allows user |
| 77 | 77 | programs, such as cdrtools, to send ATAPI commands directly to a |
| @@ -111,7 +111,7 @@ config PARIDE_ATEN · 33 unmodified lines | ||
| 111 | 111 | config PARIDE_BPCK |
| 112 | 112 | tristate "MicroSolutions backpack (Series 5) protocol" |
| 113 | 113 | depends on PARIDE |
| 114 | − ---help--- | |
| 114 | + help | |
| 115 | 115 | This option enables support for the Micro Solutions BACKPACK |
| 116 | 116 | parallel port Series 5 IDE protocol. (Most BACKPACK drives made |
| 117 | 117 | before 1999 were Series 5) Series 5 drives will NOT always have the |
| @@ -129,7 +129,7 @@ config PARIDE_BPCK · 11 unmodified lines | ||
| 129 | 129 | config PARIDE_BPCK6 |
| 130 | 130 | tristate "MicroSolutions backpack (Series 6) protocol" |
| 131 | 131 | depends on PARIDE && !64BIT |
| 132 | − ---help--- | |
| 132 | + help | |
| 133 | 133 | This option enables support for the Micro Solutions BACKPACK |
| 134 | 134 | parallel port Series 6 IDE protocol. (Most BACKPACK drives made |
| 135 | 135 | after 1999 were Series 6) Series 6 drives will have the Series noted |
| @@ -11,7 +11,7 @@ config TTY_PRINTK · 10 unmodified lines | ||
| 11 | 11 | tristate "TTY driver to output user messages via printk" |
| 12 | 12 | depends on EXPERT && TTY |
| 13 | 13 | default n |
| 14 | − ---help--- | |
| 14 | + help | |
| 15 | 15 | If you say Y here, the support for writing user messages (i.e. |
| 16 | 16 | console messages) via printk is available. |
| 17 | 17 | |
| @@ -33,7 +33,7 @@ config TTY_PRINTK_LEVEL · 15 unmodified lines | ||
| 33 | 33 | config PRINTER |
| 34 | 34 | tristate "Parallel printer support" |
| 35 | 35 | depends on PARPORT |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | If you intend to attach a printer to the parallel port of your Linux |
| 38 | 38 | box (as opposed to using a serial printer; if the connector at the |
| 39 | 39 | printer has 9 or 25 holes ["female"], then it's serial), say Y. |
| @@ -59,7 +59,7 @@ config PRINTER · 19 unmodified lines | ||
| 59 | 59 | config LP_CONSOLE |
| 60 | 60 | bool "Support for console on line printer" |
| 61 | 61 | depends on PRINTER |
| 62 | − ---help--- | |
| 62 | + help | |
| 63 | 63 | If you want kernel messages to be printed out as they occur, you |
| 64 | 64 | can have a console on the printer. This option adds support for |
| 65 | 65 | doing that; to actually get it to happen you need to pass the |
| @@ -76,7 +76,7 @@ config LP_CONSOLE · 10 unmodified lines | ||
| 76 | 76 | config PPDEV |
| 77 | 77 | tristate "Support for user-space parallel port device drivers" |
| 78 | 78 | depends on PARPORT |
| 79 | − ---help--- | |
| 79 | + help | |
| 80 | 80 | Saying Y to this adds support for /dev/parport device nodes. This |
| 81 | 81 | is needed for programs that want portable access to the parallel |
| 82 | 82 | port, for instance deviceid (which displays Plug-and-Play device |
| @@ -146,7 +146,7 @@ config DS1620 · 63 unmodified lines | ||
| 146 | 146 | config NWBUTTON |
| 147 | 147 | tristate "NetWinder Button" |
| 148 | 148 | depends on ARCH_NETWINDER |
| 149 | − ---help--- | |
| 149 | + help | |
| 150 | 150 | If you say Y here and create a character device node /dev/nwbutton |
| 151 | 151 | with major and minor numbers 10 and 158 ("man mknod"), then every |
| 152 | 152 | time the orange button is pressed a number of times, the number of |
| @@ -182,7 +182,7 @@ config NWBUTTON_REBOOT · 29 unmodified lines | ||
| 182 | 182 | config NWFLASH |
| 183 | 183 | tristate "NetWinder flash support" |
| 184 | 184 | depends on ARCH_NETWINDER |
| 185 | − ---help--- | |
| 185 | + help | |
| 186 | 186 | If you say Y here and create a character device /dev/flash with |
| 187 | 187 | major 10 and minor 160 you can manipulate the flash ROM containing |
| 188 | 188 | the NetWinder firmware. Be careful as accidentally overwriting the |
| @@ -220,7 +220,7 @@ config XILINX_HWICAP · 31 unmodified lines | ||
| 220 | 220 | config R3964 |
| 221 | 221 | tristate "Siemens R3964 line discipline" |
| 222 | 222 | depends on TTY && BROKEN |
| 223 | − ---help--- | |
| 223 | + help | |
| 224 | 224 | This driver allows synchronous communication with devices using the |
| 225 | 225 | Siemens R3964 packet protocol. Unless you are dealing with special |
| 226 | 226 | hardware like PLCs, you are unlikely to need this. |
| @@ -233,7 +233,7 @@ config R3964 · 6 unmodified lines | ||
| 233 | 233 | config APPLICOM |
| 234 | 234 | tristate "Applicom intelligent fieldbus card support" |
| 235 | 235 | depends on PCI |
| 236 | − ---help--- | |
| 236 | + help | |
| 237 | 237 | This driver provides the kernel-side support for the intelligent |
| 238 | 238 | fieldbus cards made by Applicom International. More information |
| 239 | 239 | about these cards can be found on the WWW at the address |
| @@ -248,7 +248,7 @@ config APPLICOM · 8 unmodified lines | ||
| 248 | 248 | config SONYPI |
| 249 | 249 | tristate "Sony Vaio Programmable I/O Control Device support" |
| 250 | 250 | depends on X86_32 && PCI && INPUT |
| 251 | − ---help--- | |
| 251 | + help | |
| 252 | 252 | This driver enables access to the Sony Programmable I/O Control |
| 253 | 253 | Device which can be found in many (all ?) Sony Vaio laptops. |
| 254 | 254 | |
| @@ -269,7 +269,7 @@ config MWAVE · 14 unmodified lines | ||
| 269 | 269 | tristate "ACP Modem (Mwave) support" |
| 270 | 270 | depends on X86 && TTY |
| 271 | 271 | select SERIAL_8250 |
| 272 | − ---help--- | |
| 272 | + help | |
| 273 | 273 | The ACP modem (Mwave) for Linux is a WinModem. It is composed of a |
| 274 | 274 | kernel driver and a user level application. Together these components |
| 275 | 275 | support direct attachment to public switched telephone networks (PSTNs) |
| @@ -347,7 +347,7 @@ config NVRAM · 71 unmodified lines | ||
| 347 | 347 | tristate "/dev/nvram support" |
| 348 | 348 | depends on X86 || HAVE_ARCH_NVRAM_OPS |
| 349 | 349 | default M68K || PPC |
| 350 | − ---help--- | |
| 350 | + help | |
| 351 | 351 | If you say Y here and create a character special file /dev/nvram |
| 352 | 352 | with major number 10 and minor number 144 using mknod ("man mknod"), |
| 353 | 353 | you get read and write access to the non-volatile memory. |
| @@ -3,7 +3,7 @@ menuconfig AGP · 2 unmodified lines | ||
| 3 | 3 | tristate "/dev/agpgart (AGP Support)" |
| 4 | 4 | depends on ALPHA || IA64 || PARISC || PPC || X86 |
| 5 | 5 | depends on PCI |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | AGP (Accelerated Graphics Port) is a bus system mainly used to |
| 8 | 8 | connect graphics cards to the rest of the system. |
| 9 | 9 | |
| @@ -30,7 +30,7 @@ menuconfig AGP · 20 unmodified lines | ||
| 30 | 30 | config AGP_ALI |
| 31 | 31 | tristate "ALI chipset support" |
| 32 | 32 | depends on AGP && X86_32 |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | This option gives you AGP support for the GLX component of |
| 35 | 35 | X on the following ALi chipsets. The supported chipsets |
| 36 | 36 | include M1541, M1621, M1631, M1632, M1641,M1647,and M1651. |
| @@ -45,7 +45,7 @@ config AGP_ALI · 8 unmodified lines | ||
| 45 | 45 | config AGP_ATI |
| 46 | 46 | tristate "ATI chipset support" |
| 47 | 47 | depends on AGP && X86_32 |
| 48 | − ---help--- | |
| 48 | + help | |
| 49 | 49 | This option gives you AGP support for the GLX component of |
| 50 | 50 | X on the ATI RadeonIGP family of chipsets. |
| 51 | 51 | |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | menuconfig HW_RANDOM |
| 7 | 7 | tristate "Hardware Random Number Generator Core support" |
| 8 | 8 | default m |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Hardware Random Number Generator Core infrastructure. |
| 11 | 11 | |
| 12 | 12 | To compile this driver as a module, choose M here: the |
| @@ -24,7 +24,7 @@ if HW_RANDOM · 11 unmodified lines | ||
| 24 | 24 | config HW_RANDOM_TIMERIOMEM |
| 25 | 25 | tristate "Timer IOMEM HW Random Number Generator support" |
| 26 | 26 | depends on HAS_IOMEM |
| 27 | − ---help--- | |
| 27 | + help | |
| 28 | 28 | This driver provides kernel-side support for a generic Random |
| 29 | 29 | Number Generator used by reading a 'dumb' iomem address that |
| 30 | 30 | is to be read no faster than, for example, once a second; |
| @@ -39,7 +39,7 @@ config HW_RANDOM_INTEL · 8 unmodified lines | ||
| 39 | 39 | tristate "Intel HW Random Number Generator support" |
| 40 | 40 | depends on (X86 || IA64) && PCI |
| 41 | 41 | default HW_RANDOM |
| 42 | − ---help--- | |
| 42 | + help | |
| 43 | 43 | This driver provides kernel-side support for the Random Number |
| 44 | 44 | Generator hardware found on Intel i8xx-based motherboards. |
| 45 | 45 | |
| @@ -52,7 +52,7 @@ config HW_RANDOM_AMD · 6 unmodified lines | ||
| 52 | 52 | tristate "AMD HW Random Number Generator support" |
| 53 | 53 | depends on (X86 || PPC_MAPLE) && PCI |
| 54 | 54 | default HW_RANDOM |
| 55 | − ---help--- | |
| 55 | + help | |
| 56 | 56 | This driver provides kernel-side support for the Random Number |
| 57 | 57 | Generator hardware found on AMD 76x-based motherboards. |
| 58 | 58 | |
| @@ -65,7 +65,7 @@ config HW_RANDOM_ATMEL · 6 unmodified lines | ||
| 65 | 65 | tristate "Atmel Random Number Generator support" |
| 66 | 66 | depends on ARCH_AT91 && HAVE_CLK && OF |
| 67 | 67 | default HW_RANDOM |
| 68 | − ---help--- | |
| 68 | + help | |
| 69 | 69 | This driver provides kernel-side support for the Random Number |
| 70 | 70 | Generator hardware found on Atmel AT91 devices. |
| 71 | 71 | |
| @@ -79,7 +79,7 @@ config HW_RANDOM_BCM2835 · 7 unmodified lines | ||
| 79 | 79 | depends on ARCH_BCM2835 || ARCH_BCM_NSP || ARCH_BCM_5301X || \ |
| 80 | 80 | ARCH_BCM_63XX || BCM63XX || BMIPS_GENERIC |
| 81 | 81 | default HW_RANDOM |
| 82 | − ---help--- | |
| 82 | + help | |
| 83 | 83 | This driver provides kernel-side support for the Random Number |
| 84 | 84 | Generator hardware found on the Broadcom BCM2835 and BCM63xx SoCs. |
| 85 | 85 | |
| @@ -92,7 +92,7 @@ config HW_RANDOM_IPROC_RNG200 · 6 unmodified lines | ||
| 92 | 92 | tristate "Broadcom iProc/STB RNG200 support" |
| 93 | 93 | depends on ARCH_BCM_IPROC || ARCH_BCM2835 || ARCH_BRCMSTB |
| 94 | 94 | default HW_RANDOM |
| 95 | − ---help--- | |
| 95 | + help | |
| 96 | 96 | This driver provides kernel-side support for the RNG200 |
| 97 | 97 | hardware found on the Broadcom iProc and STB SoCs. |
| 98 | 98 | |
| @@ -105,7 +105,7 @@ config HW_RANDOM_GEODE · 6 unmodified lines | ||
| 105 | 105 | tristate "AMD Geode HW Random Number Generator support" |
| 106 | 106 | depends on X86_32 && PCI |
| 107 | 107 | default HW_RANDOM |
| 108 | − ---help--- | |
| 108 | + help | |
| 109 | 109 | This driver provides kernel-side support for the Random Number |
| 110 | 110 | Generator hardware found on the AMD Geode LX. |
| 111 | 111 | |
| @@ -118,7 +118,7 @@ config HW_RANDOM_N2RNG · 6 unmodified lines | ||
| 118 | 118 | tristate "Niagara2 Random Number Generator support" |
| 119 | 119 | depends on SPARC64 |
| 120 | 120 | default HW_RANDOM |
| 121 | − ---help--- | |
| 121 | + help | |
| 122 | 122 | This driver provides kernel-side support for the Random Number |
| 123 | 123 | Generator hardware found on Niagara2 cpus. |
| 124 | 124 | |
| @@ -131,7 +131,7 @@ config HW_RANDOM_VIA · 6 unmodified lines | ||
| 131 | 131 | tristate "VIA HW Random Number Generator support" |
| 132 | 132 | depends on X86 |
| 133 | 133 | default HW_RANDOM |
| 134 | − ---help--- | |
| 134 | + help | |
| 135 | 135 | This driver provides kernel-side support for the Random Number |
| 136 | 136 | Generator hardware found on VIA based motherboards. |
| 137 | 137 | |
| @@ -144,7 +144,7 @@ config HW_RANDOM_IXP4XX · 6 unmodified lines | ||
| 144 | 144 | tristate "Intel IXP4xx NPU HW Pseudo-Random Number Generator support" |
| 145 | 145 | depends on ARCH_IXP4XX |
| 146 | 146 | default HW_RANDOM |
| 147 | − ---help--- | |
| 147 | + help | |
| 148 | 148 | This driver provides kernel-side support for the Pseudo-Random |
| 149 | 149 | Number Generator hardware found on the Intel IXP45x/46x NPU. |
| 150 | 150 | |
| @@ -157,7 +157,7 @@ config HW_RANDOM_OMAP · 6 unmodified lines | ||
| 157 | 157 | tristate "OMAP Random Number Generator support" |
| 158 | 158 | depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS || ARCH_MVEBU |
| 159 | 159 | default HW_RANDOM |
| 160 | − ---help--- | |
| 160 | + help | |
| 161 | 161 | This driver provides kernel-side support for the Random Number |
| 162 | 162 | Generator hardware found on OMAP16xx, OMAP2/3/4/5, AM33xx/AM43xx |
| 163 | 163 | multimedia processors, and Marvell Armada 7k/8k SoCs. |
| @@ -171,7 +171,7 @@ config HW_RANDOM_OMAP3_ROM · 7 unmodified lines | ||
| 171 | 171 | tristate "OMAP3 ROM Random Number Generator support" |
| 172 | 172 | depends on ARCH_OMAP3 |
| 173 | 173 | default HW_RANDOM |
| 174 | − ---help--- | |
| 174 | + help | |
| 175 | 175 | This driver provides kernel-side support for the Random Number |
| 176 | 176 | Generator hardware found on OMAP34xx processors. |
| 177 | 177 | |
| @@ -184,7 +184,7 @@ config HW_RANDOM_OCTEON · 6 unmodified lines | ||
| 184 | 184 | tristate "Octeon Random Number Generator support" |
| 185 | 185 | depends on CAVIUM_OCTEON_SOC |
| 186 | 186 | default HW_RANDOM |
| 187 | − ---help--- | |
| 187 | + help | |
| 188 | 188 | This driver provides kernel-side support for the Random Number |
| 189 | 189 | Generator hardware found on Octeon processors. |
| 190 | 190 | |
| @@ -197,7 +197,7 @@ config HW_RANDOM_PASEMI · 6 unmodified lines | ||
| 197 | 197 | tristate "PA Semi HW Random Number Generator support" |
| 198 | 198 | depends on PPC_PASEMI |
| 199 | 199 | default HW_RANDOM |
| 200 | − ---help--- | |
| 200 | + help | |
| 201 | 201 | This driver provides kernel-side support for the Random Number |
| 202 | 202 | Generator hardware found on PA Semi PWRficient SoCs. |
| 203 | 203 | |
| @@ -209,7 +209,7 @@ config HW_RANDOM_PASEMI · 5 unmodified lines | ||
| 209 | 209 | config HW_RANDOM_VIRTIO |
| 210 | 210 | tristate "VirtIO Random Number Generator support" |
| 211 | 211 | depends on VIRTIO |
| 212 | − ---help--- | |
| 212 | + help | |
| 213 | 213 | This driver provides kernel-side support for the virtual Random Number |
| 214 | 214 | Generator hardware. |
| 215 | 215 | |
| @@ -220,7 +220,7 @@ config HW_RANDOM_TX4939 · 4 unmodified lines | ||
| 220 | 220 | tristate "TX4939 Random Number Generator support" |
| 221 | 221 | depends on SOC_TX4939 |
| 222 | 222 | default HW_RANDOM |
| 223 | − ---help--- | |
| 223 | + help | |
| 224 | 224 | This driver provides kernel-side support for the Random Number |
| 225 | 225 | Generator hardware found on TX4939 SoC. |
| 226 | 226 | |
| @@ -233,7 +233,7 @@ config HW_RANDOM_MXC_RNGA · 6 unmodified lines | ||
| 233 | 233 | tristate "Freescale i.MX RNGA Random Number Generator" |
| 234 | 234 | depends on SOC_IMX31 |
| 235 | 235 | default HW_RANDOM |
| 236 | − ---help--- | |
| 236 | + help | |
| 237 | 237 | This driver provides kernel-side support for the Random Number |
| 238 | 238 | Generator hardware found on Freescale i.MX processors. |
| 239 | 239 | |
| @@ -247,7 +247,7 @@ config HW_RANDOM_IMX_RNGC · 7 unmodified lines | ||
| 247 | 247 | depends on HAS_IOMEM && HAVE_CLK |
| 248 | 248 | depends on SOC_IMX25 || COMPILE_TEST |
| 249 | 249 | default HW_RANDOM |
| 250 | − ---help--- | |
| 250 | + help | |
| 251 | 251 | This driver provides kernel-side support for the Random Number |
| 252 | 252 | Generator Version C hardware found on some Freescale i.MX |
| 253 | 253 | processors. Version B is also supported by this driver. |
| @@ -261,7 +261,7 @@ config HW_RANDOM_NOMADIK · 7 unmodified lines | ||
| 261 | 261 | tristate "ST-Ericsson Nomadik Random Number Generator support" |
| 262 | 262 | depends on ARCH_NOMADIK |
| 263 | 263 | default HW_RANDOM |
| 264 | − ---help--- | |
| 264 | + help | |
| 265 | 265 | This driver provides kernel-side support for the Random Number |
| 266 | 266 | Generator hardware found on ST-Ericsson SoCs (8815 and 8500). |
| 267 | 267 | |
| @@ -274,7 +274,7 @@ config HW_RANDOM_PSERIES · 6 unmodified lines | ||
| 274 | 274 | tristate "pSeries HW Random Number Generator support" |
| 275 | 275 | depends on PPC64 && IBMVIO |
| 276 | 276 | default HW_RANDOM |
| 277 | − ---help--- | |
| 277 | + help | |
| 278 | 278 | This driver provides kernel-side support for the Random Number |
| 279 | 279 | Generator hardware found on POWER7+ machines and above |
| 280 | 280 | |
| @@ -287,7 +287,7 @@ config HW_RANDOM_POWERNV · 6 unmodified lines | ||
| 287 | 287 | tristate "PowerNV Random Number Generator support" |
| 288 | 288 | depends on PPC_POWERNV |
| 289 | 289 | default HW_RANDOM |
| 290 | − ---help--- | |
| 290 | + help | |
| 291 | 291 | This is the driver for Random Number Generator hardware found |
| 292 | 292 | in POWER7+ and above machines for PowerNV platform. |
| 293 | 293 | |
| @@ -300,7 +300,7 @@ config HW_RANDOM_HISI · 6 unmodified lines | ||
| 300 | 300 | tristate "Hisilicon Random Number Generator support" |
| 301 | 301 | depends on HW_RANDOM && ARCH_HISI |
| 302 | 302 | default HW_RANDOM |
| 303 | − ---help--- | |
| 303 | + help | |
| 304 | 304 | This driver provides kernel-side support for the Random Number |
| 305 | 305 | Generator hardware found on Hisilicon Hip04 and Hip05 SoC. |
| 306 | 306 | |
| @@ -325,7 +325,7 @@ config HW_RANDOM_HISI_V2 · 18 unmodified lines | ||
| 325 | 325 | config HW_RANDOM_ST |
| 326 | 326 | tristate "ST Microelectronics HW Random Number Generator support" |
| 327 | 327 | depends on HW_RANDOM && ARCH_STI |
| 328 | − ---help--- | |
| 328 | + help | |
| 329 | 329 | This driver provides kernel-side support for the Random Number |
| 330 | 330 | Generator hardware found on STi series of SoCs. |
| 331 | 331 | |
| @@ -336,7 +336,7 @@ config HW_RANDOM_XGENE · 4 unmodified lines | ||
| 336 | 336 | tristate "APM X-Gene True Random Number Generator (TRNG) support" |
| 337 | 337 | depends on HW_RANDOM && ARCH_XGENE |
| 338 | 338 | default HW_RANDOM |
| 339 | − ---help--- | |
| 339 | + help | |
| 340 | 340 | This driver provides kernel-side support for the Random Number |
| 341 | 341 | Generator hardware found on APM X-Gene SoC. |
| 342 | 342 | |
| @@ -363,7 +363,7 @@ config HW_RANDOM_PIC32 · 20 unmodified lines | ||
| 363 | 363 | tristate "Microchip PIC32 Random Number Generator support" |
| 364 | 364 | depends on HW_RANDOM && MACH_PIC32 |
| 365 | 365 | default y |
| 366 | − ---help--- | |
| 366 | + help | |
| 367 | 367 | This driver provides kernel-side support for the Random Number |
| 368 | 368 | Generator hardware found on a PIC32. |
| 369 | 369 | |
| @@ -377,7 +377,7 @@ config HW_RANDOM_MESON · 7 unmodified lines | ||
| 377 | 377 | depends on HW_RANDOM |
| 378 | 378 | depends on ARCH_MESON || COMPILE_TEST |
| 379 | 379 | default y |
| 380 | − ---help--- | |
| 380 | + help | |
| 381 | 381 | This driver provides kernel-side support for the Random Number |
| 382 | 382 | Generator hardware found on Amlogic Meson SoCs. |
| 383 | 383 | |
| @@ -390,7 +390,7 @@ config HW_RANDOM_CAVIUM · 6 unmodified lines | ||
| 390 | 390 | tristate "Cavium ThunderX Random Number Generator support" |
| 391 | 391 | depends on HW_RANDOM && PCI && (ARM64 || (COMPILE_TEST && 64BIT)) |
| 392 | 392 | default HW_RANDOM |
| 393 | − ---help--- | |
| 393 | + help | |
| 394 | 394 | This driver provides kernel-side support for the Random Number |
| 395 | 395 | Generator hardware found on Cavium SoCs. |
| 396 | 396 | |
| @@ -404,7 +404,7 @@ config HW_RANDOM_MTK · 7 unmodified lines | ||
| 404 | 404 | depends on HW_RANDOM |
| 405 | 405 | depends on ARCH_MEDIATEK || COMPILE_TEST |
| 406 | 406 | default y |
| 407 | − ---help--- | |
| 407 | + help | |
| 408 | 408 | This driver provides kernel-side support for the Random Number |
| 409 | 409 | Generator hardware found on Mediatek SoCs. |
| 410 | 410 | |
| @@ -417,7 +417,7 @@ config HW_RANDOM_S390 · 6 unmodified lines | ||
| 417 | 417 | tristate "S390 True Random Number Generator support" |
| 418 | 418 | depends on S390 |
| 419 | 419 | default HW_RANDOM |
| 420 | − ---help--- | |
| 420 | + help | |
| 421 | 421 | This driver provides kernel-side support for the True |
| 422 | 422 | Random Number Generator available as CPACF extension |
| 423 | 423 | on modern s390 hardware platforms. |
| @@ -431,7 +431,7 @@ config HW_RANDOM_EXYNOS · 7 unmodified lines | ||
| 431 | 431 | tristate "Samsung Exynos True Random Number Generator support" |
| 432 | 432 | depends on ARCH_EXYNOS || COMPILE_TEST |
| 433 | 433 | default HW_RANDOM |
| 434 | − ---help--- | |
| 434 | + help | |
| 435 | 435 | This driver provides support for the True Random Number |
| 436 | 436 | Generator available in Exynos SoCs. |
| 437 | 437 | |
| @@ -9,7 +9,7 @@ menuconfig TCG_TPM · 8 unmodified lines | ||
| 9 | 9 | imply SECURITYFS |
| 10 | 10 | select CRYPTO |
| 11 | 11 | select CRYPTO_HASH_INFO |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | If you have a TPM security chip in your system, which |
| 14 | 14 | implements the Trusted Computing Group's specification, |
| 15 | 15 | say Yes and it will be accessible from within Linux. For |
| @@ -31,7 +31,7 @@ config HW_RANDOM_TPM · 15 unmodified lines | ||
| 31 | 31 | bool "TPM HW Random Number Generator support" |
| 32 | 32 | depends on TCG_TPM && HW_RANDOM && !(TCG_TPM=y && HW_RANDOM=m) |
| 33 | 33 | default y |
| 34 | − ---help--- | |
| 34 | + help | |
| 35 | 35 | This setting exposes the TPM's Random Number Generator as a hwrng |
| 36 | 36 | device. This allows the kernel to collect randomness from the TPM at |
| 37 | 37 | boot, and provides the TPM randomines in /dev/hwrng. |
| @@ -40,7 +40,7 @@ config HW_RANDOM_TPM · 2 unmodified lines | ||
| 40 | 40 | |
| 41 | 41 | config TCG_TIS_CORE |
| 42 | 42 | tristate |
| 43 | − ---help--- | |
| 43 | + help | |
| 44 | 44 | TCG TIS TPM core driver. It implements the TPM TCG TIS logic and hooks |
| 45 | 45 | into the TPM kernel APIs. Physical layers will register against it. |
| 46 | 46 | |
| @@ -48,7 +48,7 @@ config TCG_TIS · 1 unmodified line | ||
| 48 | 48 | tristate "TPM Interface Specification 1.2 Interface / TPM 2.0 FIFO Interface" |
| 49 | 49 | depends on X86 || OF |
| 50 | 50 | select TCG_TIS_CORE |
| 51 | − ---help--- | |
| 51 | + help | |
| 52 | 52 | If you have a TPM security chip that is compliant with the |
| 53 | 53 | TCG TIS 1.2 TPM specification (TPM1.2) or the TCG PTP FIFO |
| 54 | 54 | specification (TPM2.0) say Yes and it will be accessible from |
| @@ -59,7 +59,7 @@ config TCG_TIS_SPI · 4 unmodified lines | ||
| 59 | 59 | tristate "TPM Interface Specification 1.3 Interface / TPM 2.0 FIFO Interface - (SPI)" |
| 60 | 60 | depends on SPI |
| 61 | 61 | select TCG_TIS_CORE |
| 62 | − ---help--- | |
| 62 | + help | |
| 63 | 63 | If you have a TPM security chip which is connected to a regular, |
| 64 | 64 | non-tcg SPI master (i.e. most embedded platforms) that is compliant with the |
| 65 | 65 | TCG TIS 1.3 TPM specification (TPM1.2) or the TCG PTP FIFO |
| @@ -77,7 +77,7 @@ config TCG_TIS_SPI_CR50 · 11 unmodified lines | ||
| 77 | 77 | config TCG_TIS_I2C_ATMEL |
| 78 | 78 | tristate "TPM Interface Specification 1.2 Interface (I2C - Atmel)" |
| 79 | 79 | depends on I2C |
| 80 | − ---help--- | |
| 80 | + help | |
| 81 | 81 | If you have an Atmel I2C TPM security chip say Yes and it will be |
| 82 | 82 | accessible from within Linux. |
| 83 | 83 | To compile this driver as a module, choose M here; the module will |
| @@ -86,7 +86,7 @@ config TCG_TIS_I2C_ATMEL · 2 unmodified lines | ||
| 86 | 86 | config TCG_TIS_I2C_INFINEON |
| 87 | 87 | tristate "TPM Interface Specification 1.2 Interface (I2C - Infineon)" |
| 88 | 88 | depends on I2C |
| 89 | − ---help--- | |
| 89 | + help | |
| 90 | 90 | If you have a TPM security chip that is compliant with the |
| 91 | 91 | TCG TIS 1.2 TPM specification and Infineon's I2C Protocol Stack |
| 92 | 92 | Specification 0.20 say Yes and it will be accessible from within |
| @@ -97,7 +97,7 @@ config TCG_TIS_I2C_INFINEON · 4 unmodified lines | ||
| 97 | 97 | config TCG_TIS_I2C_NUVOTON |
| 98 | 98 | tristate "TPM Interface Specification 1.2 Interface (I2C - Nuvoton)" |
| 99 | 99 | depends on I2C |
| 100 | − ---help--- | |
| 100 | + help | |
| 101 | 101 | If you have a TPM security chip with an I2C interface from |
| 102 | 102 | Nuvoton Technology Corp. say Yes and it will be accessible |
| 103 | 103 | from within Linux. |
| @@ -107,7 +107,7 @@ config TCG_TIS_I2C_NUVOTON · 3 unmodified lines | ||
| 107 | 107 | config TCG_NSC |
| 108 | 108 | tristate "National Semiconductor TPM Interface" |
| 109 | 109 | depends on X86 |
| 110 | − ---help--- | |
| 110 | + help | |
| 111 | 111 | If you have a TPM security chip from National Semiconductor |
| 112 | 112 | say Yes and it will be accessible from within Linux. To |
| 113 | 113 | compile this driver as a module, choose M here; the module |
| @@ -116,7 +116,7 @@ config TCG_NSC · 2 unmodified lines | ||
| 116 | 116 | config TCG_ATMEL |
| 117 | 117 | tristate "Atmel TPM Interface" |
| 118 | 118 | depends on PPC64 || HAS_IOPORT_MAP |
| 119 | − ---help--- | |
| 119 | + help | |
| 120 | 120 | If you have a TPM security chip from Atmel say Yes and it |
| 121 | 121 | will be accessible from within Linux. To compile this driver |
| 122 | 122 | as a module, choose M here; the module will be called tpm_atmel. |
| @@ -124,7 +124,7 @@ config TCG_ATMEL · 1 unmodified line | ||
| 124 | 124 | config TCG_INFINEON |
| 125 | 125 | tristate "Infineon Technologies TPM Interface" |
| 126 | 126 | depends on PNP |
| 127 | − ---help--- | |
| 127 | + help | |
| 128 | 128 | If you have a TPM security chip from Infineon Technologies |
| 129 | 129 | (either SLD 9630 TT 1.1 or SLB 9635 TT 1.2) say Yes and it |
| 130 | 130 | will be accessible from within Linux. |
| @@ -136,7 +136,7 @@ config TCG_INFINEON · 5 unmodified lines | ||
| 136 | 136 | config TCG_IBMVTPM |
| 137 | 137 | tristate "IBM VTPM Interface" |
| 138 | 138 | depends on PPC_PSERIES |
| 139 | − ---help--- | |
| 139 | + help | |
| 140 | 140 | If you have IBM virtual TPM (VTPM) support say Yes and it |
| 141 | 141 | will be accessible from within Linux. To compile this driver |
| 142 | 142 | as a module, choose M here; the module will be called tpm_ibmvtpm. |
| @@ -145,7 +145,7 @@ config TCG_XEN · 2 unmodified lines | ||
| 145 | 145 | tristate "XEN TPM Interface" |
| 146 | 146 | depends on TCG_TPM && XEN |
| 147 | 147 | select XEN_XENBUS_FRONTEND |
| 148 | − ---help--- | |
| 148 | + help | |
| 149 | 149 | If you want to make TPM support available to a Xen user domain, |
| 150 | 150 | say Yes and it will be accessible from within Linux. See |
| 151 | 151 | the manpages for xl, xl.conf, and docs/misc/vtpm.txt in |
| @@ -156,7 +156,7 @@ config TCG_XEN · 4 unmodified lines | ||
| 156 | 156 | config TCG_CRB |
| 157 | 157 | tristate "TPM 2.0 CRB Interface" |
| 158 | 158 | depends on ACPI |
| 159 | − ---help--- | |
| 159 | + help | |
| 160 | 160 | If you have a TPM security chip that is compliant with the |
| 161 | 161 | TCG CRB 2.0 TPM specification say Yes and it will be accessible |
| 162 | 162 | from within Linux. To compile this driver as a module, choose |
| @@ -165,7 +165,7 @@ config TCG_CRB · 2 unmodified lines | ||
| 165 | 165 | config TCG_VTPM_PROXY |
| 166 | 166 | tristate "VTPM Proxy Interface" |
| 167 | 167 | depends on TCG_TPM |
| 168 | − ---help--- | |
| 168 | + help | |
| 169 | 169 | This driver proxies for an emulated TPM (vTPM) running in userspace. |
| 170 | 170 | A device /dev/vtpmx is provided that creates a device pair |
| 171 | 171 | /dev/vtpmX and a server-side file descriptor on which the vTPM |
| @@ -1,7 +1,7 @@ | ||
| 1 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | 2 | config TCG_TIS_ST33ZP24 |
| 3 | 3 | tristate |
| 4 | − ---help--- | |
| 4 | + help | |
| 5 | 5 | STMicroelectronics ST33ZP24 core driver. It implements the core |
| 6 | 6 | TPM1.2 logic and hooks into the TPM kernel APIs. Physical layers will |
| 7 | 7 | register against it. |
| @@ -13,7 +13,7 @@ config TCG_TIS_ST33ZP24_I2C · 5 unmodified lines | ||
| 13 | 13 | tristate "STMicroelectronics TPM Interface Specification 1.2 Interface (I2C)" |
| 14 | 14 | depends on I2C |
| 15 | 15 | select TCG_TIS_ST33ZP24 |
| 16 | − ---help--- | |
| 16 | + help | |
| 17 | 17 | This module adds support for the STMicroelectronics TPM security chip |
| 18 | 18 | ST33ZP24 with i2c interface. |
| 19 | 19 | To compile this driver as a module, choose M here; the module will be |
| @@ -23,7 +23,7 @@ config TCG_TIS_ST33ZP24_SPI · 3 unmodified lines | ||
| 23 | 23 | tristate "STMicroelectronics TPM Interface Specification 1.2 Interface (SPI)" |
| 24 | 24 | depends on SPI |
| 25 | 25 | select TCG_TIS_ST33ZP24 |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | This module adds support for the STMicroelectronics TPM security chip |
| 28 | 28 | ST33ZP24 with spi interface. |
| 29 | 29 | To compile this driver as a module, choose M here; the module will be |
| @@ -29,7 +29,7 @@ menuconfig COMMON_CLK · 28 unmodified lines | ||
| 29 | 29 | select CLKDEV_LOOKUP |
| 30 | 30 | select SRCU |
| 31 | 31 | select RATIONAL |
| 32 | − ---help--- | |
| 32 | + help | |
| 33 | 33 | The common clock framework is a single definition of struct |
| 34 | 34 | clk, useful across many platforms, as well as an |
| 35 | 35 | implementation of the clock API in include/linux/clk.h. |
| @@ -41,7 +41,7 @@ if COMMON_CLK · 5 unmodified lines | ||
| 41 | 41 | config COMMON_CLK_WM831X |
| 42 | 42 | tristate "Clock driver for WM831x/2x PMICs" |
| 43 | 43 | depends on MFD_WM831X |
| 44 | − ---help--- | |
| 44 | + help | |
| 45 | 45 | Supports the clocking subsystem of the WM831x/2x series of |
| 46 | 46 | PMICs from Wolfson Microelectronics. |
| 47 | 47 | |
| @@ -50,14 +50,14 @@ source "drivers/clk/versatile/Kconfig" · 2 unmodified lines | ||
| 50 | 50 | config CLK_HSDK |
| 51 | 51 | bool "PLL Driver for HSDK platform" |
| 52 | 52 | depends on OF || COMPILE_TEST |
| 53 | − ---help--- | |
| 53 | + help | |
| 54 | 54 | This driver supports the HSDK core, system, ddr, tunnel and hdmi PLLs |
| 55 | 55 | control. |
| 56 | 56 | |
| 57 | 57 | config COMMON_CLK_MAX77686 |
| 58 | 58 | tristate "Clock driver for Maxim 77620/77686/77802 MFD" |
| 59 | 59 | depends on MFD_MAX77686 || MFD_MAX77620 || COMPILE_TEST |
| 60 | − ---help--- | |
| 60 | + help | |
| 61 | 61 | This driver supports Maxim 77620/77686/77802 crystal oscillator |
| 62 | 62 | clock. |
| 63 | 63 | |
| @@ -70,7 +70,7 @@ config COMMON_CLK_MAX9485 · 6 unmodified lines | ||
| 70 | 70 | config COMMON_CLK_RK808 |
| 71 | 71 | tristate "Clock driver for RK805/RK808/RK809/RK817/RK818" |
| 72 | 72 | depends on MFD_RK808 |
| 73 | − ---help--- | |
| 73 | + help | |
| 74 | 74 | This driver supports RK805, RK809 and RK817, RK808 and RK818 crystal oscillator clock. |
| 75 | 75 | These multi-function devices have two fixed-rate oscillators, clocked at 32KHz each. |
| 76 | 76 | Clkout1 is always on, Clkout2 can off by control register. |
| @@ -80,7 +80,7 @@ config COMMON_CLK_HI655X · 3 unmodified lines | ||
| 80 | 80 | depends on (MFD_HI655X_PMIC || COMPILE_TEST) |
| 81 | 81 | depends on REGMAP |
| 82 | 82 | default MFD_HI655X_PMIC |
| 83 | − ---help--- | |
| 83 | + help | |
| 84 | 84 | This driver supports the hi655x PMIC clock. This |
| 85 | 85 | multi-function device has one fixed-rate oscillator, clocked |
| 86 | 86 | at 32KHz. |
| @@ -88,7 +88,7 @@ config COMMON_CLK_HI655X · 1 unmodified line | ||
| 88 | 88 | config COMMON_CLK_SCMI |
| 89 | 89 | tristate "Clock driver controlled via SCMI interface" |
| 90 | 90 | depends on ARM_SCMI_PROTOCOL || COMPILE_TEST |
| 91 | − ---help--- | |
| 91 | + help | |
| 92 | 92 | This driver provides support for clocks that are controlled |
| 93 | 93 | by firmware that implements the SCMI interface. |
| 94 | 94 | |
| @@ -98,7 +98,7 @@ config COMMON_CLK_SCMI · 3 unmodified lines | ||
| 98 | 98 | config COMMON_CLK_SCPI |
| 99 | 99 | tristate "Clock driver controlled via SCPI interface" |
| 100 | 100 | depends on ARM_SCPI_PROTOCOL || COMPILE_TEST |
| 101 | − ---help--- | |
| 101 | + help | |
| 102 | 102 | This driver provides support for clocks that are controlled |
| 103 | 103 | by firmware that implements the SCPI interface. |
| 104 | 104 | |
| @@ -121,7 +121,7 @@ config COMMON_CLK_SI5351 · 16 unmodified lines | ||
| 121 | 121 | depends on I2C |
| 122 | 122 | select REGMAP_I2C |
| 123 | 123 | select RATIONAL |
| 124 | − ---help--- | |
| 124 | + help | |
| 125 | 125 | This driver supports Silicon Labs 5351A/B/C programmable clock |
| 126 | 126 | generators. |
| 127 | 127 | |
| @@ -163,7 +163,7 @@ config COMMON_CLK_CDCE706 · 35 unmodified lines | ||
| 163 | 163 | depends on I2C |
| 164 | 164 | select REGMAP_I2C |
| 165 | 165 | select RATIONAL |
| 166 | − ---help--- | |
| 166 | + help | |
| 167 | 167 | This driver supports TI CDCE706 programmable 3-PLL clock synthesizer. |
| 168 | 168 | |
| 169 | 169 | config COMMON_CLK_CDCE925 |
| @@ -206,7 +206,7 @@ config COMMON_CLK_GEMINI · 36 unmodified lines | ||
| 206 | 206 | depends on ARCH_GEMINI || COMPILE_TEST |
| 207 | 207 | select MFD_SYSCON |
| 208 | 208 | select RESET_CONTROLLER |
| 209 | − ---help--- | |
| 209 | + help | |
| 210 | 210 | This driver supports the SoC clocks on the Cortina Systems Gemini |
| 211 | 211 | platform, also known as SL3516 or CS3516. |
| 212 | 212 | |
| @@ -216,7 +216,7 @@ config COMMON_CLK_ASPEED · 3 unmodified lines | ||
| 216 | 216 | default ARCH_ASPEED |
| 217 | 217 | select MFD_SYSCON |
| 218 | 218 | select RESET_CONTROLLER |
| 219 | − ---help--- | |
| 219 | + help | |
| 220 | 220 | This driver supports the SoC clocks on the Aspeed BMC platforms. |
| 221 | 221 | |
| 222 | 222 | The G4 and G5 series, including the ast2400 and ast2500, are supported |
| @@ -225,7 +225,7 @@ config COMMON_CLK_ASPEED · 2 unmodified lines | ||
| 225 | 225 | config COMMON_CLK_S2MPS11 |
| 226 | 226 | tristate "Clock driver for S2MPS1X/S5M8767 MFD" |
| 227 | 227 | depends on MFD_SEC_CORE || COMPILE_TEST |
| 228 | − ---help--- | |
| 228 | + help | |
| 229 | 229 | This driver supports S2MPS11/S2MPS14/S5M8767 crystal oscillator |
| 230 | 230 | clock. These multi-function devices have two (S2MPS14) or three |
| 231 | 231 | (S2MPS11, S5M8767) fixed-rate oscillators, clocked at 32KHz each. |
| @@ -233,7 +233,7 @@ config COMMON_CLK_S2MPS11 · 1 unmodified line | ||
| 233 | 233 | config CLK_TWL6040 |
| 234 | 234 | tristate "External McPDM functional clock from twl6040" |
| 235 | 235 | depends on TWL6040_CORE |
| 236 | − ---help--- | |
| 236 | + help | |
| 237 | 237 | Enable the external functional clock support on OMAP4+ platforms for |
| 238 | 238 | McPDM. McPDM module is using the external bit clock on the McPDM bus |
| 239 | 239 | as functional clock. |
| @@ -248,7 +248,7 @@ config COMMON_CLK_AXI_CLKGEN · 8 unmodified lines | ||
| 248 | 248 | config CLK_QORIQ |
| 249 | 249 | bool "Clock driver for Freescale QorIQ platforms" |
| 250 | 250 | depends on (PPC_E500MC || ARM || ARM64 || COMPILE_TEST) && OF |
| 251 | − ---help--- | |
| 251 | + help | |
| 252 | 252 | This adds the clock driver support for Freescale QorIQ platforms |
| 253 | 253 | using common clock framework. |
| 254 | 254 | |
| @@ -266,7 +266,7 @@ config COMMON_CLK_XGENE · 11 unmodified lines | ||
| 266 | 266 | bool "Clock driver for APM XGene SoC" |
| 267 | 267 | default ARCH_XGENE |
| 268 | 268 | depends on ARM64 || COMPILE_TEST |
| 269 | − ---help--- | |
| 269 | + help | |
| 270 | 270 | Support for the APM X-Gene SoC reference, PLL, and device clocks. |
| 271 | 271 | |
| 272 | 272 | config COMMON_CLK_LOCHNAGAR |
| @@ -280,26 +280,26 @@ config COMMON_CLK_NXP · 7 unmodified lines | ||
| 280 | 280 | def_bool COMMON_CLK && (ARCH_LPC18XX || ARCH_LPC32XX) |
| 281 | 281 | select REGMAP_MMIO if ARCH_LPC32XX |
| 282 | 282 | select MFD_SYSCON if ARCH_LPC18XX |
| 283 | − ---help--- | |
| 283 | + help | |
| 284 | 284 | Support for clock providers on NXP platforms. |
| 285 | 285 | |
| 286 | 286 | config COMMON_CLK_PALMAS |
| 287 | 287 | tristate "Clock driver for TI Palmas devices" |
| 288 | 288 | depends on MFD_PALMAS |
| 289 | − ---help--- | |
| 289 | + help | |
| 290 | 290 | This driver supports TI Palmas devices 32KHz output KG and KG_AUDIO |
| 291 | 291 | using common clock framework. |
| 292 | 292 | |
| 293 | 293 | config COMMON_CLK_PWM |
| 294 | 294 | tristate "Clock driver for PWMs used as clock outputs" |
| 295 | 295 | depends on PWM |
| 296 | − ---help--- | |
| 296 | + help | |
| 297 | 297 | Adapter driver so that any PWM output can be (mis)used as clock signal |
| 298 | 298 | at 50% duty cycle. |
| 299 | 299 | |
| 300 | 300 | config COMMON_CLK_PXA |
| 301 | 301 | def_bool COMMON_CLK && ARCH_PXA |
| 302 | − ---help--- | |
| 302 | + help | |
| 303 | 303 | Support for the Marvell PXA SoC. |
| 304 | 304 | |
| 305 | 305 | config COMMON_CLK_PIC32 |
| @@ -309,7 +309,7 @@ config COMMON_CLK_OXNAS · 3 unmodified lines | ||
| 309 | 309 | bool "Clock driver for the OXNAS SoC Family" |
| 310 | 310 | depends on ARCH_OXNAS || COMPILE_TEST |
| 311 | 311 | select MFD_SYSCON |
| 312 | − ---help--- | |
| 312 | + help | |
| 313 | 313 | Support for the OXNAS SoC Family clocks. |
| 314 | 314 | |
| 315 | 315 | config COMMON_CLK_VC5 |
| @@ -3,7 +3,7 @@ config COMMON_CLK_BOSTON · 2 unmodified lines | ||
| 3 | 3 | bool "Clock driver for MIPS Boston boards" |
| 4 | 4 | depends on MIPS || COMPILE_TEST |
| 5 | 5 | select MFD_SYSCON |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | Enable this to support the system & CPU clocks on the MIPS Boston |
| 8 | 8 | development board from Imagination Technologies. These are simple |
| 9 | 9 | fixed rate clocks whose rate is determined by reading a platform |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config COMMON_CLK_KEYSTONE |
| 3 | 3 | tristate "Clock drivers for Keystone based SOCs" |
| 4 | 4 | depends on (ARCH_KEYSTONE || COMPILE_TEST) && OF |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | Supports clock drivers for Keystone based SOCs. These SOCs have local |
| 7 | 7 | a power sleep control module that gate the clock to the IPs and PLLs. |
| 8 | 8 | |
| @@ -11,7 +11,7 @@ config TI_SCI_CLK · 2 unmodified lines | ||
| 11 | 11 | depends on (ARCH_KEYSTONE || ARCH_K3 || COMPILE_TEST) && OF |
| 12 | 12 | depends on TI_SCI_PROTOCOL |
| 13 | 13 | default ARCH_KEYSTONE |
| 14 | − ---help--- | |
| 14 | + help | |
| 15 | 15 | This adds the clock driver support over TI System Control Interface. |
| 16 | 16 | If you wish to use clock resources from the PMMC firmware, say Y. |
| 17 | 17 | Otherwise, say N. |
| @@ -8,7 +8,7 @@ menu "Clock driver for MediaTek SoC" · 7 unmodified lines | ||
| 8 | 8 | config COMMON_CLK_MEDIATEK |
| 9 | 9 | bool |
| 10 | 10 | select RESET_CONTROLLER |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | MediaTek SoCs' clock support. |
| 13 | 13 | |
| 14 | 14 | config COMMON_CLK_MT2701 |
| @@ -16,55 +16,55 @@ config COMMON_CLK_MT2701 · 1 unmodified line | ||
| 16 | 16 | depends on (ARCH_MEDIATEK && ARM) || COMPILE_TEST |
| 17 | 17 | select COMMON_CLK_MEDIATEK |
| 18 | 18 | default ARCH_MEDIATEK && ARM |
| 19 | − ---help--- | |
| 19 | + help | |
| 20 | 20 | This driver supports MediaTek MT2701 basic clocks. |
| 21 | 21 | |
| 22 | 22 | config COMMON_CLK_MT2701_MMSYS |
| 23 | 23 | bool "Clock driver for MediaTek MT2701 mmsys" |
| 24 | 24 | depends on COMMON_CLK_MT2701 |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | This driver supports MediaTek MT2701 mmsys clocks. |
| 27 | 27 | |
| 28 | 28 | config COMMON_CLK_MT2701_IMGSYS |
| 29 | 29 | bool "Clock driver for MediaTek MT2701 imgsys" |
| 30 | 30 | depends on COMMON_CLK_MT2701 |
| 31 | − ---help--- | |
| 31 | + help | |
| 32 | 32 | This driver supports MediaTek MT2701 imgsys clocks. |
| 33 | 33 | |
| 34 | 34 | config COMMON_CLK_MT2701_VDECSYS |
| 35 | 35 | bool "Clock driver for MediaTek MT2701 vdecsys" |
| 36 | 36 | depends on COMMON_CLK_MT2701 |
| 37 | − ---help--- | |
| 37 | + help | |
| 38 | 38 | This driver supports MediaTek MT2701 vdecsys clocks. |
| 39 | 39 | |
| 40 | 40 | config COMMON_CLK_MT2701_HIFSYS |
| 41 | 41 | bool "Clock driver for MediaTek MT2701 hifsys" |
| 42 | 42 | depends on COMMON_CLK_MT2701 |
| 43 | − ---help--- | |
| 43 | + help | |
| 44 | 44 | This driver supports MediaTek MT2701 hifsys clocks. |
| 45 | 45 | |
| 46 | 46 | config COMMON_CLK_MT2701_ETHSYS |
| 47 | 47 | bool "Clock driver for MediaTek MT2701 ethsys" |
| 48 | 48 | depends on COMMON_CLK_MT2701 |
| 49 | − ---help--- | |
| 49 | + help | |
| 50 | 50 | This driver supports MediaTek MT2701 ethsys clocks. |
| 51 | 51 | |
| 52 | 52 | config COMMON_CLK_MT2701_BDPSYS |
| 53 | 53 | bool "Clock driver for MediaTek MT2701 bdpsys" |
| 54 | 54 | depends on COMMON_CLK_MT2701 |
| 55 | − ---help--- | |
| 55 | + help | |
| 56 | 56 | This driver supports MediaTek MT2701 bdpsys clocks. |
| 57 | 57 | |
| 58 | 58 | config COMMON_CLK_MT2701_AUDSYS |
| 59 | 59 | bool "Clock driver for Mediatek MT2701 audsys" |
| 60 | 60 | depends on COMMON_CLK_MT2701 |
| 61 | − ---help--- | |
| 61 | + help | |
| 62 | 62 | This driver supports Mediatek MT2701 audsys clocks. |
| 63 | 63 | |
| 64 | 64 | config COMMON_CLK_MT2701_G3DSYS |
| 65 | 65 | bool "Clock driver for MediaTek MT2701 g3dsys" |
| 66 | 66 | depends on COMMON_CLK_MT2701 |
| 67 | − ---help--- | |
| 67 | + help | |
| 68 | 68 | This driver supports MediaTek MT2701 g3dsys clocks. |
| 69 | 69 | |
| 70 | 70 | config COMMON_CLK_MT2712 |
| @@ -72,49 +72,49 @@ config COMMON_CLK_MT2712 · 1 unmodified line | ||
| 72 | 72 | depends on (ARCH_MEDIATEK && ARM64) || COMPILE_TEST |
| 73 | 73 | select COMMON_CLK_MEDIATEK |
| 74 | 74 | default ARCH_MEDIATEK && ARM64 |
| 75 | − ---help--- | |
| 75 | + help | |
| 76 | 76 | This driver supports MediaTek MT2712 basic clocks. |
| 77 | 77 | |
| 78 | 78 | config COMMON_CLK_MT2712_BDPSYS |
| 79 | 79 | bool "Clock driver for MediaTek MT2712 bdpsys" |
| 80 | 80 | depends on COMMON_CLK_MT2712 |
| 81 | − ---help--- | |
| 81 | + help | |
| 82 | 82 | This driver supports MediaTek MT2712 bdpsys clocks. |
| 83 | 83 | |
| 84 | 84 | config COMMON_CLK_MT2712_IMGSYS |
| 85 | 85 | bool "Clock driver for MediaTek MT2712 imgsys" |
| 86 | 86 | depends on COMMON_CLK_MT2712 |
| 87 | − ---help--- | |
| 87 | + help | |
| 88 | 88 | This driver supports MediaTek MT2712 imgsys clocks. |
| 89 | 89 | |
| 90 | 90 | config COMMON_CLK_MT2712_JPGDECSYS |
| 91 | 91 | bool "Clock driver for MediaTek MT2712 jpgdecsys" |
| 92 | 92 | depends on COMMON_CLK_MT2712 |
| 93 | − ---help--- | |
| 93 | + help | |
| 94 | 94 | This driver supports MediaTek MT2712 jpgdecsys clocks. |
| 95 | 95 | |
| 96 | 96 | config COMMON_CLK_MT2712_MFGCFG |
| 97 | 97 | bool "Clock driver for MediaTek MT2712 mfgcfg" |
| 98 | 98 | depends on COMMON_CLK_MT2712 |
| 99 | − ---help--- | |
| 99 | + help | |
| 100 | 100 | This driver supports MediaTek MT2712 mfgcfg clocks. |
| 101 | 101 | |
| 102 | 102 | config COMMON_CLK_MT2712_MMSYS |
| 103 | 103 | bool "Clock driver for MediaTek MT2712 mmsys" |
| 104 | 104 | depends on COMMON_CLK_MT2712 |
| 105 | − ---help--- | |
| 105 | + help | |
| 106 | 106 | This driver supports MediaTek MT2712 mmsys clocks. |
| 107 | 107 | |
| 108 | 108 | config COMMON_CLK_MT2712_VDECSYS |
| 109 | 109 | bool "Clock driver for MediaTek MT2712 vdecsys" |
| 110 | 110 | depends on COMMON_CLK_MT2712 |
| 111 | − ---help--- | |
| 111 | + help | |
| 112 | 112 | This driver supports MediaTek MT2712 vdecsys clocks. |
| 113 | 113 | |
| 114 | 114 | config COMMON_CLK_MT2712_VENCSYS |
| 115 | 115 | bool "Clock driver for MediaTek MT2712 vencsys" |
| 116 | 116 | depends on COMMON_CLK_MT2712 |
| 117 | − ---help--- | |
| 117 | + help | |
| 118 | 118 | This driver supports MediaTek MT2712 vencsys clocks. |
| 119 | 119 | |
| 120 | 120 | config COMMON_CLK_MT6765 |
| @@ -264,31 +264,31 @@ config COMMON_CLK_MT6797 · 143 unmodified lines | ||
| 264 | 264 | depends on (ARCH_MEDIATEK && ARM64) || COMPILE_TEST |
| 265 | 265 | select COMMON_CLK_MEDIATEK |
| 266 | 266 | default ARCH_MEDIATEK && ARM64 |
| 267 | − ---help--- | |
| 267 | + help | |
| 268 | 268 | This driver supports MediaTek MT6797 basic clocks. |
| 269 | 269 | |
| 270 | 270 | config COMMON_CLK_MT6797_MMSYS |
| 271 | 271 | bool "Clock driver for MediaTek MT6797 mmsys" |
| 272 | 272 | depends on COMMON_CLK_MT6797 |
| 273 | − ---help--- | |
| 273 | + help | |
| 274 | 274 | This driver supports MediaTek MT6797 mmsys clocks. |
| 275 | 275 | |
| 276 | 276 | config COMMON_CLK_MT6797_IMGSYS |
| 277 | 277 | bool "Clock driver for MediaTek MT6797 imgsys" |
| 278 | 278 | depends on COMMON_CLK_MT6797 |
| 279 | − ---help--- | |
| 279 | + help | |
| 280 | 280 | This driver supports MediaTek MT6797 imgsys clocks. |
| 281 | 281 | |
| 282 | 282 | config COMMON_CLK_MT6797_VDECSYS |
| 283 | 283 | bool "Clock driver for MediaTek MT6797 vdecsys" |
| 284 | 284 | depends on COMMON_CLK_MT6797 |
| 285 | − ---help--- | |
| 285 | + help | |
| 286 | 286 | This driver supports MediaTek MT6797 vdecsys clocks. |
| 287 | 287 | |
| 288 | 288 | config COMMON_CLK_MT6797_VENCSYS |
| 289 | 289 | bool "Clock driver for MediaTek MT6797 vencsys" |
| 290 | 290 | depends on COMMON_CLK_MT6797 |
| 291 | − ---help--- | |
| 291 | + help | |
| 292 | 292 | This driver supports MediaTek MT6797 vencsys clocks. |
| 293 | 293 | |
| 294 | 294 | config COMMON_CLK_MT7622 |
| @@ -296,28 +296,28 @@ config COMMON_CLK_MT7622 · 1 unmodified line | ||
| 296 | 296 | depends on ARCH_MEDIATEK || COMPILE_TEST |
| 297 | 297 | select COMMON_CLK_MEDIATEK |
| 298 | 298 | default ARCH_MEDIATEK |
| 299 | − ---help--- | |
| 299 | + help | |
| 300 | 300 | This driver supports MediaTek MT7622 basic clocks and clocks |
| 301 | 301 | required for various periperals found on MediaTek. |
| 302 | 302 | |
| 303 | 303 | config COMMON_CLK_MT7622_ETHSYS |
| 304 | 304 | bool "Clock driver for MediaTek MT7622 ETHSYS" |
| 305 | 305 | depends on COMMON_CLK_MT7622 |
| 306 | − ---help--- | |
| 306 | + help | |
| 307 | 307 | This driver add support for clocks for Ethernet and SGMII |
| 308 | 308 | required on MediaTek MT7622 SoC. |
| 309 | 309 | |
| 310 | 310 | config COMMON_CLK_MT7622_HIFSYS |
| 311 | 311 | bool "Clock driver for MediaTek MT7622 HIFSYS" |
| 312 | 312 | depends on COMMON_CLK_MT7622 |
| 313 | − ---help--- | |
| 313 | + help | |
| 314 | 314 | This driver supports MediaTek MT7622 HIFSYS clocks providing |
| 315 | 315 | to PCI-E and USB. |
| 316 | 316 | |
| 317 | 317 | config COMMON_CLK_MT7622_AUDSYS |
| 318 | 318 | bool "Clock driver for MediaTek MT7622 AUDSYS" |
| 319 | 319 | depends on COMMON_CLK_MT7622 |
| 320 | − ---help--- | |
| 320 | + help | |
| 321 | 321 | This driver supports MediaTek MT7622 AUDSYS clocks providing |
| 322 | 322 | to audio consumers such as I2S and TDM. |
| 323 | 323 | |
| @@ -326,21 +326,21 @@ config COMMON_CLK_MT7629 · 2 unmodified lines | ||
| 326 | 326 | depends on (ARCH_MEDIATEK && ARM) || COMPILE_TEST |
| 327 | 327 | select COMMON_CLK_MEDIATEK |
| 328 | 328 | default ARCH_MEDIATEK && ARM |
| 329 | − ---help--- | |
| 329 | + help | |
| 330 | 330 | This driver supports MediaTek MT7629 basic clocks and clocks |
| 331 | 331 | required for various periperals found on MediaTek. |
| 332 | 332 | |
| 333 | 333 | config COMMON_CLK_MT7629_ETHSYS |
| 334 | 334 | bool "Clock driver for MediaTek MT7629 ETHSYS" |
| 335 | 335 | depends on COMMON_CLK_MT7629 |
| 336 | − ---help--- | |
| 336 | + help | |
| 337 | 337 | This driver add support for clocks for Ethernet and SGMII |
| 338 | 338 | required on MediaTek MT7629 SoC. |
| 339 | 339 | |
| 340 | 340 | config COMMON_CLK_MT7629_HIFSYS |
| 341 | 341 | bool "Clock driver for MediaTek MT7629 HIFSYS" |
| 342 | 342 | depends on COMMON_CLK_MT7629 |
| 343 | − ---help--- | |
| 343 | + help | |
| 344 | 344 | This driver supports MediaTek MT7629 HIFSYS clocks providing |
| 345 | 345 | to PCI-E and USB. |
| 346 | 346 | |
| @@ -349,7 +349,7 @@ config COMMON_CLK_MT8135 · 2 unmodified lines | ||
| 349 | 349 | depends on (ARCH_MEDIATEK && ARM) || COMPILE_TEST |
| 350 | 350 | select COMMON_CLK_MEDIATEK |
| 351 | 351 | default ARCH_MEDIATEK && ARM |
| 352 | − ---help--- | |
| 352 | + help | |
| 353 | 353 | This driver supports MediaTek MT8135 clocks. |
| 354 | 354 | |
| 355 | 355 | config COMMON_CLK_MT8173 |
| @@ -357,7 +357,7 @@ config COMMON_CLK_MT8173 · 1 unmodified line | ||
| 357 | 357 | depends on ARCH_MEDIATEK || COMPILE_TEST |
| 358 | 358 | select COMMON_CLK_MEDIATEK |
| 359 | 359 | default ARCH_MEDIATEK |
| 360 | − ---help--- | |
| 360 | + help | |
| 361 | 361 | This driver supports MediaTek MT8173 clocks. |
| 362 | 362 | |
| 363 | 363 | config COMMON_CLK_MT8173_MMSYS |
| @@ -3,5 +3,5 @@ config COMMON_CLK_TI_ADPLL · 2 unmodified lines | ||
| 3 | 3 | tristate "Clock driver for dm814x ADPLL" |
| 4 | 4 | depends on ARCH_OMAP2PLUS || COMPILE_TEST |
| 5 | 5 | default y if SOC_TI81XX |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | ADPLL clock driver for the dm814x SoC using common clock framework. |
| @@ -7,7 +7,7 @@ menu "Clock driver for ARM Reference designs" · 6 unmodified lines | ||
| 7 | 7 | config ICST |
| 8 | 8 | bool "Clock driver for ARM Reference designs ICST" |
| 9 | 9 | select REGMAP_MMIO |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Supports clocking on ARM Reference designs: |
| 12 | 12 | - Integrator/AP and Integrator/CP |
| 13 | 13 | - RealView PB1176, EB, PB11MP and PBX |
| @@ -15,7 +15,7 @@ config ICST · 1 unmodified line | ||
| 15 | 15 | config CLK_SP810 |
| 16 | 16 | bool "Clock driver for ARM SP810 System Controller" |
| 17 | 17 | default y if (ARCH_VEXPRESS && ARM) |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | Supports clock muxing (REFCLK/TIMCLK to TIMERCLKEN0-3) capabilities |
| 20 | 20 | of the ARM SP810 System Controller cell. |
| 21 | 21 | |
| @@ -24,7 +24,7 @@ config CLK_VEXPRESS_OSC · 2 unmodified lines | ||
| 24 | 24 | depends on VEXPRESS_CONFIG |
| 25 | 25 | select REGMAP_MMIO |
| 26 | 26 | default y if ARCH_VEXPRESS |
| 27 | − ---help--- | |
| 27 | + help | |
| 28 | 28 | Simple regmap-based driver driving clock generators on Versatile |
| 29 | 29 | Express platforms hidden behind its configuration infrastructure, |
| 30 | 30 | commonly known as OSCs. |
| @@ -3,7 +3,7 @@ · 2 unmodified lines | ||
| 3 | 3 | menuconfig CONNECTOR |
| 4 | 4 | tristate "Connector - unified userspace <-> kernelspace linker" |
| 5 | 5 | depends on NET |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | This is unified userspace <-> kernelspace connector working on top |
| 8 | 8 | of the netlink socket protocol. |
| 9 | 9 | |
| @@ -16,7 +16,7 @@ config PROC_EVENTS · 6 unmodified lines | ||
| 16 | 16 | bool "Report process events to userspace" |
| 17 | 17 | depends on CONNECTOR=y |
| 18 | 18 | default y |
| 19 | − ---help--- | |
| 19 | + help | |
| 20 | 20 | Provide a connector that reports process events to userspace. Send |
| 21 | 21 | events such as fork, exec, id change (uid, gid, suid, etc), and exit. |
| 22 | 22 | |
| @@ -75,7 +75,7 @@ config X86_SFI_CPUFREQ · 74 unmodified lines | ||
| 75 | 75 | config ELAN_CPUFREQ |
| 76 | 76 | tristate "AMD Elan SC400 and SC410" |
| 77 | 77 | depends on MELAN |
| 78 | − ---help--- | |
| 78 | + help | |
| 79 | 79 | This adds the CPUFreq driver for AMD Elan SC400 and SC410 |
| 80 | 80 | processors. |
| 81 | 81 | |
| @@ -90,7 +90,7 @@ config ELAN_CPUFREQ · 8 unmodified lines | ||
| 90 | 90 | config SC520_CPUFREQ |
| 91 | 91 | tristate "AMD Elan SC520" |
| 92 | 92 | depends on MELAN |
| 93 | − ---help--- | |
| 93 | + help | |
| 94 | 94 | This adds the CPUFreq driver for AMD Elan SC520 processor. |
| 95 | 95 | |
| 96 | 96 | For details, take a look at <file:Documentation/cpu-freq/>. |
| @@ -3,7 +3,7 @@ · 2 unmodified lines | ||
| 3 | 3 | menuconfig CRYPTO_HW |
| 4 | 4 | bool "Hardware crypto devices" |
| 5 | 5 | default y |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | Say Y here to get to see options for hardware crypto devices and |
| 8 | 8 | processors. This option alone does not add any kernel code. |
| 9 | 9 | |
| @@ -334,7 +334,7 @@ config HW_RANDOM_PPC4XX · 324 unmodified lines | ||
| 334 | 334 | bool "PowerPC 4xx generic true random number generator support" |
| 335 | 335 | depends on CRYPTO_DEV_PPC4XX && HW_RANDOM |
| 336 | 336 | default y |
| 337 | − ---help--- | |
| 337 | + help | |
| 338 | 338 | This option provides the kernel-side support for the TRNG hardware |
| 339 | 339 | found in the security function of some PowerPC 4xx SoCs. |
| 340 | 340 | |
| @@ -420,7 +420,7 @@ config CRYPTO_DEV_EXYNOS_RNG · 79 unmodified lines | ||
| 420 | 420 | depends on ARCH_EXYNOS || COMPILE_TEST |
| 421 | 421 | depends on HAS_IOMEM |
| 422 | 422 | select CRYPTO_RNG |
| 423 | − ---help--- | |
| 423 | + help | |
| 424 | 424 | This driver provides kernel-side support through the |
| 425 | 425 | cryptographic API for the pseudo random number generator hardware |
| 426 | 426 | found on Exynos SoCs. |
| @@ -597,7 +597,7 @@ source "drivers/crypto/marvell/Kconfig" · 170 unmodified lines | ||
| 597 | 597 | config CRYPTO_DEV_CAVIUM_ZIP |
| 598 | 598 | tristate "Cavium ZIP driver" |
| 599 | 599 | depends on PCI && 64BIT && (ARM64 || COMPILE_TEST) |
| 600 | − ---help--- | |
| 600 | + help | |
| 601 | 601 | Select this option if you want to enable compression/decompression |
| 602 | 602 | acceleration on Cavium's ARM based SoCs |
| 603 | 603 | |
| @@ -8,7 +8,7 @@ config CRYPTO_DEV_CHELSIO · 7 unmodified lines | ||
| 8 | 8 | select CRYPTO_SHA512 |
| 9 | 9 | select CRYPTO_AUTHENC |
| 10 | 10 | select CRYPTO_GF128MUL |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | The Chelsio Crypto Co-processor driver for T6 adapters. |
| 13 | 13 | |
| 14 | 14 | For general information about Chelsio and our products, visit |
| @@ -29,7 +29,7 @@ config CHELSIO_IPSEC_INLINE · 14 unmodified lines | ||
| 29 | 29 | depends on XFRM_OFFLOAD |
| 30 | 30 | depends on INET_ESP_OFFLOAD || INET6_ESP_OFFLOAD |
| 31 | 31 | default n |
| 32 | − ---help--- | |
| 32 | + help | |
| 33 | 33 | Enable support for IPSec Tx Inline. |
| 34 | 34 | |
| 35 | 35 | config CRYPTO_DEV_CHELSIO_TLS |
| @@ -37,7 +37,7 @@ config CRYPTO_DEV_CHELSIO_TLS · 1 unmodified line | ||
| 37 | 37 | depends on CHELSIO_T4 |
| 38 | 38 | depends on TLS_TOE |
| 39 | 39 | select CRYPTO_DEV_CHELSIO |
| 40 | − ---help--- | |
| 40 | + help | |
| 41 | 41 | Support Chelsio Inline TLS with Chelsio crypto accelerator. |
| 42 | 42 | |
| 43 | 43 | To compile this driver as a module, choose M here: the module |
| @@ -5,7 +5,7 @@ config SYNC_FILE · 4 unmodified lines | ||
| 5 | 5 | bool "Explicit Synchronization Framework" |
| 6 | 6 | default n |
| 7 | 7 | select DMA_SHARED_BUFFER |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | The Sync File Framework adds explicit synchronization via |
| 10 | 10 | userspace. It enables send/receive 'struct dma_fence' objects to/from |
| 11 | 11 | userspace via Sync File fds for synchronization between drivers via |
| @@ -22,7 +22,7 @@ config SW_SYNC · 10 unmodified lines | ||
| 22 | 22 | default n |
| 23 | 23 | depends on SYNC_FILE |
| 24 | 24 | depends on DEBUG_FS |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | A sync object driver that uses a 32bit counter to coordinate |
| 27 | 27 | synchronization. Useful when there is no hardware primitive backing |
| 28 | 28 | the synchronization. |
| @@ -198,7 +198,7 @@ config FSL_DMA · 197 unmodified lines | ||
| 198 | 198 | depends on FSL_SOC |
| 199 | 199 | select DMA_ENGINE |
| 200 | 200 | select ASYNC_TX_ENABLE_CHANNEL_SWITCH |
| 201 | − ---help--- | |
| 201 | + help | |
| 202 | 202 | Enable support for the Freescale Elo series DMA controllers. |
| 203 | 203 | The Elo is the DMA controller on some mpc82xx and mpc83xx parts, the |
| 204 | 204 | EloPlus is on mpc85xx and mpc86xx and Pxxx parts, and the Elo3 is on |
| @@ -233,7 +233,7 @@ config FSL_RAID · 28 unmodified lines | ||
| 233 | 233 | depends on FSL_SOC && !ASYNC_TX_ENABLE_CHANNEL_SWITCH |
| 234 | 234 | select DMA_ENGINE |
| 235 | 235 | select DMA_ENGINE_RAID |
| 236 | − ---help--- | |
| 236 | + help | |
| 237 | 237 | Enable support for Freescale RAID Engine. RAID Engine is |
| 238 | 238 | available on some QorIQ SoCs (like P5020/P5040). It has |
| 239 | 239 | the capability to offload memcpy, xor and pq computation |
| @@ -414,7 +414,7 @@ config MPC512X_DMA · 174 unmodified lines | ||
| 414 | 414 | tristate "Freescale MPC512x built-in DMA engine support" |
| 415 | 415 | depends on PPC_MPC512x || PPC_MPC831x |
| 416 | 416 | select DMA_ENGINE |
| 417 | − ---help--- | |
| 417 | + help | |
| 418 | 418 | Enable support for the Freescale MPC512x built-in DMA engine. |
| 419 | 419 | |
| 420 | 420 | config MV_XOR |
| @@ -423,7 +423,7 @@ config MV_XOR · 2 unmodified lines | ||
| 423 | 423 | select DMA_ENGINE |
| 424 | 424 | select DMA_ENGINE_RAID |
| 425 | 425 | select ASYNC_TX_ENABLE_CHANNEL_SWITCH |
| 426 | − ---help--- | |
| 426 | + help | |
| 427 | 427 | Enable support for the Marvell XOR engine. |
| 428 | 428 | |
| 429 | 429 | config MV_XOR_V2 |
| @@ -433,7 +433,7 @@ config MV_XOR_V2 · 3 unmodified lines | ||
| 433 | 433 | select DMA_ENGINE_RAID |
| 434 | 434 | select ASYNC_TX_ENABLE_CHANNEL_SWITCH |
| 435 | 435 | select GENERIC_MSI_IRQ_DOMAIN |
| 436 | − ---help--- | |
| 436 | + help | |
| 437 | 437 | Enable support for the Marvell version 2 XOR engine. |
| 438 | 438 | |
| 439 | 439 | This engine provides acceleration for copy, XOR and RAID6 |
| @@ -5,7 +5,7 @@ config MTK_HSDMA · 4 unmodified lines | ||
| 5 | 5 | depends on ARCH_MEDIATEK || COMPILE_TEST |
| 6 | 6 | select DMA_ENGINE |
| 7 | 7 | select DMA_VIRTUAL_CHANNELS |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | Enable support for High-Speed DMA controller on MediaTek |
| 10 | 10 | SoCs. |
| 11 | 11 | |
| @@ -4,7 +4,7 @@ config QCOM_BAM_DMA · 3 unmodified lines | ||
| 4 | 4 | depends on ARCH_QCOM || (COMPILE_TEST && OF && ARM) |
| 5 | 5 | select DMA_ENGINE |
| 6 | 6 | select DMA_VIRTUAL_CHANNELS |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | Enable support for the QCOM BAM DMA controller. This controller |
| 9 | 9 | provides DMA capabilities for a variety of on-chip devices. |
| 10 | 10 | |
| @@ -44,7 +44,7 @@ config EDAC_DECODE_MCE · 43 unmodified lines | ||
| 44 | 44 | tristate "Decode MCEs in human-readable form (only on AMD for now)" |
| 45 | 45 | depends on CPU_SUP_AMD && X86_MCE_AMD |
| 46 | 46 | default y |
| 47 | − ---help--- | |
| 47 | + help | |
| 48 | 48 | Enable this option if you want to decode Machine Check Exceptions |
| 49 | 49 | occurring on your machine in human-readable form. |
| 50 | 50 | |
| @@ -9,7 +9,7 @@ config HAVE_EISA · 8 unmodified lines | ||
| 9 | 9 | menuconfig EISA |
| 10 | 10 | bool "EISA support" |
| 11 | 11 | depends on HAVE_EISA |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | The Extended Industry Standard Architecture (EISA) bus was |
| 14 | 14 | developed as an open alternative to the IBM MicroChannel bus. |
| 15 | 15 | |
| @@ -26,7 +26,7 @@ config EISA_VLB_PRIMING · 10 unmodified lines | ||
| 26 | 26 | bool "Vesa Local Bus priming" |
| 27 | 27 | depends on X86 && EISA |
| 28 | 28 | default n |
| 29 | − ---help--- | |
| 29 | + help | |
| 30 | 30 | Activate this option if your system contains a Vesa Local |
| 31 | 31 | Bus (VLB) card that identify itself as an EISA card (such as |
| 32 | 32 | the Adaptec AHA-284x). |
| @@ -37,7 +37,7 @@ config EISA_PCI_EISA · 4 unmodified lines | ||
| 37 | 37 | bool "Generic PCI/EISA bridge" |
| 38 | 38 | depends on !PARISC && PCI && EISA |
| 39 | 39 | default y |
| 40 | − ---help--- | |
| 40 | + help | |
| 41 | 41 | Activate this option if your system contains a PCI to EISA |
| 42 | 42 | bridge. If your system have both PCI and EISA slots, you |
| 43 | 43 | certainly need this option. |
| @@ -51,7 +51,7 @@ config EISA_VIRTUAL_ROOT · 7 unmodified lines | ||
| 51 | 51 | bool "EISA virtual root device" |
| 52 | 52 | depends on EISA && (ALPHA || X86) |
| 53 | 53 | default y |
| 54 | − ---help--- | |
| 54 | + help | |
| 55 | 55 | Activate this option if your system only have EISA bus |
| 56 | 56 | (no PCI slots). The Alpha Jensen is an example of such |
| 57 | 57 | a system. |
| @@ -62,7 +62,7 @@ config EISA_NAMES · 4 unmodified lines | ||
| 62 | 62 | bool "EISA device name database" |
| 63 | 63 | depends on EISA |
| 64 | 64 | default y |
| 65 | − ---help--- | |
| 65 | + help | |
| 66 | 66 | By default, the kernel contains a database of all known EISA |
| 67 | 67 | device names to make the information in sysfs comprehensible |
| 68 | 68 | to the user. This database increases size of the kernel |
| @@ -139,7 +139,7 @@ config EFI_BOOTLOADER_CONTROL · 138 unmodified lines | ||
| 139 | 139 | tristate "EFI Bootloader Control" |
| 140 | 140 | depends on EFI_VARS |
| 141 | 141 | default n |
| 142 | − ---help--- | |
| 142 | + help | |
| 143 | 143 | This module installs a reboot hook, such that if reboot() is |
| 144 | 144 | invoked with a string argument NNN, "NNN" is copied to the |
| 145 | 145 | "LoaderEntryOneShot" EFI variable, to be read by the |
| @@ -7,7 +7,7 @@ menuconfig FSI · 6 unmodified lines | ||
| 7 | 7 | tristate "FSI support" |
| 8 | 8 | depends on OF |
| 9 | 9 | select CRC4 |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | FSI - the FRU Support Interface - is a simple bus for low-level |
| 12 | 12 | access to POWER-based hardware. |
| 13 | 13 | |
| @@ -16,7 +16,7 @@ if FSI · 2 unmodified lines | ||
| 16 | 16 | config FSI_NEW_DEV_NODE |
| 17 | 17 | bool "Create '/dev/fsi' directory for char devices" |
| 18 | 18 | default n |
| 19 | − ---help--- | |
| 19 | + help | |
| 20 | 20 | This option causes char devices created for FSI devices to be |
| 21 | 21 | located under a common /dev/fsi/ directory. Set to N unless your |
| 22 | 22 | userspace has been updated to handle the new location. |
| @@ -32,12 +32,12 @@ config FSI_MASTER_GPIO · 9 unmodified lines | ||
| 32 | 32 | tristate "GPIO-based FSI master" |
| 33 | 33 | depends on GPIOLIB |
| 34 | 34 | select CRC4 |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | This option enables a FSI master driver using GPIO lines. |
| 37 | 37 | |
| 38 | 38 | config FSI_MASTER_HUB |
| 39 | 39 | tristate "FSI hub master" |
| 40 | − ---help--- | |
| 40 | + help | |
| 41 | 41 | This option enables a FSI hub master driver. Hub is a type of FSI |
| 42 | 42 | master that is connected to the upstream master via a slave. Hubs |
| 43 | 43 | allow chaining of FSI links to an arbitrary depth. This allows for |
| @@ -48,7 +48,7 @@ config FSI_MASTER_AST_CF · 4 unmodified lines | ||
| 48 | 48 | depends on GPIOLIB |
| 49 | 49 | depends on GPIO_ASPEED |
| 50 | 50 | select GENERIC_ALLOCATOR |
| 51 | − ---help--- | |
| 51 | + help | |
| 52 | 52 | This option enables a FSI master using the AST2400 and AST2500 GPIO |
| 53 | 53 | lines driven by the internal ColdFire coprocessor. This requires |
| 54 | 54 | the corresponding machine specific ColdFire firmware to be available. |
| @@ -64,13 +64,13 @@ config FSI_MASTER_ASPEED · 9 unmodified lines | ||
| 64 | 64 | |
| 65 | 65 | config FSI_SCOM |
| 66 | 66 | tristate "SCOM FSI client device driver" |
| 67 | − ---help--- | |
| 67 | + help | |
| 68 | 68 | This option enables an FSI based SCOM device driver. |
| 69 | 69 | |
| 70 | 70 | config FSI_SBEFIFO |
| 71 | 71 | tristate "SBEFIFO FSI client device driver" |
| 72 | 72 | depends on OF_ADDRESS |
| 73 | − ---help--- | |
| 73 | + help | |
| 74 | 74 | This option enables an FSI based SBEFIFO device driver. The SBEFIFO is |
| 75 | 75 | a pipe-like FSI device for communicating with the self boot engine |
| 76 | 76 | (SBE) on POWER processors. |
| @@ -78,7 +78,7 @@ config FSI_SBEFIFO · 1 unmodified line | ||
| 78 | 78 | config FSI_OCC |
| 79 | 79 | tristate "OCC SBEFIFO client device driver" |
| 80 | 80 | depends on FSI_SBEFIFO |
| 81 | − ---help--- | |
| 81 | + help | |
| 82 | 82 | This option enables an SBEFIFO based On-Chip Controller (OCC) device |
| 83 | 83 | driver. The OCC is a device embedded on a POWER processor that collects |
| 84 | 84 | and aggregates sensor data from the processor and system. The OCC can |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | |
| 6 | 6 | menuconfig GNSS |
| 7 | 7 | tristate "GNSS receiver support" |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | Say Y here if you have a GNSS receiver (e.g. a GPS receiver). |
| 10 | 10 | |
| 11 | 11 | To compile this driver as a module, choose M here: the module will |
| @@ -32,7 +32,7 @@ config GNSS_MTK_SERIAL · 20 unmodified lines | ||
| 32 | 32 | config GNSS_SIRF_SERIAL |
| 33 | 33 | tristate "SiRFstar GNSS receiver support" |
| 34 | 34 | depends on SERIAL_DEV_BUS |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | Say Y here if you have a SiRFstar-based GNSS receiver which uses a |
| 37 | 37 | serial interface. |
| 38 | 38 | |
| @@ -45,7 +45,7 @@ config GNSS_UBX_SERIAL · 6 unmodified lines | ||
| 45 | 45 | tristate "u-blox GNSS receiver support" |
| 46 | 46 | depends on SERIAL_DEV_BUS |
| 47 | 47 | select GNSS_SERIAL |
| 48 | − ---help--- | |
| 48 | + help | |
| 49 | 49 | Say Y here if you have a u-blox GNSS receiver which uses a serial |
| 50 | 50 | interface. |
| 51 | 51 | |
| @@ -1236,7 +1236,7 @@ config GPIO_TC3589X · 1235 unmodified lines | ||
| 1236 | 1236 | config GPIO_TIMBERDALE |
| 1237 | 1237 | bool "Support for timberdale GPIO IP" |
| 1238 | 1238 | depends on MFD_TIMBERDALE |
| 1239 | − ---help--- | |
| 1239 | + help | |
| 1240 | 1240 | Add support for the GPIO IP in the timberdale FPGA. |
| 1241 | 1241 | |
| 1242 | 1242 | config GPIO_TPS65086 |
| @@ -62,7 +62,7 @@ config DRM_MEGACHIPS_STDPXXXX_GE_B850V3_FW · 61 unmodified lines | ||
| 62 | 62 | depends on OF |
| 63 | 63 | select DRM_KMS_HELPER |
| 64 | 64 | select DRM_PANEL |
| 65 | − ---help--- | |
| 65 | + help | |
| 66 | 66 | This is a driver for the display bridges of |
| 67 | 67 | GE B850v3 that convert dual channel LVDS |
| 68 | 68 | to DP++. This is used with the i.MX6 imx-ldb |
| @@ -89,7 +89,7 @@ config DRM_NXP_PTN3460 · 20 unmodified lines | ||
| 89 | 89 | depends on OF |
| 90 | 90 | select DRM_KMS_HELPER |
| 91 | 91 | select DRM_PANEL |
| 92 | − ---help--- | |
| 92 | + help | |
| 93 | 93 | NXP PTN3460 eDP-LVDS bridge chip driver. |
| 94 | 94 | |
| 95 | 95 | config DRM_PARADE_PS8622 |
| @@ -98,7 +98,7 @@ config DRM_PARADE_PS8622 · 2 unmodified lines | ||
| 98 | 98 | select DRM_PANEL |
| 99 | 99 | select DRM_KMS_HELPER |
| 100 | 100 | select BACKLIGHT_CLASS_DEVICE |
| 101 | − ---help--- | |
| 101 | + help | |
| 102 | 102 | Parade eDP-LVDS bridge chip driver. |
| 103 | 103 | |
| 104 | 104 | config DRM_PARADE_PS8640 |
| @@ -128,13 +128,13 @@ config DRM_SII902X · 23 unmodified lines | ||
| 128 | 128 | select REGMAP_I2C |
| 129 | 129 | select I2C_MUX |
| 130 | 130 | select SND_SOC_HDMI_CODEC if SND_SOC |
| 131 | − ---help--- | |
| 131 | + help | |
| 132 | 132 | Silicon Image sii902x bridge chip driver. |
| 133 | 133 | |
| 134 | 134 | config DRM_SII9234 |
| 135 | 135 | tristate "Silicon Image SII9234 HDMI/MHL bridge" |
| 136 | 136 | depends on OF |
| 137 | − ---help--- | |
| 137 | + help | |
| 138 | 138 | Say Y here if you want support for the MHL interface. |
| 139 | 139 | It is an I2C driver, that detects connection of MHL bridge |
| 140 | 140 | and starts encapsulation of HDMI signal. |
| @@ -150,7 +150,7 @@ config DRM_SIMPLE_BRIDGE · 9 unmodified lines | ||
| 150 | 150 | config DRM_THINE_THC63LVD1024 |
| 151 | 151 | tristate "Thine THC63LVD1024 LVDS decoder bridge" |
| 152 | 152 | depends on OF |
| 153 | − ---help--- | |
| 153 | + help | |
| 154 | 154 | Thine THC63LVD1024 LVDS/parallel converter driver. |
| 155 | 155 | |
| 156 | 156 | config DRM_TOSHIBA_TC358764 |
| @@ -168,7 +168,7 @@ config DRM_TOSHIBA_TC358767 · 11 unmodified lines | ||
| 168 | 168 | select DRM_KMS_HELPER |
| 169 | 169 | select REGMAP_I2C |
| 170 | 170 | select DRM_PANEL |
| 171 | − ---help--- | |
| 171 | + help | |
| 172 | 172 | Toshiba TC358767 eDP bridge chip driver. |
| 173 | 173 | |
| 174 | 174 | config DRM_TOSHIBA_TC358768 |
| @@ -185,7 +185,7 @@ config DRM_TI_TFP410 · 10 unmodified lines | ||
| 185 | 185 | tristate "TI TFP410 DVI/HDMI bridge" |
| 186 | 186 | depends on OF |
| 187 | 187 | select DRM_KMS_HELPER |
| 188 | − ---help--- | |
| 188 | + help | |
| 189 | 189 | Texas Instruments TFP410 DVI/HDMI Transmitter driver |
| 190 | 190 | |
| 191 | 191 | config DRM_TI_SN65DSI86 |
| @@ -71,7 +71,7 @@ config OMAP4_DSS_HDMI_CEC · 70 unmodified lines | ||
| 71 | 71 | depends on OMAP4_DSS_HDMI |
| 72 | 72 | select CEC_CORE |
| 73 | 73 | default y |
| 74 | − ---help--- | |
| 74 | + help | |
| 75 | 75 | When selected the HDMI transmitter will support the CEC feature. |
| 76 | 76 | |
| 77 | 77 | config OMAP5_DSS_HDMI |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | menuconfig GREYBUS |
| 3 | 3 | tristate "Greybus support" |
| 4 | 4 | depends on SYSFS |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This option enables the Greybus driver core. Greybus is a |
| 7 | 7 | hardware protocol that was designed to provide Unipro with a |
| 8 | 8 | sane application layer. It was originally designed for the |
| @@ -20,7 +20,7 @@ if GREYBUS · 11 unmodified lines | ||
| 20 | 20 | config GREYBUS_ES2 |
| 21 | 21 | tristate "Greybus ES3 USB host controller" |
| 22 | 22 | depends on USB |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | Select this option if you have a Toshiba ES3 USB device that |
| 25 | 25 | acts as a Greybus "host controller". This device is a bridge |
| 26 | 26 | from a USB device to a Unipro network. |
| @@ -9,7 +9,7 @@ config HID · 8 unmodified lines | ||
| 9 | 9 | tristate "HID bus support" |
| 10 | 10 | depends on INPUT |
| 11 | 11 | default y |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | A human interface device (HID) is a type of computer device that |
| 14 | 14 | interacts directly with and takes input from humans. The term "HID" |
| 15 | 15 | most commonly used to refer to the USB-HID specification, but other |
| @@ -31,7 +31,7 @@ config HID_BATTERY_STRENGTH · 15 unmodified lines | ||
| 31 | 31 | depends on HID |
| 32 | 32 | select POWER_SUPPLY |
| 33 | 33 | default n |
| 34 | − ---help--- | |
| 34 | + help | |
| 35 | 35 | This option adds support of reporting battery strength (for HID devices |
| 36 | 36 | that support this feature) through power_supply class so that userspace |
| 37 | 37 | tools, such as upower, can display it. |
| @@ -39,7 +39,7 @@ config HID_BATTERY_STRENGTH · 1 unmodified line | ||
| 39 | 39 | config HIDRAW |
| 40 | 40 | bool "/dev/hidraw raw HID device support" |
| 41 | 41 | depends on HID |
| 42 | − ---help--- | |
| 42 | + help | |
| 43 | 43 | Say Y here if you want to support HID devices (from the USB |
| 44 | 44 | specification standpoint) that aren't strictly user interface |
| 45 | 45 | devices, like monitor controls and Uninterruptible Power Supplies. |
| @@ -59,7 +59,7 @@ config UHID · 13 unmodified lines | ||
| 59 | 59 | tristate "User-space I/O driver support for HID subsystem" |
| 60 | 60 | depends on HID |
| 61 | 61 | default n |
| 62 | − ---help--- | |
| 62 | + help | |
| 63 | 63 | Say Y here if you want to provide HID I/O Drivers from user-space. |
| 64 | 64 | This allows to write I/O drivers in user-space and feed the data from |
| 65 | 65 | the device into the kernel. The kernel parses the HID reports, loads the |
| @@ -80,7 +80,7 @@ config HID_GENERIC · 14 unmodified lines | ||
| 80 | 80 | tristate "Generic HID driver" |
| 81 | 81 | depends on HID |
| 82 | 82 | default HID |
| 83 | − ---help--- | |
| 83 | + help | |
| 84 | 84 | Support for generic devices on the HID bus. This includes most |
| 85 | 85 | keyboards and mice, joysticks, tablets and digitizers. |
| 86 | 86 | |
| @@ -96,13 +96,13 @@ config HID_A4TECH · 9 unmodified lines | ||
| 96 | 96 | tristate "A4 tech mice" |
| 97 | 97 | depends on HID |
| 98 | 98 | default !EXPERT |
| 99 | − ---help--- | |
| 99 | + help | |
| 100 | 100 | Support for A4 tech X5 and WOP-35 / Trust 450L mice. |
| 101 | 101 | |
| 102 | 102 | config HID_ACCUTOUCH |
| 103 | 103 | tristate "Accutouch touch device" |
| 104 | 104 | depends on USB_HID |
| 105 | − ---help--- | |
| 105 | + help | |
| 106 | 106 | This selects a driver for the Accutouch 2216 touch controller. |
| 107 | 107 | |
| 108 | 108 | The driver works around a problem in the reported device capabilities |
| @@ -114,14 +114,14 @@ config HID_ACCUTOUCH · 5 unmodified lines | ||
| 114 | 114 | config HID_ACRUX |
| 115 | 115 | tristate "ACRUX game controller support" |
| 116 | 116 | depends on HID |
| 117 | − ---help--- | |
| 117 | + help | |
| 118 | 118 | Say Y here if you want to enable support for ACRUX game controllers. |
| 119 | 119 | |
| 120 | 120 | config HID_ACRUX_FF |
| 121 | 121 | bool "ACRUX force feedback support" |
| 122 | 122 | depends on HID_ACRUX |
| 123 | 123 | select INPUT_FF_MEMLESS |
| 124 | − ---help--- | |
| 124 | + help | |
| 125 | 125 | Say Y here if you want to enable force feedback support for ACRUX |
| 126 | 126 | game controllers. |
| 127 | 127 | |
| @@ -129,7 +129,7 @@ config HID_APPLE · 1 unmodified line | ||
| 129 | 129 | tristate "Apple {i,Power,Mac}Books" |
| 130 | 130 | depends on HID |
| 131 | 131 | default !EXPERT |
| 132 | − ---help--- | |
| 132 | + help | |
| 133 | 133 | Support for some Apple devices which less or more break |
| 134 | 134 | HID specification. |
| 135 | 135 | |
| @@ -139,7 +139,7 @@ config HID_APPLE · 3 unmodified lines | ||
| 139 | 139 | config HID_APPLEIR |
| 140 | 140 | tristate "Apple infrared receiver" |
| 141 | 141 | depends on (USB_HID) |
| 142 | − ---help--- | |
| 142 | + help | |
| 143 | 143 | Support for Apple infrared remote control. All the Apple computers from |
| 144 | 144 | 2005 onwards include such a port, except the unibody Macbook (2009), |
| 145 | 145 | and Mac Pros. This receiver is also used in the Apple TV set-top box |
| @@ -153,7 +153,7 @@ config HID_ASUS · 7 unmodified lines | ||
| 153 | 153 | depends on LEDS_CLASS |
| 154 | 154 | depends on ASUS_WMI || ASUS_WMI=n |
| 155 | 155 | select POWER_SUPPLY |
| 156 | − ---help--- | |
| 156 | + help | |
| 157 | 157 | Support for Asus notebook built-in keyboard and touchpad via i2c, and |
| 158 | 158 | the Asus Republic of Gamers laptop keyboard special keys. |
| 159 | 159 | |
| @@ -166,21 +166,21 @@ config HID_ASUS · 6 unmodified lines | ||
| 166 | 166 | config HID_AUREAL |
| 167 | 167 | tristate "Aureal" |
| 168 | 168 | depends on HID |
| 169 | − ---help--- | |
| 169 | + help | |
| 170 | 170 | Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes. |
| 171 | 171 | |
| 172 | 172 | config HID_BELKIN |
| 173 | 173 | tristate "Belkin Flip KVM and Wireless keyboard" |
| 174 | 174 | depends on HID |
| 175 | 175 | default !EXPERT |
| 176 | − ---help--- | |
| 176 | + help | |
| 177 | 177 | Support for Belkin Flip KVM and Wireless keyboard. |
| 178 | 178 | |
| 179 | 179 | config HID_BETOP_FF |
| 180 | 180 | tristate "Betop Production Inc. force feedback support" |
| 181 | 181 | depends on USB_HID |
| 182 | 182 | select INPUT_FF_MEMLESS |
| 183 | − ---help--- | |
| 183 | + help | |
| 184 | 184 | Say Y here if you want to enable force feedback support for devices by |
| 185 | 185 | BETOP Production Ltd. |
| 186 | 186 | Currently the following devices are known to be supported: |
| @@ -202,20 +202,20 @@ config HID_CHERRY · 15 unmodified lines | ||
| 202 | 202 | tristate "Cherry Cymotion keyboard" |
| 203 | 203 | depends on HID |
| 204 | 204 | default !EXPERT |
| 205 | − ---help--- | |
| 205 | + help | |
| 206 | 206 | Support for Cherry Cymotion keyboard. |
| 207 | 207 | |
| 208 | 208 | config HID_CHICONY |
| 209 | 209 | tristate "Chicony devices" |
| 210 | 210 | depends on HID |
| 211 | 211 | default !EXPERT |
| 212 | − ---help--- | |
| 212 | + help | |
| 213 | 213 | Support for Chicony Tactical pad and special keys on Chicony keyboards. |
| 214 | 214 | |
| 215 | 215 | config HID_CORSAIR |
| 216 | 216 | tristate "Corsair devices" |
| 217 | 217 | depends on HID && USB && LEDS_CLASS |
| 218 | − ---help--- | |
| 218 | + help | |
| 219 | 219 | Support for Corsair devices that are not fully compliant with the |
| 220 | 220 | HID standard. |
| 221 | 221 | |
| @@ -247,7 +247,7 @@ config HID_PRODIKEYS · 25 unmodified lines | ||
| 247 | 247 | tristate "Prodikeys PC-MIDI Keyboard support" |
| 248 | 248 | depends on HID && SND |
| 249 | 249 | select SND_RAWMIDI |
| 250 | − ---help--- | |
| 250 | + help | |
| 251 | 251 | Support for Prodikeys PC-MIDI Keyboard device support. |
| 252 | 252 | Say Y here to enable support for this device. |
| 253 | 253 | - Prodikeys PC-MIDI keyboard. |
| @@ -261,14 +261,14 @@ config HID_PRODIKEYS · 7 unmodified lines | ||
| 261 | 261 | config HID_CMEDIA |
| 262 | 262 | tristate "CMedia CM6533 HID audio jack controls" |
| 263 | 263 | depends on HID |
| 264 | − ---help--- | |
| 264 | + help | |
| 265 | 265 | Support for CMedia CM6533 HID audio jack controls. |
| 266 | 266 | |
| 267 | 267 | config HID_CP2112 |
| 268 | 268 | tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support" |
| 269 | 269 | depends on USB_HID && HIDRAW && I2C && GPIOLIB |
| 270 | 270 | select GPIOLIB_IRQCHIP |
| 271 | − ---help--- | |
| 271 | + help | |
| 272 | 272 | Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge. |
| 273 | 273 | This is a HID device driver which registers as an i2c adapter |
| 274 | 274 | and gpiochip to expose these functions of the CP2112. The |
| @@ -287,13 +287,13 @@ config HID_CYPRESS · 12 unmodified lines | ||
| 287 | 287 | tristate "Cypress mouse and barcode readers" |
| 288 | 288 | depends on HID |
| 289 | 289 | default !EXPERT |
| 290 | − ---help--- | |
| 290 | + help | |
| 291 | 291 | Support for cypress mouse and barcode readers. |
| 292 | 292 | |
| 293 | 293 | config HID_DRAGONRISE |
| 294 | 294 | tristate "DragonRise Inc. game controller" |
| 295 | 295 | depends on HID |
| 296 | − ---help--- | |
| 296 | + help | |
| 297 | 297 | Say Y here if you have DragonRise Inc. game controllers. |
| 298 | 298 | These might be branded as: |
| 299 | 299 | - Tesun USB-703 |
| @@ -305,7 +305,7 @@ config DRAGONRISE_FF · 5 unmodified lines | ||
| 305 | 305 | bool "DragonRise Inc. force feedback" |
| 306 | 306 | depends on HID_DRAGONRISE |
| 307 | 307 | select INPUT_FF_MEMLESS |
| 308 | − ---help--- | |
| 308 | + help | |
| 309 | 309 | Say Y here if you want to enable force feedback support for DragonRise Inc. |
| 310 | 310 | game controllers. |
| 311 | 311 | |
| @@ -313,7 +313,7 @@ config HID_EMS_FF · 1 unmodified line | ||
| 313 | 313 | tristate "EMS Production Inc. force feedback support" |
| 314 | 314 | depends on HID |
| 315 | 315 | select INPUT_FF_MEMLESS |
| 316 | − ---help--- | |
| 316 | + help | |
| 317 | 317 | Say Y here if you want to enable force feedback support for devices by |
| 318 | 318 | EMS Production Ltd. |
| 319 | 319 | Currently the following devices are known to be supported: |
| @@ -322,7 +322,7 @@ config HID_EMS_FF · 2 unmodified lines | ||
| 322 | 322 | config HID_ELAN |
| 323 | 323 | tristate "ELAN USB Touchpad Support" |
| 324 | 324 | depends on LEDS_CLASS && USB_HID |
| 325 | − ---help--- | |
| 325 | + help | |
| 326 | 326 | Say Y to enable support for the USB ELAN touchpad |
| 327 | 327 | Currently the following devices are known to be supported: |
| 328 | 328 | - HP Pavilion X2 10-p0XX. |
| @@ -330,7 +330,7 @@ config HID_ELAN · 1 unmodified line | ||
| 330 | 330 | config HID_ELECOM |
| 331 | 331 | tristate "ELECOM HID devices" |
| 332 | 332 | depends on HID |
| 333 | − ---help--- | |
| 333 | + help | |
| 334 | 334 | Support for ELECOM devices: |
| 335 | 335 | - BM084 Bluetooth Mouse |
| 336 | 336 | - EX-G Trackballs (M-XT3DRBK, M-XT3URBK) |
| @@ -340,7 +340,7 @@ config HID_ELECOM · 3 unmodified lines | ||
| 340 | 340 | config HID_ELO |
| 341 | 341 | tristate "ELO USB 4000/4500 touchscreen" |
| 342 | 342 | depends on USB_HID |
| 343 | − ---help--- | |
| 343 | + help | |
| 344 | 344 | Support for the ELO USB 4000/4500 touchscreens. Note that this is for |
| 345 | 345 | different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO. |
| 346 | 346 | |
| @@ -348,19 +348,19 @@ config HID_EZKEY · 1 unmodified line | ||
| 348 | 348 | tristate "Ezkey BTC 8193 keyboard" |
| 349 | 349 | depends on HID |
| 350 | 350 | default !EXPERT |
| 351 | − ---help--- | |
| 351 | + help | |
| 352 | 352 | Support for Ezkey BTC 8193 keyboard. |
| 353 | 353 | |
| 354 | 354 | config HID_GEMBIRD |
| 355 | 355 | tristate "Gembird Joypad" |
| 356 | 356 | depends on HID |
| 357 | − ---help--- | |
| 357 | + help | |
| 358 | 358 | Support for Gembird JPD-DualForce 2. |
| 359 | 359 | |
| 360 | 360 | config HID_GFRM |
| 361 | 361 | tristate "Google Fiber TV Box remote control support" |
| 362 | 362 | depends on HID |
| 363 | − ---help--- | |
| 363 | + help | |
| 364 | 364 | Support for Google Fiber TV Box remote controls |
| 365 | 365 | |
| 366 | 366 | config HID_GLORIOUS |
| @@ -373,7 +373,7 @@ config HID_GLORIOUS · 6 unmodified lines | ||
| 373 | 373 | config HID_HOLTEK |
| 374 | 374 | tristate "Holtek HID devices" |
| 375 | 375 | depends on USB_HID |
| 376 | − ---help--- | |
| 376 | + help | |
| 377 | 377 | Support for Holtek based devices: |
| 378 | 378 | - Holtek On Line Grip based game controller |
| 379 | 379 | - Trust GXT 18 Gaming Keyboard |
| @@ -387,20 +387,20 @@ config HOLTEK_FF · 7 unmodified lines | ||
| 387 | 387 | bool "Holtek On Line Grip force feedback support" |
| 388 | 388 | depends on HID_HOLTEK |
| 389 | 389 | select INPUT_FF_MEMLESS |
| 390 | − ---help--- | |
| 390 | + help | |
| 391 | 391 | Say Y here if you have a Holtek On Line Grip based game controller |
| 392 | 392 | and want to have force feedback support for it. |
| 393 | 393 | |
| 394 | 394 | config HID_GOOGLE_HAMMER |
| 395 | 395 | tristate "Google Hammer Keyboard" |
| 396 | 396 | depends on USB_HID && LEDS_CLASS && CROS_EC |
| 397 | − ---help--- | |
| 397 | + help | |
| 398 | 398 | Say Y here if you have a Google Hammer device. |
| 399 | 399 | |
| 400 | 400 | config HID_GT683R |
| 401 | 401 | tristate "MSI GT68xR LED support" |
| 402 | 402 | depends on LEDS_CLASS && USB_HID |
| 403 | − ---help--- | |
| 403 | + help | |
| 404 | 404 | Say Y here if you want to enable support for the three MSI GT68xR LEDs |
| 405 | 405 | |
| 406 | 406 | This driver support following modes: |
| @@ -414,7 +414,7 @@ config HID_GT683R · 7 unmodified lines | ||
| 414 | 414 | config HID_KEYTOUCH |
| 415 | 415 | tristate "Keytouch HID devices" |
| 416 | 416 | depends on HID |
| 417 | − ---help--- | |
| 417 | + help | |
| 418 | 418 | Support for Keytouch HID devices not fully compliant with |
| 419 | 419 | the specification. Currently supported: |
| 420 | 420 | - Keytouch IEC 60945 |
| @@ -422,7 +422,7 @@ config HID_KEYTOUCH · 1 unmodified line | ||
| 422 | 422 | config HID_KYE |
| 423 | 423 | tristate "KYE/Genius devices" |
| 424 | 424 | depends on HID |
| 425 | − ---help--- | |
| 425 | + help | |
| 426 | 426 | Support for KYE/Genius devices not fully compliant with HID standard: |
| 427 | 427 | - Ergo Mouse |
| 428 | 428 | - EasyPen i405X tablet |
| @@ -432,13 +432,13 @@ config HID_KYE · 3 unmodified lines | ||
| 432 | 432 | config HID_UCLOGIC |
| 433 | 433 | tristate "UC-Logic" |
| 434 | 434 | depends on USB_HID |
| 435 | − ---help--- | |
| 435 | + help | |
| 436 | 436 | Support for UC-Logic and Huion tablets. |
| 437 | 437 | |
| 438 | 438 | config HID_WALTOP |
| 439 | 439 | tristate "Waltop" |
| 440 | 440 | depends on HID |
| 441 | − ---help--- | |
| 441 | + help | |
| 442 | 442 | Support for Waltop tablets. |
| 443 | 443 | |
| 444 | 444 | config HID_VIEWSONIC |
| @@ -450,13 +450,13 @@ config HID_VIEWSONIC · 5 unmodified lines | ||
| 450 | 450 | config HID_GYRATION |
| 451 | 451 | tristate "Gyration remote control" |
| 452 | 452 | depends on HID |
| 453 | − ---help--- | |
| 453 | + help | |
| 454 | 454 | Support for Gyration remote control. |
| 455 | 455 | |
| 456 | 456 | config HID_ICADE |
| 457 | 457 | tristate "ION iCade arcade controller" |
| 458 | 458 | depends on HID |
| 459 | − ---help--- | |
| 459 | + help | |
| 460 | 460 | Support for the ION iCade arcade controller to work as a joystick. |
| 461 | 461 | |
| 462 | 462 | To compile this driver as a module, choose M here: the |
| @@ -466,13 +466,13 @@ config HID_ITE · 3 unmodified lines | ||
| 466 | 466 | tristate "ITE devices" |
| 467 | 467 | depends on HID |
| 468 | 468 | default !EXPERT |
| 469 | − ---help--- | |
| 469 | + help | |
| 470 | 470 | Support for ITE devices not fully compliant with HID standard. |
| 471 | 471 | |
| 472 | 472 | config HID_JABRA |
| 473 | 473 | tristate "Jabra USB HID Driver" |
| 474 | 474 | depends on HID |
| 475 | − ---help--- | |
| 475 | + help | |
| 476 | 476 | Support for Jabra USB HID devices. |
| 477 | 477 | |
| 478 | 478 | Prevents mapping of vendor defined HID usages to input events. Without |
| @@ -483,27 +483,27 @@ config HID_JABRA · 4 unmodified lines | ||
| 483 | 483 | config HID_TWINHAN |
| 484 | 484 | tristate "Twinhan IR remote control" |
| 485 | 485 | depends on HID |
| 486 | − ---help--- | |
| 486 | + help | |
| 487 | 487 | Support for Twinhan IR remote control. |
| 488 | 488 | |
| 489 | 489 | config HID_KENSINGTON |
| 490 | 490 | tristate "Kensington Slimblade Trackball" |
| 491 | 491 | depends on HID |
| 492 | 492 | default !EXPERT |
| 493 | − ---help--- | |
| 493 | + help | |
| 494 | 494 | Support for Kensington Slimblade Trackball. |
| 495 | 495 | |
| 496 | 496 | config HID_LCPOWER |
| 497 | 497 | tristate "LC-Power" |
| 498 | 498 | depends on HID |
| 499 | − ---help--- | |
| 499 | + help | |
| 500 | 500 | Support for LC-Power RC1000MCE RF remote control. |
| 501 | 501 | |
| 502 | 502 | config HID_LED |
| 503 | 503 | tristate "Simple RGB LED support" |
| 504 | 504 | depends on HID |
| 505 | 505 | depends on LEDS_CLASS |
| 506 | − ---help--- | |
| 506 | + help | |
| 507 | 507 | Support for simple RGB LED devices. Currently supported are: |
| 508 | 508 | - Riso Kagaku Webmail Notifier |
| 509 | 509 | - Dream Cheeky Webmail Notifier and Friends Alert |
| @@ -519,7 +519,7 @@ config HID_LENOVO · 9 unmodified lines | ||
| 519 | 519 | depends on HID |
| 520 | 520 | select NEW_LEDS |
| 521 | 521 | select LEDS_CLASS |
| 522 | − ---help--- | |
| 522 | + help | |
| 523 | 523 | Support for IBM/Lenovo devices that are not fully compliant with HID standard. |
| 524 | 524 | |
| 525 | 525 | Say Y if you want support for horizontal scrolling of the IBM/Lenovo |
| @@ -535,7 +535,7 @@ config HID_LOGITECH · 9 unmodified lines | ||
| 535 | 535 | depends on HID |
| 536 | 536 | depends on LEDS_CLASS |
| 537 | 537 | default !EXPERT |
| 538 | − ---help--- | |
| 538 | + help | |
| 539 | 539 | Support for Logitech devices that are not fully compliant with HID standard. |
| 540 | 540 | |
| 541 | 541 | config HID_LOGITECH_DJ |
| @@ -544,7 +544,7 @@ config HID_LOGITECH_DJ · 2 unmodified lines | ||
| 544 | 544 | depends on HIDRAW |
| 545 | 545 | depends on HID_LOGITECH |
| 546 | 546 | select HID_LOGITECH_HIDPP |
| 547 | − ---help--- | |
| 547 | + help | |
| 548 | 548 | Say Y if you want support for Logitech receivers and devices. |
| 549 | 549 | Logitech receivers are capable of pairing multiple Logitech compliant |
| 550 | 550 | devices to the same receiver. Without this driver it will be handled by |
| @@ -555,7 +555,7 @@ config HID_LOGITECH_HIDPP · 4 unmodified lines | ||
| 555 | 555 | tristate "Logitech HID++ devices support" |
| 556 | 556 | depends on HID_LOGITECH |
| 557 | 557 | select POWER_SUPPLY |
| 558 | − ---help--- | |
| 558 | + help | |
| 559 | 559 | Support for Logitech devices relyingon the HID++ Logitech specification |
| 560 | 560 | |
| 561 | 561 | Say Y if you want support for Logitech devices relying on the HID++ |
| @@ -621,7 +621,7 @@ config LOGIWHEELS_FF · 59 unmodified lines | ||
| 621 | 621 | config HID_MAGICMOUSE |
| 622 | 622 | tristate "Apple Magic Mouse/Trackpad multi-touch support" |
| 623 | 623 | depends on HID |
| 624 | − ---help--- | |
| 624 | + help | |
| 625 | 625 | Support for the Apple Magic Mouse/Trackpad multi-touch. |
| 626 | 626 | |
| 627 | 627 | Say Y here if you want support for the multi-touch features of the |
| @@ -630,7 +630,7 @@ config HID_MAGICMOUSE · 2 unmodified lines | ||
| 630 | 630 | config HID_MALTRON |
| 631 | 631 | tristate "Maltron L90 keyboard" |
| 632 | 632 | depends on HID |
| 633 | − ---help--- | |
| 633 | + help | |
| 634 | 634 | Adds support for the volume up, volume down, mute, and play/pause buttons |
| 635 | 635 | of the Maltron L90 keyboard. |
| 636 | 636 | |
| @@ -638,7 +638,7 @@ config HID_MAYFLASH · 1 unmodified line | ||
| 638 | 638 | tristate "Mayflash game controller adapter force feedback" |
| 639 | 639 | depends on HID |
| 640 | 640 | select INPUT_FF_MEMLESS |
| 641 | − ---help--- | |
| 641 | + help | |
| 642 | 642 | Say Y here if you have HJZ Mayflash PS3 game controller adapters |
| 643 | 643 | and want to enable force feedback support. |
| 644 | 644 | |
| @@ -646,7 +646,7 @@ config HID_REDRAGON · 1 unmodified line | ||
| 646 | 646 | tristate "Redragon keyboards" |
| 647 | 647 | depends on HID |
| 648 | 648 | default !EXPERT |
| 649 | − ---help--- | |
| 649 | + help | |
| 650 | 650 | Support for Redragon keyboards that need fix-ups to work properly. |
| 651 | 651 | |
| 652 | 652 | config HID_MICROSOFT |
| @@ -654,20 +654,20 @@ config HID_MICROSOFT · 1 unmodified line | ||
| 654 | 654 | depends on HID |
| 655 | 655 | default !EXPERT |
| 656 | 656 | select INPUT_FF_MEMLESS |
| 657 | − ---help--- | |
| 657 | + help | |
| 658 | 658 | Support for Microsoft devices that are not fully compliant with HID standard. |
| 659 | 659 | |
| 660 | 660 | config HID_MONTEREY |
| 661 | 661 | tristate "Monterey Genius KB29E keyboard" |
| 662 | 662 | depends on HID |
| 663 | 663 | default !EXPERT |
| 664 | − ---help--- | |
| 664 | + help | |
| 665 | 665 | Support for Monterey Genius KB29E. |
| 666 | 666 | |
| 667 | 667 | config HID_MULTITOUCH |
| 668 | 668 | tristate "HID Multitouch panels" |
| 669 | 669 | depends on HID |
| 670 | − ---help--- | |
| 670 | + help | |
| 671 | 671 | Generic support for HID multitouch panels. |
| 672 | 672 | |
| 673 | 673 | Say Y here if you have one of the following devices: |
| @@ -712,20 +712,20 @@ config HID_MULTITOUCH · 38 unmodified lines | ||
| 712 | 712 | |
| 713 | 713 | config HID_NTI |
| 714 | 714 | tristate "NTI keyboard adapters" |
| 715 | − ---help--- | |
| 715 | + help | |
| 716 | 716 | Support for the "extra" Sun keyboard keys on keyboards attached |
| 717 | 717 | through Network Technologies USB-SUN keyboard adapters. |
| 718 | 718 | |
| 719 | 719 | config HID_NTRIG |
| 720 | 720 | tristate "N-Trig touch screen" |
| 721 | 721 | depends on USB_HID |
| 722 | − ---help--- | |
| 722 | + help | |
| 723 | 723 | Support for N-Trig touch screen. |
| 724 | 724 | |
| 725 | 725 | config HID_ORTEK |
| 726 | 726 | tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad" |
| 727 | 727 | depends on HID |
| 728 | − ---help--- | |
| 728 | + help | |
| 729 | 729 | There are certain devices which have LogicalMaximum wrong in the keyboard |
| 730 | 730 | usage page of their report descriptor. The most prevailing ones so far |
| 731 | 731 | are manufactured by Ortek, thus the name of the driver. Currently |
| @@ -738,7 +738,7 @@ config HID_ORTEK · 6 unmodified lines | ||
| 738 | 738 | config HID_PANTHERLORD |
| 739 | 739 | tristate "Pantherlord/GreenAsia game controller" |
| 740 | 740 | depends on HID |
| 741 | − ---help--- | |
| 741 | + help | |
| 742 | 742 | Say Y here if you have a PantherLord/GreenAsia based game controller |
| 743 | 743 | or adapter. |
| 744 | 744 | |
| @@ -746,14 +746,14 @@ config PANTHERLORD_FF · 1 unmodified line | ||
| 746 | 746 | bool "Pantherlord force feedback support" |
| 747 | 747 | depends on HID_PANTHERLORD |
| 748 | 748 | select INPUT_FF_MEMLESS |
| 749 | − ---help--- | |
| 749 | + help | |
| 750 | 750 | Say Y here if you have a PantherLord/GreenAsia based game controller |
| 751 | 751 | or adapter and want to enable force feedback support for it. |
| 752 | 752 | |
| 753 | 753 | config HID_PENMOUNT |
| 754 | 754 | tristate "Penmount touch device" |
| 755 | 755 | depends on USB_HID |
| 756 | − ---help--- | |
| 756 | + help | |
| 757 | 757 | This selects a driver for the PenMount 6000 touch controller. |
| 758 | 758 | |
| 759 | 759 | The driver works around a problem in the report descript allowing |
| @@ -764,13 +764,13 @@ config HID_PENMOUNT · 4 unmodified lines | ||
| 764 | 764 | config HID_PETALYNX |
| 765 | 765 | tristate "Petalynx Maxter remote control" |
| 766 | 766 | depends on HID |
| 767 | − ---help--- | |
| 767 | + help | |
| 768 | 768 | Support for Petalynx Maxter remote control. |
| 769 | 769 | |
| 770 | 770 | config HID_PICOLCD |
| 771 | 771 | tristate "PicoLCD (graphic version)" |
| 772 | 772 | depends on HID |
| 773 | − ---help--- | |
| 773 | + help | |
| 774 | 774 | This provides support for Minibox PicoLCD devices, currently |
| 775 | 775 | only the graphical ones are supported. |
| 776 | 776 | |
| @@ -796,7 +796,7 @@ config HID_PICOLCD_FB · 19 unmodified lines | ||
| 796 | 796 | select FB_SYS_COPYAREA |
| 797 | 797 | select FB_SYS_IMAGEBLIT |
| 798 | 798 | select FB_SYS_FOPS |
| 799 | − ---help--- | |
| 799 | + help | |
| 800 | 800 | Provide access to PicoLCD's 256x64 monochrome display via a |
| 801 | 801 | framebuffer device. |
| 802 | 802 | |
| @@ -805,7 +805,7 @@ config HID_PICOLCD_BACKLIGHT · 2 unmodified lines | ||
| 805 | 805 | default !EXPERT |
| 806 | 806 | depends on HID_PICOLCD |
| 807 | 807 | depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y |
| 808 | − ---help--- | |
| 808 | + help | |
| 809 | 809 | Provide access to PicoLCD's backlight control via backlight |
| 810 | 810 | class. |
| 811 | 811 | |
| @@ -814,7 +814,7 @@ config HID_PICOLCD_LCD · 2 unmodified lines | ||
| 814 | 814 | default !EXPERT |
| 815 | 815 | depends on HID_PICOLCD |
| 816 | 816 | depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y |
| 817 | − ---help--- | |
| 817 | + help | |
| 818 | 818 | Provide access to PicoLCD's LCD contrast via lcd class. |
| 819 | 819 | |
| 820 | 820 | config HID_PICOLCD_LEDS |
| @@ -822,7 +822,7 @@ config HID_PICOLCD_LEDS · 1 unmodified line | ||
| 822 | 822 | default !EXPERT |
| 823 | 823 | depends on HID_PICOLCD |
| 824 | 824 | depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y |
| 825 | − ---help--- | |
| 825 | + help | |
| 826 | 826 | Provide access to PicoLCD's GPO pins via leds class. |
| 827 | 827 | |
| 828 | 828 | config HID_PICOLCD_CIR |
| @@ -830,13 +830,13 @@ config HID_PICOLCD_CIR · 1 unmodified line | ||
| 830 | 830 | default !EXPERT |
| 831 | 831 | depends on HID_PICOLCD |
| 832 | 832 | depends on HID_PICOLCD=RC_CORE || RC_CORE=y |
| 833 | − ---help--- | |
| 833 | + help | |
| 834 | 834 | Provide access to PicoLCD's CIR interface via remote control (LIRC). |
| 835 | 835 | |
| 836 | 836 | config HID_PLANTRONICS |
| 837 | 837 | tristate "Plantronics USB HID Driver" |
| 838 | 838 | depends on HID |
| 839 | − ---help--- | |
| 839 | + help | |
| 840 | 840 | Provides HID support for Plantronics USB audio devices. |
| 841 | 841 | Correctly maps vendor unique volume up/down HID usages to |
| 842 | 842 | KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping |
| @@ -847,21 +847,21 @@ config HID_PLANTRONICS · 4 unmodified lines | ||
| 847 | 847 | config HID_PRIMAX |
| 848 | 848 | tristate "Primax non-fully HID-compliant devices" |
| 849 | 849 | depends on HID |
| 850 | − ---help--- | |
| 850 | + help | |
| 851 | 851 | Support for Primax devices that are not fully compliant with the |
| 852 | 852 | HID standard. |
| 853 | 853 | |
| 854 | 854 | config HID_RETRODE |
| 855 | 855 | tristate "Retrode 2 USB adapter for vintage video games" |
| 856 | 856 | depends on USB_HID |
| 857 | − ---help--- | |
| 857 | + help | |
| 858 | 858 | Support for |
| 859 | 859 | * Retrode 2 cartridge and controller adapter |
| 860 | 860 | |
| 861 | 861 | config HID_ROCCAT |
| 862 | 862 | tristate "Roccat device support" |
| 863 | 863 | depends on USB_HID |
| 864 | − ---help--- | |
| 864 | + help | |
| 865 | 865 | Support for Roccat devices. |
| 866 | 866 | Say Y here if you have a Roccat mouse or keyboard and want |
| 867 | 867 | support for its special functionalities. |
| @@ -869,7 +869,7 @@ config HID_ROCCAT · 1 unmodified line | ||
| 869 | 869 | config HID_SAITEK |
| 870 | 870 | tristate "Saitek (Mad Catz) non-fully HID-compliant devices" |
| 871 | 871 | depends on HID |
| 872 | − ---help--- | |
| 872 | + help | |
| 873 | 873 | Support for Saitek devices that are not fully compliant with the |
| 874 | 874 | HID standard. |
| 875 | 875 | |
| @@ -881,7 +881,7 @@ config HID_SAITEK · 5 unmodified lines | ||
| 881 | 881 | config HID_SAMSUNG |
| 882 | 882 | tristate "Samsung InfraRed remote control or keyboards" |
| 883 | 883 | depends on HID |
| 884 | − ---help--- | |
| 884 | + help | |
| 885 | 885 | Support for Samsung InfraRed remote control or keyboards. |
| 886 | 886 | |
| 887 | 887 | config HID_SONY |
| @@ -890,7 +890,7 @@ config HID_SONY · 2 unmodified lines | ||
| 890 | 890 | depends on NEW_LEDS |
| 891 | 891 | depends on LEDS_CLASS |
| 892 | 892 | select POWER_SUPPLY |
| 893 | − ---help--- | |
| 893 | + help | |
| 894 | 894 | Support for |
| 895 | 895 | |
| 896 | 896 | * Sony PS3 6-axis controllers |
| @@ -903,21 +903,21 @@ config SONY_FF · 6 unmodified lines | ||
| 903 | 903 | bool "Sony PS2/3/4 accessories force feedback support" |
| 904 | 904 | depends on HID_SONY |
| 905 | 905 | select INPUT_FF_MEMLESS |
| 906 | − ---help--- | |
| 906 | + help | |
| 907 | 907 | Say Y here if you have a Sony PS2/3/4 accessory and want to enable |
| 908 | 908 | force feedback support for it. |
| 909 | 909 | |
| 910 | 910 | config HID_SPEEDLINK |
| 911 | 911 | tristate "Speedlink VAD Cezanne mouse support" |
| 912 | 912 | depends on HID |
| 913 | − ---help--- | |
| 913 | + help | |
| 914 | 914 | Support for Speedlink Vicious and Divine Cezanne mouse. |
| 915 | 915 | |
| 916 | 916 | config HID_STEAM |
| 917 | 917 | tristate "Steam Controller support" |
| 918 | 918 | depends on HID |
| 919 | 919 | select POWER_SUPPLY |
| 920 | − ---help--- | |
| 920 | + help | |
| 921 | 921 | Say Y here if you have a Steam Controller if you want to use it |
| 922 | 922 | without running the Steam Client. It supports both the wired and |
| 923 | 923 | the wireless adaptor. |
| @@ -925,13 +925,13 @@ config HID_STEAM · 1 unmodified line | ||
| 925 | 925 | config HID_STEELSERIES |
| 926 | 926 | tristate "Steelseries SRW-S1 steering wheel support" |
| 927 | 927 | depends on HID |
| 928 | − ---help--- | |
| 928 | + help | |
| 929 | 929 | Support for Steelseries SRW-S1 steering wheel |
| 930 | 930 | |
| 931 | 931 | config HID_SUNPLUS |
| 932 | 932 | tristate "Sunplus wireless desktop" |
| 933 | 933 | depends on HID |
| 934 | − ---help--- | |
| 934 | + help | |
| 935 | 935 | Support for Sunplus wireless desktop. |
| 936 | 936 | |
| 937 | 937 | config HID_RMI |
| @@ -942,7 +942,7 @@ config HID_RMI · 4 unmodified lines | ||
| 942 | 942 | select RMI4_F11 |
| 943 | 943 | select RMI4_F12 |
| 944 | 944 | select RMI4_F30 |
| 945 | − ---help--- | |
| 945 | + help | |
| 946 | 946 | Support for Synaptics RMI4 touchpads. |
| 947 | 947 | Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid |
| 948 | 948 | and want support for its special functionalities. |
| @@ -950,7 +950,7 @@ config HID_RMI · 1 unmodified line | ||
| 950 | 950 | config HID_GREENASIA |
| 951 | 951 | tristate "GreenAsia (Product ID 0x12) game controller support" |
| 952 | 952 | depends on HID |
| 953 | − ---help--- | |
| 953 | + help | |
| 954 | 954 | Say Y here if you have a GreenAsia (Product ID 0x12) based game |
| 955 | 955 | controller or adapter. |
| 956 | 956 | |
| @@ -958,7 +958,7 @@ config GREENASIA_FF · 1 unmodified line | ||
| 958 | 958 | bool "GreenAsia (Product ID 0x12) force feedback support" |
| 959 | 959 | depends on HID_GREENASIA |
| 960 | 960 | select INPUT_FF_MEMLESS |
| 961 | − ---help--- | |
| 961 | + help | |
| 962 | 962 | Say Y here if you have a GreenAsia (Product ID 0x12) based game controller |
| 963 | 963 | (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter |
| 964 | 964 | and want to enable force feedback support for it. |
| @@ -966,13 +966,13 @@ config GREENASIA_FF · 1 unmodified line | ||
| 966 | 966 | config HID_HYPERV_MOUSE |
| 967 | 967 | tristate "Microsoft Hyper-V mouse driver" |
| 968 | 968 | depends on HYPERV |
| 969 | − ---help--- | |
| 969 | + help | |
| 970 | 970 | Select this option to enable the Hyper-V mouse driver. |
| 971 | 971 | |
| 972 | 972 | config HID_SMARTJOYPLUS |
| 973 | 973 | tristate "SmartJoy PLUS PS2/USB adapter support" |
| 974 | 974 | depends on HID |
| 975 | − ---help--- | |
| 975 | + help | |
| 976 | 976 | Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box, |
| 977 | 977 | Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro. |
| 978 | 978 | |
| @@ -983,20 +983,20 @@ config SMARTJOYPLUS_FF · 4 unmodified lines | ||
| 983 | 983 | bool "SmartJoy PLUS PS2/USB adapter force feedback support" |
| 984 | 984 | depends on HID_SMARTJOYPLUS |
| 985 | 985 | select INPUT_FF_MEMLESS |
| 986 | − ---help--- | |
| 986 | + help | |
| 987 | 987 | Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to |
| 988 | 988 | enable force feedback support for it. |
| 989 | 989 | |
| 990 | 990 | config HID_TIVO |
| 991 | 991 | tristate "TiVo Slide Bluetooth remote control support" |
| 992 | 992 | depends on HID |
| 993 | − ---help--- | |
| 993 | + help | |
| 994 | 994 | Say Y if you have a TiVo Slide Bluetooth remote control. |
| 995 | 995 | |
| 996 | 996 | config HID_TOPSEED |
| 997 | 997 | tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support" |
| 998 | 998 | depends on HID |
| 999 | − ---help--- | |
| 999 | + help | |
| 1000 | 1000 | Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic |
| 1001 | 1001 | CLLRCMCE remote control. |
| 1002 | 1002 | |
| @@ -1005,7 +1005,7 @@ config HID_THINGM · 2 unmodified lines | ||
| 1005 | 1005 | depends on HID |
| 1006 | 1006 | depends on LEDS_CLASS |
| 1007 | 1007 | select HID_LED |
| 1008 | − ---help--- | |
| 1008 | + help | |
| 1009 | 1009 | Support for the ThingM blink(1) USB RGB LED. This driver has been |
| 1010 | 1010 | merged into the generic hid led driver. Config symbol HID_THINGM |
| 1011 | 1011 | just selects HID_LED and will be removed soon. |
| @@ -1013,7 +1013,7 @@ config HID_THINGM · 1 unmodified line | ||
| 1013 | 1013 | config HID_THRUSTMASTER |
| 1014 | 1014 | tristate "ThrustMaster devices support" |
| 1015 | 1015 | depends on HID |
| 1016 | − ---help--- | |
| 1016 | + help | |
| 1017 | 1017 | Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or |
| 1018 | 1018 | a THRUSTMASTER Ferrari GT Rumble Wheel. |
| 1019 | 1019 | |
| @@ -1021,7 +1021,7 @@ config THRUSTMASTER_FF · 1 unmodified line | ||
| 1021 | 1021 | bool "ThrustMaster devices force feedback support" |
| 1022 | 1022 | depends on HID_THRUSTMASTER |
| 1023 | 1023 | select INPUT_FF_MEMLESS |
| 1024 | − ---help--- | |
| 1024 | + help | |
| 1025 | 1025 | Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3, |
| 1026 | 1026 | a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT |
| 1027 | 1027 | Rumble Force or Force Feedback Wheel. |
| @@ -1029,7 +1029,7 @@ config THRUSTMASTER_FF · 1 unmodified line | ||
| 1029 | 1029 | config HID_UDRAW_PS3 |
| 1030 | 1030 | tristate "THQ PS3 uDraw tablet" |
| 1031 | 1031 | depends on HID |
| 1032 | − ---help--- | |
| 1032 | + help | |
| 1033 | 1033 | Say Y here if you want to use the THQ uDraw gaming tablet for |
| 1034 | 1034 | the PS3. |
| 1035 | 1035 | |
| @@ -1069,7 +1069,7 @@ config HID_WIIMOTE · 33 unmodified lines | ||
| 1069 | 1069 | depends on LEDS_CLASS |
| 1070 | 1070 | select POWER_SUPPLY |
| 1071 | 1071 | select INPUT_FF_MEMLESS |
| 1072 | − ---help--- | |
| 1072 | + help | |
| 1073 | 1073 | Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported |
| 1074 | 1074 | devices are the Wii Remote and its extension devices, but also devices |
| 1075 | 1075 | based on the Wii Remote like the Wii U Pro Controller or the |
| @@ -1091,7 +1091,7 @@ config HID_WIIMOTE · 15 unmodified lines | ||
| 1091 | 1091 | config HID_XINMO |
| 1092 | 1092 | tristate "Xin-Mo non-fully compliant devices" |
| 1093 | 1093 | depends on HID |
| 1094 | − ---help--- | |
| 1094 | + help | |
| 1095 | 1095 | Support for Xin-Mo devices that are not fully compliant with the HID |
| 1096 | 1096 | standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here |
| 1097 | 1097 | if you have a Xin-Mo Dual Arcade controller. |
| @@ -1099,21 +1099,21 @@ config HID_XINMO · 1 unmodified line | ||
| 1099 | 1099 | config HID_ZEROPLUS |
| 1100 | 1100 | tristate "Zeroplus based game controller support" |
| 1101 | 1101 | depends on HID |
| 1102 | − ---help--- | |
| 1102 | + help | |
| 1103 | 1103 | Say Y here if you have a Zeroplus based game controller. |
| 1104 | 1104 | |
| 1105 | 1105 | config ZEROPLUS_FF |
| 1106 | 1106 | bool "Zeroplus based game controller force feedback support" |
| 1107 | 1107 | depends on HID_ZEROPLUS |
| 1108 | 1108 | select INPUT_FF_MEMLESS |
| 1109 | − ---help--- | |
| 1109 | + help | |
| 1110 | 1110 | Say Y here if you have a Zeroplus based game controller and want |
| 1111 | 1111 | to have force feedback support for it. |
| 1112 | 1112 | |
| 1113 | 1113 | config HID_ZYDACRON |
| 1114 | 1114 | tristate "Zydacron remote control support" |
| 1115 | 1115 | depends on HID |
| 1116 | − ---help--- | |
| 1116 | + help | |
| 1117 | 1117 | Support for Zydacron remote control. |
| 1118 | 1118 | |
| 1119 | 1119 | config HID_SENSOR_HUB |
| @@ -1121,7 +1121,7 @@ config HID_SENSOR_HUB · 1 unmodified line | ||
| 1121 | 1121 | depends on HID && HAS_IOMEM |
| 1122 | 1122 | select MFD_CORE |
| 1123 | 1123 | default n |
| 1124 | − ---help--- | |
| 1124 | + help | |
| 1125 | 1125 | Support for HID Sensor framework. This creates a MFD instance |
| 1126 | 1126 | for a sensor hub and identifies all the sensors connected to it. |
| 1127 | 1127 | Each sensor is registered as a MFD cell, so that sensor specific |
| @@ -1134,7 +1134,7 @@ config HID_SENSOR_CUSTOM_SENSOR · 6 unmodified lines | ||
| 1134 | 1134 | tristate "HID Sensors hub custom sensor support" |
| 1135 | 1135 | depends on HID_SENSOR_HUB |
| 1136 | 1136 | default n |
| 1137 | − ---help--- | |
| 1137 | + help | |
| 1138 | 1138 | HID Sensor hub specification allows definition of some custom and |
| 1139 | 1139 | generic sensors. Unlike other HID sensors, they can't be exported |
| 1140 | 1140 | via Linux IIO because of custom fields. This is up to the manufacturer |
| @@ -1148,7 +1148,7 @@ config HID_SENSOR_CUSTOM_SENSOR · 7 unmodified lines | ||
| 1148 | 1148 | config HID_ALPS |
| 1149 | 1149 | tristate "Alps HID device support" |
| 1150 | 1150 | depends on HID |
| 1151 | − ---help--- | |
| 1151 | + help | |
| 1152 | 1152 | Support for Alps I2C HID touchpads and StickPointer. |
| 1153 | 1153 | Say Y here if you have a Alps touchpads over i2c-hid or usbhid |
| 1154 | 1154 | and want support for its special functionalities. |
| @@ -1157,7 +1157,7 @@ config HID_MCP2221 · 2 unmodified lines | ||
| 1157 | 1157 | tristate "Microchip MCP2221 HID USB-to-I2C/SMbus host support" |
| 1158 | 1158 | depends on USB_HID && I2C |
| 1159 | 1159 | depends on GPIOLIB |
| 1160 | − ---help--- | |
| 1160 | + help | |
| 1161 | 1161 | Provides I2C and SMBUS host adapter functionality over USB-HID |
| 1162 | 1162 | through MCP2221 device. |
| 1163 | 1163 | |
| @@ -7,7 +7,7 @@ config I2C_HID · 6 unmodified lines | ||
| 7 | 7 | default n |
| 8 | 8 | depends on I2C && INPUT |
| 9 | 9 | select HID |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Say Y here if you use a keyboard, a touchpad, a touchscreen, or any |
| 12 | 12 | other HID based devices which is connected to your computer via I2C. |
| 13 | 13 | |
| @@ -7,7 +7,7 @@ config USB_HID · 6 unmodified lines | ||
| 7 | 7 | default y |
| 8 | 8 | depends on USB && INPUT |
| 9 | 9 | select HID |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Say Y here if you want to connect USB keyboards, |
| 12 | 12 | mice, joysticks, graphic tablets, or any other HID based devices |
| 13 | 13 | to your computer via USB, as well as Uninterruptible Power Supply |
| @@ -51,7 +51,7 @@ menu "USB HID Boot Protocol drivers" · 37 unmodified lines | ||
| 51 | 51 | config USB_KBD |
| 52 | 52 | tristate "USB HIDBP Keyboard (simple Boot) support" |
| 53 | 53 | depends on USB && INPUT |
| 54 | − ---help--- | |
| 54 | + help | |
| 55 | 55 | Say Y here only if you are absolutely sure that you don't want |
| 56 | 56 | to use the generic HID driver for your USB keyboard and prefer |
| 57 | 57 | to use the keyboard in its limited Boot Protocol mode instead. |
| @@ -67,7 +67,7 @@ config USB_KBD · 9 unmodified lines | ||
| 67 | 67 | config USB_MOUSE |
| 68 | 68 | tristate "USB HIDBP Mouse (simple Boot) support" |
| 69 | 69 | depends on USB && INPUT |
| 70 | − ---help--- | |
| 70 | + help | |
| 71 | 71 | Say Y here only if you are absolutely sure that you don't want |
| 72 | 72 | to use the generic HID driver for your USB mouse and prefer |
| 73 | 73 | to use the mouse in its limited Boot Protocol mode instead. |
| @@ -4,7 +4,7 @@ · 3 unmodified lines | ||
| 4 | 4 | # |
| 5 | 5 | menuconfig HSI |
| 6 | 6 | tristate "HSI support" |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | The "High speed synchronous Serial Interface" is |
| 9 | 9 | synchronous serial interface used mainly to connect |
| 10 | 10 | application engines and cellular modems. |
| @@ -35,7 +35,7 @@ config SSI_PROTOCOL · 34 unmodified lines | ||
| 35 | 35 | config HSI_CHAR |
| 36 | 36 | tristate "HSI/SSI character driver" |
| 37 | 37 | depends on HSI |
| 38 | − ---help--- | |
| 38 | + help | |
| 39 | 39 | If you say Y here, you will enable the HSI/SSI character driver. |
| 40 | 40 | This driver provides a simple character device interface for |
| 41 | 41 | serial communication with the cellular modem over HSI/SSI bus. |
| @@ -8,7 +8,7 @@ config OMAP_SSI · 7 unmodified lines | ||
| 8 | 8 | tristate "OMAP SSI hardware driver" |
| 9 | 9 | depends on HSI && OF && ARM && COMMON_CLK |
| 10 | 10 | depends on ARCH_OMAP3 || COMPILE_TEST |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | SSI is a legacy version of HSI. It is usually used to connect |
| 13 | 13 | an application engine with a cellular modem. |
| 14 | 14 | If you say Y here, you will enable the OMAP SSI hardware driver. |
| @@ -9,7 +9,7 @@ config I2C · 8 unmodified lines | ||
| 9 | 9 | tristate "I2C support" |
| 10 | 10 | select RT_MUTEXES |
| 11 | 11 | select IRQ_DOMAIN |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | I2C (pronounce: I-squared-C) is a slow serial bus protocol used in |
| 14 | 14 | many micro controller applications and developed by Philips. SMBus, |
| 15 | 15 | or System Management Bus is a subset of the I2C protocol. More |
| @@ -12,7 +12,7 @@ menuconfig IDE · 11 unmodified lines | ||
| 12 | 12 | depends on HAVE_IDE |
| 13 | 13 | depends on BLOCK |
| 14 | 14 | select BLK_SCSI_REQUEST |
| 15 | − ---help--- | |
| 15 | + help | |
| 16 | 16 | If you say Y here, your kernel will be able to manage ATA/(E)IDE and |
| 17 | 17 | ATAPI units. The most common cases are IDE hard drives and ATAPI |
| 18 | 18 | CD-ROM drives. |
| @@ -49,7 +49,7 @@ config IDE_LEGACY · 30 unmodified lines | ||
| 49 | 49 | config BLK_DEV_IDE_SATA |
| 50 | 50 | bool "Support for SATA (deprecated; conflicts with libata SATA driver)" |
| 51 | 51 | default n |
| 52 | − ---help--- | |
| 52 | + help | |
| 53 | 53 | There are two drivers for Serial ATA controllers. |
| 54 | 54 | |
| 55 | 55 | The main driver, "libata", uses the SCSI subsystem |
| @@ -121,7 +121,7 @@ config BLK_DEV_IDECD · 65 unmodified lines | ||
| 121 | 121 | depends on BLK_DEV |
| 122 | 122 | select IDE_ATAPI |
| 123 | 123 | select CDROM |
| 124 | − ---help--- | |
| 124 | + help | |
| 125 | 125 | If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is |
| 126 | 126 | a newer protocol used by IDE CD-ROM and TAPE drives, similar to the |
| 127 | 127 | SCSI protocol. Most new CD-ROM drives use ATAPI, including the |
| @@ -172,7 +172,7 @@ config BLK_DEV_IDETAPE · 44 unmodified lines | ||
| 172 | 172 | config BLK_DEV_IDEACPI |
| 173 | 173 | bool "IDE ACPI support" |
| 174 | 174 | depends on ACPI |
| 175 | − ---help--- | |
| 175 | + help | |
| 176 | 176 | Implement ACPI support for generic IDE devices. On modern |
| 177 | 177 | machines ACPI support is required to properly handle ACPI S3 states. |
| 178 | 178 | |
| @@ -232,7 +232,7 @@ config BLK_DEV_CMD640 · 53 unmodified lines | ||
| 232 | 232 | tristate "CMD640 chipset bugfix/support" |
| 233 | 233 | depends on X86 |
| 234 | 234 | select IDE_TIMINGS |
| 235 | − ---help--- | |
| 235 | + help | |
| 236 | 236 | The CMD-Technologies CMD640 IDE chip is used on many common 486 and |
| 237 | 237 | Pentium motherboards, usually in combination with a "Neptune" or |
| 238 | 238 | "SiS" chipset. Unfortunately, it has a number of rather nasty |
| @@ -325,7 +325,7 @@ config MAX5821 · 324 unmodified lines | ||
| 325 | 325 | config MCP4725 |
| 326 | 326 | tristate "MCP4725/6 DAC driver" |
| 327 | 327 | depends on I2C |
| 328 | − ---help--- | |
| 328 | + help | |
| 329 | 329 | Say Y here if you want to build a driver for the Microchip |
| 330 | 330 | MCP 4725/6 12-bit digital-to-analog converter (DAC) with I2C |
| 331 | 331 | interface. |
| @@ -8,7 +8,7 @@ menuconfig INFINIBAND · 7 unmodified lines | ||
| 8 | 8 | depends on !ALPHA |
| 9 | 9 | select IRQ_POLL |
| 10 | 10 | select DIMLIB |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | Core support for InfiniBand (IB). Make sure to also select |
| 13 | 13 | any protocols you wish to use as well as drivers for your |
| 14 | 14 | InfiniBand hardware. |
| @@ -18,7 +18,7 @@ if INFINIBAND · 3 unmodified lines | ||
| 18 | 18 | config INFINIBAND_USER_MAD |
| 19 | 19 | tristate "InfiniBand userspace MAD support" |
| 20 | 20 | depends on INFINIBAND |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | Userspace InfiniBand Management Datagram (MAD) support. This |
| 23 | 23 | is the kernel side of the userspace MAD support, which allows |
| 24 | 24 | userspace processes to send and receive MADs. You will also |
| @@ -28,7 +28,7 @@ config INFINIBAND_USER_MAD · 3 unmodified lines | ||
| 28 | 28 | config INFINIBAND_USER_ACCESS |
| 29 | 29 | tristate "InfiniBand userspace access (verbs and CM)" |
| 30 | 30 | depends on MMU |
| 31 | − ---help--- | |
| 31 | + help | |
| 32 | 32 | Userspace InfiniBand access support. This enables the |
| 33 | 33 | kernel side of userspace verbs and the userspace |
| 34 | 34 | communication manager (CM). This allows userspace processes |
| @@ -40,7 +40,7 @@ config INFINIBAND_USER_ACCESS · 5 unmodified lines | ||
| 40 | 40 | config INFINIBAND_EXP_LEGACY_VERBS_NEW_UAPI |
| 41 | 41 | bool "Allow experimental legacy verbs in new ioctl uAPI (EXPERIMENTAL)" |
| 42 | 42 | depends on INFINIBAND_USER_ACCESS |
| 43 | − ---help--- | |
| 43 | + help | |
| 44 | 44 | IOCTL based uAPI support for Infiniband is enabled by default for |
| 45 | 45 | new verbs only. This allows userspace to invoke the IOCTL based uAPI |
| 46 | 46 | for current legacy verbs too. |
| @@ -57,7 +57,7 @@ config INFINIBAND_ON_DEMAND_PAGING · 10 unmodified lines | ||
| 57 | 57 | select MMU_NOTIFIER |
| 58 | 58 | select INTERVAL_TREE |
| 59 | 59 | default y |
| 60 | − ---help--- | |
| 60 | + help | |
| 61 | 61 | On demand paging support for the InfiniBand subsystem. |
| 62 | 62 | Together with driver support this allows registration of |
| 63 | 63 | memory regions without pinning their pages, fetching the |
| @@ -67,7 +67,7 @@ config INFINIBAND_ADDR_TRANS · 3 unmodified lines | ||
| 67 | 67 | bool "RDMA/CM" |
| 68 | 68 | depends on INFINIBAND |
| 69 | 69 | default y |
| 70 | − ---help--- | |
| 70 | + help | |
| 71 | 71 | Support for RDMA communication manager (CM). |
| 72 | 72 | This allows for a generic connection abstraction over RDMA. |
| 73 | 73 | |
| @@ -75,7 +75,7 @@ config INFINIBAND_ADDR_TRANS_CONFIGFS · 1 unmodified line | ||
| 75 | 75 | bool |
| 76 | 76 | depends on INFINIBAND_ADDR_TRANS && CONFIGFS_FS && !(INFINIBAND=y && CONFIGFS_FS=m) |
| 77 | 77 | default y |
| 78 | − ---help--- | |
| 78 | + help | |
| 79 | 79 | ConfigFS support for RDMA communication manager (CM). |
| 80 | 80 | This allows the user to config the default GID type that the CM |
| 81 | 81 | uses for each device, when initiaing new connections. |
| @@ -5,7 +5,7 @@ config INFINIBAND_BNXT_RE · 4 unmodified lines | ||
| 5 | 5 | depends on ETHERNET && NETDEVICES && PCI && INET && DCB |
| 6 | 6 | select NET_VENDOR_BROADCOM |
| 7 | 7 | select BNXT |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | This driver supports Broadcom NetXtreme-E 10/25/40/50 gigabit |
| 10 | 10 | RoCE HCAs. To compile this driver as a module, choose M here: |
| 11 | 11 | the module will be called bnxt_re. |
| @@ -5,7 +5,7 @@ config INFINIBAND_CXGB4 · 4 unmodified lines | ||
| 5 | 5 | depends on INFINIBAND_ADDR_TRANS |
| 6 | 6 | select CHELSIO_LIB |
| 7 | 7 | select GENERIC_ALLOCATOR |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | This is an iWARP/RDMA driver for the Chelsio T4 and T5 |
| 10 | 10 | 1GbE, 10GbE adapters and T5 40GbE adapter. |
| 11 | 11 | |
| @@ -5,19 +5,19 @@ config INFINIBAND_HFI1 · 4 unmodified lines | ||
| 5 | 5 | select MMU_NOTIFIER |
| 6 | 6 | select CRC32 |
| 7 | 7 | select I2C_ALGOBIT |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | This is a low-level driver for Intel OPA Gen1 adapter. |
| 10 | 10 | config HFI1_DEBUG_SDMA_ORDER |
| 11 | 11 | bool "HFI1 SDMA Order debug" |
| 12 | 12 | depends on INFINIBAND_HFI1 |
| 13 | 13 | default n |
| 14 | − ---help--- | |
| 14 | + help | |
| 15 | 15 | This is a debug flag to test for out of order |
| 16 | 16 | sdma completions for unit testing |
| 17 | 17 | config SDMA_VERBOSITY |
| 18 | 18 | bool "Config SDMA Verbosity" |
| 19 | 19 | depends on INFINIBAND_HFI1 |
| 20 | 20 | default n |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | This is a configuration flag to enable verbose |
| 23 | 23 | SDMA debug |
| @@ -4,7 +4,7 @@ config INFINIBAND_HNS · 3 unmodified lines | ||
| 4 | 4 | depends on NET_VENDOR_HISILICON |
| 5 | 5 | depends on ARM64 || (COMPILE_TEST && 64BIT) |
| 6 | 6 | depends on (HNS_DSAF && HNS_ENET) || HNS3 |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | This is a RoCE/RDMA driver for the Hisilicon RoCE engine. The engine |
| 9 | 9 | is used in Hisilicon Hip06 and more further ICT SoC based on |
| 10 | 10 | platform device. |
| @@ -15,7 +15,7 @@ config INFINIBAND_HNS_HIP06 · 4 unmodified lines | ||
| 15 | 15 | bool "Hisilicon Hip06 Family RoCE support" |
| 16 | 16 | depends on INFINIBAND_HNS && HNS && HNS_DSAF && HNS_ENET |
| 17 | 17 | depends on INFINIBAND_HNS=m || (HNS_DSAF=y && HNS_ENET=y) |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | RoCE driver support for Hisilicon RoCE engine in Hisilicon Hip06 and |
| 20 | 20 | Hip07 SoC. These RoCE engines are platform devices. |
| 21 | 21 | |
| @@ -26,7 +26,7 @@ config INFINIBAND_HNS_HIP08 · 4 unmodified lines | ||
| 26 | 26 | bool "Hisilicon Hip08 Family RoCE support" |
| 27 | 27 | depends on INFINIBAND_HNS && PCI && HNS3 |
| 28 | 28 | depends on INFINIBAND_HNS=m || HNS3=y |
| 29 | − ---help--- | |
| 29 | + help | |
| 30 | 30 | RoCE driver support for Hisilicon RoCE engine in Hisilicon Hip08 SoC. |
| 31 | 31 | The RoCE engine is a PCI device. |
| 32 | 32 | |
| @@ -5,5 +5,5 @@ config INFINIBAND_I40IW · 4 unmodified lines | ||
| 5 | 5 | depends on IPV6 || !IPV6 |
| 6 | 6 | depends on PCI |
| 7 | 7 | select GENERIC_ALLOCATOR |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | Intel(R) Ethernet X722 iWARP Driver |
| @@ -4,7 +4,7 @@ config MLX4_INFINIBAND · 3 unmodified lines | ||
| 4 | 4 | depends on NETDEVICES && ETHERNET && PCI && INET |
| 5 | 5 | select NET_VENDOR_MELLANOX |
| 6 | 6 | select MLX4_CORE |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | This driver provides low-level InfiniBand support for |
| 9 | 9 | Mellanox ConnectX PCI Express host channel adapters (HCAs). |
| 10 | 10 | This is required to use InfiniBand protocols such as |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config MLX5_INFINIBAND |
| 3 | 3 | tristate "Mellanox 5th generation network adapters (ConnectX series) support" |
| 4 | 4 | depends on NETDEVICES && ETHERNET && PCI && MLX5_CORE |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This driver provides low-level InfiniBand support for |
| 7 | 7 | Mellanox Connect-IB PCI Express host channel adapters (HCAs). |
| 8 | 8 | This is required to use InfiniBand protocols such as |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config INFINIBAND_MTHCA |
| 3 | 3 | tristate "Mellanox HCA support" |
| 4 | 4 | depends on PCI |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This is a low-level driver for Mellanox InfiniHost host |
| 7 | 7 | channel adapters (HCAs), including the MT23108 PCI-X HCA |
| 8 | 8 | ("Tavor") and the MT25208 PCI Express HCA ("Arbel"). |
| @@ -11,7 +11,7 @@ config INFINIBAND_MTHCA_DEBUG · 2 unmodified lines | ||
| 11 | 11 | bool "Verbose debugging output" if EXPERT |
| 12 | 12 | depends on INFINIBAND_MTHCA |
| 13 | 13 | default y |
| 14 | − ---help--- | |
| 14 | + help | |
| 15 | 15 | This option causes debugging code to be compiled into the |
| 16 | 16 | mthca driver. The output can be turned on via the |
| 17 | 17 | debug_level module parameter (which can also be set after |
| @@ -4,6 +4,6 @@ config INFINIBAND_OCRDMA · 3 unmodified lines | ||
| 4 | 4 | depends on ETHERNET && NETDEVICES && PCI && INET && (IPV6 || IPV6=n) |
| 5 | 5 | select NET_VENDOR_EMULEX |
| 6 | 6 | select BE2NET |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | This driver provides low-level InfiniBand over Ethernet |
| 9 | 9 | support for Emulex One Connect host channel adapters (HCAs). |
| @@ -6,6 +6,6 @@ config INFINIBAND_QEDR · 5 unmodified lines | ||
| 6 | 6 | select QED_LL2 |
| 7 | 7 | select QED_OOO |
| 8 | 8 | select QED_RDMA |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This driver provides low-level InfiniBand over Ethernet |
| 11 | 11 | support for QLogic QED host channel adapters (HCAs). |
| @@ -3,7 +3,7 @@ config INFINIBAND_QIB · 2 unmodified lines | ||
| 3 | 3 | tristate "Intel PCIe HCA support" |
| 4 | 4 | depends on 64BIT && INFINIBAND_RDMAVT |
| 5 | 5 | depends on PCI |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | This is a low-level driver for Intel PCIe QLE InfiniBand host |
| 8 | 8 | channel adapters. This driver does not support the Intel |
| 9 | 9 | HyperTransport card (model QHT7140). |
| @@ -12,6 +12,6 @@ config INFINIBAND_QIB_DCA · 2 unmodified lines | ||
| 12 | 12 | bool "QIB DCA support" |
| 13 | 13 | depends on INFINIBAND_QIB && DCA && SMP && !(INFINIBAND_QIB=y && DCA=m) |
| 14 | 14 | default y |
| 15 | − ---help--- | |
| 15 | + help | |
| 16 | 16 | Setting this enables DCA support on some Intel chip sets |
| 17 | 17 | with the iba7322 HCA. |
| @@ -6,6 +6,6 @@ config INFINIBAND_USNIC · 5 unmodified lines | ||
| 6 | 6 | select ENIC |
| 7 | 7 | select NET_VENDOR_CISCO |
| 8 | 8 | select PCI_IOV |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This is a low-level driver for Cisco's Virtual Interface |
| 11 | 11 | Cards (VICs), including the VIC 1240 and 1280 cards. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config INFINIBAND_VMWARE_PVRDMA |
| 3 | 3 | tristate "VMware Paravirtualized RDMA Driver" |
| 4 | 4 | depends on NETDEVICES && ETHERNET && PCI && INET && VMXNET3 |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This driver provides low-level support for VMware Paravirtual |
| 7 | 7 | RDMA adapter. It interacts with the VMXNet3 driver to provide |
| 8 | 8 | Ethernet capabilities. |
| @@ -4,5 +4,5 @@ config INFINIBAND_RDMAVT · 3 unmodified lines | ||
| 4 | 4 | depends on X86_64 && ARCH_DMA_ADDR_T_64BIT |
| 5 | 5 | depends on PCI |
| 6 | 6 | select DMA_VIRT_OPS |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | This is a common software verbs provider for RDMA networks. |
| @@ -6,7 +6,7 @@ config RDMA_RXE · 5 unmodified lines | ||
| 6 | 6 | select NET_UDP_TUNNEL |
| 7 | 7 | select CRYPTO_CRC32 |
| 8 | 8 | select DMA_VIRT_OPS |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This driver implements the InfiniBand RDMA transport over |
| 11 | 11 | the Linux network stack. It enables a system with a |
| 12 | 12 | standard Ethernet adapter to interoperate with a RoCE |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config INFINIBAND_IPOIB |
| 3 | 3 | tristate "IP-over-InfiniBand" |
| 4 | 4 | depends on NETDEVICES && INET && (IPV6 || IPV6=n) |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | Support for the IP-over-InfiniBand protocol (IPoIB). This |
| 7 | 7 | transports IP packets over InfiniBand so you can use your IB |
| 8 | 8 | device as a fancy NIC. |
| @@ -13,7 +13,7 @@ config INFINIBAND_IPOIB_CM · 4 unmodified lines | ||
| 13 | 13 | bool "IP-over-InfiniBand Connected Mode support" |
| 14 | 14 | depends on INFINIBAND_IPOIB |
| 15 | 15 | default n |
| 16 | − ---help--- | |
| 16 | + help | |
| 17 | 17 | This option enables support for IPoIB connected mode. After |
| 18 | 18 | enabling this option, you need to switch to connected mode |
| 19 | 19 | through /sys/class/net/ibXXX/mode to actually create |
| @@ -28,7 +28,7 @@ config INFINIBAND_IPOIB_DEBUG · 8 unmodified lines | ||
| 28 | 28 | bool "IP-over-InfiniBand debugging" if EXPERT |
| 29 | 29 | depends on INFINIBAND_IPOIB |
| 30 | 30 | default y |
| 31 | − ---help--- | |
| 31 | + help | |
| 32 | 32 | This option causes debugging code to be compiled into the |
| 33 | 33 | IPoIB driver. The output can be turned on via the |
| 34 | 34 | debug_level and mcast_debug_level module parameters (which |
| @@ -42,7 +42,7 @@ config INFINIBAND_IPOIB_DEBUG · 7 unmodified lines | ||
| 42 | 42 | config INFINIBAND_IPOIB_DEBUG_DATA |
| 43 | 43 | bool "IP-over-InfiniBand data path debugging" |
| 44 | 44 | depends on INFINIBAND_IPOIB_DEBUG |
| 45 | − ---help--- | |
| 45 | + help | |
| 46 | 46 | This option compiles debugging code into the data path |
| 47 | 47 | of the IPoIB driver. The output can be turned on via the |
| 48 | 48 | data_debug_level module parameter; however, even with output |
| @@ -3,7 +3,7 @@ config INFINIBAND_ISER · 2 unmodified lines | ||
| 3 | 3 | tristate "iSCSI Extensions for RDMA (iSER)" |
| 4 | 4 | depends on SCSI && INET && INFINIBAND_ADDR_TRANS |
| 5 | 5 | select SCSI_ISCSI_ATTRS |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | Support for the iSCSI Extensions for RDMA (iSER) Protocol |
| 8 | 8 | over InfiniBand. This allows you to access storage devices |
| 9 | 9 | that speak iSCSI over iSER over InfiniBand. |
| @@ -2,5 +2,5 @@ · 1 unmodified line | ||
| 2 | 2 | config INFINIBAND_ISERT |
| 3 | 3 | tristate "iSCSI Extensions for RDMA (iSER) target support" |
| 4 | 4 | depends on INET && INFINIBAND_ADDR_TRANS && TARGET_CORE && ISCSI_TARGET |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | Support for iSCSI Extensions for RDMA (iSER) Target on Infiniband fabrics. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config INFINIBAND_OPA_VNIC |
| 3 | 3 | tristate "Intel OPA VNIC support" |
| 4 | 4 | depends on X86_64 && INFINIBAND |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This is Omni-Path (OPA) Virtual Network Interface Controller (VNIC) |
| 7 | 7 | driver for Ethernet over Omni-Path feature. It implements the HW |
| 8 | 8 | independent VNIC functionality. It interfaces with Linux stack for |
| @@ -3,7 +3,7 @@ config INFINIBAND_SRP · 2 unmodified lines | ||
| 3 | 3 | tristate "InfiniBand SCSI RDMA Protocol" |
| 4 | 4 | depends on SCSI && INFINIBAND_ADDR_TRANS |
| 5 | 5 | select SCSI_SRP_ATTRS |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | Support for the SCSI RDMA Protocol over InfiniBand. This |
| 8 | 8 | allows you to access storage devices that speak SRP over |
| 9 | 9 | InfiniBand. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config INFINIBAND_SRPT |
| 3 | 3 | tristate "InfiniBand SCSI RDMA Protocol target support" |
| 4 | 4 | depends on INFINIBAND && INFINIBAND_ADDR_TRANS && TARGET_CORE |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | |
| 7 | 7 | Support for the SCSI RDMA Protocol (SRP) Target driver. The |
| 8 | 8 | SRP protocol is a protocol that allows an initiator to access |
| @@ -4,7 +4,7 @@ · 3 unmodified lines | ||
| 4 | 4 | # |
| 5 | 5 | config GAMEPORT |
| 6 | 6 | tristate "Gameport support" |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | Gameport support is for the standard 15-pin PC gameport. If you |
| 9 | 9 | have a joystick, gamepad, gameport card, a soundcard with a gameport |
| 10 | 10 | or anything else that uses the gameport, say Y or M here and also to |
| @@ -18,7 +18,7 @@ if INPUT_JOYSTICK · 17 unmodified lines | ||
| 18 | 18 | config JOYSTICK_ANALOG |
| 19 | 19 | tristate "Classic PC analog joysticks and gamepads" |
| 20 | 20 | select GAMEPORT |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | Say Y here if you have a joystick that connects to the PC |
| 23 | 23 | gameport. In addition to the usual PC analog joystick, this driver |
| 24 | 24 | supports many extensions, including joysticks with throttle control, |
| @@ -225,7 +225,7 @@ config JOYSTICK_GAMECON · 200 unmodified lines | ||
| 225 | 225 | tristate "Multisystem, NES, SNES, N64, PSX joysticks and gamepads" |
| 226 | 226 | depends on PARPORT |
| 227 | 227 | select INPUT_FF_MEMLESS |
| 228 | − ---help--- | |
| 228 | + help | |
| 229 | 229 | Say Y here if you have a Nintendo Entertainment System gamepad, |
| 230 | 230 | Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad, |
| 231 | 231 | Sony PlayStation gamepad or a Multisystem -- Atari, Amiga, |
| @@ -298,13 +298,13 @@ config JOYSTICK_XPAD_FF · 66 unmodified lines | ||
| 298 | 298 | bool "X-Box gamepad rumble support" |
| 299 | 299 | depends on JOYSTICK_XPAD && INPUT |
| 300 | 300 | select INPUT_FF_MEMLESS |
| 301 | − ---help--- | |
| 301 | + help | |
| 302 | 302 | Say Y here if you want to take advantage of xbox 360 rumble features. |
| 303 | 303 | |
| 304 | 304 | config JOYSTICK_XPAD_LEDS |
| 305 | 305 | bool "LED Support for Xbox360 controller 'BigX' LED" |
| 306 | 306 | depends on JOYSTICK_XPAD && (LEDS_CLASS=y || LEDS_CLASS=JOYSTICK_XPAD) |
| 307 | − ---help--- | |
| 307 | + help | |
| 308 | 308 | This option enables support for the LED which surrounds the Big X on |
| 309 | 309 | XBox 360 controller. |
| 310 | 310 | |
| @@ -223,7 +223,7 @@ config SERIO_AMS_DELTA · 222 unmodified lines | ||
| 223 | 223 | tristate "Amstrad Delta (E3) mailboard support" |
| 224 | 224 | depends on MACH_AMS_DELTA |
| 225 | 225 | default y |
| 226 | − ---help--- | |
| 226 | + help | |
| 227 | 227 | Say Y here if you have an E3 and want to use its mailboard, |
| 228 | 228 | or any standard AT keyboard connected to the mailboard port. |
| 229 | 229 | |
| @@ -15,7 +15,7 @@ menuconfig IOMMU_SUPPORT · 14 unmodified lines | ||
| 15 | 15 | bool "IOMMU Hardware Support" |
| 16 | 16 | depends on MMU |
| 17 | 17 | default y |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | Say Y here if you want to compile device drivers for IO Memory |
| 20 | 20 | Management Units into the kernel. These devices usually allow to |
| 21 | 21 | remap DMA requests and/or remap interrupts from other devices on the |
| @@ -144,7 +144,7 @@ config AMD_IOMMU · 122 unmodified lines | ||
| 144 | 144 | select IOMMU_IOVA |
| 145 | 145 | select IOMMU_DMA |
| 146 | 146 | depends on X86_64 && PCI && ACPI |
| 147 | − ---help--- | |
| 147 | + help | |
| 148 | 148 | With this option you can enable support for AMD IOMMU hardware in |
| 149 | 149 | your system. An IOMMU is a hardware component which provides |
| 150 | 150 | remapping of DMA memory accesses from devices. With an AMD IOMMU you |
| @@ -159,7 +159,7 @@ config AMD_IOMMU_V2 · 8 unmodified lines | ||
| 159 | 159 | tristate "AMD IOMMU Version 2 driver" |
| 160 | 160 | depends on AMD_IOMMU |
| 161 | 161 | select MMU_NOTIFIER |
| 162 | − ---help--- | |
| 162 | + help | |
| 163 | 163 | This option enables support for the AMD IOMMUv2 features of the IOMMU |
| 164 | 164 | hardware. Select this option if you want to use devices that support |
| 165 | 165 | the PCI PRI and PASID interface. |
| @@ -167,7 +167,7 @@ config AMD_IOMMU_V2 · 1 unmodified line | ||
| 167 | 167 | config AMD_IOMMU_DEBUGFS |
| 168 | 168 | bool "Enable AMD IOMMU internals in DebugFS" |
| 169 | 169 | depends on AMD_IOMMU && IOMMU_DEBUGFS |
| 170 | − ---help--- | |
| 170 | + help | |
| 171 | 171 | !!!WARNING!!! !!!WARNING!!! !!!WARNING!!! !!!WARNING!!! |
| 172 | 172 | |
| 173 | 173 | DO NOT ENABLE THIS OPTION UNLESS YOU REALLY, -REALLY- KNOW WHAT YOU ARE DOING!!! |
| @@ -233,7 +233,7 @@ config INTEL_IOMMU_DEFAULT_ON · 59 unmodified lines | ||
| 233 | 233 | config INTEL_IOMMU_BROKEN_GFX_WA |
| 234 | 234 | bool "Workaround broken graphics drivers (going away soon)" |
| 235 | 235 | depends on INTEL_IOMMU && BROKEN && X86 |
| 236 | − ---help--- | |
| 236 | + help | |
| 237 | 237 | Current Graphics drivers tend to use physical address |
| 238 | 238 | for DMA and avoid using DMA APIs. Setting this config |
| 239 | 239 | option permits the IOMMU driver to set a unity map for |
| @@ -244,7 +244,7 @@ config INTEL_IOMMU_BROKEN_GFX_WA · 4 unmodified lines | ||
| 244 | 244 | config INTEL_IOMMU_FLOPPY_WA |
| 245 | 245 | def_bool y |
| 246 | 246 | depends on INTEL_IOMMU && X86 |
| 247 | − ---help--- | |
| 247 | + help | |
| 248 | 248 | Floppy disk drivers are known to bypass DMA API calls |
| 249 | 249 | thereby failing to work when IOMMU is enabled. This |
| 250 | 250 | workaround will setup a 1:1 mapping for the first |
| @@ -266,7 +266,7 @@ config IRQ_REMAP · 15 unmodified lines | ||
| 266 | 266 | bool "Support for Interrupt Remapping" |
| 267 | 267 | depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI |
| 268 | 268 | select DMAR_TABLE |
| 269 | − ---help--- | |
| 269 | + help | |
| 270 | 270 | Supports Interrupt remapping for IO-APIC and MSI devices. |
| 271 | 271 | To use x2apic mode in the CPU's which support x2APIC enhancements or |
| 272 | 272 | to support platforms with CPU's having > 8 bit APIC ID, say Y. |
| @@ -277,14 +277,14 @@ config OMAP_IOMMU · 4 unmodified lines | ||
| 277 | 277 | depends on ARM && MMU || (COMPILE_TEST && (ARM || ARM64 || IA64 || SPARC)) |
| 278 | 278 | depends on ARCH_OMAP2PLUS || COMPILE_TEST |
| 279 | 279 | select IOMMU_API |
| 280 | − ---help--- | |
| 280 | + help | |
| 281 | 281 | The OMAP3 media platform drivers depend on iommu support, |
| 282 | 282 | if you need them say Y here. |
| 283 | 283 | |
| 284 | 284 | config OMAP_IOMMU_DEBUG |
| 285 | 285 | bool "Export OMAP IOMMU internals in DebugFS" |
| 286 | 286 | depends on OMAP_IOMMU && DEBUG_FS |
| 287 | − ---help--- | |
| 287 | + help | |
| 288 | 288 | Select this to see extensive information about |
| 289 | 289 | the internal state of OMAP IOMMU in debugfs. |
| 290 | 290 | |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | menuconfig IPACK_BUS |
| 7 | 7 | tristate "IndustryPack bus support" |
| 8 | 8 | depends on HAS_IOMEM |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This option provides support for the IndustryPack framework. There |
| 11 | 11 | are IndustryPack carrier boards, which interface another bus (such as |
| 12 | 12 | PCI) to an IndustryPack bus, and IndustryPack modules, that are |
| @@ -7,7 +7,7 @@ menuconfig ISDN · 6 unmodified lines | ||
| 7 | 7 | bool "ISDN support" |
| 8 | 8 | depends on NET && NETDEVICES |
| 9 | 9 | depends on !S390 && !UML |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | ISDN ("Integrated Services Digital Network", called RNIS in France) |
| 12 | 12 | is a fully digital telephone service that can be used for voice and |
| 13 | 13 | data connections. If your computer is equipped with an ISDN |
| @@ -4,7 +4,7 @@ menuconfig MACINTOSH_DRIVERS · 3 unmodified lines | ||
| 4 | 4 | bool "Macintosh device drivers" |
| 5 | 5 | depends on PPC || MAC || X86 |
| 6 | 6 | default y if (PPC_PMAC || MAC) |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | Say Y here to get to see options for devices used with Macintosh |
| 9 | 9 | computers. This option alone does not add any kernel code. |
| 10 | 10 | |
| @@ -15,7 +15,7 @@ if MD · 14 unmodified lines | ||
| 15 | 15 | |
| 16 | 16 | config BLK_DEV_MD |
| 17 | 17 | tristate "RAID support" |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | This driver lets you combine several hard disk partitions into one |
| 20 | 20 | logical block device. This can be used to simply append one |
| 21 | 21 | partition to another one or to combine several redundant hard disks |
| @@ -36,7 +36,7 @@ config MD_AUTODETECT · 14 unmodified lines | ||
| 36 | 36 | bool "Autodetect RAID arrays during kernel boot" |
| 37 | 37 | depends on BLK_DEV_MD=y |
| 38 | 38 | default y |
| 39 | − ---help--- | |
| 39 | + help | |
| 40 | 40 | If you say Y here, then the kernel will try to autodetect raid |
| 41 | 41 | arrays as part of its boot process. |
| 42 | 42 | |
| @@ -49,7 +49,7 @@ config MD_AUTODETECT · 6 unmodified lines | ||
| 49 | 49 | config MD_LINEAR |
| 50 | 50 | tristate "Linear (append) mode" |
| 51 | 51 | depends on BLK_DEV_MD |
| 52 | − ---help--- | |
| 52 | + help | |
| 53 | 53 | If you say Y here, then your multiple devices driver will be able to |
| 54 | 54 | use the so-called linear mode, i.e. it will combine the hard disk |
| 55 | 55 | partitions by simply appending one to the other. |
| @@ -62,7 +62,7 @@ config MD_LINEAR · 6 unmodified lines | ||
| 62 | 62 | config MD_RAID0 |
| 63 | 63 | tristate "RAID-0 (striping) mode" |
| 64 | 64 | depends on BLK_DEV_MD |
| 65 | − ---help--- | |
| 65 | + help | |
| 66 | 66 | If you say Y here, then your multiple devices driver will be able to |
| 67 | 67 | use the so-called raid0 mode, i.e. it will combine the hard disk |
| 68 | 68 | partitions into one logical device in such a fashion as to fill them |
| @@ -82,7 +82,7 @@ config MD_RAID0 · 13 unmodified lines | ||
| 82 | 82 | config MD_RAID1 |
| 83 | 83 | tristate "RAID-1 (mirroring) mode" |
| 84 | 84 | depends on BLK_DEV_MD |
| 85 | − ---help--- | |
| 85 | + help | |
| 86 | 86 | A RAID-1 set consists of several disk drives which are exact copies |
| 87 | 87 | of each other. In the event of a mirror failure, the RAID driver |
| 88 | 88 | will continue to use the operational mirrors in the set, providing |
| @@ -104,7 +104,7 @@ config MD_RAID1 · 15 unmodified lines | ||
| 104 | 104 | config MD_RAID10 |
| 105 | 105 | tristate "RAID-10 (mirrored striping) mode" |
| 106 | 106 | depends on BLK_DEV_MD |
| 107 | − ---help--- | |
| 107 | + help | |
| 108 | 108 | RAID-10 provides a combination of striping (RAID-0) and |
| 109 | 109 | mirroring (RAID-1) with easier configuration and more flexible |
| 110 | 110 | layout. |
| @@ -129,7 +129,7 @@ config MD_RAID456 · 18 unmodified lines | ||
| 129 | 129 | select ASYNC_XOR |
| 130 | 130 | select ASYNC_PQ |
| 131 | 131 | select ASYNC_RAID6_RECOV |
| 132 | − ---help--- | |
| 132 | + help | |
| 133 | 133 | A RAID-5 set of N drives with a capacity of C MB per drive provides |
| 134 | 134 | the capacity of C * (N - 1) MB, and protects against a failure |
| 135 | 135 | of a single drive. For a given sector (row) number, (N - 1) drives |
| @@ -183,7 +183,7 @@ config MD_CLUSTER · 47 unmodified lines | ||
| 183 | 183 | depends on BLK_DEV_MD |
| 184 | 184 | depends on DLM |
| 185 | 185 | default n |
| 186 | − ---help--- | |
| 186 | + help | |
| 187 | 187 | Clustering support for MD devices. This enables locking and |
| 188 | 188 | synchronization across multiple systems on the cluster, so all |
| 189 | 189 | nodes in the cluster can access the MD devices simultaneously. |
| @@ -203,7 +203,7 @@ config BLK_DEV_DM · 13 unmodified lines | ||
| 203 | 203 | tristate "Device mapper support" |
| 204 | 204 | select BLK_DEV_DM_BUILTIN |
| 205 | 205 | depends on DAX || DAX=n |
| 206 | − ---help--- | |
| 206 | + help | |
| 207 | 207 | Device-mapper is a low level volume manager. It works by allowing |
| 208 | 208 | people to specify mappings for ranges of logical sectors. Various |
| 209 | 209 | mapping types are available, in addition people may write their own |
| @@ -219,7 +219,7 @@ config BLK_DEV_DM · 9 unmodified lines | ||
| 219 | 219 | config DM_DEBUG |
| 220 | 220 | bool "Device mapper debugging support" |
| 221 | 221 | depends on BLK_DEV_DM |
| 222 | − ---help--- | |
| 222 | + help | |
| 223 | 223 | Enable this for messages that may help debug device-mapper problems. |
| 224 | 224 | |
| 225 | 225 | If unsure, say N. |
| @@ -227,7 +227,7 @@ config DM_DEBUG · 1 unmodified line | ||
| 227 | 227 | config DM_BUFIO |
| 228 | 228 | tristate |
| 229 | 229 | depends on BLK_DEV_DM |
| 230 | − ---help--- | |
| 230 | + help | |
| 231 | 231 | This interface allows you to do buffered I/O on a device and acts |
| 232 | 232 | as a cache, holding recently-read blocks in memory and performing |
| 233 | 233 | delayed writes. |
| @@ -235,7 +235,7 @@ config DM_BUFIO · 1 unmodified line | ||
| 235 | 235 | config DM_DEBUG_BLOCK_MANAGER_LOCKING |
| 236 | 236 | bool "Block manager locking" |
| 237 | 237 | depends on DM_BUFIO |
| 238 | − ---help--- | |
| 238 | + help | |
| 239 | 239 | Block manager locking can catch various metadata corruption issues. |
| 240 | 240 | |
| 241 | 241 | If unsure, say N. |
| @@ -244,7 +244,7 @@ config DM_DEBUG_BLOCK_STACK_TRACING · 2 unmodified lines | ||
| 244 | 244 | bool "Keep stack trace of persistent data block lock holders" |
| 245 | 245 | depends on STACKTRACE_SUPPORT && DM_DEBUG_BLOCK_MANAGER_LOCKING |
| 246 | 246 | select STACKTRACE |
| 247 | − ---help--- | |
| 247 | + help | |
| 248 | 248 | Enable this for messages that may help debug problems with the |
| 249 | 249 | block manager locking used by thin provisioning and caching. |
| 250 | 250 | |
| @@ -253,7 +253,7 @@ config DM_DEBUG_BLOCK_STACK_TRACING · 2 unmodified lines | ||
| 253 | 253 | config DM_BIO_PRISON |
| 254 | 254 | tristate |
| 255 | 255 | depends on BLK_DEV_DM |
| 256 | − ---help--- | |
| 256 | + help | |
| 257 | 257 | Some bio locking schemes used by other device-mapper targets |
| 258 | 258 | including thin provisioning. |
| 259 | 259 | |
| @@ -262,7 +262,7 @@ source "drivers/md/persistent-data/Kconfig" · 2 unmodified lines | ||
| 262 | 262 | config DM_UNSTRIPED |
| 263 | 263 | tristate "Unstriped target" |
| 264 | 264 | depends on BLK_DEV_DM |
| 265 | − ---help--- | |
| 265 | + help | |
| 266 | 266 | Unstripes I/O so it is issued solely on a single drive in a HW |
| 267 | 267 | RAID0 or dm-striped target. |
| 268 | 268 | |
| @@ -273,7 +273,7 @@ config DM_CRYPT · 4 unmodified lines | ||
| 273 | 273 | select CRYPTO |
| 274 | 274 | select CRYPTO_CBC |
| 275 | 275 | select CRYPTO_ESSIV |
| 276 | − ---help--- | |
| 276 | + help | |
| 277 | 277 | This device-mapper target allows you to create a device that |
| 278 | 278 | transparently encrypts the data on it. You'll need to activate |
| 279 | 279 | the ciphers you're going to use in the cryptoapi configuration. |
| @@ -290,7 +290,7 @@ config DM_SNAPSHOT · 10 unmodified lines | ||
| 290 | 290 | tristate "Snapshot target" |
| 291 | 291 | depends on BLK_DEV_DM |
| 292 | 292 | select DM_BUFIO |
| 293 | − ---help--- | |
| 293 | + help | |
| 294 | 294 | Allow volume managers to take writable snapshots of a device. |
| 295 | 295 | |
| 296 | 296 | config DM_THIN_PROVISIONING |
| @@ -298,7 +298,7 @@ config DM_THIN_PROVISIONING · 1 unmodified line | ||
| 298 | 298 | depends on BLK_DEV_DM |
| 299 | 299 | select DM_PERSISTENT_DATA |
| 300 | 300 | select DM_BIO_PRISON |
| 301 | − ---help--- | |
| 301 | + help | |
| 302 | 302 | Provides thin provisioning and snapshots that share a data store. |
| 303 | 303 | |
| 304 | 304 | config DM_CACHE |
| @@ -307,7 +307,7 @@ config DM_CACHE · 2 unmodified lines | ||
| 307 | 307 | default n |
| 308 | 308 | select DM_PERSISTENT_DATA |
| 309 | 309 | select DM_BIO_PRISON |
| 310 | − ---help--- | |
| 310 | + help | |
| 311 | 311 | dm-cache attempts to improve performance of a block device by |
| 312 | 312 | moving frequently used data to a smaller, higher performance |
| 313 | 313 | device. Different 'policy' plugins can be used to change the |
| @@ -318,7 +318,7 @@ config DM_CACHE_SMQ · 4 unmodified lines | ||
| 318 | 318 | tristate "Stochastic MQ Cache Policy (EXPERIMENTAL)" |
| 319 | 319 | depends on DM_CACHE |
| 320 | 320 | default y |
| 321 | − ---help--- | |
| 321 | + help | |
| 322 | 322 | A cache policy that uses a multiqueue ordered by recent hits |
| 323 | 323 | to select which blocks should be promoted and demoted. |
| 324 | 324 | This is meant to be a general purpose policy. It prioritises |
| @@ -329,7 +329,7 @@ config DM_CACHE_SMQ · 4 unmodified lines | ||
| 329 | 329 | config DM_WRITECACHE |
| 330 | 330 | tristate "Writecache target" |
| 331 | 331 | depends on BLK_DEV_DM |
| 332 | − ---help--- | |
| 332 | + help | |
| 333 | 333 | The writecache target caches writes on persistent memory or SSD. |
| 334 | 334 | It is intended for databases or other programs that need extremely |
| 335 | 335 | low commit latency. |
| @@ -351,7 +351,7 @@ config DM_ERA · 15 unmodified lines | ||
| 351 | 351 | default n |
| 352 | 352 | select DM_PERSISTENT_DATA |
| 353 | 353 | select DM_BIO_PRISON |
| 354 | − ---help--- | |
| 354 | + help | |
| 355 | 355 | dm-era tracks which parts of a block device are written to |
| 356 | 356 | over time. Useful for maintaining cache coherency when using |
| 357 | 357 | vendor snapshots. |
| @@ -361,7 +361,7 @@ config DM_CLONE · 3 unmodified lines | ||
| 361 | 361 | depends on BLK_DEV_DM |
| 362 | 362 | default n |
| 363 | 363 | select DM_PERSISTENT_DATA |
| 364 | − ---help--- | |
| 364 | + help | |
| 365 | 365 | dm-clone produces a one-to-one copy of an existing, read-only source |
| 366 | 366 | device into a writable destination device. The cloned device is |
| 367 | 367 | visible/mountable immediately and the copy of the source device to the |
| @@ -373,7 +373,7 @@ config DM_CLONE · 5 unmodified lines | ||
| 373 | 373 | config DM_MIRROR |
| 374 | 374 | tristate "Mirror target" |
| 375 | 375 | depends on BLK_DEV_DM |
| 376 | − ---help--- | |
| 376 | + help | |
| 377 | 377 | Allow volume managers to mirror logical volumes, also |
| 378 | 378 | needed for live data migration tools such as 'pvmove'. |
| 379 | 379 | |
| @@ -381,7 +381,7 @@ config DM_LOG_USERSPACE · 1 unmodified line | ||
| 381 | 381 | tristate "Mirror userspace logging" |
| 382 | 382 | depends on DM_MIRROR && NET |
| 383 | 383 | select CONNECTOR |
| 384 | − ---help--- | |
| 384 | + help | |
| 385 | 385 | The userspace logging module provides a mechanism for |
| 386 | 386 | relaying the dm-dirty-log API to userspace. Log designs |
| 387 | 387 | which are more suited to userspace implementation (e.g. |
| @@ -396,7 +396,7 @@ config DM_RAID · 8 unmodified lines | ||
| 396 | 396 | select MD_RAID10 |
| 397 | 397 | select MD_RAID456 |
| 398 | 398 | select BLK_DEV_MD |
| 399 | − ---help--- | |
| 399 | + help | |
| 400 | 400 | A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings |
| 401 | 401 | |
| 402 | 402 | A RAID-5 set of N drives with a capacity of C MB per drive provides |
| @@ -418,7 +418,7 @@ config DM_RAID · 15 unmodified lines | ||
| 418 | 418 | config DM_ZERO |
| 419 | 419 | tristate "Zero target" |
| 420 | 420 | depends on BLK_DEV_DM |
| 421 | − ---help--- | |
| 421 | + help | |
| 422 | 422 | A target that discards writes, and returns all zeroes for |
| 423 | 423 | reads. Useful in some recovery situations. |
| 424 | 424 | |
| @@ -430,13 +430,13 @@ config DM_MULTIPATH · 5 unmodified lines | ||
| 430 | 430 | # it is, DM_MULTIPATH must depend on it. We get a build |
| 431 | 431 | # error if SCSI_DH=m and DM_MULTIPATH=y |
| 432 | 432 | depends on !SCSI_DH || SCSI |
| 433 | − ---help--- | |
| 433 | + help | |
| 434 | 434 | Allow volume managers to support multipath hardware. |
| 435 | 435 | |
| 436 | 436 | config DM_MULTIPATH_QL |
| 437 | 437 | tristate "I/O Path Selector based on the number of in-flight I/Os" |
| 438 | 438 | depends on DM_MULTIPATH |
| 439 | − ---help--- | |
| 439 | + help | |
| 440 | 440 | This path selector is a dynamic load balancer which selects |
| 441 | 441 | the path with the least number of in-flight I/Os. |
| 442 | 442 | |
| @@ -445,7 +445,7 @@ config DM_MULTIPATH_QL · 2 unmodified lines | ||
| 445 | 445 | config DM_MULTIPATH_ST |
| 446 | 446 | tristate "I/O Path Selector based on the service time" |
| 447 | 447 | depends on DM_MULTIPATH |
| 448 | − ---help--- | |
| 448 | + help | |
| 449 | 449 | This path selector is a dynamic load balancer which selects |
| 450 | 450 | the path expected to complete the incoming I/O in the shortest |
| 451 | 451 | time. |
| @@ -466,7 +466,7 @@ config DM_MULTIPATH_HST · 14 unmodified lines | ||
| 466 | 466 | config DM_DELAY |
| 467 | 467 | tristate "I/O delaying target" |
| 468 | 468 | depends on BLK_DEV_DM |
| 469 | − ---help--- | |
| 469 | + help | |
| 470 | 470 | A target that delays reads and/or writes and can send |
| 471 | 471 | them to different devices. Useful for testing. |
| 472 | 472 | |
| @@ -475,7 +475,7 @@ config DM_DELAY · 2 unmodified lines | ||
| 475 | 475 | config DM_DUST |
| 476 | 476 | tristate "Bad sector simulation target" |
| 477 | 477 | depends on BLK_DEV_DM |
| 478 | − ---help--- | |
| 478 | + help | |
| 479 | 479 | A target that simulates bad sector behavior. |
| 480 | 480 | Useful for testing. |
| 481 | 481 | |
| @@ -484,7 +484,7 @@ config DM_DUST · 2 unmodified lines | ||
| 484 | 484 | config DM_INIT |
| 485 | 485 | bool "DM \"dm-mod.create=\" parameter support" |
| 486 | 486 | depends on BLK_DEV_DM=y |
| 487 | − ---help--- | |
| 487 | + help | |
| 488 | 488 | Enable "dm-mod.create=" parameter to create mapped devices at init time. |
| 489 | 489 | This option is useful to allow mounting rootfs without requiring an |
| 490 | 490 | initramfs. |
| @@ -496,13 +496,13 @@ config DM_INIT · 5 unmodified lines | ||
| 496 | 496 | config DM_UEVENT |
| 497 | 497 | bool "DM uevents" |
| 498 | 498 | depends on BLK_DEV_DM |
| 499 | − ---help--- | |
| 499 | + help | |
| 500 | 500 | Generate udev events for DM events. |
| 501 | 501 | |
| 502 | 502 | config DM_FLAKEY |
| 503 | 503 | tristate "Flakey target" |
| 504 | 504 | depends on BLK_DEV_DM |
| 505 | − ---help--- | |
| 505 | + help | |
| 506 | 506 | A target that intermittently fails I/O for debugging purposes. |
| 507 | 507 | |
| 508 | 508 | config DM_VERITY |
| @@ -511,7 +511,7 @@ config DM_VERITY · 2 unmodified lines | ||
| 511 | 511 | select CRYPTO |
| 512 | 512 | select CRYPTO_HASH |
| 513 | 513 | select DM_BUFIO |
| 514 | − ---help--- | |
| 514 | + help | |
| 515 | 515 | This device-mapper target creates a read-only device that |
| 516 | 516 | transparently validates the data on one underlying device against |
| 517 | 517 | a pre-generated tree of cryptographic checksums stored on a second |
| @@ -542,7 +542,7 @@ config DM_VERITY_FEC · 24 unmodified lines | ||
| 542 | 542 | depends on DM_VERITY |
| 543 | 543 | select REED_SOLOMON |
| 544 | 544 | select REED_SOLOMON_DEC8 |
| 545 | − ---help--- | |
| 545 | + help | |
| 546 | 546 | Add forward error correction support to dm-verity. This option |
| 547 | 547 | makes it possible to use pre-generated error correction data to |
| 548 | 548 | recover from corrupted blocks. |
| @@ -552,7 +552,7 @@ config DM_VERITY_FEC · 3 unmodified lines | ||
| 552 | 552 | config DM_SWITCH |
| 553 | 553 | tristate "Switch target support (EXPERIMENTAL)" |
| 554 | 554 | depends on BLK_DEV_DM |
| 555 | − ---help--- | |
| 555 | + help | |
| 556 | 556 | This device-mapper target creates a device that supports an arbitrary |
| 557 | 557 | mapping of fixed-size regions of I/O across a fixed set of paths. |
| 558 | 558 | The path used for any specific region can be switched dynamically |
| @@ -566,7 +566,7 @@ config DM_SWITCH · 7 unmodified lines | ||
| 566 | 566 | config DM_LOG_WRITES |
| 567 | 567 | tristate "Log writes target support" |
| 568 | 568 | depends on BLK_DEV_DM |
| 569 | − ---help--- | |
| 569 | + help | |
| 570 | 570 | This device-mapper target takes two devices, one device to use |
| 571 | 571 | normally, one to log all write operations done to the first device. |
| 572 | 572 | This is for use by file system developers wishing to verify that |
| @@ -586,7 +586,7 @@ config DM_INTEGRITY · 13 unmodified lines | ||
| 586 | 586 | select DM_BUFIO |
| 587 | 587 | select CRYPTO |
| 588 | 588 | select ASYNC_XOR |
| 589 | − ---help--- | |
| 589 | + help | |
| 590 | 590 | This device-mapper target emulates a block device that has |
| 591 | 591 | additional per-sector tags that can be used for storing |
| 592 | 592 | integrity information. |
| @@ -602,7 +602,7 @@ config DM_ZONED · 9 unmodified lines | ||
| 602 | 602 | tristate "Drive-managed zoned block device target support" |
| 603 | 603 | depends on BLK_DEV_DM |
| 604 | 604 | depends on BLK_DEV_ZONED |
| 605 | − ---help--- | |
| 605 | + help | |
| 606 | 606 | This device-mapper target takes a host-managed or host-aware zoned |
| 607 | 607 | block device and exposes most of its capacity as a regular block |
| 608 | 608 | device (drive-managed zoned block device) without any write |
| @@ -4,7 +4,7 @@ config DM_PERSISTENT_DATA · 3 unmodified lines | ||
| 4 | 4 | depends on BLK_DEV_DM |
| 5 | 5 | select LIBCRC32C |
| 6 | 6 | select DM_BUFIO |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | Library providing immutable on-disk data structure support for |
| 9 | 9 | device-mapper targets such as the thin provisioning target. |
| 10 | 10 | |
| @@ -32,7 +32,7 @@ config CEC_MESON_G12A_AO · 31 unmodified lines | ||
| 32 | 32 | select REGMAP_MMIO |
| 33 | 33 | select CEC_CORE |
| 34 | 34 | select CEC_NOTIFIER |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | This is a driver for Amlogic Meson G12A SoCs AO CEC interface. |
| 37 | 37 | This driver if for the new AO-CEC module found in G12A SoCs, |
| 38 | 38 | usually named AO_CEC_B in documentation. |
| @@ -3,7 +3,7 @@ · 2 unmodified lines | ||
| 3 | 3 | menuconfig FUSION |
| 4 | 4 | bool "Fusion MPT device support" |
| 5 | 5 | depends on PCI |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | Say Y here to get to see options for Fusion Message |
| 8 | 8 | Passing Technology (MPT) drivers. |
| 9 | 9 | This option alone does not add any kernel code. |
| @@ -16,7 +16,7 @@ config FUSION_SPI · 6 unmodified lines | ||
| 16 | 16 | tristate "Fusion MPT ScsiHost drivers for SPI" |
| 17 | 17 | depends on PCI && SCSI |
| 18 | 18 | select SCSI_SPI_ATTRS |
| 19 | − ---help--- | |
| 19 | + help | |
| 20 | 20 | SCSI HOST support for a parallel SCSI host adapters. |
| 21 | 21 | |
| 22 | 22 | List of supported controllers: |
| @@ -31,7 +31,7 @@ config FUSION_FC · 8 unmodified lines | ||
| 31 | 31 | tristate "Fusion MPT ScsiHost drivers for FC" |
| 32 | 32 | depends on PCI && SCSI |
| 33 | 33 | depends on SCSI_FC_ATTRS |
| 34 | − ---help--- | |
| 34 | + help | |
| 35 | 35 | SCSI HOST support for a Fiber Channel host adapters. |
| 36 | 36 | |
| 37 | 37 | List of supported controllers: |
| @@ -50,7 +50,7 @@ config FUSION_SAS · 12 unmodified lines | ||
| 50 | 50 | tristate "Fusion MPT ScsiHost drivers for SAS" |
| 51 | 51 | depends on PCI && SCSI |
| 52 | 52 | select SCSI_SAS_ATTRS |
| 53 | − ---help--- | |
| 53 | + help | |
| 54 | 54 | SCSI HOST support for a SAS host adapters. |
| 55 | 55 | |
| 56 | 56 | List of supported controllers: |
| @@ -75,7 +75,7 @@ config FUSION_MAX_SGE · 18 unmodified lines | ||
| 75 | 75 | config FUSION_CTL |
| 76 | 76 | tristate "Fusion MPT misc device (ioctl) driver" |
| 77 | 77 | depends on FUSION_SPI || FUSION_FC || FUSION_SAS |
| 78 | − ---help--- | |
| 78 | + help | |
| 79 | 79 | The Fusion MPT misc device driver provides specialized control |
| 80 | 80 | of MPT adapters via system ioctl calls. Use of ioctl calls to |
| 81 | 81 | the MPT driver requires that you create and use a misc device |
| @@ -94,7 +94,7 @@ config FUSION_CTL · 12 unmodified lines | ||
| 94 | 94 | config FUSION_LAN |
| 95 | 95 | tristate "Fusion MPT LAN driver" |
| 96 | 96 | depends on FUSION_FC && NET_FC |
| 97 | − ---help--- | |
| 97 | + help | |
| 98 | 98 | This module supports LAN IP traffic over Fibre Channel port(s) |
| 99 | 99 | on Fusion MPT compatible hardware (LSIFC9xx chips). |
| 100 | 100 | The physical interface used is defined in RFC 2625. |
| @@ -110,7 +110,7 @@ config FUSION_LAN · 9 unmodified lines | ||
| 110 | 110 | |
| 111 | 111 | config FUSION_LOGGING |
| 112 | 112 | bool "Fusion MPT logging facility" |
| 113 | − ---help--- | |
| 113 | + help | |
| 114 | 114 | This turns on a logging facility that can be used to debug a number |
| 115 | 115 | of Fusion MPT related problems. |
| 116 | 116 | |
| @@ -15,7 +15,7 @@ config MFD_CS5535 · 14 unmodified lines | ||
| 15 | 15 | tristate "AMD CS5535 and CS5536 southbridge core functions" |
| 16 | 16 | select MFD_CORE |
| 17 | 17 | depends on PCI && (X86_32 || (X86 && COMPILE_TEST)) |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | This is the core driver for CS5535/CS5536 MFD functions. This is |
| 20 | 20 | necessary for using the board's GPIO and MFGPT functionality. |
| 21 | 21 | |
| @@ -292,7 +292,7 @@ config MFD_ASIC3 · 270 unmodified lines | ||
| 292 | 292 | bool "Compaq ASIC3" |
| 293 | 293 | depends on GPIOLIB && ARM |
| 294 | 294 | select MFD_CORE |
| 295 | − ---help--- | |
| 295 | + help | |
| 296 | 296 | This driver supports the ASIC3 multifunction chip found on many |
| 297 | 297 | PDAs (mainly iPAQ and HTC based ones) |
| 298 | 298 | |
| @@ -1165,7 +1165,7 @@ config MFD_SI476X_CORE · 866 unmodified lines | ||
| 1165 | 1165 | config MFD_SM501 |
| 1166 | 1166 | tristate "Silicon Motion SM501" |
| 1167 | 1167 | depends on HAS_DMA |
| 1168 | − ---help--- | |
| 1168 | + help | |
| 1169 | 1169 | This is the core driver for the Silicon Motion SM501 multimedia |
| 1170 | 1170 | companion chip. This device is a multifunction device which may |
| 1171 | 1171 | provide numerous interfaces including USB host controller, USB gadget, |
| @@ -1176,7 +1176,7 @@ config MFD_SM501 · 4 unmodified lines | ||
| 1176 | 1176 | config MFD_SM501_GPIO |
| 1177 | 1177 | bool "Export GPIO via GPIO layer" |
| 1178 | 1178 | depends on MFD_SM501 && GPIOLIB |
| 1179 | − ---help--- | |
| 1179 | + help | |
| 1180 | 1180 | This option uses the gpio library layer to export the 64 GPIO |
| 1181 | 1181 | lines on the SM501. The platform data is used to supply the |
| 1182 | 1182 | base number for the first GPIO line to register. |
| @@ -1721,7 +1721,7 @@ config MFD_TIMBERDALE · 538 unmodified lines | ||
| 1721 | 1721 | tristate "Timberdale FPGA" |
| 1722 | 1722 | select MFD_CORE |
| 1723 | 1723 | depends on PCI && GPIOLIB && (X86_32 || COMPILE_TEST) |
| 1724 | − ---help--- | |
| 1724 | + help | |
| 1725 | 1725 | This is the core driver for the timberdale FPGA. This device is a |
| 1726 | 1726 | multifunction device which exposes numerous platform devices. |
| 1727 | 1727 | |
| @@ -60,7 +60,7 @@ config ATMEL_TCLIB · 59 unmodified lines | ||
| 60 | 60 | |
| 61 | 61 | config DUMMY_IRQ |
| 62 | 62 | tristate "Dummy IRQ handler" |
| 63 | − ---help--- | |
| 63 | + help | |
| 64 | 64 | This module accepts a single 'irq' parameter, which it should register for. |
| 65 | 65 | The sole purpose of this module is to help with debugging of systems on |
| 66 | 66 | which spurious IRQs would happen on disabled IRQ vector. |
| @@ -69,7 +69,7 @@ config IBM_ASM · 2 unmodified lines | ||
| 69 | 69 | tristate "Device driver for IBM RSA service processor" |
| 70 | 70 | depends on X86 && PCI && INPUT |
| 71 | 71 | depends on SERIAL_8250 || SERIAL_8250=n |
| 72 | − ---help--- | |
| 72 | + help | |
| 73 | 73 | This option enables device driver support for in-band access to the |
| 74 | 74 | IBM RSA (Condor) service processor in eServer xSeries systems. |
| 75 | 75 | The ibmasm device driver allows user space application to access |
| @@ -167,7 +167,7 @@ config ICS932S401 · 91 unmodified lines | ||
| 167 | 167 | config ATMEL_SSC |
| 168 | 168 | tristate "Device driver for Atmel SSC peripheral" |
| 169 | 169 | depends on HAS_IOMEM && (ARCH_AT91 || COMPILE_TEST) |
| 170 | − ---help--- | |
| 170 | + help | |
| 171 | 171 | This option enables device driver support for Atmel Synchronized |
| 172 | 172 | Serial Communication peripheral (SSC). |
| 173 | 173 | |
| @@ -190,7 +190,7 @@ config SGI_XP · 16 unmodified lines | ||
| 190 | 190 | depends on (IA64_SGI_UV || X86_UV) && SMP |
| 191 | 191 | depends on X86_64 || BROKEN |
| 192 | 192 | select SGI_GRU if X86_64 && SMP |
| 193 | − ---help--- | |
| 193 | + help | |
| 194 | 194 | An SGI machine can be divided into multiple Single System |
| 195 | 195 | Images which act independently of each other and have |
| 196 | 196 | hardware based memory protection from the others. Enabling |
| @@ -267,7 +267,7 @@ config SGI_GRU · 70 unmodified lines | ||
| 267 | 267 | tristate "SGI GRU driver" |
| 268 | 268 | depends on X86_UV && SMP |
| 269 | 269 | select MMU_NOTIFIER |
| 270 | − ---help--- | |
| 270 | + help | |
| 271 | 271 | The GRU is a hardware resource located in the system chipset. The GRU |
| 272 | 272 | contains memory that can be mmapped into the user address space. This memory is |
| 273 | 273 | used to communicate with the GRU to perform functions such as load/store, |
| @@ -280,7 +280,7 @@ config SGI_GRU · 6 unmodified lines | ||
| 280 | 280 | config SGI_GRU_DEBUG |
| 281 | 281 | bool "SGI GRU driver debug" |
| 282 | 282 | depends on SGI_GRU |
| 283 | − ---help--- | |
| 283 | + help | |
| 284 | 284 | This option enables additional debugging code for the SGI GRU driver. |
| 285 | 285 | If you are unsure, say N. |
| 286 | 286 | |
| @@ -327,7 +327,7 @@ config SENSORS_TSL2550 · 40 unmodified lines | ||
| 327 | 327 | config SENSORS_BH1770 |
| 328 | 328 | tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor" |
| 329 | 329 | depends on I2C |
| 330 | − ---help--- | |
| 330 | + help | |
| 331 | 331 | Say Y here if you want to build a driver for BH1770GLC (ROHM) or |
| 332 | 332 | SFH7770 (Osram) combined ambient light and proximity sensor chip. |
| 333 | 333 | |
| @@ -337,7 +337,7 @@ config SENSORS_BH1770 · 3 unmodified lines | ||
| 337 | 337 | config SENSORS_APDS990X |
| 338 | 338 | tristate "APDS990X combined als and proximity sensors" |
| 339 | 339 | depends on I2C |
| 340 | − ---help--- | |
| 340 | + help | |
| 341 | 341 | Say Y here if you want to build a driver for Avago APDS990x |
| 342 | 342 | combined ambient light and proximity sensor chip. |
| 343 | 343 | |
| @@ -427,7 +427,7 @@ config PCI_ENDPOINT_TEST · 83 unmodified lines | ||
| 427 | 427 | depends on PCI |
| 428 | 428 | select CRC32 |
| 429 | 429 | tristate "PCI Endpoint Test driver" |
| 430 | − ---help--- | |
| 430 | + help | |
| 431 | 431 | Enable this configuration option to enable the host side test driver |
| 432 | 432 | for PCI Endpoint. |
| 433 | 433 | |
| @@ -1,7 +1,7 @@ | ||
| 1 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | 2 | config ECHO |
| 3 | 3 | tristate "Line Echo Canceller support" |
| 4 | − ---help--- | |
| 4 | + help | |
| 5 | 5 | This driver provides line echo cancelling support for mISDN and |
| 6 | 6 | Zaptel drivers. |
| 7 | 7 | |
| @@ -577,7 +577,7 @@ config MMC_MVSDIO · 576 unmodified lines | ||
| 577 | 577 | tristate "Marvell MMC/SD/SDIO host driver" |
| 578 | 578 | depends on PLAT_ORION |
| 579 | 579 | depends on OF |
| 580 | − ---help--- | |
| 580 | + help | |
| 581 | 581 | This selects the Marvell SDIO host driver. |
| 582 | 582 | SDIO may currently be found on the Kirkwood 88F6281 and 88F6192 |
| 583 | 583 | SoC controllers. |
| @@ -7,7 +7,7 @@ menuconfig NETDEVICES · 6 unmodified lines | ||
| 7 | 7 | default y if UML |
| 8 | 8 | depends on NET |
| 9 | 9 | bool "Network device support" |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | You can say N here if you don't intend to connect your Linux box to |
| 12 | 12 | any other computer at all. |
| 13 | 13 | |
| @@ -32,7 +32,7 @@ config MII · 18 unmodified lines | ||
| 32 | 32 | config NET_CORE |
| 33 | 33 | default y |
| 34 | 34 | bool "Network core driver support" |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | You can say N here if you do not intend to use any of the |
| 37 | 37 | networking core drivers (i.e. VLAN, bridging, bonding, etc.) |
| 38 | 38 | |
| @@ -42,7 +42,7 @@ config BONDING · 3 unmodified lines | ||
| 42 | 42 | tristate "Bonding driver support" |
| 43 | 43 | depends on INET |
| 44 | 44 | depends on IPV6 || IPV6=n |
| 45 | − ---help--- | |
| 45 | + help | |
| 46 | 46 | Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet |
| 47 | 47 | Channels together. This is called 'Etherchannel' by Cisco, |
| 48 | 48 | 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux. |
| @@ -58,7 +58,7 @@ config BONDING · 9 unmodified lines | ||
| 58 | 58 | |
| 59 | 59 | config DUMMY |
| 60 | 60 | tristate "Dummy net driver support" |
| 61 | − ---help--- | |
| 61 | + help | |
| 62 | 62 | This is essentially a bit-bucket device (i.e. traffic you send to |
| 63 | 63 | this device is consigned into oblivion) with a configurable IP |
| 64 | 64 | address. It is most commonly used in order to make your currently |
| @@ -116,7 +116,7 @@ config WIREGUARD_DEBUG · 51 unmodified lines | ||
| 116 | 116 | |
| 117 | 117 | config EQUALIZER |
| 118 | 118 | tristate "EQL (serial line load balancing) support" |
| 119 | − ---help--- | |
| 119 | + help | |
| 120 | 120 | If you have two serial connections to some other computer (this |
| 121 | 121 | usually requires two modems and two telephone lines) and you use |
| 122 | 122 | SLIP (the protocol for sending Internet traffic over telephone |
| @@ -150,7 +150,7 @@ config IFB · 27 unmodified lines | ||
| 150 | 150 | tristate "Intermediate Functional Block support" |
| 151 | 151 | depends on NET_CLS_ACT |
| 152 | 152 | select NET_REDIRECT |
| 153 | − ---help--- | |
| 153 | + help | |
| 154 | 154 | This is an intermediate driver that allows sharing of |
| 155 | 155 | resources. |
| 156 | 156 | To compile this driver as a module, choose M here: the module |
| @@ -164,7 +164,7 @@ source "drivers/net/team/Kconfig" · 7 unmodified lines | ||
| 164 | 164 | |
| 165 | 165 | config MACVLAN |
| 166 | 166 | tristate "MAC-VLAN support" |
| 167 | − ---help--- | |
| 167 | + help | |
| 168 | 168 | This allows one to create virtual interfaces that map packets to |
| 169 | 169 | or from specific MAC addresses to a particular interface. |
| 170 | 170 | |
| @@ -200,7 +200,7 @@ config IPVLAN · 29 unmodified lines | ||
| 200 | 200 | tristate "IP-VLAN support" |
| 201 | 201 | depends on INET |
| 202 | 202 | depends on IPV6 || !IPV6 |
| 203 | − ---help--- | |
| 203 | + help | |
| 204 | 204 | This allows one to create virtual devices off of a main interface |
| 205 | 205 | and packets will be delivered based on the dest L3 (IPv6/IPv4 addr) |
| 206 | 206 | on packets. All interfaces (including the main interface) share L2 |
| @@ -219,7 +219,7 @@ config IPVTAP · 12 unmodified lines | ||
| 219 | 219 | depends on IPVLAN |
| 220 | 220 | depends on INET |
| 221 | 221 | select TAP |
| 222 | − ---help--- | |
| 222 | + help | |
| 223 | 223 | This adds a specialized tap character device driver that is based |
| 224 | 224 | on the IP-VLAN network interface, called ipvtap. An ipvtap device |
| 225 | 225 | can be added in the same way as a ipvlan device, using 'type |
| @@ -233,7 +233,7 @@ config VXLAN · 7 unmodified lines | ||
| 233 | 233 | depends on INET |
| 234 | 234 | select NET_UDP_TUNNEL |
| 235 | 235 | select GRO_CELLS |
| 236 | − ---help--- | |
| 236 | + help | |
| 237 | 237 | This allows one to create vxlan virtual interfaces that provide |
| 238 | 238 | Layer 2 Networks over Layer 3 Networks. VXLAN is often used |
| 239 | 239 | to tunnel virtual network infrastructure in virtualized environments. |
| @@ -249,7 +249,7 @@ config GENEVE · 9 unmodified lines | ||
| 249 | 249 | depends on IPV6 || !IPV6 |
| 250 | 250 | select NET_UDP_TUNNEL |
| 251 | 251 | select GRO_CELLS |
| 252 | − ---help--- | |
| 252 | + help | |
| 253 | 253 | This allows one to create geneve virtual interfaces that provide |
| 254 | 254 | Layer 2 Networks over Layer 3 Networks. GENEVE is often used |
| 255 | 255 | to tunnel virtual network infrastructure in virtualized environments. |
| @@ -276,7 +276,7 @@ config GTP · 20 unmodified lines | ||
| 276 | 276 | tristate "GPRS Tunneling Protocol datapath (GTP-U)" |
| 277 | 277 | depends on INET |
| 278 | 278 | select NET_UDP_TUNNEL |
| 279 | − ---help--- | |
| 279 | + help | |
| 280 | 280 | This allows one to create gtp virtual interfaces that provide |
| 281 | 281 | the GPRS Tunneling Protocol datapath (GTP-U). This tunneling protocol |
| 282 | 282 | is used to prevent subscribers from accessing mobile carrier core |
| @@ -295,12 +295,12 @@ config MACSEC · 12 unmodified lines | ||
| 295 | 295 | select CRYPTO_AES |
| 296 | 296 | select CRYPTO_GCM |
| 297 | 297 | select GRO_CELLS |
| 298 | − ---help--- | |
| 298 | + help | |
| 299 | 299 | MACsec is an encryption standard for Ethernet. |
| 300 | 300 | |
| 301 | 301 | config NETCONSOLE |
| 302 | 302 | tristate "Network console logging support" |
| 303 | − ---help--- | |
| 303 | + help | |
| 304 | 304 | If you want to log kernel messages over the network, enable this. |
| 305 | 305 | See <file:Documentation/networking/netconsole.rst> for details. |
| 306 | 306 | |
| @@ -343,7 +343,7 @@ config TUN · 36 unmodified lines | ||
| 343 | 343 | tristate "Universal TUN/TAP device driver support" |
| 344 | 344 | depends on INET |
| 345 | 345 | select CRC32 |
| 346 | − ---help--- | |
| 346 | + help | |
| 347 | 347 | TUN/TAP provides packet reception and transmission for user space |
| 348 | 348 | programs. It can be viewed as a simple Point-to-Point or Ethernet |
| 349 | 349 | device, which instead of receiving packets from a physical media, |
| @@ -365,14 +365,14 @@ config TUN · 15 unmodified lines | ||
| 365 | 365 | |
| 366 | 366 | config TAP |
| 367 | 367 | tristate |
| 368 | − ---help--- | |
| 368 | + help | |
| 369 | 369 | This option is selected by any driver implementing tap user space |
| 370 | 370 | interface for a virtual interface to re-use core tap functionality. |
| 371 | 371 | |
| 372 | 372 | config TUN_VNET_CROSS_LE |
| 373 | 373 | bool "Support for cross-endian vnet headers on little-endian kernels" |
| 374 | 374 | default n |
| 375 | − ---help--- | |
| 375 | + help | |
| 376 | 376 | This option allows TUN/TAP and MACVTAP device drivers in a |
| 377 | 377 | little-endian kernel to parse vnet headers that come from a |
| 378 | 378 | big-endian legacy virtio device. |
| @@ -385,7 +385,7 @@ config TUN_VNET_CROSS_LE · 6 unmodified lines | ||
| 385 | 385 | |
| 386 | 386 | config VETH |
| 387 | 387 | tristate "Virtual ethernet pair device" |
| 388 | − ---help--- | |
| 388 | + help | |
| 389 | 389 | This device is a local ethernet tunnel. Devices are created in pairs. |
| 390 | 390 | When one end receives the packet it appears on its pair and vice |
| 391 | 391 | versa. |
| @@ -394,13 +394,13 @@ config VIRTIO_NET · 2 unmodified lines | ||
| 394 | 394 | tristate "Virtio network driver" |
| 395 | 395 | depends on VIRTIO |
| 396 | 396 | select NET_FAILOVER |
| 397 | − ---help--- | |
| 397 | + help | |
| 398 | 398 | This is the virtual network driver for virtio. It can be used with |
| 399 | 399 | QEMU based VMMs (like KVM or Xen). Say Y or M. |
| 400 | 400 | |
| 401 | 401 | config NLMON |
| 402 | 402 | tristate "Virtual netlink monitoring device" |
| 403 | − ---help--- | |
| 403 | + help | |
| 404 | 404 | This option enables a monitoring net device for netlink skbs. The |
| 405 | 405 | purpose of this is to analyze netlink messages with packet sockets. |
| 406 | 406 | Thus applications like tcpdump will be able to see local netlink |
| @@ -414,14 +414,14 @@ config NET_VRF · 7 unmodified lines | ||
| 414 | 414 | depends on NET_L3_MASTER_DEV |
| 415 | 415 | depends on IPV6 || IPV6=n |
| 416 | 416 | depends on IPV6_MULTIPLE_TABLES || IPV6=n |
| 417 | − ---help--- | |
| 417 | + help | |
| 418 | 418 | This option enables the support for mapping interfaces into VRF's. The |
| 419 | 419 | support enables VRF devices. |
| 420 | 420 | |
| 421 | 421 | config VSOCKMON |
| 422 | 422 | tristate "Virtual vsock monitoring device" |
| 423 | 423 | depends on VHOST_VSOCK |
| 424 | − ---help--- | |
| 424 | + help | |
| 425 | 425 | This option enables a monitoring net device for vsock sockets. It is |
| 426 | 426 | mostly intended for developers or support to debug vsock issues. If |
| 427 | 427 | unsure, say N. |
| @@ -450,7 +450,7 @@ source "drivers/net/ipa/Kconfig" · 22 unmodified lines | ||
| 450 | 450 | config NET_SB1000 |
| 451 | 451 | tristate "General Instruments Surfboard 1000" |
| 452 | 452 | depends on PNP |
| 453 | − ---help--- | |
| 453 | + help | |
| 454 | 454 | This is a driver for the General Instrument (also known as |
| 455 | 455 | NextLevel) SURFboard 1000 internal |
| 456 | 456 | cable modem. This is an ISA card which is used by a number of cable |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | config ATALK |
| 6 | 6 | tristate "Appletalk protocol support" |
| 7 | 7 | select LLC |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | AppleTalk is the protocol that Apple computers can use to communicate |
| 10 | 10 | on a network. If your Linux box is connected to such a network and you |
| 11 | 11 | wish to connect to it, say Y. You will need to use the netatalk package |
| @@ -79,7 +79,7 @@ config COPS_TANGENT · 67 unmodified lines | ||
| 79 | 79 | config IPDDP |
| 80 | 80 | tristate "Appletalk-IP driver support" |
| 81 | 81 | depends on DEV_APPLETALK && ATALK |
| 82 | − ---help--- | |
| 82 | + help | |
| 83 | 83 | This allows IP networking for users who only have AppleTalk |
| 84 | 84 | networking available. This feature is experimental. With this |
| 85 | 85 | driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | menuconfig ARCNET |
| 7 | 7 | depends on NETDEVICES && (ISA || PCI || PCMCIA) |
| 8 | 8 | tristate "ARCnet support" |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network card of this type, say Y and check out the |
| 11 | 11 | (arguably) beautiful poetry in |
| 12 | 12 | <file:Documentation/networking/arcnet.rst>. |
| @@ -33,7 +33,7 @@ config ARCNET_1201 · 20 unmodified lines | ||
| 33 | 33 | |
| 34 | 34 | config ARCNET_1051 |
| 35 | 35 | tristate "Enable old ARCNet packet format (RFC 1051)" |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | This allows you to use RFC1051 with your ARCnet card via the virtual |
| 38 | 38 | arc0s device. You only need arc0s if you want to talk to ARCnet |
| 39 | 39 | software complying with the "old" standard, specifically, the DOS |
| @@ -82,7 +82,7 @@ config ARCNET_COM90xx · 42 unmodified lines | ||
| 82 | 82 | |
| 83 | 83 | config ARCNET_COM90xxIO |
| 84 | 84 | tristate "ARCnet COM90xx (IO mapped) chipset driver" |
| 85 | − ---help--- | |
| 85 | + help | |
| 86 | 86 | This is the chipset driver for the COM90xx cards, using them in |
| 87 | 87 | IO-mapped mode instead of memory-mapped mode. This is slower than |
| 88 | 88 | the normal driver. Only use it if your card doesn't support shared |
| @@ -93,7 +93,7 @@ config ARCNET_COM90xxIO · 4 unmodified lines | ||
| 93 | 93 | |
| 94 | 94 | config ARCNET_RIM_I |
| 95 | 95 | tristate "ARCnet COM90xx (RIM I) chipset driver" |
| 96 | − ---help--- | |
| 96 | + help | |
| 97 | 97 | This is yet another chipset driver for the COM90xx cards, but this |
| 98 | 98 | time only using memory-mapped mode, and no IO ports at all. This |
| 99 | 99 | driver is completely untested, so if you have one of these cards, |
| @@ -15,7 +15,7 @@ config CAIF_TTY · 14 unmodified lines | ||
| 15 | 15 | tristate "CAIF TTY transport driver" |
| 16 | 16 | depends on CAIF && TTY |
| 17 | 17 | default n |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | The CAIF TTY transport driver is a Line Discipline (ldisc) |
| 20 | 20 | identified as N_CAIF. When this ldisc is opened from user space |
| 21 | 21 | it will redirect the TTY's traffic into the CAIF stack. |
| @@ -24,7 +24,7 @@ config CAIF_SPI_SLAVE · 2 unmodified lines | ||
| 24 | 24 | tristate "CAIF SPI transport driver for slave interface" |
| 25 | 25 | depends on CAIF && HAS_DMA |
| 26 | 26 | default n |
| 27 | − ---help--- | |
| 27 | + help | |
| 28 | 28 | The CAIF Link layer SPI Protocol driver for Slave SPI interface. |
| 29 | 29 | This driver implements a platform driver to accommodate for a |
| 30 | 30 | platform specific SPI device. A sample CAIF SPI Platform device is |
| @@ -34,7 +34,7 @@ config CAIF_SPI_SYNC · 3 unmodified lines | ||
| 34 | 34 | bool "Next command and length in start of frame" |
| 35 | 35 | depends on CAIF_SPI_SLAVE |
| 36 | 36 | default n |
| 37 | − ---help--- | |
| 37 | + help | |
| 38 | 38 | Putting the next command and length in the start of the frame can |
| 39 | 39 | help to synchronize to the next transfer in case of over or under-runs. |
| 40 | 40 | This option also needs to be enabled on the modem. |
| @@ -43,7 +43,7 @@ config CAIF_HSI · 2 unmodified lines | ||
| 43 | 43 | tristate "CAIF HSI transport driver" |
| 44 | 44 | depends on CAIF |
| 45 | 45 | default n |
| 46 | − ---help--- | |
| 46 | + help | |
| 47 | 47 | The CAIF low level driver for CAIF over HSI. |
| 48 | 48 | Be aware that if you enable this then you also need to |
| 49 | 49 | enable a low-level HSI driver. |
| @@ -55,7 +55,7 @@ config CAIF_VIRTIO · 5 unmodified lines | ||
| 55 | 55 | select VIRTIO |
| 56 | 56 | select GENERIC_ALLOCATOR |
| 57 | 57 | default n |
| 58 | − ---help--- | |
| 58 | + help | |
| 59 | 59 | The CAIF driver for CAIF over Virtio. |
| 60 | 60 | |
| 61 | 61 | endif # CAIF_DRIVERS |
| @@ -3,7 +3,7 @@ menu "CAN Device Drivers" · 2 unmodified lines | ||
| 3 | 3 | |
| 4 | 4 | config CAN_VCAN |
| 5 | 5 | tristate "Virtual Local CAN Interface (vcan)" |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | Similar to the network loopback devices, vcan offers a |
| 8 | 8 | virtual local CAN interface. |
| 9 | 9 | |
| @@ -12,7 +12,7 @@ config CAN_VCAN · 2 unmodified lines | ||
| 12 | 12 | |
| 13 | 13 | config CAN_VXCAN |
| 14 | 14 | tristate "Virtual CAN Tunnel (vxcan)" |
| 15 | − ---help--- | |
| 15 | + help | |
| 16 | 16 | Similar to the virtual ethernet driver veth, vxcan implements a |
| 17 | 17 | local CAN traffic tunnel between two virtual CAN network devices. |
| 18 | 18 | When creating a vxcan, two vxcan devices are created as pair. |
| @@ -31,7 +31,7 @@ config CAN_VXCAN · 12 unmodified lines | ||
| 31 | 31 | config CAN_SLCAN |
| 32 | 32 | tristate "Serial / USB serial CAN Adaptors (slcan)" |
| 33 | 33 | depends on TTY |
| 34 | − ---help--- | |
| 34 | + help | |
| 35 | 35 | CAN driver for several 'low cost' CAN interfaces that are attached |
| 36 | 36 | via serial lines or via USB-to-serial adapters using the LAWICEL |
| 37 | 37 | ASCII protocol. The driver implements the tty linediscipline N_SLCAN. |
| @@ -51,7 +51,7 @@ config CAN_SLCAN · 13 unmodified lines | ||
| 51 | 51 | config CAN_DEV |
| 52 | 52 | tristate "Platform CAN drivers with Netlink support" |
| 53 | 53 | default y |
| 54 | − ---help--- | |
| 54 | + help | |
| 55 | 55 | Enables the common framework for platform CAN drivers with Netlink |
| 56 | 56 | support. This is the standard library for CAN drivers. |
| 57 | 57 | If unsure, say Y. |
| @@ -61,7 +61,7 @@ if CAN_DEV · 3 unmodified lines | ||
| 61 | 61 | config CAN_CALC_BITTIMING |
| 62 | 62 | bool "CAN bit-timing calculation" |
| 63 | 63 | default y |
| 64 | − ---help--- | |
| 64 | + help | |
| 65 | 65 | If enabled, CAN bit-timing parameters will be calculated for the |
| 66 | 66 | bit-rate specified via Netlink argument "bitrate" when the device |
| 67 | 67 | get started. This works fine for the most common CAN controllers |
| @@ -81,7 +81,7 @@ config CAN_LEDS · 13 unmodified lines | ||
| 81 | 81 | # fulfills your needs instead of fixing this driver. |
| 82 | 82 | depends on BROKEN |
| 83 | 83 | select LEDS_TRIGGERS |
| 84 | − ---help--- | |
| 84 | + help | |
| 85 | 85 | This option adds two LED triggers for packet receive and transmit |
| 86 | 86 | events on each supported CAN device. |
| 87 | 87 | |
| @@ -91,20 +91,20 @@ config CAN_LEDS · 3 unmodified lines | ||
| 91 | 91 | config CAN_AT91 |
| 92 | 92 | tristate "Atmel AT91 onchip CAN controller" |
| 93 | 93 | depends on (ARCH_AT91 || COMPILE_TEST) && HAS_IOMEM |
| 94 | − ---help--- | |
| 94 | + help | |
| 95 | 95 | This is a driver for the SoC CAN controller in Atmel's AT91SAM9263 |
| 96 | 96 | and AT91SAM9X5 processors. |
| 97 | 97 | |
| 98 | 98 | config CAN_FLEXCAN |
| 99 | 99 | tristate "Support for Freescale FLEXCAN based chips" |
| 100 | 100 | depends on OF && HAS_IOMEM |
| 101 | − ---help--- | |
| 101 | + help | |
| 102 | 102 | Say Y here if you want to support for Freescale FlexCAN. |
| 103 | 103 | |
| 104 | 104 | config CAN_GRCAN |
| 105 | 105 | tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices" |
| 106 | 106 | depends on OF && HAS_DMA |
| 107 | − ---help--- | |
| 107 | + help | |
| 108 | 108 | Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN. |
| 109 | 109 | Note that the driver supports little endian, even though little |
| 110 | 110 | endian syntheses of the cores would need some modifications on |
| @@ -113,7 +113,7 @@ config CAN_GRCAN · 2 unmodified lines | ||
| 113 | 113 | config CAN_JANZ_ICAN3 |
| 114 | 114 | tristate "Janz VMOD-ICAN3 Intelligent CAN controller" |
| 115 | 115 | depends on MFD_JANZ_CMODIO |
| 116 | − ---help--- | |
| 116 | + help | |
| 117 | 117 | Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which |
| 118 | 118 | connects to a MODULbus carrier board. |
| 119 | 119 | |
| @@ -136,7 +136,7 @@ config CAN_KVASER_PCIEFD · 16 unmodified lines | ||
| 136 | 136 | config CAN_SUN4I |
| 137 | 137 | tristate "Allwinner A10 CAN controller" |
| 138 | 138 | depends on MACH_SUN4I || MACH_SUN7I || COMPILE_TEST |
| 139 | − ---help--- | |
| 139 | + help | |
| 140 | 140 | Say Y here if you want to use CAN controller found on Allwinner |
| 141 | 141 | A10/A20 SoCs. |
| 142 | 142 | |
| @@ -146,7 +146,7 @@ config CAN_SUN4I · 3 unmodified lines | ||
| 146 | 146 | config CAN_TI_HECC |
| 147 | 147 | depends on ARM |
| 148 | 148 | tristate "TI High End CAN Controller" |
| 149 | − ---help--- | |
| 149 | + help | |
| 150 | 150 | Driver for TI HECC (High End CAN Controller) module found on many |
| 151 | 151 | TI devices. The device specifications are available from www.ti.com |
| 152 | 152 | |
| @@ -154,14 +154,14 @@ config CAN_XILINXCAN · 1 unmodified line | ||
| 154 | 154 | tristate "Xilinx CAN" |
| 155 | 155 | depends on ARCH_ZYNQ || ARM64 || MICROBLAZE || COMPILE_TEST |
| 156 | 156 | depends on COMMON_CLK && HAS_IOMEM |
| 157 | − ---help--- | |
| 157 | + help | |
| 158 | 158 | Xilinx CAN driver. This driver supports both soft AXI CAN IP and |
| 159 | 159 | Zynq CANPS IP. |
| 160 | 160 | |
| 161 | 161 | config PCH_CAN |
| 162 | 162 | tristate "Intel EG20T PCH CAN controller" |
| 163 | 163 | depends on PCI && (X86_32 || COMPILE_TEST) |
| 164 | − ---help--- | |
| 164 | + help | |
| 165 | 165 | This driver is for PCH CAN of Topcliff (Intel EG20T PCH) which |
| 166 | 166 | is an IOH for x86 embedded processor (Intel Atom E6xx series). |
| 167 | 167 | This driver can access CAN bus. |
| @@ -182,7 +182,7 @@ endif · 14 unmodified lines | ||
| 182 | 182 | |
| 183 | 183 | config CAN_DEBUG_DEVICES |
| 184 | 184 | bool "CAN devices debugging messages" |
| 185 | − ---help--- | |
| 185 | + help | |
| 186 | 186 | Say Y here if you want the CAN device drivers to produce a bunch of |
| 187 | 187 | debug messages to the system log. Select this if you are having |
| 188 | 188 | a problem with CAN support and want to see more of what is going |
| @@ -7,7 +7,7 @@ if CAN_C_CAN · 6 unmodified lines | ||
| 7 | 7 | |
| 8 | 8 | config CAN_C_CAN_PLATFORM |
| 9 | 9 | tristate "Generic Platform Bus based C_CAN/D_CAN driver" |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | This driver adds support for the C_CAN/D_CAN chips connected |
| 12 | 12 | to the "platform bus" (Linux abstraction for directly to the |
| 13 | 13 | processor attached devices) which can be found on various |
| @@ -18,7 +18,7 @@ config CAN_C_CAN_PLATFORM · 4 unmodified lines | ||
| 18 | 18 | config CAN_C_CAN_PCI |
| 19 | 19 | tristate "Generic PCI Bus based C_CAN/D_CAN driver" |
| 20 | 20 | depends on PCI |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | This driver adds support for the C_CAN/D_CAN chips connected |
| 23 | 23 | to the PCI bus. |
| 24 | 24 | endif |
| @@ -7,14 +7,14 @@ if CAN_CC770 · 6 unmodified lines | ||
| 7 | 7 | |
| 8 | 8 | config CAN_CC770_ISA |
| 9 | 9 | tristate "ISA Bus based legacy CC770 driver" |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | This driver adds legacy support for CC770 and AN82527 chips |
| 12 | 12 | connected to the ISA bus using I/O port, memory mapped or |
| 13 | 13 | indirect access. |
| 14 | 14 | |
| 15 | 15 | config CAN_CC770_PLATFORM |
| 16 | 16 | tristate "Generic Platform Bus based CC770 driver" |
| 17 | − ---help--- | |
| 17 | + help | |
| 18 | 18 | This driver adds support for the CC770 and AN82527 chips |
| 19 | 19 | connected to the "platform bus" (Linux abstraction for directly |
| 20 | 20 | to the processor attached devices). |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config CAN_IFI_CANFD |
| 3 | 3 | depends on HAS_IOMEM |
| 4 | 4 | tristate "IFI CAN_FD IP" |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This driver adds support for the I/F/I CAN_FD soft IP block |
| 7 | 7 | connected to the "platform bus" (Linux abstraction for directly |
| 8 | 8 | to the processor attached devices). The CAN_FD is most often |
| @@ -1,7 +1,7 @@ | ||
| 1 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | 2 | config CAN_M_CAN |
| 3 | 3 | tristate "Bosch M_CAN support" |
| 4 | − ---help--- | |
| 4 | + help | |
| 5 | 5 | Say Y here if you want support for Bosch M_CAN controller framework. |
| 6 | 6 | This is common support for devices that embed the Bosch M_CAN IP. |
| 7 | 7 | |
| @@ -9,7 +9,7 @@ config CAN_M_CAN_PLATFORM · 1 unmodified line | ||
| 9 | 9 | tristate "Bosch M_CAN support for io-mapped devices" |
| 10 | 10 | depends on HAS_IOMEM |
| 11 | 11 | depends on CAN_M_CAN |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | Say Y here if you want support for IO Mapped Bosch M_CAN controller. |
| 14 | 14 | This support is for devices that have the Bosch M_CAN controller |
| 15 | 15 | IP embedded into the device and the IP is IO Mapped to the processor. |
| @@ -18,7 +18,7 @@ config CAN_M_CAN_TCAN4X5X · 2 unmodified lines | ||
| 18 | 18 | depends on CAN_M_CAN |
| 19 | 19 | depends on REGMAP_SPI |
| 20 | 20 | tristate "TCAN4X5X M_CAN device" |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | Say Y here if you want support for Texas Instruments TCAN4x5x |
| 23 | 23 | M_CAN controller. This device is a peripherial device that uses the |
| 24 | 24 | SPI bus for communication. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config CAN_MSCAN |
| 3 | 3 | depends on PPC |
| 4 | 4 | tristate "Support for Freescale MSCAN based chips" |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | The Motorola Scalable Controller Area Network (MSCAN) definition |
| 7 | 7 | is based on the MSCAN12 definition which is the specific |
| 8 | 8 | implementation of the Motorola Scalable CAN concept targeted for |
| @@ -13,7 +13,7 @@ if CAN_MSCAN · 4 unmodified lines | ||
| 13 | 13 | config CAN_MPC5XXX |
| 14 | 14 | tristate "Freescale MPC5xxx onboard CAN controller" |
| 15 | 15 | depends on (PPC_MPC52xx || PPC_MPC512x) |
| 16 | − ---help--- | |
| 16 | + help | |
| 17 | 17 | If you say yes here you get support for Freescale's MPC5xxx |
| 18 | 18 | onboard CAN controller. Currently, the MPC5200, MPC5200B and |
| 19 | 19 | MPC5121 (Rev. 2 and later) are supported. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config CAN_PEAK_PCIEFD |
| 3 | 3 | depends on PCI |
| 4 | 4 | tristate "PEAK-System PCAN-PCIe FD cards" |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This driver adds support for the PEAK-System PCI Express FD |
| 7 | 7 | CAN-FD cards family. |
| 8 | 8 | These 1x or 2x CAN-FD channels cards offer CAN 2.0 a/b as well as |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config CAN_RCAR |
| 3 | 3 | tristate "Renesas R-Car CAN controller" |
| 4 | 4 | depends on ARCH_RENESAS || ARM |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | Say Y here if you want to use CAN controller found on Renesas R-Car |
| 7 | 7 | SoCs. |
| 8 | 8 | |
| @@ -12,7 +12,7 @@ config CAN_RCAR · 3 unmodified lines | ||
| 12 | 12 | config CAN_RCAR_CANFD |
| 13 | 13 | tristate "Renesas R-Car CAN FD controller" |
| 14 | 14 | depends on ARCH_RENESAS || ARM |
| 15 | − ---help--- | |
| 15 | + help | |
| 16 | 16 | Say Y here if you want to use CAN FD controller found on |
| 17 | 17 | Renesas R-Car SoCs. The driver puts the controller in CAN FD only |
| 18 | 18 | mode, which can interoperate with CAN2.0 nodes but does not support |
| @@ -9,7 +9,7 @@ if CAN_SJA1000 · 8 unmodified lines | ||
| 9 | 9 | config CAN_EMS_PCI |
| 10 | 10 | tristate "EMS CPC-PCI, CPC-PCIe and CPC-104P Card" |
| 11 | 11 | depends on PCI |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | This driver is for the one, two or four channel CPC-PCI, |
| 14 | 14 | CPC-PCIe and CPC-104P cards from EMS Dr. Thomas Wuensche |
| 15 | 15 | (http://www.ems-wuensche.de). |
| @@ -17,7 +17,7 @@ config CAN_EMS_PCI · 1 unmodified line | ||
| 17 | 17 | config CAN_EMS_PCMCIA |
| 18 | 18 | tristate "EMS CPC-CARD Card" |
| 19 | 19 | depends on PCMCIA |
| 20 | − ---help--- | |
| 20 | + help | |
| 21 | 21 | This driver is for the one or two channel CPC-CARD cards from |
| 22 | 22 | EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de). |
| 23 | 23 | |
| @@ -34,14 +34,14 @@ config CAN_F81601 · 10 unmodified lines | ||
| 34 | 34 | config CAN_KVASER_PCI |
| 35 | 35 | tristate "Kvaser PCIcanx and Kvaser PCIcan PCI Cards" |
| 36 | 36 | depends on PCI |
| 37 | − ---help--- | |
| 37 | + help | |
| 38 | 38 | This driver is for the PCIcanx and PCIcan cards (1, 2 or |
| 39 | 39 | 4 channel) from Kvaser (http://www.kvaser.com). |
| 40 | 40 | |
| 41 | 41 | config CAN_PEAK_PCI |
| 42 | 42 | tristate "PEAK PCAN-PCI/PCIe/miniPCI Cards" |
| 43 | 43 | depends on PCI |
| 44 | − ---help--- | |
| 44 | + help | |
| 45 | 45 | This driver is for the PCAN-PCI/PCIe/miniPCI cards |
| 46 | 46 | (1, 2, 3 or 4 channels) from PEAK-System Technik |
| 47 | 47 | (http://www.peak-system.com). |
| @@ -52,7 +52,7 @@ config CAN_PEAK_PCIEC · 4 unmodified lines | ||
| 52 | 52 | select I2C |
| 53 | 53 | select I2C_ALGOBIT |
| 54 | 54 | default y |
| 55 | − ---help--- | |
| 55 | + help | |
| 56 | 56 | Say Y here if you want to use a PCAN-ExpressCard from PEAK-System |
| 57 | 57 | Technik. This will also automatically select I2C and I2C_ALGO |
| 58 | 58 | configuration options. |
| @@ -61,7 +61,7 @@ config CAN_PEAK_PCMCIA · 2 unmodified lines | ||
| 61 | 61 | tristate "PEAK PCAN-PC Card" |
| 62 | 62 | depends on PCMCIA |
| 63 | 63 | depends on HAS_IOPORT_MAP |
| 64 | − ---help--- | |
| 64 | + help | |
| 65 | 65 | This driver is for the PCAN-PC Card PCMCIA adapter (1 or 2 channels) |
| 66 | 66 | from PEAK-System (http://www.peak-system.com). To compile this |
| 67 | 67 | driver as a module, choose M here: the module will be called |
| @@ -70,7 +70,7 @@ config CAN_PEAK_PCMCIA · 2 unmodified lines | ||
| 70 | 70 | config CAN_PLX_PCI |
| 71 | 71 | tristate "PLX90xx PCI-bridge based Cards" |
| 72 | 72 | depends on PCI |
| 73 | − ---help--- | |
| 73 | + help | |
| 74 | 74 | This driver is for CAN interface cards based on |
| 75 | 75 | the PLX90xx PCI bridge. |
| 76 | 76 | Driver supports now: |
| @@ -87,13 +87,13 @@ config CAN_PLX_PCI · 10 unmodified lines | ||
| 87 | 87 | |
| 88 | 88 | config CAN_SJA1000_ISA |
| 89 | 89 | tristate "ISA Bus based legacy SJA1000 driver" |
| 90 | − ---help--- | |
| 90 | + help | |
| 91 | 91 | This driver adds legacy support for SJA1000 chips connected to |
| 92 | 92 | the ISA bus using I/O port, memory mapped or indirect access. |
| 93 | 93 | |
| 94 | 94 | config CAN_SJA1000_PLATFORM |
| 95 | 95 | tristate "Generic Platform Bus based SJA1000 driver" |
| 96 | − ---help--- | |
| 96 | + help | |
| 97 | 97 | This driver adds support for the SJA1000 chips connected to |
| 98 | 98 | the "platform bus" (Linux abstraction for directly to the |
| 99 | 99 | processor attached devices). Which can be found on various |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config CAN_SOFTING |
| 3 | 3 | tristate "Softing Gmbh CAN generic support" |
| 4 | 4 | depends on HAS_IOMEM |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | Support for CAN cards from Softing Gmbh & some cards |
| 7 | 7 | from Vector Gmbh. |
| 8 | 8 | Softing Gmbh CAN cards come with 1 or 2 physical busses. |
| @@ -20,7 +20,7 @@ config CAN_SOFTING_CS · 11 unmodified lines | ||
| 20 | 20 | tristate "Softing Gmbh CAN pcmcia cards" |
| 21 | 21 | depends on PCMCIA |
| 22 | 22 | depends on CAN_SOFTING |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | Support for PCMCIA cards from Softing Gmbh & some cards |
| 25 | 25 | from Vector Gmbh. |
| 26 | 26 | You need firmware for these, which you can get at |
| @@ -5,13 +5,13 @@ menu "CAN SPI interfaces" · 4 unmodified lines | ||
| 5 | 5 | config CAN_HI311X |
| 6 | 6 | tristate "Holt HI311x SPI CAN controllers" |
| 7 | 7 | depends on CAN_DEV && SPI && HAS_DMA |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | Driver for the Holt HI311x SPI CAN controllers. |
| 10 | 10 | |
| 11 | 11 | config CAN_MCP251X |
| 12 | 12 | tristate "Microchip MCP251x and MCP25625 SPI CAN controllers" |
| 13 | 13 | depends on HAS_DMA |
| 14 | − ---help--- | |
| 14 | + help | |
| 15 | 15 | Driver for the Microchip MCP251x and MCP25625 SPI CAN |
| 16 | 16 | controllers. |
| 17 | 17 | |
| @@ -4,25 +4,25 @@ menu "CAN USB interfaces" · 3 unmodified lines | ||
| 4 | 4 | |
| 5 | 5 | config CAN_8DEV_USB |
| 6 | 6 | tristate "8 devices USB2CAN interface" |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | This driver supports the USB2CAN interface |
| 9 | 9 | from 8 devices (http://www.8devices.com). |
| 10 | 10 | |
| 11 | 11 | config CAN_EMS_USB |
| 12 | 12 | tristate "EMS CPC-USB/ARM7 CAN/USB interface" |
| 13 | − ---help--- | |
| 13 | + help | |
| 14 | 14 | This driver is for the one channel CPC-USB/ARM7 CAN/USB interface |
| 15 | 15 | from EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de). |
| 16 | 16 | |
| 17 | 17 | config CAN_ESD_USB2 |
| 18 | 18 | tristate "ESD USB/2 CAN/USB interface" |
| 19 | − ---help--- | |
| 19 | + help | |
| 20 | 20 | This driver supports the CAN-USB/2 interface |
| 21 | 21 | from esd electronic system design gmbh (http://www.esd.eu). |
| 22 | 22 | |
| 23 | 23 | config CAN_GS_USB |
| 24 | 24 | tristate "Geschwister Schneider UG interfaces" |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | This driver supports the Geschwister Schneider and bytewerk.org |
| 27 | 27 | candleLight USB CAN interfaces USB/CAN devices |
| 28 | 28 | If unsure choose N, |
| @@ -31,7 +31,7 @@ config CAN_GS_USB · 2 unmodified lines | ||
| 31 | 31 | |
| 32 | 32 | config CAN_KVASER_USB |
| 33 | 33 | tristate "Kvaser CAN/USB interface" |
| 34 | − ---help--- | |
| 34 | + help | |
| 35 | 35 | This driver adds support for Kvaser CAN/USB devices like Kvaser |
| 36 | 36 | Leaf Light, Kvaser USBcan II and Kvaser Memorator Pro 5xHS. |
| 37 | 37 | |
| @@ -82,13 +82,13 @@ config CAN_KVASER_USB · 44 unmodified lines | ||
| 82 | 82 | |
| 83 | 83 | config CAN_MCBA_USB |
| 84 | 84 | tristate "Microchip CAN BUS Analyzer interface" |
| 85 | − ---help--- | |
| 85 | + help | |
| 86 | 86 | This driver supports the CAN BUS Analyzer interface |
| 87 | 87 | from Microchip (http://www.microchip.com/development-tools/). |
| 88 | 88 | |
| 89 | 89 | config CAN_PEAK_USB |
| 90 | 90 | tristate "PEAK PCAN-USB/USB Pro interfaces for CAN 2.0b/CAN-FD" |
| 91 | − ---help--- | |
| 91 | + help | |
| 92 | 92 | This driver supports the PEAK-System Technik USB adapters that enable |
| 93 | 93 | access to the CAN bus, with repect to the CAN 2.0b and/or CAN-FD |
| 94 | 94 | standards, that is: |
| @@ -104,7 +104,7 @@ config CAN_PEAK_USB · 9 unmodified lines | ||
| 104 | 104 | |
| 105 | 105 | config CAN_UCAN |
| 106 | 106 | tristate "Theobroma Systems UCAN interface" |
| 107 | − ---help--- | |
| 107 | + help | |
| 108 | 108 | This driver supports the Theobroma Systems |
| 109 | 109 | UCAN USB-CAN interface. |
| 110 | 110 | |
| @@ -12,7 +12,7 @@ config NET_DSA_BCM_SF2 · 11 unmodified lines | ||
| 12 | 12 | select BCM7XXX_PHY |
| 13 | 13 | select MDIO_BCM_UNIMAC |
| 14 | 14 | select B53 |
| 15 | − ---help--- | |
| 15 | + help | |
| 16 | 16 | This enables support for the Broadcom Starfighter 2 Ethernet |
| 17 | 17 | switch chips. |
| 18 | 18 | |
| @@ -20,7 +20,7 @@ config NET_DSA_LOOP · 1 unmodified line | ||
| 20 | 20 | tristate "DSA mock-up Ethernet switch chip support" |
| 21 | 21 | depends on NET_DSA |
| 22 | 22 | select FIXED_PHY |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | This enables support for a fake mock-up switch chip which |
| 25 | 25 | exercises the DSA APIs. |
| 26 | 26 | |
| @@ -28,7 +28,7 @@ config NET_DSA_LANTIQ_GSWIP · 1 unmodified line | ||
| 28 | 28 | tristate "Lantiq / Intel GSWIP" |
| 29 | 29 | depends on HAS_IOMEM && NET_DSA |
| 30 | 30 | select NET_DSA_TAG_GSWIP |
| 31 | − ---help--- | |
| 31 | + help | |
| 32 | 32 | This enables support for the Lantiq / Intel GSWIP 2.1 found in |
| 33 | 33 | the xrx200 / VR9 SoC. |
| 34 | 34 | |
| @@ -36,7 +36,7 @@ config NET_DSA_MT7530 · 1 unmodified line | ||
| 36 | 36 | tristate "Mediatek MT7530 Ethernet switch support" |
| 37 | 37 | depends on NET_DSA |
| 38 | 38 | select NET_DSA_TAG_MTK |
| 39 | − ---help--- | |
| 39 | + help | |
| 40 | 40 | This enables support for the Mediatek MT7530 Ethernet switch |
| 41 | 41 | chip. |
| 42 | 42 | |
| @@ -44,7 +44,7 @@ config NET_DSA_MV88E6060 · 1 unmodified line | ||
| 44 | 44 | tristate "Marvell 88E6060 ethernet switch chip support" |
| 45 | 45 | depends on NET_DSA |
| 46 | 46 | select NET_DSA_TAG_TRAILER |
| 47 | − ---help--- | |
| 47 | + help | |
| 48 | 48 | This enables support for the Marvell 88E6060 ethernet switch |
| 49 | 49 | chip. |
| 50 | 50 | |
| @@ -63,7 +63,7 @@ config NET_DSA_QCA8K · 12 unmodified lines | ||
| 63 | 63 | depends on NET_DSA |
| 64 | 64 | select NET_DSA_TAG_QCA |
| 65 | 65 | select REGMAP |
| 66 | − ---help--- | |
| 66 | + help | |
| 67 | 67 | This enables support for the Qualcomm Atheros QCA8K Ethernet |
| 68 | 68 | switch chips. |
| 69 | 69 | |
| @@ -74,7 +74,7 @@ config NET_DSA_REALTEK_SMI · 4 unmodified lines | ||
| 74 | 74 | select IRQ_DOMAIN |
| 75 | 75 | select REALTEK_PHY |
| 76 | 76 | select REGMAP |
| 77 | − ---help--- | |
| 77 | + help | |
| 78 | 78 | This enables support for the Realtek SMI-based switch |
| 79 | 79 | chips, currently only RTL8366RB. |
| 80 | 80 | |
| @@ -82,7 +82,7 @@ config NET_DSA_SMSC_LAN9303 · 1 unmodified line | ||
| 82 | 82 | tristate |
| 83 | 83 | select NET_DSA_TAG_LAN9303 |
| 84 | 84 | select REGMAP |
| 85 | − ---help--- | |
| 85 | + help | |
| 86 | 86 | This enables support for the SMSC/Microchip LAN9303 3 port ethernet |
| 87 | 87 | switch chips. |
| 88 | 88 | |
| @@ -91,7 +91,7 @@ config NET_DSA_SMSC_LAN9303_I2C · 2 unmodified lines | ||
| 91 | 91 | depends on NET_DSA && I2C |
| 92 | 92 | select NET_DSA_SMSC_LAN9303 |
| 93 | 93 | select REGMAP_I2C |
| 94 | − ---help--- | |
| 94 | + help | |
| 95 | 95 | Enable access functions if the SMSC/Microchip LAN9303 is configured |
| 96 | 96 | for I2C managed mode. |
| 97 | 97 | |
| @@ -99,7 +99,7 @@ config NET_DSA_SMSC_LAN9303_MDIO · 1 unmodified line | ||
| 99 | 99 | tristate "SMSC/Microchip LAN9303 3-ports 10/100 ethernet switch in MDIO managed mode" |
| 100 | 100 | depends on NET_DSA |
| 101 | 101 | select NET_DSA_SMSC_LAN9303 |
| 102 | − ---help--- | |
| 102 | + help | |
| 103 | 103 | Enable access functions if the SMSC/Microchip LAN9303 is configured |
| 104 | 104 | for MDIO managed mode. |
| 105 | 105 | |
| @@ -109,7 +109,7 @@ config NET_DSA_VITESSE_VSC73XX · 3 unmodified lines | ||
| 109 | 109 | select FIXED_PHY |
| 110 | 110 | select VITESSE_PHY |
| 111 | 111 | select GPIOLIB |
| 112 | − ---help--- | |
| 112 | + help | |
| 113 | 113 | This enables support for the Vitesse VSC7385, VSC7388, |
| 114 | 114 | VSC7395 and VSC7398 SparX integrated ethernet switches. |
| 115 | 115 | |
| @@ -118,7 +118,7 @@ config NET_DSA_VITESSE_VSC73XX_SPI · 2 unmodified lines | ||
| 118 | 118 | depends on NET_DSA |
| 119 | 119 | depends on SPI |
| 120 | 120 | select NET_DSA_VITESSE_VSC73XX |
| 121 | − ---help--- | |
| 121 | + help | |
| 122 | 122 | This enables support for the Vitesse VSC7385, VSC7388, VSC7395 |
| 123 | 123 | and VSC7398 SparX integrated ethernet switches in SPI managed mode. |
| 124 | 124 | |
| @@ -127,7 +127,7 @@ config NET_DSA_VITESSE_VSC73XX_PLATFORM · 2 unmodified lines | ||
| 127 | 127 | depends on NET_DSA |
| 128 | 128 | depends on HAS_IOMEM |
| 129 | 129 | select NET_DSA_VITESSE_VSC73XX |
| 130 | − ---help--- | |
| 130 | + help | |
| 131 | 131 | This enables support for the Vitesse VSC7385, VSC7388, VSC7395 |
| 132 | 132 | and VSC7398 SparX integrated ethernet switches, connected over |
| 133 | 133 | a CPU-attached address bus and work in memory-mapped I/O mode. |
| @@ -4,6 +4,6 @@ config NET_DSA_AR9331 · 3 unmodified lines | ||
| 4 | 4 | depends on NET_DSA |
| 5 | 5 | select NET_DSA_TAG_AR9331 |
| 6 | 6 | select REGMAP |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | This enables support for the Qualcomm Atheros AR9331 built-in Ethernet |
| 9 | 9 | switch. |
| @@ -7,7 +7,7 @@ config NET_VENDOR_3COM · 6 unmodified lines | ||
| 7 | 7 | bool "3Com devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on ISA || EISA || PCI || PCMCIA |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ if NET_VENDOR_3COM · 6 unmodified lines | ||
| 20 | 20 | config EL3 |
| 21 | 21 | tristate "3c509/3c579 \"EtherLink III\" support" |
| 22 | 22 | depends on (ISA || EISA) |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | If you have a network (Ethernet) card belonging to the 3Com |
| 25 | 25 | EtherLinkIII series, say Y here. |
| 26 | 26 | |
| @@ -34,7 +34,7 @@ config EL3 · 7 unmodified lines | ||
| 34 | 34 | config 3C515 |
| 35 | 35 | tristate "3c515 ISA \"Fast EtherLink\"" |
| 36 | 36 | depends on ISA && ISA_DMA_API && !PPC32 |
| 37 | − ---help--- | |
| 37 | + help | |
| 38 | 38 | If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet |
| 39 | 39 | network card, say Y here. |
| 40 | 40 | |
| @@ -44,7 +44,7 @@ config 3C515 · 3 unmodified lines | ||
| 44 | 44 | config PCMCIA_3C574 |
| 45 | 45 | tristate "3Com 3c574 PCMCIA support" |
| 46 | 46 | depends on PCMCIA |
| 47 | − ---help--- | |
| 47 | + help | |
| 48 | 48 | Say Y here if you intend to attach a 3Com 3c574 or compatible PCMCIA |
| 49 | 49 | (PC-card) Fast Ethernet card to your computer. |
| 50 | 50 | |
| @@ -54,7 +54,7 @@ config PCMCIA_3C574 · 3 unmodified lines | ||
| 54 | 54 | config PCMCIA_3C589 |
| 55 | 55 | tristate "3Com 3c589 PCMCIA support" |
| 56 | 56 | depends on PCMCIA |
| 57 | − ---help--- | |
| 57 | + help | |
| 58 | 58 | Say Y here if you intend to attach a 3Com 3c589 or compatible PCMCIA |
| 59 | 59 | (PC-card) Ethernet card to your computer. |
| 60 | 60 | |
| @@ -65,7 +65,7 @@ config VORTEX · 4 unmodified lines | ||
| 65 | 65 | tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support" |
| 66 | 66 | depends on (PCI || EISA) && HAS_IOPORT_MAP |
| 67 | 67 | select MII |
| 68 | − ---help--- | |
| 68 | + help | |
| 69 | 69 | This option enables driver support for a large number of 10Mbps and |
| 70 | 70 | 10/100Mbps EISA, PCI and Cardbus 3Com network cards: |
| 71 | 71 | |
| @@ -86,7 +86,7 @@ config TYPHOON · 14 unmodified lines | ||
| 86 | 86 | tristate "3cr990 series \"Typhoon\" support" |
| 87 | 87 | depends on PCI |
| 88 | 88 | select CRC32 |
| 89 | − ---help--- | |
| 89 | + help | |
| 90 | 90 | This option enables driver support for the 3cr990 series of cards: |
| 91 | 91 | |
| 92 | 92 | 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97, |
| @@ -7,7 +7,7 @@ config NET_VENDOR_8390 · 6 unmodified lines | ||
| 7 | 7 | bool "National Semiconductor 8390 devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on NET_VENDOR_NATSEMI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ if NET_VENDOR_8390 · 6 unmodified lines | ||
| 20 | 20 | config PCMCIA_AXNET |
| 21 | 21 | tristate "Asix AX88190 PCMCIA support" |
| 22 | 22 | depends on PCMCIA |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | Say Y here if you intend to attach an Asix AX88190-based PCMCIA |
| 25 | 25 | (PC-card) Fast Ethernet card to your computer. These cards are |
| 26 | 26 | nearly NE2000 compatible but need a separate driver due to a few |
| @@ -35,7 +35,7 @@ config AX88796 · 8 unmodified lines | ||
| 35 | 35 | select CRC32 |
| 36 | 36 | select PHYLIB |
| 37 | 37 | select MDIO_BITBANG |
| 38 | − ---help--- | |
| 38 | + help | |
| 39 | 39 | AX88796 driver, using platform bus to provide |
| 40 | 40 | chip detection and resources |
| 41 | 41 | |
| @@ -43,7 +43,7 @@ config AX88796_93CX6 · 1 unmodified line | ||
| 43 | 43 | bool "ASIX AX88796 external 93CX6 eeprom support" |
| 44 | 44 | depends on AX88796 |
| 45 | 45 | select EEPROM_93CX6 |
| 46 | − ---help--- | |
| 46 | + help | |
| 47 | 47 | Select this if your platform comes with an external 93CX6 eeprom. |
| 48 | 48 | |
| 49 | 49 | config XSURF100 |
| @@ -63,7 +63,7 @@ config HYDRA · 13 unmodified lines | ||
| 63 | 63 | tristate "Hydra support" |
| 64 | 64 | depends on ZORRO |
| 65 | 65 | select CRC32 |
| 66 | − ---help--- | |
| 66 | + help | |
| 67 | 67 | If you have a Hydra Ethernet adapter, say Y. Otherwise, say N. |
| 68 | 68 | |
| 69 | 69 | To compile this driver as a module, choose M here: the module |
| @@ -73,7 +73,7 @@ config ARM_ETHERH · 3 unmodified lines | ||
| 73 | 73 | tristate "I-cubed EtherH/ANT EtherM support" |
| 74 | 74 | depends on ARM && ARCH_ACORN |
| 75 | 75 | select CRC32 |
| 76 | − ---help--- | |
| 76 | + help | |
| 77 | 77 | If you have an Acorn system with one of these network cards, you |
| 78 | 78 | should say Y to this option if you wish to use it with Linux. |
| 79 | 79 | |
| @@ -81,7 +81,7 @@ config MAC8390 · 1 unmodified line | ||
| 81 | 81 | tristate "Macintosh NS 8390 based ethernet cards" |
| 82 | 82 | depends on MAC |
| 83 | 83 | select CRC32 |
| 84 | − ---help--- | |
| 84 | + help | |
| 85 | 85 | If you want to include a driver to support Nubus or LC-PDS |
| 86 | 86 | Ethernet cards using an NS8390 chipset or its equivalent, say Y. |
| 87 | 87 | |
| @@ -89,7 +89,7 @@ config MCF8390 · 1 unmodified line | ||
| 89 | 89 | tristate "ColdFire NS8390 based Ethernet support" |
| 90 | 90 | depends on COLDFIRE |
| 91 | 91 | select CRC32 |
| 92 | − ---help--- | |
| 92 | + help | |
| 93 | 93 | This driver is for Ethernet devices using an NS8390-compatible |
| 94 | 94 | chipset on many common ColdFire CPU based boards. Many of the older |
| 95 | 95 | Freescale dev boards use this, and some other common boards like |
| @@ -103,7 +103,7 @@ config NE2000 · 7 unmodified lines | ||
| 103 | 103 | tristate "NE2000/NE1000 support" |
| 104 | 104 | depends on (ISA || (Q40 && m) || MACH_TX49XX || ATARI_ETHERNEC) |
| 105 | 105 | select CRC32 |
| 106 | − ---help--- | |
| 106 | + help | |
| 107 | 107 | If you have a network (Ethernet) card of this type, say Y here. |
| 108 | 108 | Many Ethernet cards without a specific driver are compatible with |
| 109 | 109 | the NE2000. |
| @@ -118,7 +118,7 @@ config NE2K_PCI · 8 unmodified lines | ||
| 118 | 118 | tristate "PCI NE2000 and clones support (see help)" |
| 119 | 119 | depends on PCI |
| 120 | 120 | select CRC32 |
| 121 | − ---help--- | |
| 121 | + help | |
| 122 | 122 | This driver is for NE2000 compatible PCI cards. It will not work |
| 123 | 123 | with ISA NE2000 cards (they have their own driver, "NE2000/NE1000 |
| 124 | 124 | support" below). If you have a PCI NE2000 network (Ethernet) card, |
| @@ -136,7 +136,7 @@ config APNE · 11 unmodified lines | ||
| 136 | 136 | tristate "PCMCIA NE2000 support" |
| 137 | 137 | depends on AMIGA_PCMCIA |
| 138 | 138 | select CRC32 |
| 139 | − ---help--- | |
| 139 | + help | |
| 140 | 140 | If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise, |
| 141 | 141 | say N. |
| 142 | 142 | |
| @@ -147,7 +147,7 @@ config PCMCIA_PCNET · 4 unmodified lines | ||
| 147 | 147 | tristate "NE2000 compatible PCMCIA support" |
| 148 | 148 | depends on PCMCIA |
| 149 | 149 | select CRC32 |
| 150 | − ---help--- | |
| 150 | + help | |
| 151 | 151 | Say Y here if you intend to attach an NE2000 compatible PCMCIA |
| 152 | 152 | (PC-card) Ethernet or Fast Ethernet card to your computer. |
| 153 | 153 | |
| @@ -158,7 +158,7 @@ config STNIC · 4 unmodified lines | ||
| 158 | 158 | tristate "National DP83902AV support" |
| 159 | 159 | depends on SUPERH |
| 160 | 160 | select CRC32 |
| 161 | − ---help--- | |
| 161 | + help | |
| 162 | 162 | Support for cards based on the National Semiconductor DP83902AV |
| 163 | 163 | ST-NIC Serial Network Interface Controller for Twisted Pair. This |
| 164 | 164 | is a 10Mbit/sec Ethernet controller. Product overview and specs at |
| @@ -170,7 +170,7 @@ config ULTRA · 5 unmodified lines | ||
| 170 | 170 | tristate "SMC Ultra support" |
| 171 | 171 | depends on ISA |
| 172 | 172 | select CRC32 |
| 173 | − ---help--- | |
| 173 | + help | |
| 174 | 174 | If you have a network (Ethernet) card of this type, say Y here. |
| 175 | 175 | |
| 176 | 176 | Important: There have been many reports that, with some motherboards |
| @@ -187,7 +187,7 @@ config WD80x3 · 10 unmodified lines | ||
| 187 | 187 | tristate "WD80*3 support" |
| 188 | 188 | depends on ISA |
| 189 | 189 | select CRC32 |
| 190 | − ---help--- | |
| 190 | + help | |
| 191 | 191 | If you have a network (Ethernet) card of this type, say Y here. |
| 192 | 192 | |
| 193 | 193 | To compile this driver as a module, choose M here. The module |
| @@ -197,7 +197,7 @@ config ZORRO8390 · 3 unmodified lines | ||
| 197 | 197 | tristate "Zorro NS8390-based Ethernet support" |
| 198 | 198 | depends on ZORRO |
| 199 | 199 | select CRC32 |
| 200 | − ---help--- | |
| 200 | + help | |
| 201 | 201 | This driver is for Zorro Ethernet cards using an NS8390-compatible |
| 202 | 202 | chipset, like the Village Tronic Ariadne II and the Individual |
| 203 | 203 | Computers X-Surf Ethernet cards. If you have such a card, say Y. |
| @@ -7,7 +7,7 @@ menuconfig ETHERNET · 6 unmodified lines | ||
| 7 | 7 | bool "Ethernet driver support" |
| 8 | 8 | depends on NET |
| 9 | 9 | default y |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | This section contains all the Ethernet device drivers. |
| 12 | 12 | |
| 13 | 13 | if ETHERNET |
| @@ -48,7 +48,7 @@ config CX_ECAT · 34 unmodified lines | ||
| 48 | 48 | tristate "Beckhoff CX5020 EtherCAT master support" |
| 49 | 49 | depends on PCI |
| 50 | 50 | depends on X86 || COMPILE_TEST |
| 51 | − ---help--- | |
| 51 | + help | |
| 52 | 52 | Driver for EtherCAT master module located on CCAT FPGA |
| 53 | 53 | that can be found on Beckhoff CX5020, and possibly other of CX |
| 54 | 54 | Beckhoff CX series industrial PCs. |
| @@ -62,7 +62,7 @@ config DNET · 7 unmodified lines | ||
| 62 | 62 | tristate "Dave ethernet support (DNET)" |
| 63 | 63 | depends on HAS_IOMEM |
| 64 | 64 | select PHYLIB |
| 65 | − ---help--- | |
| 65 | + help | |
| 66 | 66 | The Dave ethernet interface (DNET) is found on Qong Board FPGA. |
| 67 | 67 | Say Y to include support for the DNET chip. |
| 68 | 68 | |
| @@ -89,7 +89,7 @@ config JME · 20 unmodified lines | ||
| 89 | 89 | depends on PCI |
| 90 | 90 | select CRC32 |
| 91 | 91 | select MII |
| 92 | − ---help--- | |
| 92 | + help | |
| 93 | 93 | This driver supports the PCI-Express gigabit ethernet adapters |
| 94 | 94 | based on JMicron JMC250 chipset. |
| 95 | 95 | |
| @@ -99,20 +99,20 @@ config JME · 3 unmodified lines | ||
| 99 | 99 | config KORINA |
| 100 | 100 | tristate "Korina (IDT RC32434) Ethernet support" |
| 101 | 101 | depends on MIKROTIK_RB532 |
| 102 | − ---help--- | |
| 102 | + help | |
| 103 | 103 | If you have a Mikrotik RouterBoard 500 or IDT RC32434 |
| 104 | 104 | based system say Y. Otherwise say N. |
| 105 | 105 | |
| 106 | 106 | config LANTIQ_ETOP |
| 107 | 107 | tristate "Lantiq SoC ETOP driver" |
| 108 | 108 | depends on SOC_TYPE_XWAY |
| 109 | − ---help--- | |
| 109 | + help | |
| 110 | 110 | Support for the MII0 inside the Lantiq SoC |
| 111 | 111 | |
| 112 | 112 | config LANTIQ_XRX200 |
| 113 | 113 | tristate "Lantiq / Intel xRX200 PMAC network driver" |
| 114 | 114 | depends on SOC_TYPE_XWAY |
| 115 | − ---help--- | |
| 115 | + help | |
| 116 | 116 | Support for the PMAC of the Gigabit switch (GSWIP) inside the |
| 117 | 117 | Lantiq / Intel VRX200 VDSL SoC |
| 118 | 118 | |
| @@ -130,7 +130,7 @@ config FEALNX · 11 unmodified lines | ||
| 130 | 130 | depends on PCI |
| 131 | 131 | select CRC32 |
| 132 | 132 | select MII |
| 133 | − ---help--- | |
| 133 | + help | |
| 134 | 134 | Say Y here to support the Myson MTD-800 family of PCI-based Ethernet |
| 135 | 135 | cards. <http://www.myson.com.tw/> |
| 136 | 136 | |
| @@ -150,7 +150,7 @@ config ETHOC · 13 unmodified lines | ||
| 150 | 150 | select PHYLIB |
| 151 | 151 | select CRC32 |
| 152 | 152 | select BITREVERSE |
| 153 | − ---help--- | |
| 153 | + help | |
| 154 | 154 | Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC. |
| 155 | 155 | |
| 156 | 156 | source "drivers/net/ethernet/packetengines/Kconfig" |
| @@ -7,7 +7,7 @@ config NET_VENDOR_ADAPTEC · 6 unmodified lines | ||
| 7 | 7 | bool "Adaptec devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -22,7 +22,7 @@ config ADAPTEC_STARFIRE · 8 unmodified lines | ||
| 22 | 22 | depends on PCI |
| 23 | 23 | select CRC32 |
| 24 | 24 | select MII |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network |
| 27 | 27 | adapter. The DuraLAN chip is used on the 64 bit PCI boards from |
| 28 | 28 | Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip |
| @@ -8,5 +8,5 @@ config GRETH · 7 unmodified lines | ||
| 8 | 8 | depends on SPARC |
| 9 | 9 | select PHYLIB |
| 10 | 10 | select CRC32 |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC. |
| @@ -7,7 +7,7 @@ config NET_VENDOR_AGERE · 6 unmodified lines | ||
| 7 | 7 | bool "Agere devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -21,7 +21,7 @@ config ET131X · 7 unmodified lines | ||
| 21 | 21 | tristate "Agere ET-1310 Gigabit Ethernet support" |
| 22 | 22 | depends on PCI |
| 23 | 23 | select PHYLIB |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | This driver supports Agere ET-1310 ethernet adapters. |
| 26 | 26 | |
| 27 | 27 | To compile this driver as a module, choose M here. The module |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config NET_VENDOR_ALACRITECH |
| 3 | 3 | bool "Alacritech devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -16,7 +16,7 @@ config SLICOSS · 7 unmodified lines | ||
| 16 | 16 | tristate "Alacritech Slicoss support" |
| 17 | 17 | depends on PCI |
| 18 | 18 | select CRC32 |
| 19 | − ---help--- | |
| 19 | + help | |
| 20 | 20 | This driver supports Gigabit Ethernet adapters based on the |
| 21 | 21 | Session Layer Interface (SLIC) technology by Alacritech. |
| 22 | 22 | |
| @@ -8,7 +8,7 @@ config NET_VENDOR_ALLWINNER · 7 unmodified lines | ||
| 8 | 8 | default y |
| 9 | 9 | |
| 10 | 10 | depends on ARCH_SUNXI |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | If you have a network (Ethernet) card belonging to this |
| 13 | 13 | class, say Y here. |
| 14 | 14 | |
| @@ -28,7 +28,7 @@ config SUN4I_EMAC · 13 unmodified lines | ||
| 28 | 28 | select MII |
| 29 | 29 | select PHYLIB |
| 30 | 30 | select MDIO_SUN4I |
| 31 | − ---help--- | |
| 31 | + help | |
| 32 | 32 | Support for Allwinner A10 EMAC ethernet driver. |
| 33 | 33 | |
| 34 | 34 | To compile this driver as a module, choose M here. The module |
| @@ -7,7 +7,7 @@ config NET_VENDOR_ALTEON · 6 unmodified lines | ||
| 7 | 7 | bool "Alteon devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ if NET_VENDOR_ALTEON · 6 unmodified lines | ||
| 20 | 20 | config ACENIC |
| 21 | 21 | tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support" |
| 22 | 22 | depends on PCI |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear |
| 25 | 25 | GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet |
| 26 | 26 | adapter. The driver allows for using the Jumbo Frame option (9000 |
| @@ -34,7 +34,7 @@ config ACENIC · 7 unmodified lines | ||
| 34 | 34 | config ACENIC_OMIT_TIGON_I |
| 35 | 35 | bool "Omit support for old Tigon I based AceNICs" |
| 36 | 36 | depends on ACENIC |
| 37 | − ---help--- | |
| 37 | + help | |
| 38 | 38 | Say Y here if you only have Tigon II based AceNICs and want to leave |
| 39 | 39 | out support for the older Tigon I based cards which are no longer |
| 40 | 40 | being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B |
| @@ -3,7 +3,7 @@ config ALTERA_TSE · 2 unmodified lines | ||
| 3 | 3 | tristate "Altera Triple-Speed Ethernet MAC support" |
| 4 | 4 | depends on HAS_DMA |
| 5 | 5 | select PHYLIB |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | This driver supports the Altera Triple-Speed (TSE) Ethernet MAC. |
| 8 | 8 | |
| 9 | 9 | To compile this driver as a module, choose M here. The module |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_AMAZON |
| 7 | 7 | bool "Amazon Devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) device belonging to this class, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ config ENA_ETHERNET · 7 unmodified lines | ||
| 20 | 20 | tristate "Elastic Network Adapter (ENA) support" |
| 21 | 21 | depends on PCI_MSI && !CPU_BIG_ENDIAN |
| 22 | 22 | select DIMLIB |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | This driver supports Elastic Network Adapter (ENA)" |
| 25 | 25 | |
| 26 | 26 | To compile this driver as a module, choose M here. |
| @@ -9,7 +9,7 @@ config NET_VENDOR_AMD · 8 unmodified lines | ||
| 9 | 9 | depends on DIO || MACH_DECSTATION || MVME147 || ATARI || SUN3 || \ |
| 10 | 10 | SUN3X || SBUS || PCI || ZORRO || (ISA && ISA_DMA_API) || \ |
| 11 | 11 | (ARM && ARCH_EBSA110) || ISA || EISA || PCMCIA || ARM64 |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | If you have a network (Ethernet) chipset belonging to this class, |
| 14 | 14 | say Y. |
| 15 | 15 | |
| @@ -24,7 +24,7 @@ config A2065 · 8 unmodified lines | ||
| 24 | 24 | tristate "A2065 support" |
| 25 | 25 | depends on ZORRO |
| 26 | 26 | select CRC32 |
| 27 | − ---help--- | |
| 27 | + help | |
| 28 | 28 | If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise, |
| 29 | 29 | say N. |
| 30 | 30 | |
| @@ -36,7 +36,7 @@ config AMD8111_ETH · 5 unmodified lines | ||
| 36 | 36 | depends on PCI |
| 37 | 37 | select CRC32 |
| 38 | 38 | select MII |
| 39 | − ---help--- | |
| 39 | + help | |
| 40 | 40 | If you have an AMD 8111-based PCI LANCE ethernet card, |
| 41 | 41 | answer Y here. |
| 42 | 42 | |
| @@ -46,7 +46,7 @@ config AMD8111_ETH · 3 unmodified lines | ||
| 46 | 46 | config LANCE |
| 47 | 47 | tristate "AMD LANCE and PCnet (AT1500 and NE2100) support" |
| 48 | 48 | depends on ISA && ISA_DMA_API && !ARM && !PPC32 |
| 49 | − ---help--- | |
| 49 | + help | |
| 50 | 50 | If you have a network (Ethernet) card of this type, say Y here. |
| 51 | 51 | Some LinkSys cards are of this type. |
| 52 | 52 | |
| @@ -58,7 +58,7 @@ config PCNET32 · 5 unmodified lines | ||
| 58 | 58 | depends on PCI |
| 59 | 59 | select CRC32 |
| 60 | 60 | select MII |
| 61 | − ---help--- | |
| 61 | + help | |
| 62 | 62 | If you have a PCnet32 or PCnetPCI based network (Ethernet) card, |
| 63 | 63 | answer Y here. |
| 64 | 64 | |
| @@ -68,7 +68,7 @@ config PCNET32 · 3 unmodified lines | ||
| 68 | 68 | config ARIADNE |
| 69 | 69 | tristate "Ariadne support" |
| 70 | 70 | depends on ZORRO |
| 71 | − ---help--- | |
| 71 | + help | |
| 72 | 72 | If you have a Village Tronic Ariadne Ethernet adapter, say Y. |
| 73 | 73 | Otherwise, say N. |
| 74 | 74 | |
| @@ -79,14 +79,14 @@ config ARM_AM79C961A · 4 unmodified lines | ||
| 79 | 79 | bool "ARM EBSA110 AM79C961A support" |
| 80 | 80 | depends on ARM && ARCH_EBSA110 |
| 81 | 81 | select CRC32 |
| 82 | − ---help--- | |
| 82 | + help | |
| 83 | 83 | If you wish to compile a kernel for the EBSA-110, then you should |
| 84 | 84 | always answer Y to this. |
| 85 | 85 | |
| 86 | 86 | config ATARILANCE |
| 87 | 87 | tristate "Atari LANCE support" |
| 88 | 88 | depends on ATARI |
| 89 | − ---help--- | |
| 89 | + help | |
| 90 | 90 | Say Y to include support for several Atari Ethernet adapters based |
| 91 | 91 | on the AMD LANCE chipset: RieblCard (with or without battery), or |
| 92 | 92 | PAMCard VME (also the version by Rhotron, with different addresses). |
| @@ -95,7 +95,7 @@ config DECLANCE · 2 unmodified lines | ||
| 95 | 95 | tristate "DEC LANCE ethernet controller support" |
| 96 | 96 | depends on MACH_DECSTATION |
| 97 | 97 | select CRC32 |
| 98 | − ---help--- | |
| 98 | + help | |
| 99 | 99 | This driver is for the series of Ethernet controllers produced by |
| 100 | 100 | DEC (now Compaq) based on the AMD LANCE chipset, including the |
| 101 | 101 | DEPCA series. (This chipset is better known via the NE2100 cards.) |
| @@ -104,7 +104,7 @@ config HPLANCE · 2 unmodified lines | ||
| 104 | 104 | tristate "HP on-board LANCE support" |
| 105 | 105 | depends on DIO |
| 106 | 106 | select CRC32 |
| 107 | − ---help--- | |
| 107 | + help | |
| 108 | 108 | If you want to use the builtin "LANCE" Ethernet controller on an |
| 109 | 109 | HP300 machine, say Y here. |
| 110 | 110 | |
| @@ -113,7 +113,7 @@ config MIPS_AU1X00_ENET · 2 unmodified lines | ||
| 113 | 113 | depends on MIPS_ALCHEMY |
| 114 | 114 | select PHYLIB |
| 115 | 115 | select CRC32 |
| 116 | − ---help--- | |
| 116 | + help | |
| 117 | 117 | If you have an Alchemy Semi AU1X00 based system |
| 118 | 118 | say Y. Otherwise, say N. |
| 119 | 119 | |
| @@ -121,7 +121,7 @@ config MVME147_NET · 1 unmodified line | ||
| 121 | 121 | tristate "MVME147 (LANCE) Ethernet support" |
| 122 | 122 | depends on MVME147 |
| 123 | 123 | select CRC32 |
| 124 | − ---help--- | |
| 124 | + help | |
| 125 | 125 | Support for the on-board Ethernet interface on the Motorola MVME147 |
| 126 | 126 | single-board computer. Say Y here to include the |
| 127 | 127 | driver for this chip in your kernel. |
| @@ -140,7 +140,7 @@ config PCMCIA_NMCLAN · 12 unmodified lines | ||
| 140 | 140 | config NI65 |
| 141 | 141 | tristate "NI6510 support" |
| 142 | 142 | depends on ISA && ISA_DMA_API && !ARM && !PPC32 |
| 143 | − ---help--- | |
| 143 | + help | |
| 144 | 144 | If you have a network (Ethernet) card of this type, say Y here. |
| 145 | 145 | |
| 146 | 146 | To compile this driver as a module, choose M here. The module |
| @@ -149,7 +149,7 @@ config NI65 · 2 unmodified lines | ||
| 149 | 149 | config SUN3LANCE |
| 150 | 150 | tristate "Sun3/Sun3x on-board LANCE support" |
| 151 | 151 | depends on (SUN3 || SUN3X) |
| 152 | − ---help--- | |
| 152 | + help | |
| 153 | 153 | Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80) |
| 154 | 154 | featured an AMD LANCE 10Mbit Ethernet controller on board; say Y |
| 155 | 155 | here to compile in the Linux driver for this and enable Ethernet. |
| @@ -163,7 +163,7 @@ config SUNLANCE · 7 unmodified lines | ||
| 163 | 163 | tristate "Sun LANCE support" |
| 164 | 164 | depends on SBUS |
| 165 | 165 | select CRC32 |
| 166 | − ---help--- | |
| 166 | + help | |
| 167 | 167 | This driver supports the "le" interface present on all 32-bit Sparc |
| 168 | 168 | systems, on some older Ultra systems and as an Sbus option. These |
| 169 | 169 | cards are based on the AMD LANCE chipset, which is better known |
| @@ -181,7 +181,7 @@ config AMD_XGBE · 11 unmodified lines | ||
| 181 | 181 | select PHYLIB |
| 182 | 182 | select AMD_XGBE_HAVE_ECC if X86 |
| 183 | 183 | imply PTP_1588_CLOCK |
| 184 | − ---help--- | |
| 184 | + help | |
| 185 | 185 | This driver supports the AMD 10GbE Ethernet device found on an |
| 186 | 186 | AMD SoC. |
| 187 | 187 | |
| @@ -192,7 +192,7 @@ config AMD_XGBE_DCB · 4 unmodified lines | ||
| 192 | 192 | bool "Data Center Bridging (DCB) support" |
| 193 | 193 | default n |
| 194 | 194 | depends on AMD_XGBE && DCB |
| 195 | − ---help--- | |
| 195 | + help | |
| 196 | 196 | Say Y here to enable Data Center Bridging (DCB) support in the |
| 197 | 197 | driver. |
| 198 | 198 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_APPLE · 6 unmodified lines | ||
| 7 | 7 | bool "Apple devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on (PPC_PMAC && PPC32) || MAC |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -21,7 +21,7 @@ config MACE · 7 unmodified lines | ||
| 21 | 21 | tristate "MACE (Power Mac ethernet) support" |
| 22 | 22 | depends on PPC_PMAC && PPC32 |
| 23 | 23 | select CRC32 |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | Power Macintoshes and clones with Ethernet built-in on the |
| 26 | 26 | motherboard will usually use a MACE (Medium Access Control for |
| 27 | 27 | Ethernet) interface. Say Y to include support for the MACE chip. |
| @@ -32,7 +32,7 @@ config MACE · 4 unmodified lines | ||
| 32 | 32 | config MACE_AAUI_PORT |
| 33 | 33 | bool "Use AAUI port instead of TP by default" |
| 34 | 34 | depends on MACE |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | Some Apple machines (notably the Apple Network Server) which use the |
| 37 | 37 | MACE ethernet chip have an Apple AUI port (small 15-pin connector), |
| 38 | 38 | instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say |
| @@ -44,7 +44,7 @@ config BMAC · 5 unmodified lines | ||
| 44 | 44 | tristate "BMAC (G3 ethernet) support" |
| 45 | 45 | depends on PPC_PMAC && PPC32 |
| 46 | 46 | select CRC32 |
| 47 | − ---help--- | |
| 47 | + help | |
| 48 | 48 | Say Y for support of BMAC Ethernet interfaces. These are used on G3 |
| 49 | 49 | computers. |
| 50 | 50 | |
| @@ -55,7 +55,7 @@ config MACMACE · 4 unmodified lines | ||
| 55 | 55 | tristate "Macintosh (AV) onboard MACE ethernet" |
| 56 | 56 | depends on MAC |
| 57 | 57 | select CRC32 |
| 58 | − ---help--- | |
| 58 | + help | |
| 59 | 59 | Support for the onboard AMD 79C940 MACE Ethernet controller used in |
| 60 | 60 | the 660AV and 840AV Macintosh. If you have one of these Macintoshes |
| 61 | 61 | say Y here. |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_AQUANTIA |
| 7 | 7 | bool "aQuantia devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Set this to y if you have an Ethernet network cards that uses the aQuantia |
| 11 | 11 | AQC107/AQC108 chipset. |
| 12 | 12 | |
| @@ -21,7 +21,7 @@ config AQTION · 8 unmodified lines | ||
| 21 | 21 | depends on PCI |
| 22 | 22 | depends on X86_64 || ARM64 || COMPILE_TEST |
| 23 | 23 | depends on MACSEC || MACSEC=n |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | This enables the support for the aQuantia AQtion(tm) Ethernet card. |
| 26 | 26 | |
| 27 | 27 | endif # NET_VENDOR_AQUANTIA |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_ARC |
| 7 | 7 | bool "ARC devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -27,7 +27,7 @@ config ARC_EMAC · 14 unmodified lines | ||
| 27 | 27 | select ARC_EMAC_CORE |
| 28 | 28 | depends on OF_IRQ && OF_NET |
| 29 | 29 | depends on ARC || COMPILE_TEST |
| 30 | − ---help--- | |
| 30 | + help | |
| 31 | 31 | On some legacy ARC (Synopsys) FPGA boards such as ARCAngel4/ML50x |
| 32 | 32 | non-standard on-chip ethernet device ARC EMAC 10/100 is used. |
| 33 | 33 | Say Y here if you have such a board. If unsure, say N. |
| @@ -37,7 +37,7 @@ config EMAC_ROCKCHIP · 3 unmodified lines | ||
| 37 | 37 | select ARC_EMAC_CORE |
| 38 | 38 | depends on OF_IRQ && OF_NET && REGULATOR |
| 39 | 39 | depends on ARCH_ROCKCHIP || COMPILE_TEST |
| 40 | − ---help--- | |
| 40 | + help | |
| 41 | 41 | Support for Rockchip RK3036/RK3066/RK3188 EMAC ethernet controllers. |
| 42 | 42 | This selects Rockchip SoC glue layer support for the |
| 43 | 43 | emac device driver. This driver is used for RK3036/RK3066/RK3188 |
| @@ -7,7 +7,7 @@ config NET_VENDOR_ATHEROS · 6 unmodified lines | ||
| 7 | 7 | bool "Atheros devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on (PCI || ATH79) |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -30,7 +30,7 @@ config ATL2 · 16 unmodified lines | ||
| 30 | 30 | depends on PCI |
| 31 | 31 | select CRC32 |
| 32 | 32 | select MII |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | This driver supports the Atheros L2 fast ethernet adapter. |
| 35 | 35 | |
| 36 | 36 | To compile this driver as a module, choose M here. The module |
| @@ -41,7 +41,7 @@ config ATL1 · 4 unmodified lines | ||
| 41 | 41 | depends on PCI |
| 42 | 42 | select CRC32 |
| 43 | 43 | select MII |
| 44 | − ---help--- | |
| 44 | + help | |
| 45 | 45 | This driver supports the Atheros/Attansic L1 gigabit ethernet |
| 46 | 46 | adapter. |
| 47 | 47 | |
| @@ -53,7 +53,7 @@ config ATL1E · 5 unmodified lines | ||
| 53 | 53 | depends on PCI |
| 54 | 54 | select CRC32 |
| 55 | 55 | select MII |
| 56 | − ---help--- | |
| 56 | + help | |
| 57 | 57 | This driver supports the Atheros L1E gigabit ethernet adapter. |
| 58 | 58 | |
| 59 | 59 | To compile this driver as a module, choose M here. The module |
| @@ -64,7 +64,7 @@ config ATL1C · 4 unmodified lines | ||
| 64 | 64 | depends on PCI |
| 65 | 65 | select CRC32 |
| 66 | 66 | select MII |
| 67 | − ---help--- | |
| 67 | + help | |
| 68 | 68 | This driver supports the Atheros L1C gigabit ethernet adapter. |
| 69 | 69 | |
| 70 | 70 | To compile this driver as a module, choose M here. The module |
| @@ -8,7 +8,7 @@ config NET_VENDOR_BROADCOM · 7 unmodified lines | ||
| 8 | 8 | default y |
| 9 | 9 | depends on (SSB_POSSIBLE && HAS_DMA) || PCI || BCM63XX || \ |
| 10 | 10 | SIBYTE_SB1xxx_SOC |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | If you have a network (Ethernet) chipset belonging to this class, |
| 13 | 13 | say Y. |
| 14 | 14 | |
| @@ -25,7 +25,7 @@ config B44 · 10 unmodified lines | ||
| 25 | 25 | select SSB |
| 26 | 26 | select MII |
| 27 | 27 | select PHYLIB |
| 28 | − ---help--- | |
| 28 | + help | |
| 29 | 29 | If you have a network (Ethernet) controller of this type, say Y |
| 30 | 30 | or M here. |
| 31 | 31 | |
| @@ -79,7 +79,7 @@ config BNX2 · 47 unmodified lines | ||
| 79 | 79 | depends on PCI |
| 80 | 80 | select CRC32 |
| 81 | 81 | select FW_LOADER |
| 82 | − ---help--- | |
| 82 | + help | |
| 83 | 83 | This driver supports QLogic bnx2 gigabit Ethernet cards. |
| 84 | 84 | |
| 85 | 85 | To compile this driver as a module, choose M here: the module |
| @@ -90,7 +90,7 @@ config CNIC · 4 unmodified lines | ||
| 90 | 90 | depends on PCI && (IPV6 || IPV6=n) |
| 91 | 91 | select BNX2 |
| 92 | 92 | select UIO |
| 93 | − ---help--- | |
| 93 | + help | |
| 94 | 94 | This driver supports offload features of QLogic bnx2 gigabit |
| 95 | 95 | Ethernet cards. |
| 96 | 96 | |
| @@ -101,7 +101,7 @@ config SB1250_MAC · 4 unmodified lines | ||
| 101 | 101 | tristate "SB1250 Gigabit Ethernet support" |
| 102 | 102 | depends on SIBYTE_SB1xxx_SOC |
| 103 | 103 | select PHYLIB |
| 104 | − ---help--- | |
| 104 | + help | |
| 105 | 105 | This driver supports Gigabit Ethernet interfaces based on the |
| 106 | 106 | Broadcom SiByte family of System-On-a-Chip parts. They include |
| 107 | 107 | the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455 |
| @@ -115,7 +115,7 @@ config TIGON3 · 7 unmodified lines | ||
| 115 | 115 | depends on PCI |
| 116 | 116 | select PHYLIB |
| 117 | 117 | imply PTP_1588_CLOCK |
| 118 | − ---help--- | |
| 118 | + help | |
| 119 | 119 | This driver supports Broadcom Tigon3 based gigabit Ethernet cards. |
| 120 | 120 | |
| 121 | 121 | To compile this driver as a module, choose M here: the module |
| @@ -125,7 +125,7 @@ config TIGON3_HWMON · 3 unmodified lines | ||
| 125 | 125 | bool "Broadcom Tigon3 HWMON support" |
| 126 | 126 | default y |
| 127 | 127 | depends on TIGON3 && HWMON && !(TIGON3=y && HWMON=m) |
| 128 | − ---help--- | |
| 128 | + help | |
| 129 | 129 | Say Y if you want to expose the thermal sensor on Tigon3 devices. |
| 130 | 130 | |
| 131 | 131 | config BNX2X |
| @@ -136,7 +136,7 @@ config BNX2X · 4 unmodified lines | ||
| 136 | 136 | select ZLIB_INFLATE |
| 137 | 137 | select LIBCRC32C |
| 138 | 138 | select MDIO |
| 139 | − ---help--- | |
| 139 | + help | |
| 140 | 140 | This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards. |
| 141 | 141 | To compile this driver as a module, choose M here: the module |
| 142 | 142 | will be called bnx2x. This is recommended. |
| @@ -145,7 +145,7 @@ config BNX2X_SRIOV · 2 unmodified lines | ||
| 145 | 145 | bool "Broadcom 578xx and 57712 SR-IOV support" |
| 146 | 146 | depends on BNX2X && PCI_IOV |
| 147 | 147 | default y |
| 148 | − ---help--- | |
| 148 | + help | |
| 149 | 149 | This configuration parameter enables Single Root Input Output |
| 150 | 150 | Virtualization support in the 578xx and 57712 products. This |
| 151 | 151 | allows for virtual function acceleration in virtual environments. |
| @@ -164,7 +164,7 @@ config BGMAC_BCMA · 12 unmodified lines | ||
| 164 | 164 | select BGMAC |
| 165 | 165 | select PHYLIB |
| 166 | 166 | select FIXED_PHY |
| 167 | − ---help--- | |
| 167 | + help | |
| 168 | 168 | This driver supports GBit MAC and BCM4706 GBit MAC cores on BCMA bus. |
| 169 | 169 | They can be found on BCM47xx SoCs and provide gigabit ethernet. |
| 170 | 170 | In case of using this driver on BCM4706 it's also requires to enable |
| @@ -178,7 +178,7 @@ config BGMAC_PLATFORM · 7 unmodified lines | ||
| 178 | 178 | select PHYLIB |
| 179 | 179 | select FIXED_PHY |
| 180 | 180 | default ARCH_BCM_IPROC |
| 181 | − ---help--- | |
| 181 | + help | |
| 182 | 182 | Say Y here if you want to use the Broadcom iProc Gigabit Ethernet |
| 183 | 183 | controller through the generic platform interface |
| 184 | 184 | |
| @@ -203,7 +203,7 @@ config BNXT · 18 unmodified lines | ||
| 203 | 203 | select NET_DEVLINK |
| 204 | 204 | select PAGE_POOL |
| 205 | 205 | select DIMLIB |
| 206 | − ---help--- | |
| 206 | + help | |
| 207 | 207 | This driver supports Broadcom NetXtreme-C/E 10/25/40/50 gigabit |
| 208 | 208 | Ethernet cards. To compile this driver as a module, choose M here: |
| 209 | 209 | the module will be called bnxt_en. This is recommended. |
| @@ -212,7 +212,7 @@ config BNXT_SRIOV · 2 unmodified lines | ||
| 212 | 212 | bool "Broadcom NetXtreme-C/E SR-IOV support" |
| 213 | 213 | depends on BNXT && PCI_IOV |
| 214 | 214 | default y |
| 215 | − ---help--- | |
| 215 | + help | |
| 216 | 216 | This configuration parameter enables Single Root Input Output |
| 217 | 217 | Virtualization support in the NetXtreme-C/E products. This |
| 218 | 218 | allows for virtual function acceleration in virtual environments. |
| @@ -221,7 +221,7 @@ config BNXT_FLOWER_OFFLOAD · 2 unmodified lines | ||
| 221 | 221 | bool "TC Flower offload support for NetXtreme-C/E" |
| 222 | 222 | depends on BNXT |
| 223 | 223 | default y |
| 224 | − ---help--- | |
| 224 | + help | |
| 225 | 225 | This configuration parameter enables TC Flower packet classifier |
| 226 | 226 | offload for eswitch. This option enables SR-IOV switchdev eswitch |
| 227 | 227 | offload. |
| @@ -230,7 +230,7 @@ config BNXT_DCB · 2 unmodified lines | ||
| 230 | 230 | bool "Data Center Bridging (DCB) Support" |
| 231 | 231 | default n |
| 232 | 232 | depends on BNXT && DCB |
| 233 | − ---help--- | |
| 233 | + help | |
| 234 | 234 | Say Y here if you want to use Data Center Bridging (DCB) in the |
| 235 | 235 | driver. |
| 236 | 236 | |
| @@ -240,7 +240,7 @@ config BNXT_HWMON · 3 unmodified lines | ||
| 240 | 240 | bool "Broadcom NetXtreme-C/E HWMON support" |
| 241 | 241 | default y |
| 242 | 242 | depends on BNXT && HWMON && !(BNXT=y && HWMON=m) |
| 243 | − ---help--- | |
| 243 | + help | |
| 244 | 244 | Say Y if you want to expose the thermal sensor data on NetXtreme-C/E |
| 245 | 245 | devices, via the hwmon sysfs interface. |
| 246 | 246 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_BROCADE · 6 unmodified lines | ||
| 7 | 7 | bool "QLogic BR-series devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config BNA |
| 7 | 7 | tristate "QLogic BR-series 1010/1020/1860 10Gb Ethernet Driver support" |
| 8 | 8 | depends on PCI |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This driver supports QLogic BR-series 1010/1020/1860 10Gb CEE capable |
| 11 | 11 | Ethernet cards. |
| 12 | 12 | To compile this driver as a module, choose M here: the module |
| @@ -7,7 +7,7 @@ config NET_VENDOR_CADENCE · 6 unmodified lines | ||
| 7 | 7 | bool "Cadence devices" |
| 8 | 8 | depends on HAS_IOMEM |
| 9 | 9 | default y |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | If unsure, say Y. |
| @@ -23,7 +23,7 @@ config MACB · 9 unmodified lines | ||
| 23 | 23 | tristate "Cadence MACB/GEM support" |
| 24 | 24 | depends on HAS_DMA && COMMON_CLK |
| 25 | 25 | select PHYLINK |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | The Cadence MACB ethernet interface is found on many Atmel AT32 and |
| 28 | 28 | AT91 parts. This driver also supports the Cadence GEM (Gigabit |
| 29 | 29 | Ethernet MAC found in some ARM SoC devices). Say Y to include |
| @@ -37,13 +37,13 @@ config MACB_USE_HWSTAMP · 7 unmodified lines | ||
| 37 | 37 | depends on MACB |
| 38 | 38 | depends on PTP_1588_CLOCK |
| 39 | 39 | default y |
| 40 | − ---help--- | |
| 40 | + help | |
| 41 | 41 | Enable IEEE 1588 Precision Time Protocol (PTP) support for MACB. |
| 42 | 42 | |
| 43 | 43 | config MACB_PCI |
| 44 | 44 | tristate "Cadence PCI MACB/GEM support" |
| 45 | 45 | depends on MACB && PCI |
| 46 | − ---help--- | |
| 46 | + help | |
| 47 | 47 | This is PCI wrapper for MACB driver. |
| 48 | 48 | |
| 49 | 49 | To compile this driver as a module, choose M here: the module |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_CAVIUM |
| 7 | 7 | bool "Cavium ethernet drivers" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Select this option if you want enable Cavium network support. |
| 11 | 11 | |
| 12 | 12 | If you have a Cavium SoC or network adapter, say Y. |
| @@ -17,7 +17,7 @@ config THUNDER_NIC_PF · 4 unmodified lines | ||
| 17 | 17 | tristate "Thunder Physical function driver" |
| 18 | 18 | depends on 64BIT && PCI |
| 19 | 19 | select THUNDER_NIC_BGX |
| 20 | − ---help--- | |
| 20 | + help | |
| 21 | 21 | This driver supports Thunder's NIC physical function. |
| 22 | 22 | The NIC provides the controller and DMA engines to |
| 23 | 23 | move network traffic to/from the memory. The NIC |
| @@ -29,7 +29,7 @@ config THUNDER_NIC_VF · 5 unmodified lines | ||
| 29 | 29 | tristate "Thunder Virtual function driver" |
| 30 | 30 | imply CAVIUM_PTP |
| 31 | 31 | depends on 64BIT && PCI |
| 32 | − ---help--- | |
| 32 | + help | |
| 33 | 33 | This driver supports Thunder's NIC virtual function |
| 34 | 34 | |
| 35 | 35 | config THUNDER_NIC_BGX |
| @@ -38,7 +38,7 @@ config THUNDER_NIC_BGX · 2 unmodified lines | ||
| 38 | 38 | select PHYLIB |
| 39 | 39 | select MDIO_THUNDER if PCI |
| 40 | 40 | select THUNDER_NIC_RGX |
| 41 | − ---help--- | |
| 41 | + help | |
| 42 | 42 | This driver supports programming and controlling of MAC |
| 43 | 43 | interface from NIC physical function driver. |
| 44 | 44 | |
| @@ -47,7 +47,7 @@ config THUNDER_NIC_RGX · 2 unmodified lines | ||
| 47 | 47 | depends on 64BIT && PCI |
| 48 | 48 | select PHYLIB |
| 49 | 49 | select MDIO_THUNDER if PCI |
| 50 | − ---help--- | |
| 50 | + help | |
| 51 | 51 | This driver supports configuring XCV block of RGX interface |
| 52 | 52 | present on CN81XX chip. |
| 53 | 53 | |
| @@ -55,7 +55,7 @@ config CAVIUM_PTP · 1 unmodified line | ||
| 55 | 55 | tristate "Cavium PTP coprocessor as PTP clock" |
| 56 | 56 | depends on 64BIT && PCI |
| 57 | 57 | depends on PTP_1588_CLOCK |
| 58 | − ---help--- | |
| 58 | + help | |
| 59 | 59 | This driver adds support for the Precision Time Protocol Clocks and |
| 60 | 60 | Timestamping coprocessor (PTP) found on Cavium processors. |
| 61 | 61 | PTP provides timestamping mechanism that is suitable for use in IEEE 1588 |
| @@ -70,7 +70,7 @@ config LIQUIDIO · 8 unmodified lines | ||
| 70 | 70 | select FW_LOADER |
| 71 | 71 | select LIBCRC32C |
| 72 | 72 | select NET_DEVLINK |
| 73 | − ---help--- | |
| 73 | + help | |
| 74 | 74 | This driver supports Cavium LiquidIO Intelligent Server Adapters |
| 75 | 75 | based on CN66XX, CN68XX and CN23XX chips. |
| 76 | 76 | |
| @@ -92,7 +92,7 @@ config LIQUIDIO_VF · 15 unmodified lines | ||
| 92 | 92 | tristate "Cavium LiquidIO VF support" |
| 93 | 93 | depends on 64BIT && PCI_MSI |
| 94 | 94 | imply PTP_1588_CLOCK |
| 95 | − ---help--- | |
| 95 | + help | |
| 96 | 96 | This driver supports Cavium LiquidIO Intelligent Server Adapter |
| 97 | 97 | based on CN23XX chips. |
| 98 | 98 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_CHELSIO · 6 unmodified lines | ||
| 7 | 7 | bool "Chelsio devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -22,7 +22,7 @@ config CHELSIO_T1 · 8 unmodified lines | ||
| 22 | 22 | depends on PCI |
| 23 | 23 | select CRC32 |
| 24 | 24 | select MDIO |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | This driver supports Chelsio gigabit and 10-gigabit |
| 27 | 27 | Ethernet cards. More information about adapter features and |
| 28 | 28 | performance tuning is in |
| @@ -42,7 +42,7 @@ config CHELSIO_T1 · 13 unmodified lines | ||
| 42 | 42 | config CHELSIO_T1_1G |
| 43 | 43 | bool "Chelsio gigabit Ethernet support" |
| 44 | 44 | depends on CHELSIO_T1 |
| 45 | − ---help--- | |
| 45 | + help | |
| 46 | 46 | Enables support for Chelsio's gigabit Ethernet PCI cards. If you |
| 47 | 47 | are using only 10G cards say 'N' here. |
| 48 | 48 | |
| @@ -51,7 +51,7 @@ config CHELSIO_T3 · 2 unmodified lines | ||
| 51 | 51 | depends on PCI && INET |
| 52 | 52 | select FW_LOADER |
| 53 | 53 | select MDIO |
| 54 | − ---help--- | |
| 54 | + help | |
| 55 | 55 | This driver supports Chelsio T3-based gigabit and 10Gb Ethernet |
| 56 | 56 | adapters. |
| 57 | 57 | |
| @@ -72,7 +72,7 @@ config CHELSIO_T4 · 14 unmodified lines | ||
| 72 | 72 | select FW_LOADER |
| 73 | 73 | select MDIO |
| 74 | 74 | select ZLIB_DEFLATE |
| 75 | − ---help--- | |
| 75 | + help | |
| 76 | 76 | This driver supports Chelsio T4, T5 & T6 based gigabit, 10Gb Ethernet |
| 77 | 77 | adapter and T5/T6 based 40Gb and T6 based 25Gb, 50Gb and 100Gb |
| 78 | 78 | Ethernet adapters. |
| @@ -92,7 +92,7 @@ config CHELSIO_T4_DCB · 13 unmodified lines | ||
| 92 | 92 | bool "Data Center Bridging (DCB) Support for Chelsio T4/T5/T6 cards" |
| 93 | 93 | default n |
| 94 | 94 | depends on CHELSIO_T4 && DCB |
| 95 | − ---help--- | |
| 95 | + help | |
| 96 | 96 | Enable DCB support through rtNetlink interface. |
| 97 | 97 | Say Y here if you want to enable Data Center Bridging (DCB) support |
| 98 | 98 | in the driver. |
| @@ -103,7 +103,7 @@ config CHELSIO_T4_FCOE · 4 unmodified lines | ||
| 103 | 103 | bool "Fibre Channel over Ethernet (FCoE) Support for Chelsio T5 cards" |
| 104 | 104 | default n |
| 105 | 105 | depends on CHELSIO_T4 && CHELSIO_T4_DCB && FCOE |
| 106 | − ---help--- | |
| 106 | + help | |
| 107 | 107 | Enable FCoE offload features. |
| 108 | 108 | Say Y here if you want to enable Fibre Channel over Ethernet (FCoE) support |
| 109 | 109 | in the driver. |
| @@ -113,7 +113,7 @@ config CHELSIO_T4_FCOE · 3 unmodified lines | ||
| 113 | 113 | config CHELSIO_T4VF |
| 114 | 114 | tristate "Chelsio Communications T4/T5/T6 Virtual Function Ethernet support" |
| 115 | 115 | depends on PCI |
| 116 | − ---help--- | |
| 116 | + help | |
| 117 | 117 | This driver supports Chelsio T4, T5 & T6 based gigabit, 10Gb Ethernet |
| 118 | 118 | adapters and T5/T6 based 40Gb and T6 based 25Gb, 50Gb and 100Gb |
| 119 | 119 | Ethernet adapters with PCI-E SR-IOV Virtual Functions. |
| @@ -131,7 +131,7 @@ config CHELSIO_T4VF · 11 unmodified lines | ||
| 131 | 131 | |
| 132 | 132 | config CHELSIO_LIB |
| 133 | 133 | tristate |
| 134 | − ---help--- | |
| 134 | + help | |
| 135 | 135 | Common library for Chelsio drivers. |
| 136 | 136 | |
| 137 | 137 | endif # NET_VENDOR_CHELSIO |
| @@ -7,7 +7,7 @@ config NET_VENDOR_CIRRUS · 6 unmodified lines | ||
| 7 | 7 | bool "Cirrus devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on ISA || EISA || ARM || MAC |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -21,7 +21,7 @@ config CS89x0 · 7 unmodified lines | ||
| 21 | 21 | tristate "CS89x0 support" |
| 22 | 22 | depends on ISA || EISA || ARM |
| 23 | 23 | depends on !PPC32 |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | Support for CS89x0 chipset based Ethernet cards. If you have a |
| 26 | 26 | network (Ethernet) card of this type, say Y and read the file |
| 27 | 27 | <file:Documentation/networking/device_drivers/cirrus/cs89x0.rst>. |
| @@ -51,7 +51,7 @@ config EP93XX_ETH · 23 unmodified lines | ||
| 51 | 51 | config MAC89x0 |
| 52 | 52 | tristate "Macintosh CS89x0 based ethernet cards" |
| 53 | 53 | depends on MAC |
| 54 | − ---help--- | |
| 54 | + help | |
| 55 | 55 | Support for CS89x0 chipset based Ethernet cards. If you have a |
| 56 | 56 | Nubus or LC-PDS network (Ethernet) card of this type, say Y here. |
| 57 | 57 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_CISCO · 6 unmodified lines | ||
| 7 | 7 | bool "Cisco devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -6,5 +6,5 @@ · 5 unmodified lines | ||
| 6 | 6 | config ENIC |
| 7 | 7 | tristate "Cisco VIC Ethernet NIC Support" |
| 8 | 8 | depends on PCI |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This enables the support for the Cisco VIC Ethernet card. |
| @@ -4,7 +4,7 @@ · 3 unmodified lines | ||
| 4 | 4 | config NET_VENDOR_CORTINA |
| 5 | 5 | bool "Cortina Gemini devices" |
| 6 | 6 | default y |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | If you have a network (Ethernet) card belonging to this class, say Y |
| 9 | 9 | and read the Ethernet-HOWTO, available from |
| 10 | 10 | <http://www.tldp.org/docs.html#howto>. |
| @@ -17,7 +17,7 @@ config GEMINI_ETHERNET · 6 unmodified lines | ||
| 17 | 17 | depends on HAS_IOMEM |
| 18 | 18 | select PHYLIB |
| 19 | 19 | select CRC32 |
| 20 | − ---help--- | |
| 20 | + help | |
| 21 | 21 | This driver supports StorLink SL351x (Gemini) dual Gigabit Ethernet. |
| 22 | 22 | |
| 23 | 23 | endif # NET_VENDOR_CORTINA |
| @@ -8,7 +8,7 @@ config DM9000 · 7 unmodified lines | ||
| 8 | 8 | depends on ARM || MIPS || COLDFIRE || NIOS2 |
| 9 | 9 | select CRC32 |
| 10 | 10 | select MII |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | Support for DM9000 chipset. |
| 13 | 13 | |
| 14 | 14 | To compile this driver as a module, choose M here. The module |
| @@ -17,7 +17,7 @@ config DM9000 · 2 unmodified lines | ||
| 17 | 17 | config DM9000_FORCE_SIMPLE_PHY_POLL |
| 18 | 18 | bool "Force simple NSR based PHY polling" |
| 19 | 19 | depends on DM9000 |
| 20 | − ---help--- | |
| 20 | + help | |
| 21 | 21 | This configuration forces the DM9000 to use the NSR's LinkStatus |
| 22 | 22 | bit to determine if the link is up or down instead of the more |
| 23 | 23 | costly MII PHY reads. Note, this will not work if the chip is |
| @@ -7,7 +7,7 @@ config NET_VENDOR_DEC · 6 unmodified lines | ||
| 7 | 7 | bool "Digital Equipment devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI || EISA || CARDBUS |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_TULIP |
| 7 | 7 | bool "DEC - Tulip devices" |
| 8 | 8 | depends on (PCI || EISA || CARDBUS) |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This selects the "Tulip" family of EISA/PCI network cards. |
| 11 | 11 | |
| 12 | 12 | if NET_TULIP |
| @@ -15,7 +15,7 @@ config DE2104X · 2 unmodified lines | ||
| 15 | 15 | tristate "Early DECchip Tulip (dc2104x) PCI support" |
| 16 | 16 | depends on PCI |
| 17 | 17 | select CRC32 |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | This driver is developed for the SMC EtherPower series Ethernet |
| 20 | 20 | cards and also works with cards based on the DECchip |
| 21 | 21 | 21040 (Tulip series) chips. Some LinkSys PCI cards are |
| @@ -32,7 +32,7 @@ config DE2104X_DSL · 10 unmodified lines | ||
| 32 | 32 | depends on DE2104X |
| 33 | 33 | range 0 31 |
| 34 | 34 | default 0 |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | Setting this value allows to align ring buffer descriptors into their |
| 37 | 37 | own cache lines. Value of 4 corresponds to the typical 32 byte line |
| 38 | 38 | (the descriptor is 16 bytes). This is necessary on systems that lack |
| @@ -43,7 +43,7 @@ config TULIP · 4 unmodified lines | ||
| 43 | 43 | tristate "DECchip Tulip (dc2114x) PCI support" |
| 44 | 44 | depends on PCI |
| 45 | 45 | select CRC32 |
| 46 | − ---help--- | |
| 46 | + help | |
| 47 | 47 | This driver is developed for the SMC EtherPower series Ethernet |
| 48 | 48 | cards and also works with cards based on the DECchip |
| 49 | 49 | 21140 (Tulip series) chips. Some LinkSys PCI cards are |
| @@ -58,7 +58,7 @@ config TULIP · 8 unmodified lines | ||
| 58 | 58 | config TULIP_MWI |
| 59 | 59 | bool "New bus configuration" |
| 60 | 60 | depends on TULIP |
| 61 | − ---help--- | |
| 61 | + help | |
| 62 | 62 | This configures your Tulip card specifically for the card and |
| 63 | 63 | system cache line size type you are using. |
| 64 | 64 | |
| @@ -69,7 +69,7 @@ config TULIP_MWI · 4 unmodified lines | ||
| 69 | 69 | config TULIP_MMIO |
| 70 | 70 | bool "Use PCI shared mem for NIC registers" |
| 71 | 71 | depends on TULIP |
| 72 | − ---help--- | |
| 72 | + help | |
| 73 | 73 | Use PCI shared memory for the NIC registers, rather than going through |
| 74 | 74 | the Tulip's PIO (programmed I/O ports). Faster, but could produce |
| 75 | 75 | obscure bugs if your mainboard has memory controller timing issues. |
| @@ -78,7 +78,7 @@ config TULIP_MMIO · 2 unmodified lines | ||
| 78 | 78 | config TULIP_NAPI |
| 79 | 79 | bool "Use RX polling (NAPI)" |
| 80 | 80 | depends on TULIP |
| 81 | − ---help--- | |
| 81 | + help | |
| 82 | 82 | NAPI is a new driver API designed to reduce CPU and interrupt load |
| 83 | 83 | when the driver is receiving lots of packets from the card. It is |
| 84 | 84 | still somewhat experimental and thus not yet enabled by default. |
| @@ -92,7 +92,7 @@ config TULIP_NAPI · 7 unmodified lines | ||
| 92 | 92 | config TULIP_NAPI_HW_MITIGATION |
| 93 | 93 | bool "Use Interrupt Mitigation" |
| 94 | 94 | depends on TULIP_NAPI |
| 95 | − ---help--- | |
| 95 | + help | |
| 96 | 96 | Use HW to reduce RX interrupts. Not strictly necessary since NAPI |
| 97 | 97 | reduces RX interrupts by itself. Interrupt mitigation reduces RX |
| 98 | 98 | interrupts even at low levels of traffic at the cost of a small |
| @@ -109,7 +109,7 @@ config DE4X5 · 10 unmodified lines | ||
| 109 | 109 | depends on (PCI || EISA) |
| 110 | 110 | depends on VIRT_TO_BUS || ALPHA || PPC || SPARC |
| 111 | 111 | select CRC32 |
| 112 | − ---help--- | |
| 112 | + help | |
| 113 | 113 | This is support for the DIGITAL series of PCI/EISA Ethernet cards. |
| 114 | 114 | These include the DE425, DE434, DE435, DE450 and DE500 models. If |
| 115 | 115 | you have a network card of this type, say Y. More specific |
| @@ -124,7 +124,7 @@ config WINBOND_840 · 8 unmodified lines | ||
| 124 | 124 | depends on PCI |
| 125 | 125 | select CRC32 |
| 126 | 126 | select MII |
| 127 | − ---help--- | |
| 127 | + help | |
| 128 | 128 | This driver is for the Winbond W89c840 chip. It also works with |
| 129 | 129 | the TX9882 chip on the Compex RL100-ATX board. |
| 130 | 130 | More specific information and updates are available from |
| @@ -134,7 +134,7 @@ config DM9102 · 3 unmodified lines | ||
| 134 | 134 | tristate "Davicom DM910x/DM980x support" |
| 135 | 135 | depends on PCI |
| 136 | 136 | select CRC32 |
| 137 | − ---help--- | |
| 137 | + help | |
| 138 | 138 | This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from |
| 139 | 139 | Davicom (<http://www.davicom.com.tw/>). If you have such a network |
| 140 | 140 | (Ethernet) card, say Y. Some information is contained in the file |
| @@ -147,7 +147,7 @@ config ULI526X · 6 unmodified lines | ||
| 147 | 147 | tristate "ULi M526x controller support" |
| 148 | 148 | depends on PCI |
| 149 | 149 | select CRC32 |
| 150 | − ---help--- | |
| 150 | + help | |
| 151 | 151 | This driver is for ULi M5261/M5263 10/100M Ethernet Controller |
| 152 | 152 | (<http://www.nvidia.com/page/uli_drivers.html>). |
| 153 | 153 | |
| @@ -157,7 +157,7 @@ config ULI526X · 3 unmodified lines | ||
| 157 | 157 | config PCMCIA_XIRCOM |
| 158 | 158 | tristate "Xircom CardBus support" |
| 159 | 159 | depends on CARDBUS |
| 160 | − ---help--- | |
| 160 | + help | |
| 161 | 161 | This driver is for the Digital "Tulip" Ethernet CardBus adapters. |
| 162 | 162 | It should work with most DEC 21*4*-based chips/ethercards, as well |
| 163 | 163 | as with work-alike chips from Lite-On (PNIC) and Macronix (MXIC) and |
| @@ -7,7 +7,7 @@ config NET_VENDOR_DLINK · 6 unmodified lines | ||
| 7 | 7 | bool "D-Link devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -21,7 +21,7 @@ config DL2K · 7 unmodified lines | ||
| 21 | 21 | tristate "DL2000/TC902x/IP1000A-based Gigabit Ethernet support" |
| 22 | 22 | depends on PCI |
| 23 | 23 | select CRC32 |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | This driver supports DL2000/TC902x/IP1000A-based Gigabit ethernet cards, |
| 26 | 26 | which includes |
| 27 | 27 | D-Link DGE-550T Gigabit Ethernet Adapter. |
| @@ -37,7 +37,7 @@ config SUNDANCE · 9 unmodified lines | ||
| 37 | 37 | depends on PCI |
| 38 | 38 | select CRC32 |
| 39 | 39 | select MII |
| 40 | − ---help--- | |
| 40 | + help | |
| 41 | 41 | This driver is for the Sundance "Alta" chip. |
| 42 | 42 | More specific information and updates are available from |
| 43 | 43 | <http://www.scyld.com/network/sundance.html>. |
| @@ -45,7 +45,7 @@ config SUNDANCE · 1 unmodified line | ||
| 45 | 45 | config SUNDANCE_MMIO |
| 46 | 46 | bool "Use MMIO instead of PIO" |
| 47 | 47 | depends on SUNDANCE |
| 48 | − ---help--- | |
| 48 | + help | |
| 49 | 49 | Enable memory-mapped I/O for interaction with Sundance NIC registers. |
| 50 | 50 | Do NOT enable this by default, PIO (enabled when MMIO is disabled) |
| 51 | 51 | is known to solve bugs on certain chips. |
| @@ -7,7 +7,7 @@ config NET_VENDOR_EMULEX · 6 unmodified lines | ||
| 7 | 7 | bool "Emulex devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_EZCHIP |
| 7 | 7 | bool "EZchip devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) device belonging to this class, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ config EZCHIP_NPS_MANAGEMENT_ENET · 7 unmodified lines | ||
| 20 | 20 | tristate "EZchip NPS management enet support" |
| 21 | 21 | depends on OF_IRQ && OF_NET |
| 22 | 22 | depends on HAS_IOMEM |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | Simple LAN device for debug or management purposes. |
| 25 | 25 | Device supports interrupts for RX and TX(completion). |
| 26 | 26 | Device does not have DMA ability. |
| @@ -7,7 +7,7 @@ config NET_VENDOR_FARADAY · 6 unmodified lines | ||
| 7 | 7 | bool "Faraday devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on ARM || NDS32 || COMPILE_TEST |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -22,7 +22,7 @@ config FTMAC100 · 8 unmodified lines | ||
| 22 | 22 | depends on ARM || NDS32 || COMPILE_TEST |
| 23 | 23 | depends on !64BIT || BROKEN |
| 24 | 24 | select MII |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | This driver supports the FTMAC100 10/100 Ethernet controller |
| 27 | 27 | from Faraday. It is used on Faraday A320, Andes AG101 and some |
| 28 | 28 | other ARM/NDS32 SoC's. |
| @@ -33,7 +33,7 @@ config FTGMAC100 · 4 unmodified lines | ||
| 33 | 33 | depends on !64BIT || BROKEN |
| 34 | 34 | select PHYLIB |
| 35 | 35 | select MDIO_ASPEED if MACH_ASPEED_G6 |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | This driver supports the FTGMAC100 Gigabit Ethernet controller |
| 38 | 38 | from Faraday. It is used on Faraday A369, Andes AG102 and some |
| 39 | 39 | other ARM/NDS32 SoC's. |
| @@ -10,7 +10,7 @@ config NET_VENDOR_FREESCALE · 9 unmodified lines | ||
| 10 | 10 | M523x || M527x || M5272 || M528x || M520x || M532x || \ |
| 11 | 11 | ARCH_MXC || ARCH_MXS || (PPC_MPC52xx && PPC_BESTCOMM) || \ |
| 12 | 12 | ARCH_LAYERSCAPE || COMPILE_TEST |
| 13 | − ---help--- | |
| 13 | + help | |
| 14 | 14 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 15 | 15 | |
| 16 | 16 | Note that the answer to this question doesn't directly affect the |
| @@ -27,7 +27,7 @@ config FEC · 10 unmodified lines | ||
| 27 | 27 | default ARCH_MXC || SOC_IMX28 if ARM |
| 28 | 28 | select PHYLIB |
| 29 | 29 | imply PTP_1588_CLOCK |
| 30 | − ---help--- | |
| 30 | + help | |
| 31 | 31 | Say Y here if you want to use the built-in 10/100 Fast ethernet |
| 32 | 32 | controller on some Motorola ColdFire and Freescale i.MX processors. |
| 33 | 33 | |
| @@ -37,7 +37,7 @@ config FEC_MPC52xx · 3 unmodified lines | ||
| 37 | 37 | select CRC32 |
| 38 | 38 | select PHYLIB |
| 39 | 39 | select PPC_BESTCOMM_FEC |
| 40 | − ---help--- | |
| 40 | + help | |
| 41 | 41 | This option enables support for the MPC5200's on-chip |
| 42 | 42 | Fast Ethernet Controller |
| 43 | 43 | If compiled as module, it will be called fec_mpc52xx. |
| @@ -46,7 +46,7 @@ config FEC_MPC52xx_MDIO · 2 unmodified lines | ||
| 46 | 46 | bool "FEC MPC52xx MDIO bus driver" |
| 47 | 47 | depends on FEC_MPC52xx |
| 48 | 48 | default y |
| 49 | − ---help--- | |
| 49 | + help | |
| 50 | 50 | The MPC5200's FEC can connect to the Ethernet either with |
| 51 | 51 | an external MII PHY chip or 10 Mbps 7-wire interface |
| 52 | 52 | (Motorola? industry standard). |
| @@ -60,7 +60,7 @@ source "drivers/net/ethernet/freescale/fman/Kconfig" · 7 unmodified lines | ||
| 60 | 60 | config FSL_PQ_MDIO |
| 61 | 61 | tristate "Freescale PQ MDIO" |
| 62 | 62 | select PHYLIB |
| 63 | − ---help--- | |
| 63 | + help | |
| 64 | 64 | This driver supports the MDIO bus used by the gianfar and UCC drivers. |
| 65 | 65 | |
| 66 | 66 | config FSL_XGMAC_MDIO |
| @@ -68,7 +68,7 @@ config FSL_XGMAC_MDIO · 1 unmodified line | ||
| 68 | 68 | select PHYLIB |
| 69 | 69 | depends on OF |
| 70 | 70 | select OF_MDIO |
| 71 | − ---help--- | |
| 71 | + help | |
| 72 | 72 | This driver supports the MDIO bus on the Fman 10G Ethernet MACs, and |
| 73 | 73 | on the FMan mEMAC (which supports both Clauses 22 and 45) |
| 74 | 74 | |
| @@ -78,7 +78,7 @@ config UCC_GETH · 3 unmodified lines | ||
| 78 | 78 | select FSL_PQ_MDIO |
| 79 | 79 | select PHYLIB |
| 80 | 80 | select FIXED_PHY |
| 81 | − ---help--- | |
| 81 | + help | |
| 82 | 82 | This driver supports the Gigabit Ethernet mode of the QUICC Engine, |
| 83 | 83 | which is available on some Freescale SOCs. |
| 84 | 84 | |
| @@ -93,7 +93,7 @@ config GIANFAR · 8 unmodified lines | ||
| 93 | 93 | select PHYLIB |
| 94 | 94 | select FIXED_PHY |
| 95 | 95 | select CRC32 |
| 96 | − ---help--- | |
| 96 | + help | |
| 97 | 97 | This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx, |
| 98 | 98 | and MPC86xx family of chips, the eTSEC on LS1021A and the FEC |
| 99 | 99 | on the 8540. |
| @@ -5,7 +5,7 @@ menuconfig FSL_DPAA_ETH · 4 unmodified lines | ||
| 5 | 5 | select PHYLIB |
| 6 | 6 | select FIXED_PHY |
| 7 | 7 | select FSL_FMAN_MAC |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | Data Path Acceleration Architecture Ethernet driver, |
| 10 | 10 | supporting the Freescale QorIQ chips. |
| 11 | 11 | Depends on Freescale Buffer Manager and Queue Manager |
| @@ -7,7 +7,7 @@ config NET_VENDOR_FUJITSU · 6 unmodified lines | ||
| 7 | 7 | bool "Fujitsu devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCMCIA |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ config PCMCIA_FMVJ18X · 6 unmodified lines | ||
| 20 | 20 | tristate "Fujitsu FMV-J18x PCMCIA support" |
| 21 | 21 | depends on PCMCIA |
| 22 | 22 | select CRC32 |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | Say Y here if you intend to attach a Fujitsu FMV-J18x or compatible |
| 25 | 25 | PCMCIA (PC-card) Ethernet card to your computer. |
| 26 | 26 | |
| @@ -8,7 +8,7 @@ config NET_VENDOR_HISILICON · 7 unmodified lines | ||
| 8 | 8 | default y |
| 9 | 9 | depends on OF || ACPI |
| 10 | 10 | depends on ARM || ARM64 || COMPILE_TEST |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 13 | 13 | |
| 14 | 14 | Note that the answer to this question doesn't directly affect the |
| @@ -42,7 +42,7 @@ config HIP04_ETH · 27 unmodified lines | ||
| 42 | 42 | select MARVELL_PHY |
| 43 | 43 | select MFD_SYSCON |
| 44 | 44 | select HNS_MDIO |
| 45 | − ---help--- | |
| 45 | + help | |
| 46 | 46 | If you wish to compile a kernel for a hardware with hisilicon p04 SoC and |
| 47 | 47 | want to use the internal ethernet then you should answer Y to this. |
| 48 | 48 | |
| @@ -59,13 +59,13 @@ config HI13X1_GMAC · 10 unmodified lines | ||
| 59 | 59 | config HNS_MDIO |
| 60 | 60 | tristate |
| 61 | 61 | select PHYLIB |
| 62 | − ---help--- | |
| 62 | + help | |
| 63 | 63 | This selects the HNS MDIO support. It is needed by HNS_DSAF to access |
| 64 | 64 | the PHY |
| 65 | 65 | |
| 66 | 66 | config HNS |
| 67 | 67 | tristate |
| 68 | − ---help--- | |
| 68 | + help | |
| 69 | 69 | This selects the framework support for Hisilicon Network Subsystem. It |
| 70 | 70 | is needed by any driver which provides HNS acceleration engine or make |
| 71 | 71 | use of the engine |
| @@ -74,7 +74,7 @@ config HNS_DSAF · 2 unmodified lines | ||
| 74 | 74 | tristate "Hisilicon HNS DSAF device Support" |
| 75 | 75 | select HNS |
| 76 | 76 | select HNS_MDIO |
| 77 | − ---help--- | |
| 77 | + help | |
| 78 | 78 | This selects the DSAF (Distributed System Area Frabric) network |
| 79 | 79 | acceleration engine support. The engine is used in Hisilicon hip05, |
| 80 | 80 | Hi1610 and further ICT SoC |
| @@ -83,14 +83,14 @@ config HNS_ENET · 2 unmodified lines | ||
| 83 | 83 | tristate "Hisilicon HNS Ethernet Device Support" |
| 84 | 84 | select PHYLIB |
| 85 | 85 | select HNS |
| 86 | − ---help--- | |
| 86 | + help | |
| 87 | 87 | This selects the general ethernet driver for HNS. This module make |
| 88 | 88 | use of any HNS AE driver, such as HNS_DSAF |
| 89 | 89 | |
| 90 | 90 | config HNS3 |
| 91 | 91 | tristate "Hisilicon Network Subsystem Support HNS3 (Framework)" |
| 92 | 92 | depends on PCI |
| 93 | − ---help--- | |
| 93 | + help | |
| 94 | 94 | This selects the framework support for Hisilicon Network Subsystem 3. |
| 95 | 95 | This layer facilitates clients like ENET, RoCE and user-space ethernet |
| 96 | 96 | drivers(like ODP)to register with HNAE devices and their associated |
| @@ -102,7 +102,7 @@ config HNS3_HCLGE · 5 unmodified lines | ||
| 102 | 102 | tristate "Hisilicon HNS3 HCLGE Acceleration Engine & Compatibility Layer Support" |
| 103 | 103 | default m |
| 104 | 104 | depends on PCI_MSI |
| 105 | − ---help--- | |
| 105 | + help | |
| 106 | 106 | This selects the HNS3_HCLGE network acceleration engine & its hardware |
| 107 | 107 | compatibility layer. The engine would be used in Hisilicon hip08 family of |
| 108 | 108 | SoCs and further upcoming SoCs. |
| @@ -111,7 +111,7 @@ config HNS3_DCB · 2 unmodified lines | ||
| 111 | 111 | bool "Hisilicon HNS3 Data Center Bridge Support" |
| 112 | 112 | default n |
| 113 | 113 | depends on HNS3_HCLGE && DCB |
| 114 | − ---help--- | |
| 114 | + help | |
| 115 | 115 | Say Y here if you want to use Data Center Bridging (DCB) in the HNS3 driver. |
| 116 | 116 | |
| 117 | 117 | If unsure, say N. |
| @@ -120,7 +120,7 @@ config HNS3_HCLGEVF · 2 unmodified lines | ||
| 120 | 120 | tristate "Hisilicon HNS3VF Acceleration Engine & Compatibility Layer Support" |
| 121 | 121 | depends on PCI_MSI |
| 122 | 122 | depends on HNS3_HCLGE |
| 123 | − ---help--- | |
| 123 | + help | |
| 124 | 124 | This selects the HNS3 VF drivers network acceleration engine & its hardware |
| 125 | 125 | compatibility layer. The engine would be used in Hisilicon hip08 family of |
| 126 | 126 | SoCs and further upcoming SoCs. |
| @@ -130,7 +130,7 @@ config HNS3_ENET · 3 unmodified lines | ||
| 130 | 130 | default m |
| 131 | 131 | depends on 64BIT && PCI |
| 132 | 132 | depends on INET |
| 133 | − ---help--- | |
| 133 | + help | |
| 134 | 134 | This selects the Ethernet Driver for Hisilicon Network Subsystem 3 for hip08 |
| 135 | 135 | family of SoCs. This module depends upon HNAE3 driver to access the HNAE3 |
| 136 | 136 | devices and their associated operations. |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_HUAWEI |
| 7 | 7 | bool "Huawei devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 11 | 11 | Note that the answer to this question doesn't directly affect the |
| 12 | 12 | kernel: saying N will just cause the configurator to skip all |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config HINIC |
| 7 | 7 | tristate "Huawei Intelligent PCIE Network Interface Card" |
| 8 | 8 | depends on (PCI_MSI && (X86 || ARM64)) |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This driver supports HiNIC PCIE Ethernet cards. |
| 11 | 11 | To compile this driver as part of the kernel, choose Y here. |
| 12 | 12 | If unsure, choose N. |
| @@ -7,7 +7,7 @@ config NET_VENDOR_I825XX · 6 unmodified lines | ||
| 7 | 7 | bool "Intel (82586/82593/82596) devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on NET_VENDOR_INTEL |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question does not directly affect the |
| @@ -20,14 +20,14 @@ if NET_VENDOR_I825XX · 6 unmodified lines | ||
| 20 | 20 | config ARM_ETHER1 |
| 21 | 21 | tristate "Acorn Ether1 support" |
| 22 | 22 | depends on ARM && ARCH_ACORN |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | If you have an Acorn system with one of these (AKA25) network cards, |
| 25 | 25 | you should say Y to this option if you wish to use it with Linux. |
| 26 | 26 | |
| 27 | 27 | config BVME6000_NET |
| 28 | 28 | tristate "BVME6000 Ethernet support" |
| 29 | 29 | depends on BVME6000 |
| 30 | − ---help--- | |
| 30 | + help | |
| 31 | 31 | This is the driver for the Ethernet interface on BVME4000 and |
| 32 | 32 | BVME6000 VME boards. Say Y here to include the driver for this chip |
| 33 | 33 | in your kernel. |
| @@ -36,14 +36,14 @@ config BVME6000_NET · 2 unmodified lines | ||
| 36 | 36 | config LASI_82596 |
| 37 | 37 | tristate "Lasi ethernet" |
| 38 | 38 | depends on GSC |
| 39 | − ---help--- | |
| 39 | + help | |
| 40 | 40 | Say Y here to support the builtin Intel 82596 ethernet controller |
| 41 | 41 | found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet. |
| 42 | 42 | |
| 43 | 43 | config MVME16x_NET |
| 44 | 44 | tristate "MVME16x Ethernet support" |
| 45 | 45 | depends on MVME16x |
| 46 | − ---help--- | |
| 46 | + help | |
| 47 | 47 | This is the driver for the Ethernet interface on the Motorola |
| 48 | 48 | MVME162, 166, 167, 172 and 177 boards. Say Y here to include the |
| 49 | 49 | driver for this chip in your kernel. |
| @@ -52,14 +52,14 @@ config MVME16x_NET · 2 unmodified lines | ||
| 52 | 52 | config SNI_82596 |
| 53 | 53 | tristate "SNI RM ethernet" |
| 54 | 54 | depends on SNI_RM |
| 55 | − ---help--- | |
| 55 | + help | |
| 56 | 56 | Say Y here to support the on-board Intel 82596 ethernet controller |
| 57 | 57 | built into SNI RM machines. |
| 58 | 58 | |
| 59 | 59 | config SUN3_82586 |
| 60 | 60 | bool "Sun3 on-board Intel 82586 support" |
| 61 | 61 | depends on SUN3 |
| 62 | − ---help--- | |
| 62 | + help | |
| 63 | 63 | This driver enables support for the on-board Intel 82586 based |
| 64 | 64 | Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note |
| 65 | 65 | that this driver does not support 82586-based adapters on additional |
| @@ -7,7 +7,7 @@ config NET_VENDOR_IBM · 6 unmodified lines | ||
| 7 | 7 | bool "IBM devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PPC_PSERIES || PPC_DCR || (IBMEBUS && SPARSEMEM) |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ if NET_VENDOR_IBM · 6 unmodified lines | ||
| 20 | 20 | config IBMVETH |
| 21 | 21 | tristate "IBM LAN Virtual Ethernet support" |
| 22 | 22 | depends on PPC_PSERIES |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | This driver supports virtual ethernet adapters on newer IBM iSeries |
| 25 | 25 | and pSeries systems. |
| 26 | 26 | |
| @@ -32,7 +32,7 @@ source "drivers/net/ethernet/ibm/emac/Kconfig" · 5 unmodified lines | ||
| 32 | 32 | config EHEA |
| 33 | 33 | tristate "eHEA Ethernet support" |
| 34 | 34 | depends on IBMEBUS && SPARSEMEM |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | This driver supports the IBM pSeries eHEA ethernet adapter. |
| 37 | 37 | |
| 38 | 38 | To compile the driver as a module, choose M here. The module |
| @@ -41,7 +41,7 @@ config EHEA · 2 unmodified lines | ||
| 41 | 41 | config IBMVNIC |
| 42 | 42 | tristate "IBM Virtual NIC support" |
| 43 | 43 | depends on PPC_PSERIES |
| 44 | − ---help--- | |
| 44 | + help | |
| 45 | 45 | This driver supports Virtual NIC adapters on IBM i and IBM System p |
| 46 | 46 | systems. |
| 47 | 47 | |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_INTEL |
| 7 | 7 | bool "Intel devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ config E100 · 7 unmodified lines | ||
| 20 | 20 | tristate "Intel(R) PRO/100+ support" |
| 21 | 21 | depends on PCI |
| 22 | 22 | select MII |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | This driver supports Intel(R) PRO/100 family of adapters. |
| 25 | 25 | To verify that your adapter is supported, find the board ID number |
| 26 | 26 | on the adapter. Look for a label that has a barcode and a number |
| @@ -42,7 +42,7 @@ config E100 · 15 unmodified lines | ||
| 42 | 42 | config E1000 |
| 43 | 43 | tristate "Intel(R) PRO/1000 Gigabit Ethernet support" |
| 44 | 44 | depends on PCI |
| 45 | − ---help--- | |
| 45 | + help | |
| 46 | 46 | This driver supports Intel(R) PRO/1000 gigabit ethernet family of |
| 47 | 47 | adapters. For more information on how to identify your adapter, go |
| 48 | 48 | to the Adapter & Driver ID Guide that can be located at: |
| @@ -60,7 +60,7 @@ config E1000E · 11 unmodified lines | ||
| 60 | 60 | depends on PCI && (!SPARC32 || BROKEN) |
| 61 | 61 | select CRC32 |
| 62 | 62 | imply PTP_1588_CLOCK |
| 63 | − ---help--- | |
| 63 | + help | |
| 64 | 64 | This driver supports the PCI-Express Intel(R) PRO/1000 gigabit |
| 65 | 65 | ethernet family of adapters. For PCI or PCI-X e1000 adapters, |
| 66 | 66 | use the regular e1000 driver For more information on how to |
| @@ -79,7 +79,7 @@ config E1000E_HWTS · 12 unmodified lines | ||
| 79 | 79 | bool "Support HW cross-timestamp on PCH devices" |
| 80 | 80 | default y |
| 81 | 81 | depends on E1000E && X86 |
| 82 | − ---help--- | |
| 82 | + help | |
| 83 | 83 | Say Y to enable hardware supported cross-timestamping on PCH |
| 84 | 84 | devices. The cross-timestamp is available through the PTP clock |
| 85 | 85 | driver precise cross-timestamp ioctl (PTP_SYS_OFFSET_PRECISE). |
| @@ -90,7 +90,7 @@ config IGB · 4 unmodified lines | ||
| 90 | 90 | imply PTP_1588_CLOCK |
| 91 | 91 | select I2C |
| 92 | 92 | select I2C_ALGOBIT |
| 93 | − ---help--- | |
| 93 | + help | |
| 94 | 94 | This driver supports Intel(R) 82575/82576 gigabit ethernet family of |
| 95 | 95 | adapters. For more information on how to identify your adapter, go |
| 96 | 96 | to the Adapter & Driver ID Guide that can be located at: |
| @@ -107,7 +107,7 @@ config IGB_HWMON · 10 unmodified lines | ||
| 107 | 107 | bool "Intel(R) PCI-Express Gigabit adapters HWMON support" |
| 108 | 108 | default y |
| 109 | 109 | depends on IGB && HWMON && !(IGB=y && HWMON=m) |
| 110 | − ---help--- | |
| 110 | + help | |
| 111 | 111 | Say Y if you want to expose thermal sensor data on Intel devices. |
| 112 | 112 | |
| 113 | 113 | Some of our devices contain thermal sensors, both external and internal. |
| @@ -118,7 +118,7 @@ config IGB_DCA · 4 unmodified lines | ||
| 118 | 118 | bool "Direct Cache Access (DCA) Support" |
| 119 | 119 | default y |
| 120 | 120 | depends on IGB && DCA && !(IGB=y && DCA=m) |
| 121 | − ---help--- | |
| 121 | + help | |
| 122 | 122 | Say Y here if you want to use Direct Cache Access (DCA) in the |
| 123 | 123 | driver. DCA is a method for warming the CPU cache before data |
| 124 | 124 | is used, with the intent of lessening the impact of cache misses. |
| @@ -126,7 +126,7 @@ config IGB_DCA · 1 unmodified line | ||
| 126 | 126 | config IGBVF |
| 127 | 127 | tristate "Intel(R) 82576 Virtual Function Ethernet support" |
| 128 | 128 | depends on PCI |
| 129 | − ---help--- | |
| 129 | + help | |
| 130 | 130 | This driver supports Intel(R) 82576 virtual functions. For more |
| 131 | 131 | information on how to identify your adapter, go to the Adapter & |
| 132 | 132 | Driver ID Guide that can be located at: |
| @@ -142,7 +142,7 @@ config IGBVF · 9 unmodified lines | ||
| 142 | 142 | config IXGB |
| 143 | 143 | tristate "Intel(R) PRO/10GbE support" |
| 144 | 144 | depends on PCI |
| 145 | − ---help--- | |
| 145 | + help | |
| 146 | 146 | This driver supports Intel(R) PRO/10GbE family of adapters for |
| 147 | 147 | PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver |
| 148 | 148 | instead. For more information on how to identify your adapter, go |
| @@ -162,7 +162,7 @@ config IXGBE · 13 unmodified lines | ||
| 162 | 162 | select MDIO |
| 163 | 163 | select PHYLIB |
| 164 | 164 | imply PTP_1588_CLOCK |
| 165 | − ---help--- | |
| 165 | + help | |
| 166 | 166 | This driver supports Intel(R) 10GbE PCI Express family of |
| 167 | 167 | adapters. For more information on how to identify your adapter, go |
| 168 | 168 | to the Adapter & Driver ID Guide that can be located at: |
| @@ -179,7 +179,7 @@ config IXGBE_HWMON · 10 unmodified lines | ||
| 179 | 179 | bool "Intel(R) 10GbE PCI Express adapters HWMON support" |
| 180 | 180 | default y |
| 181 | 181 | depends on IXGBE && HWMON && !(IXGBE=y && HWMON=m) |
| 182 | − ---help--- | |
| 182 | + help | |
| 183 | 183 | Say Y if you want to expose the thermal sensor data on some of |
| 184 | 184 | our cards, via a hwmon sysfs interface. |
| 185 | 185 | |
| @@ -187,7 +187,7 @@ config IXGBE_DCA · 1 unmodified line | ||
| 187 | 187 | bool "Direct Cache Access (DCA) Support" |
| 188 | 188 | default y |
| 189 | 189 | depends on IXGBE && DCA && !(IXGBE=y && DCA=m) |
| 190 | − ---help--- | |
| 190 | + help | |
| 191 | 191 | Say Y here if you want to use Direct Cache Access (DCA) in the |
| 192 | 192 | driver. DCA is a method for warming the CPU cache before data |
| 193 | 193 | is used, with the intent of lessening the impact of cache misses. |
| @@ -196,7 +196,7 @@ config IXGBE_DCB · 2 unmodified lines | ||
| 196 | 196 | bool "Data Center Bridging (DCB) Support" |
| 197 | 197 | default n |
| 198 | 198 | depends on IXGBE && DCB |
| 199 | − ---help--- | |
| 199 | + help | |
| 200 | 200 | Say Y here if you want to use Data Center Bridging (DCB) in the |
| 201 | 201 | driver. |
| 202 | 202 | |
| @@ -208,13 +208,13 @@ config IXGBE_IPSEC · 5 unmodified lines | ||
| 208 | 208 | depends on XFRM_OFFLOAD |
| 209 | 209 | default y |
| 210 | 210 | select XFRM_ALGO |
| 211 | − ---help--- | |
| 211 | + help | |
| 212 | 212 | Enable support for IPSec offload in ixgbe.ko |
| 213 | 213 | |
| 214 | 214 | config IXGBEVF |
| 215 | 215 | tristate "Intel(R) 10GbE PCI Express Virtual Function Ethernet support" |
| 216 | 216 | depends on PCI_MSI |
| 217 | − ---help--- | |
| 217 | + help | |
| 218 | 218 | This driver supports Intel(R) PCI Express virtual functions for the |
| 219 | 219 | Intel(R) ixgbe driver. For more information on how to identify your |
| 220 | 220 | adapter, go to the Adapter & Driver ID Guide that can be located at: |
| @@ -234,14 +234,14 @@ config IXGBEVF_IPSEC · 13 unmodified lines | ||
| 234 | 234 | depends on XFRM_OFFLOAD |
| 235 | 235 | default y |
| 236 | 236 | select XFRM_ALGO |
| 237 | − ---help--- | |
| 237 | + help | |
| 238 | 238 | Enable support for IPSec offload in ixgbevf.ko |
| 239 | 239 | |
| 240 | 240 | config I40E |
| 241 | 241 | tristate "Intel(R) Ethernet Controller XL710 Family support" |
| 242 | 242 | imply PTP_1588_CLOCK |
| 243 | 243 | depends on PCI |
| 244 | − ---help--- | |
| 244 | + help | |
| 245 | 245 | This driver supports Intel(R) Ethernet Controller XL710 Family of |
| 246 | 246 | devices. For more information on how to identify your adapter, go |
| 247 | 247 | to the Adapter & Driver ID Guide that can be located at: |
| @@ -258,7 +258,7 @@ config I40E_DCB · 10 unmodified lines | ||
| 258 | 258 | bool "Data Center Bridging (DCB) Support" |
| 259 | 259 | default n |
| 260 | 260 | depends on I40E && DCB |
| 261 | − ---help--- | |
| 261 | + help | |
| 262 | 262 | Say Y here if you want to use Data Center Bridging (DCB) in the |
| 263 | 263 | driver. |
| 264 | 264 | |
| @@ -272,7 +272,7 @@ config I40EVF · 7 unmodified lines | ||
| 272 | 272 | tristate "Intel(R) Ethernet Adaptive Virtual Function support" |
| 273 | 273 | select IAVF |
| 274 | 274 | depends on PCI_MSI |
| 275 | − ---help--- | |
| 275 | + help | |
| 276 | 276 | This driver supports virtual functions for Intel XL710, |
| 277 | 277 | X710, X722, XXV710, and all devices advertising support for |
| 278 | 278 | Intel Ethernet Adaptive Virtual Function devices. For more |
| @@ -295,7 +295,7 @@ config ICE · 16 unmodified lines | ||
| 295 | 295 | default n |
| 296 | 296 | depends on PCI_MSI |
| 297 | 297 | select NET_DEVLINK |
| 298 | − ---help--- | |
| 298 | + help | |
| 299 | 299 | This driver supports Intel(R) Ethernet Connection E800 Series of |
| 300 | 300 | devices. For more information on how to identify your adapter, go |
| 301 | 301 | to the Adapter & Driver ID Guide that can be located at: |
| @@ -313,7 +313,7 @@ config FM10K · 11 unmodified lines | ||
| 313 | 313 | default n |
| 314 | 314 | depends on PCI_MSI |
| 315 | 315 | imply PTP_1588_CLOCK |
| 316 | − ---help--- | |
| 316 | + help | |
| 317 | 317 | This driver supports Intel(R) FM10000 Ethernet Switch Host |
| 318 | 318 | Interface. For more information on how to identify your adapter, |
| 319 | 319 | go to the Adapter & Driver ID Guide that can be located at: |
| @@ -330,7 +330,7 @@ config IGC · 10 unmodified lines | ||
| 330 | 330 | tristate "Intel(R) Ethernet Controller I225-LM/I225-V support" |
| 331 | 331 | default n |
| 332 | 332 | depends on PCI |
| 333 | − ---help--- | |
| 333 | + help | |
| 334 | 334 | This driver supports Intel(R) Ethernet Controller I225-LM/I225-V |
| 335 | 335 | family of adapters. |
| 336 | 336 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_MARVELL · 6 unmodified lines | ||
| 7 | 7 | bool "Marvell devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI || CPU_PXA168 || MV64X60 || PPC32 || PLAT_ORION || INET || COMPILE_TEST |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -23,7 +23,7 @@ config MV643XX_ETH · 9 unmodified lines | ||
| 23 | 23 | depends on INET |
| 24 | 24 | select PHYLIB |
| 25 | 25 | select MVMDIO |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | This driver supports the gigabit ethernet MACs in the |
| 28 | 28 | Marvell Discovery PPC/MIPS chipset family (MV643XX) and |
| 29 | 29 | in the Marvell Orion ARM SoC family. |
| @@ -35,7 +35,7 @@ config MVMDIO · 5 unmodified lines | ||
| 35 | 35 | tristate "Marvell MDIO interface support" |
| 36 | 36 | depends on HAS_IOMEM |
| 37 | 37 | select PHYLIB |
| 38 | − ---help--- | |
| 38 | + help | |
| 39 | 39 | This driver supports the MDIO interface found in the network |
| 40 | 40 | interface units of the Marvell EBU SoCs (Kirkwood, Orion5x, |
| 41 | 41 | Dove, Armada 370 and Armada XP). |
| @@ -46,7 +46,7 @@ config MVNETA_BM_ENABLE · 4 unmodified lines | ||
| 46 | 46 | tristate "Marvell Armada 38x/XP network interface BM support" |
| 47 | 47 | depends on MVNETA |
| 48 | 48 | depends on !64BIT |
| 49 | − ---help--- | |
| 49 | + help | |
| 50 | 50 | This driver supports auxiliary block of the network |
| 51 | 51 | interface units in the Marvell ARMADA XP and ARMADA 38x SoC |
| 52 | 52 | family, which is called buffer manager. |
| @@ -62,7 +62,7 @@ config MVNETA · 9 unmodified lines | ||
| 62 | 62 | select MVMDIO |
| 63 | 63 | select PHYLINK |
| 64 | 64 | select PAGE_POOL |
| 65 | − ---help--- | |
| 65 | + help | |
| 66 | 66 | This driver supports the network interface units in the |
| 67 | 67 | Marvell ARMADA XP, ARMADA 370, ARMADA 38x and |
| 68 | 68 | ARMADA 37xx SoC family. |
| @@ -87,7 +87,7 @@ config MVPP2 · 18 unmodified lines | ||
| 87 | 87 | depends on ARCH_MVEBU || COMPILE_TEST |
| 88 | 88 | select MVMDIO |
| 89 | 89 | select PHYLINK |
| 90 | − ---help--- | |
| 90 | + help | |
| 91 | 91 | This driver supports the network interface units in the |
| 92 | 92 | Marvell ARMADA 375, 7K and 8K SoCs. |
| 93 | 93 | |
| @@ -96,7 +96,7 @@ config PXA168_ETH · 2 unmodified lines | ||
| 96 | 96 | depends on HAS_IOMEM |
| 97 | 97 | depends on CPU_PXA168 || ARCH_BERLIN || COMPILE_TEST |
| 98 | 98 | select PHYLIB |
| 99 | − ---help--- | |
| 99 | + help | |
| 100 | 100 | This driver supports the pxa168 Ethernet ports. |
| 101 | 101 | |
| 102 | 102 | To compile this driver as a module, choose M here. The module |
| @@ -106,7 +106,7 @@ config SKGE · 3 unmodified lines | ||
| 106 | 106 | tristate "Marvell Yukon Gigabit Ethernet support" |
| 107 | 107 | depends on PCI |
| 108 | 108 | select CRC32 |
| 109 | − ---help--- | |
| 109 | + help | |
| 110 | 110 | This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx |
| 111 | 111 | and related Gigabit Ethernet adapters. It is a new smaller driver |
| 112 | 112 | with better performance and more complete ethtool support. |
| @@ -127,7 +127,7 @@ config SKGE · 14 unmodified lines | ||
| 127 | 127 | config SKGE_DEBUG |
| 128 | 128 | bool "Debugging interface" |
| 129 | 129 | depends on SKGE && DEBUG_FS |
| 130 | − ---help--- | |
| 130 | + help | |
| 131 | 131 | This option adds the ability to dump driver state for debugging. |
| 132 | 132 | The file /sys/kernel/debug/skge/ethX displays the state of the internal |
| 133 | 133 | transmit and receive rings. |
| @@ -137,7 +137,7 @@ config SKGE_DEBUG · 3 unmodified lines | ||
| 137 | 137 | config SKGE_GENESIS |
| 138 | 138 | bool "Support for older SysKonnect Genesis boards" |
| 139 | 139 | depends on SKGE |
| 140 | − ---help--- | |
| 140 | + help | |
| 141 | 141 | This enables support for the older and uncommon SysKonnect Genesis |
| 142 | 142 | chips, which support MII via an external transceiver, instead of |
| 143 | 143 | an internal one. Disabling this option will save some memory |
| @@ -147,7 +147,7 @@ config SKY2 · 3 unmodified lines | ||
| 147 | 147 | tristate "Marvell Yukon 2 support" |
| 148 | 148 | depends on PCI |
| 149 | 149 | select CRC32 |
| 150 | − ---help--- | |
| 150 | + help | |
| 151 | 151 | This driver supports Gigabit Ethernet adapters based on the |
| 152 | 152 | Marvell Yukon 2 chipset: |
| 153 | 153 | Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/ |
| @@ -162,7 +162,7 @@ config SKY2 · 8 unmodified lines | ||
| 162 | 162 | config SKY2_DEBUG |
| 163 | 163 | bool "Debugging interface" |
| 164 | 164 | depends on SKY2 && DEBUG_FS |
| 165 | − ---help--- | |
| 165 | + help | |
| 166 | 166 | This option adds the ability to dump driver state for debugging. |
| 167 | 167 | The file /sys/kernel/debug/sky2/ethX displays the state of the internal |
| 168 | 168 | transmit and receive rings. |
| @@ -21,7 +21,7 @@ config NDC_DIS_DYNAMIC_CACHING · 20 unmodified lines | ||
| 21 | 21 | bool "Disable caching of dynamic entries in NDC" |
| 22 | 22 | depends on OCTEONTX2_AF |
| 23 | 23 | default n |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | This config option disables caching of dynamic entries such as NIX SQEs |
| 26 | 26 | , NPA stack pages etc in NDC. Also locks down NIX SQ/CQ/RQ/RSS and |
| 27 | 27 | NPA Aura/Pool contexts. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config NET_VENDOR_MEDIATEK |
| 3 | 3 | bool "MediaTek devices" |
| 4 | 4 | depends on ARCH_MEDIATEK || SOC_MT7621 || SOC_MT7620 |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a Mediatek SoC with ethernet, say Y. |
| 7 | 7 | |
| 8 | 8 | if NET_VENDOR_MEDIATEK |
| @@ -10,7 +10,7 @@ if NET_VENDOR_MEDIATEK · 1 unmodified line | ||
| 10 | 10 | config NET_MEDIATEK_SOC |
| 11 | 11 | tristate "MediaTek SoC Gigabit Ethernet support" |
| 12 | 12 | select PHYLINK |
| 13 | − ---help--- | |
| 13 | + help | |
| 14 | 14 | This driver supports the gigabit ethernet MACs in the |
| 15 | 15 | MediaTek SoC family. |
| 16 | 16 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_MELLANOX · 6 unmodified lines | ||
| 7 | 7 | bool "Mellanox devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI || I2C |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet or RDMA) device belonging to this |
| 12 | 12 | class, say Y. |
| 13 | 13 | |
| @@ -8,7 +8,7 @@ config MLX4_EN · 7 unmodified lines | ||
| 8 | 8 | depends on PCI && NETDEVICES && ETHERNET && INET |
| 9 | 9 | select MLX4_CORE |
| 10 | 10 | imply PTP_1588_CLOCK |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | This driver supports Mellanox Technologies ConnectX Ethernet |
| 13 | 13 | devices. |
| 14 | 14 | |
| @@ -16,7 +16,7 @@ config MLX4_EN_DCB · 1 unmodified line | ||
| 16 | 16 | bool "Data Center Bridging (DCB) Support" |
| 17 | 17 | default y |
| 18 | 18 | depends on MLX4_EN && DCB |
| 19 | − ---help--- | |
| 19 | + help | |
| 20 | 20 | Say Y here if you want to use Data Center Bridging (DCB) in the |
| 21 | 21 | driver. |
| 22 | 22 | If set to N, will not be able to configure QoS and ratelimit attributes. |
| @@ -34,7 +34,7 @@ config MLX4_DEBUG · 11 unmodified lines | ||
| 34 | 34 | bool "Verbose debugging output" if (MLX4_CORE && EXPERT) |
| 35 | 35 | depends on MLX4_CORE |
| 36 | 36 | default y |
| 37 | − ---help--- | |
| 37 | + help | |
| 38 | 38 | This option causes debugging code to be compiled into the |
| 39 | 39 | mlx4_core driver. The output can be turned on via the |
| 40 | 40 | debug_level module parameter (which can also be set after |
| @@ -44,6 +44,6 @@ config MLX4_CORE_GEN2 · 3 unmodified lines | ||
| 44 | 44 | bool "Support for old gen2 Mellanox PCI IDs" if (MLX4_CORE) |
| 45 | 45 | depends on MLX4_CORE |
| 46 | 46 | default y |
| 47 | − ---help--- | |
| 47 | + help | |
| 48 | 48 | Say Y here if you want to use old gen2 Mellanox devices in the |
| 49 | 49 | driver. |
| @@ -12,7 +12,7 @@ config MLX5_CORE · 11 unmodified lines | ||
| 12 | 12 | depends on PTP_1588_CLOCK || !PTP_1588_CLOCK |
| 13 | 13 | depends on PCI_HYPERV_INTERFACE || !PCI_HYPERV_INTERFACE |
| 14 | 14 | default n |
| 15 | − ---help--- | |
| 15 | + help | |
| 16 | 16 | Core driver for low level functionality of the ConnectX-4 and |
| 17 | 17 | Connect-IB cards by Mellanox Technologies. |
| 18 | 18 | |
| @@ -23,7 +23,7 @@ config MLX5_FPGA · 4 unmodified lines | ||
| 23 | 23 | bool "Mellanox Technologies Innova support" |
| 24 | 24 | depends on MLX5_CORE |
| 25 | 25 | select MLX5_ACCEL |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | Build support for the Innova family of network cards by Mellanox |
| 28 | 28 | Technologies. Innova network cards are comprised of a ConnectX chip |
| 29 | 29 | and an FPGA chip on one board. If you select this option, the |
| @@ -36,14 +36,14 @@ config MLX5_CORE_EN · 6 unmodified lines | ||
| 36 | 36 | select PAGE_POOL |
| 37 | 37 | select DIMLIB |
| 38 | 38 | default n |
| 39 | − ---help--- | |
| 39 | + help | |
| 40 | 40 | Ethernet support in Mellanox Technologies ConnectX-4 NIC. |
| 41 | 41 | |
| 42 | 42 | config MLX5_EN_ARFS |
| 43 | 43 | bool "Mellanox MLX5 ethernet accelerated receive flow steering (ARFS) support" |
| 44 | 44 | depends on MLX5_CORE_EN && RFS_ACCEL |
| 45 | 45 | default y |
| 46 | − ---help--- | |
| 46 | + help | |
| 47 | 47 | Mellanox MLX5 ethernet hardware-accelerated receive flow steering support, |
| 48 | 48 | Enables ethernet netdevice arfs support and ntuple filtering. |
| 49 | 49 | |
| @@ -51,7 +51,7 @@ config MLX5_EN_RXNFC · 1 unmodified line | ||
| 51 | 51 | bool "Mellanox MLX5 ethernet rx nfc flow steering support" |
| 52 | 52 | depends on MLX5_CORE_EN |
| 53 | 53 | default y |
| 54 | − ---help--- | |
| 54 | + help | |
| 55 | 55 | Mellanox MLX5 ethernet rx nfc flow steering support |
| 56 | 56 | Enables ethtool receive network flow classification, which allows user defined |
| 57 | 57 | flow rules to direct traffic into arbitrary rx queue via ethtool set/get_rxnfc |
| @@ -61,7 +61,7 @@ config MLX5_MPFS · 3 unmodified lines | ||
| 61 | 61 | bool "Mellanox Technologies MLX5 MPFS support" |
| 62 | 62 | depends on MLX5_CORE_EN |
| 63 | 63 | default y |
| 64 | − ---help--- | |
| 64 | + help | |
| 65 | 65 | Mellanox Technologies Ethernet Multi-Physical Function Switch (MPFS) |
| 66 | 66 | support in ConnectX NIC. MPFs is required for when multi-PF configuration |
| 67 | 67 | is enabled to allow passing user configured unicast MAC addresses to the |
| @@ -71,7 +71,7 @@ config MLX5_ESWITCH · 3 unmodified lines | ||
| 71 | 71 | bool "Mellanox Technologies MLX5 SRIOV E-Switch support" |
| 72 | 72 | depends on MLX5_CORE_EN && NET_SWITCHDEV |
| 73 | 73 | default y |
| 74 | − ---help--- | |
| 74 | + help | |
| 75 | 75 | Mellanox Technologies Ethernet SRIOV E-Switch support in ConnectX NIC. |
| 76 | 76 | E-Switch provides internal SRIOV packet steering and switching for the |
| 77 | 77 | enabled VFs and PF in two available modes: |
| @@ -107,7 +107,7 @@ config MLX5_CORE_EN_DCB · 29 unmodified lines | ||
| 107 | 107 | bool "Data Center Bridging (DCB) Support" |
| 108 | 108 | default y |
| 109 | 109 | depends on MLX5_CORE_EN && DCB |
| 110 | − ---help--- | |
| 110 | + help | |
| 111 | 111 | Say Y here if you want to use Data Center Bridging (DCB) in the |
| 112 | 112 | driver. |
| 113 | 113 | If set to N, will not be able to configure QoS and ratelimit attributes. |
| @@ -119,7 +119,7 @@ config MLX5_CORE_IPOIB · 5 unmodified lines | ||
| 119 | 119 | bool "Mellanox 5th generation network adapters (connectX series) IPoIB offloads support" |
| 120 | 120 | depends on MLX5_CORE_EN |
| 121 | 121 | default n |
| 122 | − ---help--- | |
| 122 | + help | |
| 123 | 123 | MLX5 IPoIB offloads & acceleration support. |
| 124 | 124 | |
| 125 | 125 | config MLX5_FPGA_IPSEC |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | |
| 6 | 6 | config MLXFW |
| 7 | 7 | tristate "Mellanox Technologies firmware flash module" |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | This driver supports Mellanox Technologies Firmware |
| 10 | 10 | flashing common logic. |
| 11 | 11 | |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config MLXSW_CORE |
| 7 | 7 | tristate "Mellanox Technologies Switch ASICs support" |
| 8 | 8 | select NET_DEVLINK |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This driver supports Mellanox Technologies Switch ASICs family. |
| 11 | 11 | |
| 12 | 12 | To compile this driver as a module, choose M here: the |
| @@ -17,14 +17,14 @@ config MLXSW_CORE_HWMON · 4 unmodified lines | ||
| 17 | 17 | depends on MLXSW_CORE && HWMON |
| 18 | 18 | depends on !(MLXSW_CORE=y && HWMON=m) |
| 19 | 19 | default y |
| 20 | − ---help--- | |
| 20 | + help | |
| 21 | 21 | Say Y here if you want to expose HWMON interface on mlxsw devices. |
| 22 | 22 | |
| 23 | 23 | config MLXSW_CORE_THERMAL |
| 24 | 24 | bool "Thermal zone support for Mellanox Technologies Switch ASICs" |
| 25 | 25 | depends on MLXSW_CORE && THERMAL |
| 26 | 26 | default y |
| 27 | − ---help--- | |
| 27 | + help | |
| 28 | 28 | Say Y here if you want to automatically control fans speed according |
| 29 | 29 | ambient temperature reported by ASIC. |
| 30 | 30 | |
| @@ -32,7 +32,7 @@ config MLXSW_PCI · 1 unmodified line | ||
| 32 | 32 | tristate "PCI bus implementation for Mellanox Technologies Switch ASICs" |
| 33 | 33 | depends on PCI && HAS_IOMEM && MLXSW_CORE |
| 34 | 34 | default m |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | This is PCI bus implementation for Mellanox Technologies Switch ASICs. |
| 37 | 37 | |
| 38 | 38 | To compile this driver as a module, choose M here: the |
| @@ -42,7 +42,7 @@ config MLXSW_I2C · 3 unmodified lines | ||
| 42 | 42 | tristate "I2C bus implementation for Mellanox Technologies Switch ASICs" |
| 43 | 43 | depends on I2C && MLXSW_CORE |
| 44 | 44 | default m |
| 45 | − ---help--- | |
| 45 | + help | |
| 46 | 46 | This is I2C bus implementation for Mellanox Technologies Switch ASICs. |
| 47 | 47 | |
| 48 | 48 | To compile this driver as a module, choose M here: the |
| @@ -52,7 +52,7 @@ config MLXSW_SWITCHIB · 3 unmodified lines | ||
| 52 | 52 | tristate "Mellanox Technologies SwitchIB and SwitchIB-2 support" |
| 53 | 53 | depends on MLXSW_CORE && MLXSW_PCI && NET_SWITCHDEV |
| 54 | 54 | default m |
| 55 | − ---help--- | |
| 55 | + help | |
| 56 | 56 | This driver supports Mellanox Technologies SwitchIB and SwitchIB-2 |
| 57 | 57 | Infiniband Switch ASICs. |
| 58 | 58 | |
| @@ -63,7 +63,7 @@ config MLXSW_SWITCHX2 · 4 unmodified lines | ||
| 63 | 63 | tristate "Mellanox Technologies SwitchX-2 support" |
| 64 | 64 | depends on MLXSW_CORE && MLXSW_PCI && NET_SWITCHDEV |
| 65 | 65 | default m |
| 66 | − ---help--- | |
| 66 | + help | |
| 67 | 67 | This driver supports Mellanox Technologies SwitchX-2 Ethernet |
| 68 | 68 | Switch ASICs. |
| 69 | 69 | |
| @@ -86,7 +86,7 @@ config MLXSW_SPECTRUM · 16 unmodified lines | ||
| 86 | 86 | imply PTP_1588_CLOCK |
| 87 | 87 | select NET_PTP_CLASSIFY if PTP_1588_CLOCK |
| 88 | 88 | default m |
| 89 | − ---help--- | |
| 89 | + help | |
| 90 | 90 | This driver supports Mellanox Technologies |
| 91 | 91 | Spectrum/Spectrum-2/Spectrum-3 Ethernet Switch ASICs. |
| 92 | 92 | |
| @@ -97,7 +97,7 @@ config MLXSW_SPECTRUM_DCB · 4 unmodified lines | ||
| 97 | 97 | bool "Data Center Bridging (DCB) support" |
| 98 | 98 | depends on MLXSW_SPECTRUM && DCB |
| 99 | 99 | default y |
| 100 | − ---help--- | |
| 100 | + help | |
| 101 | 101 | Say Y here if you want to use Data Center Bridging (DCB) in the |
| 102 | 102 | driver. |
| 103 | 103 | |
| @@ -105,7 +105,7 @@ config MLXSW_MINIMAL · 1 unmodified line | ||
| 105 | 105 | tristate "Mellanox Technologies minimal I2C support" |
| 106 | 106 | depends on MLXSW_CORE && MLXSW_I2C |
| 107 | 107 | default m |
| 108 | − ---help--- | |
| 108 | + help | |
| 109 | 109 | This driver supports I2C access for Mellanox Technologies Switch |
| 110 | 110 | ASICs. |
| 111 | 111 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_MICREL · 6 unmodified lines | ||
| 7 | 7 | bool "Micrel devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on (HAS_IOMEM && DMA_ENGINE) || SPI || PCI || HAS_IOMEM |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ if NET_VENDOR_MICREL · 6 unmodified lines | ||
| 20 | 20 | config KS8842 |
| 21 | 21 | tristate "Micrel KSZ8841/42 with generic bus interface" |
| 22 | 22 | depends on HAS_IOMEM && DMA_ENGINE |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | This platform driver is for KSZ8841(1-port) / KS8842(2-port) |
| 25 | 25 | ethernet switch chip (managed, VLAN, QoS) from Micrel or |
| 26 | 26 | Timberdale(FPGA). |
| @@ -31,7 +31,7 @@ config KS8851 · 4 unmodified lines | ||
| 31 | 31 | select MII |
| 32 | 32 | select CRC32 |
| 33 | 33 | select EEPROM_93CX6 |
| 34 | − ---help--- | |
| 34 | + help | |
| 35 | 35 | SPI driver for Micrel KS8851 SPI attached network chip. |
| 36 | 36 | |
| 37 | 37 | config KS8851_MLL |
| @@ -40,7 +40,7 @@ config KS8851_MLL · 2 unmodified lines | ||
| 40 | 40 | select MII |
| 41 | 41 | select CRC32 |
| 42 | 42 | select EEPROM_93CX6 |
| 43 | − ---help--- | |
| 43 | + help | |
| 44 | 44 | This platform driver is for Micrel KS8851 Address/data bus |
| 45 | 45 | multiplexed network chip. |
| 46 | 46 | |
| @@ -49,7 +49,7 @@ config KSZ884X_PCI · 2 unmodified lines | ||
| 49 | 49 | depends on PCI |
| 50 | 50 | select MII |
| 51 | 51 | select CRC32 |
| 52 | − ---help--- | |
| 52 | + help | |
| 53 | 53 | This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip. |
| 54 | 54 | |
| 55 | 55 | To compile this driver as a module, choose M here. The module |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_MICROCHIP |
| 7 | 7 | bool "Microchip devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ config ENC28J60 · 7 unmodified lines | ||
| 20 | 20 | tristate "ENC28J60 support" |
| 21 | 21 | depends on SPI |
| 22 | 22 | select CRC32 |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | Support for the Microchip EN28J60 ethernet chip. |
| 25 | 25 | |
| 26 | 26 | To compile this driver as a module, choose M here. The module will be |
| @@ -29,14 +29,14 @@ config ENC28J60 · 2 unmodified lines | ||
| 29 | 29 | config ENC28J60_WRITEVERIFY |
| 30 | 30 | bool "Enable write verify" |
| 31 | 31 | depends on ENC28J60 |
| 32 | − ---help--- | |
| 32 | + help | |
| 33 | 33 | Enable the verify after the buffer write useful for debugging purpose. |
| 34 | 34 | If unsure, say N. |
| 35 | 35 | |
| 36 | 36 | config ENCX24J600 |
| 37 | 37 | tristate "ENCX24J600 support" |
| 38 | 38 | depends on SPI |
| 39 | − ---help--- | |
| 39 | + help | |
| 40 | 40 | Support for the Microchip ENC424J600/624J600 ethernet chip. |
| 41 | 41 | |
| 42 | 42 | To compile this driver as a module, choose M here. The module will be |
| @@ -47,7 +47,7 @@ config LAN743X · 4 unmodified lines | ||
| 47 | 47 | depends on PCI |
| 48 | 48 | select PHYLIB |
| 49 | 49 | select CRC16 |
| 50 | − ---help--- | |
| 50 | + help | |
| 51 | 51 | Support for the Microchip LAN743x PCI Express Gigabit Ethernet chip |
| 52 | 52 | |
| 53 | 53 | To compile this driver as a module, choose M here. The module will be |
| @@ -7,7 +7,7 @@ config NET_VENDOR_MOXART · 6 unmodified lines | ||
| 7 | 7 | bool "MOXA ART devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on (ARM && ARCH_MOXART) |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -21,7 +21,7 @@ config ARM_MOXART_ETHER · 7 unmodified lines | ||
| 21 | 21 | tristate "MOXART Ethernet support" |
| 22 | 22 | depends on ARM && ARCH_MOXART |
| 23 | 23 | select NET_CORE |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | If you wish to compile a kernel for a hardware with MOXA ART SoC and |
| 26 | 26 | want to use the internal ethernet then you should answer Y to this. |
| 27 | 27 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_MYRI · 6 unmodified lines | ||
| 7 | 7 | bool "Myricom devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI && INET |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -22,7 +22,7 @@ config MYRI10GE · 8 unmodified lines | ||
| 22 | 22 | depends on PCI && INET |
| 23 | 23 | select FW_LOADER |
| 24 | 24 | select CRC32 |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | This driver supports Myricom Myri-10G Dual Protocol interface in |
| 27 | 27 | Ethernet mode. If the eeprom on your board is not recent enough, |
| 28 | 28 | you will need a newer firmware image. |
| @@ -37,7 +37,7 @@ config MYRI10GE_DCA · 8 unmodified lines | ||
| 37 | 37 | bool "Direct Cache Access (DCA) Support" |
| 38 | 38 | default y |
| 39 | 39 | depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m) |
| 40 | − ---help--- | |
| 40 | + help | |
| 41 | 41 | Say Y here if you want to use Direct Cache Access (DCA) in the |
| 42 | 42 | driver. DCA is a method for warming the CPU cache before data |
| 43 | 43 | is used, with the intent of lessening the impact of cache misses. |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_NATSEMI |
| 7 | 7 | bool "National Semiconductor devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -19,7 +19,7 @@ if NET_VENDOR_NATSEMI · 6 unmodified lines | ||
| 19 | 19 | config MACSONIC |
| 20 | 20 | tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)" |
| 21 | 21 | depends on MAC |
| 22 | − ---help--- | |
| 22 | + help | |
| 23 | 23 | Support for NatSemi SONIC based Ethernet devices. This includes |
| 24 | 24 | the onboard Ethernet in many Quadras as well as some LC-PDS, |
| 25 | 25 | a few Nubus and all known Comm Slot Ethernet cards. If you have |
| @@ -31,7 +31,7 @@ config MACSONIC · 5 unmodified lines | ||
| 31 | 31 | config MIPS_JAZZ_SONIC |
| 32 | 32 | tristate "MIPS JAZZ onboard SONIC Ethernet support" |
| 33 | 33 | depends on MACH_JAZZ |
| 34 | − ---help--- | |
| 34 | + help | |
| 35 | 35 | This is the driver for the onboard card of MIPS Magnum 4000, |
| 36 | 36 | Acer PICA, Olivetti M700-10 and a few other identical OEM systems. |
| 37 | 37 | |
| @@ -39,7 +39,7 @@ config NATSEMI · 1 unmodified line | ||
| 39 | 39 | tristate "National Semiconductor DP8381x series PCI Ethernet support" |
| 40 | 40 | depends on PCI |
| 41 | 41 | select CRC32 |
| 42 | − ---help--- | |
| 42 | + help | |
| 43 | 43 | This driver is for the National Semiconductor DP83810 series, |
| 44 | 44 | which is used in cards from PureData, NetGear, Linksys |
| 45 | 45 | and others, including the 83815 chip. |
| @@ -49,7 +49,7 @@ config NATSEMI · 3 unmodified lines | ||
| 49 | 49 | config NS83820 |
| 50 | 50 | tristate "National Semiconductor DP83820 support" |
| 51 | 51 | depends on PCI |
| 52 | − ---help--- | |
| 52 | + help | |
| 53 | 53 | This is a driver for the National Semiconductor DP83820 series |
| 54 | 54 | of gigabit ethernet MACs. Cards using this chipset include |
| 55 | 55 | the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX, |
| @@ -59,7 +59,7 @@ config NS83820 · 3 unmodified lines | ||
| 59 | 59 | config XTENSA_XT2000_SONIC |
| 60 | 60 | tristate "Xtensa XT2000 onboard SONIC Ethernet support" |
| 61 | 61 | depends on XTENSA_PLATFORM_XT2000 |
| 62 | − ---help--- | |
| 62 | + help | |
| 63 | 63 | This is the driver for the onboard card of the Xtensa XT2000 board. |
| 64 | 64 | |
| 65 | 65 | endif # NET_VENDOR_NATSEMI |
| @@ -7,7 +7,7 @@ config NET_VENDOR_NETERION · 6 unmodified lines | ||
| 7 | 7 | bool "Neterion (Exar) devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ if NET_VENDOR_NETERION · 6 unmodified lines | ||
| 20 | 20 | config S2IO |
| 21 | 21 | tristate "Neterion (Exar) Xframe 10Gb Ethernet Adapter" |
| 22 | 22 | depends on PCI |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters. |
| 25 | 25 | These were originally released from S2IO, which renamed itself |
| 26 | 26 | Neterion. So, the adapters might be labeled as either one, depending |
| @@ -35,7 +35,7 @@ config S2IO · 8 unmodified lines | ||
| 35 | 35 | config VXGE |
| 36 | 36 | tristate "Neterion (Exar) X3100 Series 10GbE PCIe Server Adapter" |
| 37 | 37 | depends on PCI |
| 38 | − ---help--- | |
| 38 | + help | |
| 39 | 39 | This driver supports Exar Corp's X3100 Series 10 GbE PCIe |
| 40 | 40 | I/O Virtualized Server Adapter. These were originally released from |
| 41 | 41 | Neterion, which was later acquired by Exar. So, the adapters might be |
| @@ -51,7 +51,7 @@ config VXGE_DEBUG_TRACE_ALL · 9 unmodified lines | ||
| 51 | 51 | bool "Enabling All Debug trace statements in driver" |
| 52 | 52 | default n |
| 53 | 53 | depends on VXGE |
| 54 | − ---help--- | |
| 54 | + help | |
| 55 | 55 | Say Y here if you want to enabling all the debug trace statements in |
| 56 | 56 | the vxge driver. By default only few debug trace statements are |
| 57 | 57 | enabled. |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_NETRONOME |
| 7 | 7 | bool "Netronome(R) devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a Netronome(R) network (Ethernet) card or device, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -22,7 +22,7 @@ config NFP · 9 unmodified lines | ||
| 22 | 22 | depends on VXLAN || VXLAN=n |
| 23 | 23 | depends on TLS && TLS_DEVICE || TLS_DEVICE=n |
| 24 | 24 | select NET_DEVLINK |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | This driver supports the Netronome(R) NFP4000/NFP6000 based |
| 27 | 27 | cards working as a advanced Ethernet NIC. It works with both |
| 28 | 28 | SR-IOV physical and virtual functions. |
| @@ -33,7 +33,7 @@ config NFP_APP_FLOWER · 4 unmodified lines | ||
| 33 | 33 | depends on NET_SWITCHDEV |
| 34 | 34 | depends on IPV6!=m || NFP=m |
| 35 | 35 | default y |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | Enable driver support for TC Flower offload on NFP4000 and NFP6000. |
| 38 | 38 | Say Y, if you are planning to make use of TC Flower offload |
| 39 | 39 | either directly, with Open vSwitch, or any other way. Note that |
| @@ -55,7 +55,7 @@ config NFP_APP_ABM_NIC · 15 unmodified lines | ||
| 55 | 55 | config NFP_DEBUG |
| 56 | 56 | bool "Debug support for Netronome(R) NFP4000/NFP6000 NIC drivers" |
| 57 | 57 | depends on NFP |
| 58 | − ---help--- | |
| 58 | + help | |
| 59 | 59 | Enable extra sanity checks and debugfs support in |
| 60 | 60 | Netronome(R) NFP4000/NFP6000 NIC drivers. |
| 61 | 61 | Note: selecting this option may adversely impact |
| @@ -7,7 +7,7 @@ config NET_VENDOR_NVIDIA · 6 unmodified lines | ||
| 7 | 7 | bool "NVIDIA devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ if NET_VENDOR_NVIDIA · 6 unmodified lines | ||
| 20 | 20 | config FORCEDETH |
| 21 | 21 | tristate "nForce Ethernet support" |
| 22 | 22 | depends on PCI |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | If you have a network (Ethernet) controller of this type, say Y here. |
| 25 | 25 | |
| 26 | 26 | To compile this driver as a module, choose M here. The module |
| @@ -7,7 +7,7 @@ config NET_VENDOR_OKI · 6 unmodified lines | ||
| 7 | 7 | bool "OKI Semiconductor devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -9,7 +9,7 @@ config PCH_GBE · 8 unmodified lines | ||
| 9 | 9 | select MII |
| 10 | 10 | select PTP_1588_CLOCK_PCH |
| 11 | 11 | select NET_PTP_CLASSIFY |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | This is a gigabit ethernet driver for EG20T PCH. |
| 14 | 14 | EG20T PCH is the platform controller hub that is used in Intel's |
| 15 | 15 | general embedded platform. EG20T PCH has Gigabit Ethernet interface. |
| @@ -7,7 +7,7 @@ config NET_VENDOR_PACKET_ENGINES · 6 unmodified lines | ||
| 7 | 7 | bool "Packet Engines devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -21,7 +21,7 @@ config HAMACHI · 7 unmodified lines | ||
| 21 | 21 | tristate "Packet Engines Hamachi GNIC-II support" |
| 22 | 22 | depends on PCI |
| 23 | 23 | select MII |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | If you have a Gigabit Ethernet card of this type, say Y here. |
| 26 | 26 | |
| 27 | 27 | To compile this driver as a module, choose M here. The module will be |
| @@ -31,7 +31,7 @@ config YELLOWFIN · 3 unmodified lines | ||
| 31 | 31 | tristate "Packet Engines Yellowfin Gigabit-NIC support" |
| 32 | 32 | depends on PCI |
| 33 | 33 | select CRC32 |
| 34 | − ---help--- | |
| 34 | + help | |
| 35 | 35 | Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet |
| 36 | 36 | adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is |
| 37 | 37 | used by the Beowulf Linux cluster project. See |
| @@ -7,7 +7,7 @@ config NET_VENDOR_PASEMI · 6 unmodified lines | ||
| 7 | 7 | bool "PA Semi devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PPC_PASEMI && PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -21,7 +21,7 @@ config PASEMI_MAC · 7 unmodified lines | ||
| 21 | 21 | tristate "PA Semi 1/10Gbit MAC" |
| 22 | 22 | depends on PPC_PASEMI && PCI |
| 23 | 23 | select PHYLIB |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | This driver supports the on-chip 1/10Gbit Ethernet controller on |
| 26 | 26 | PA Semi's PWRficient line of chips. |
| 27 | 27 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_QLOGIC · 6 unmodified lines | ||
| 7 | 7 | bool "QLogic devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ if NET_VENDOR_QLOGIC · 6 unmodified lines | ||
| 20 | 20 | config QLA3XXX |
| 21 | 21 | tristate "QLogic QLA3XXX Network Driver Support" |
| 22 | 22 | depends on PCI |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | This driver supports QLogic ISP3XXX gigabit Ethernet cards. |
| 25 | 25 | |
| 26 | 26 | To compile this driver as a module, choose M here: the module |
| @@ -30,7 +30,7 @@ config QLCNIC · 3 unmodified lines | ||
| 30 | 30 | tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support" |
| 31 | 31 | depends on PCI |
| 32 | 32 | select FW_LOADER |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet |
| 35 | 35 | devices. |
| 36 | 36 | |
| @@ -38,7 +38,7 @@ config QLCNIC_SRIOV · 1 unmodified line | ||
| 38 | 38 | bool "QLOGIC QLCNIC 83XX family SR-IOV Support" |
| 39 | 39 | depends on QLCNIC && PCI_IOV |
| 40 | 40 | default y |
| 41 | − ---help--- | |
| 41 | + help | |
| 42 | 42 | This configuration parameter enables Single Root Input Output |
| 43 | 43 | Virtualization support for QLE83XX Converged Ethernet devices. |
| 44 | 44 | This allows for virtual function acceleration in virtualized |
| @@ -48,7 +48,7 @@ config QLCNIC_DCB · 3 unmodified lines | ||
| 48 | 48 | bool "QLOGIC QLCNIC 82XX and 83XX family DCB Support" |
| 49 | 49 | depends on QLCNIC && DCB |
| 50 | 50 | default y |
| 51 | − ---help--- | |
| 51 | + help | |
| 52 | 52 | This configuration parameter enables DCB support in QLE83XX |
| 53 | 53 | and QLE82XX Converged Ethernet devices. This allows for DCB |
| 54 | 54 | get operations support through rtNetlink interface. Only CEE |
| @@ -59,7 +59,7 @@ config QLCNIC_HWMON · 4 unmodified lines | ||
| 59 | 59 | bool "QLOGIC QLCNIC 82XX and 83XX family HWMON support" |
| 60 | 60 | depends on QLCNIC && HWMON && !(QLCNIC=y && HWMON=m) |
| 61 | 61 | default y |
| 62 | − ---help--- | |
| 62 | + help | |
| 63 | 63 | This configuration parameter can be used to read the |
| 64 | 64 | board temperature in Converged Ethernet devices |
| 65 | 65 | supported by qlcnic. |
| @@ -70,7 +70,7 @@ config NETXEN_NIC · 4 unmodified lines | ||
| 70 | 70 | tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC" |
| 71 | 71 | depends on PCI |
| 72 | 72 | select FW_LOADER |
| 73 | − ---help--- | |
| 73 | + help | |
| 74 | 74 | This enables the support for NetXen's Gigabit Ethernet card. |
| 75 | 75 | |
| 76 | 76 | config QED |
| @@ -79,7 +79,7 @@ config QED · 2 unmodified lines | ||
| 79 | 79 | select ZLIB_INFLATE |
| 80 | 80 | select CRC8 |
| 81 | 81 | select NET_DEVLINK |
| 82 | − ---help--- | |
| 82 | + help | |
| 83 | 83 | This enables the support for ... |
| 84 | 84 | |
| 85 | 85 | config QED_LL2 |
| @@ -89,7 +89,7 @@ config QED_SRIOV · 3 unmodified lines | ||
| 89 | 89 | bool "QLogic QED 25/40/100Gb SR-IOV support" |
| 90 | 90 | depends on QED && PCI_IOV |
| 91 | 91 | default y |
| 92 | − ---help--- | |
| 92 | + help | |
| 93 | 93 | This configuration parameter enables Single Root Input Output |
| 94 | 94 | Virtualization support for QED devices. |
| 95 | 95 | This allows for virtual function acceleration in virtualized |
| @@ -99,7 +99,7 @@ config QEDE · 3 unmodified lines | ||
| 99 | 99 | tristate "QLogic QED 25/40/100Gb Ethernet NIC" |
| 100 | 100 | depends on QED |
| 101 | 101 | imply PTP_1588_CLOCK |
| 102 | − ---help--- | |
| 102 | + help | |
| 103 | 103 | This enables the support for ... |
| 104 | 104 | |
| 105 | 105 | config QED_RDMA |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_QUALCOMM |
| 7 | 7 | bool "Qualcomm devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -25,7 +25,7 @@ config QCA7000_SPI · 12 unmodified lines | ||
| 25 | 25 | tristate "Qualcomm Atheros QCA7000 SPI support" |
| 26 | 26 | select QCA7000 |
| 27 | 27 | depends on SPI_MASTER && OF |
| 28 | − ---help--- | |
| 28 | + help | |
| 29 | 29 | This SPI protocol driver supports the Qualcomm Atheros QCA7000. |
| 30 | 30 | |
| 31 | 31 | To compile this driver as a module, choose M here. The module |
| @@ -35,7 +35,7 @@ config QCA7000_UART · 3 unmodified lines | ||
| 35 | 35 | tristate "Qualcomm Atheros QCA7000 UART support" |
| 36 | 36 | select QCA7000 |
| 37 | 37 | depends on SERIAL_DEV_BUS && OF |
| 38 | − ---help--- | |
| 38 | + help | |
| 39 | 39 | This UART protocol driver supports the Qualcomm Atheros QCA7000. |
| 40 | 40 | |
| 41 | 41 | Currently the driver assumes these device UART settings: |
| @@ -52,7 +52,7 @@ config QCOM_EMAC · 10 unmodified lines | ||
| 52 | 52 | depends on HAS_DMA && HAS_IOMEM |
| 53 | 53 | select CRC32 |
| 54 | 54 | select PHYLIB |
| 55 | − ---help--- | |
| 55 | + help | |
| 56 | 56 | This driver supports the Qualcomm Technologies, Inc. Gigabit |
| 57 | 57 | Ethernet Media Access Controller (EMAC). The controller |
| 58 | 58 | supports IEEE 802.3-2002, half-duplex mode at 10/100 Mb/s, |
| @@ -7,7 +7,7 @@ menuconfig RMNET · 6 unmodified lines | ||
| 7 | 7 | tristate "RmNet MAP driver" |
| 8 | 8 | default n |
| 9 | 9 | select GRO_CELLS |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you select this, you will enable the RMNET module which is used |
| 12 | 12 | for handling data in the multiplexing and aggregation protocol (MAP) |
| 13 | 13 | format in the embedded data path. RMNET devices can be attached to |
| @@ -7,7 +7,7 @@ config NET_VENDOR_RDC · 6 unmodified lines | ||
| 7 | 7 | bool "RDC devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -23,7 +23,7 @@ config R6040 · 9 unmodified lines | ||
| 23 | 23 | select CRC32 |
| 24 | 24 | select MII |
| 25 | 25 | select PHYLIB |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | This is a driver for the R6040 Fast Ethernet MACs found in the |
| 28 | 28 | the RDC R-321x System-on-chips. |
| 29 | 29 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_REALTEK · 6 unmodified lines | ||
| 7 | 7 | bool "Realtek devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI || (PARPORT && X86) |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -21,7 +21,7 @@ config ATP · 7 unmodified lines | ||
| 21 | 21 | tristate "AT-LAN-TEC/RealTek pocket adapter support" |
| 22 | 22 | depends on PARPORT && X86 |
| 23 | 23 | select CRC32 |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | This is a network (Ethernet) device which attaches to your parallel |
| 26 | 26 | port. Read the file <file:drivers/net/ethernet/realtek/atp.c> |
| 27 | 27 | if you want to use this. If you intend to use this driver, you |
| @@ -36,7 +36,7 @@ config 8139CP · 8 unmodified lines | ||
| 36 | 36 | depends on PCI |
| 37 | 37 | select CRC32 |
| 38 | 38 | select MII |
| 39 | − ---help--- | |
| 39 | + help | |
| 40 | 40 | This is a driver for the Fast Ethernet PCI network cards based on |
| 41 | 41 | the RTL8139C+ chips. If you have one of those, say Y here. |
| 42 | 42 | |
| @@ -48,7 +48,7 @@ config 8139TOO · 5 unmodified lines | ||
| 48 | 48 | depends on PCI |
| 49 | 49 | select CRC32 |
| 50 | 50 | select MII |
| 51 | − ---help--- | |
| 51 | + help | |
| 52 | 52 | This is a driver for the Fast Ethernet PCI network cards based on |
| 53 | 53 | the RTL 8129/8130/8139 chips. If you have one of those, say Y here. |
| 54 | 54 | |
| @@ -59,7 +59,7 @@ config 8139TOO_PIO · 4 unmodified lines | ||
| 59 | 59 | bool "Use PIO instead of MMIO" |
| 60 | 60 | default y |
| 61 | 61 | depends on 8139TOO |
| 62 | − ---help--- | |
| 62 | + help | |
| 63 | 63 | This instructs the driver to use programmed I/O ports (PIO) instead |
| 64 | 64 | of PCI shared memory (MMIO). This can possibly solve some problems |
| 65 | 65 | in case your mainboard has memory consistency issues. If unsure, |
| @@ -68,7 +68,7 @@ config 8139TOO_PIO · 2 unmodified lines | ||
| 68 | 68 | config 8139TOO_TUNE_TWISTER |
| 69 | 69 | bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)" |
| 70 | 70 | depends on 8139TOO |
| 71 | − ---help--- | |
| 71 | + help | |
| 72 | 72 | This implements a function which might come in handy in case you |
| 73 | 73 | are using low quality on long cabling. It is required for RealTek |
| 74 | 74 | RTL-8139 revision K boards, and totally unused otherwise. It tries |
| @@ -79,7 +79,7 @@ config 8139TOO_TUNE_TWISTER · 4 unmodified lines | ||
| 79 | 79 | config 8139TOO_8129 |
| 80 | 80 | bool "Support for older RTL-8129/8130 boards" |
| 81 | 81 | depends on 8139TOO |
| 82 | − ---help--- | |
| 82 | + help | |
| 83 | 83 | This enables support for the older and uncommon RTL-8129 and |
| 84 | 84 | RTL-8130 chips, which support MII via an external transceiver, |
| 85 | 85 | instead of an internal one. Disabling this option will save some |
| @@ -88,7 +88,7 @@ config 8139TOO_8129 · 2 unmodified lines | ||
| 88 | 88 | config 8139_OLD_RX_RESET |
| 89 | 89 | bool "Use older RX-reset method" |
| 90 | 90 | depends on 8139TOO |
| 91 | − ---help--- | |
| 91 | + help | |
| 92 | 92 | The 8139too driver was recently updated to contain a more rapid |
| 93 | 93 | reset sequence, in the face of severe receive errors. This "new" |
| 94 | 94 | RX-reset method should be adequate for all boards. But if you |
| @@ -102,7 +102,7 @@ config R8169 · 7 unmodified lines | ||
| 102 | 102 | select CRC32 |
| 103 | 103 | select PHYLIB |
| 104 | 104 | select REALTEK_PHY |
| 105 | − ---help--- | |
| 105 | + help | |
| 106 | 106 | Say Y here if you have a Realtek Ethernet adapter belonging to |
| 107 | 107 | the following families: |
| 108 | 108 | RTL8169 Gigabit Ethernet |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_RENESAS |
| 7 | 7 | bool "Renesas devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -23,7 +23,7 @@ config SH_ETH · 10 unmodified lines | ||
| 23 | 23 | select MII |
| 24 | 24 | select MDIO_BITBANG |
| 25 | 25 | select PHYLIB |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | Renesas SuperH Ethernet device driver. |
| 28 | 28 | This driver supporting CPUs are: |
| 29 | 29 | - SH7619, SH7710, SH7712, SH7724, SH7734, SH7763, SH7757, |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_ROCKER |
| 7 | 7 | bool "Rocker devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network device belonging to this class, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -19,7 +19,7 @@ if NET_VENDOR_ROCKER · 6 unmodified lines | ||
| 19 | 19 | config ROCKER |
| 20 | 20 | tristate "Rocker switch driver (EXPERIMENTAL)" |
| 21 | 21 | depends on PCI && NET_SWITCHDEV && BRIDGE |
| 22 | − ---help--- | |
| 22 | + help | |
| 23 | 23 | This driver supports Rocker switch device. |
| 24 | 24 | |
| 25 | 25 | To compile this driver as a module, choose M here: the |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_SAMSUNG |
| 7 | 7 | bool "Samsung Ethernet devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) chipset belonging to this class, |
| 11 | 11 | say Y. |
| 12 | 12 | |
| @@ -23,7 +23,7 @@ config SXGBE_ETH · 10 unmodified lines | ||
| 23 | 23 | select PHYLIB |
| 24 | 24 | select CRC32 |
| 25 | 25 | imply PTP_1588_CLOCK |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | This is the driver for the SXGBE 10G Ethernet IP block found on |
| 28 | 28 | Samsung platforms. |
| 29 | 29 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_SEEQ · 6 unmodified lines | ||
| 7 | 7 | bool "SEEQ devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on HAS_IOMEM |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,14 +20,14 @@ if NET_VENDOR_SEEQ · 6 unmodified lines | ||
| 20 | 20 | config ARM_ETHER3 |
| 21 | 21 | tristate "Acorn/ANT Ether3 support" |
| 22 | 22 | depends on ARM && ARCH_ACORN |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | If you have an Acorn system with one of these network cards, you |
| 25 | 25 | should say Y to this option if you wish to use it with Linux. |
| 26 | 26 | |
| 27 | 27 | config SGISEEQ |
| 28 | 28 | tristate "SGI Seeq ethernet controller support" |
| 29 | 29 | depends on SGI_HAS_SEEQ |
| 30 | − ---help--- | |
| 30 | + help | |
| 31 | 31 | Say Y here if you have an Seeq based Ethernet network card. This is |
| 32 | 32 | used in many Silicon Graphics machines. |
| 33 | 33 | |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_SOLARFLARE |
| 7 | 7 | bool "Solarflare devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -22,7 +22,7 @@ config SFC · 9 unmodified lines | ||
| 22 | 22 | select MDIO |
| 23 | 23 | select CRC32 |
| 24 | 24 | imply PTP_1588_CLOCK |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | This driver supports 10/40-gigabit Ethernet cards based on |
| 27 | 27 | the Solarflare SFC9000-family and SFC9100-family controllers. |
| 28 | 28 | |
| @@ -32,7 +32,7 @@ config SFC_MTD · 3 unmodified lines | ||
| 32 | 32 | bool "Solarflare SFC9000/SFC9100-family MTD support" |
| 33 | 33 | depends on SFC && MTD && !(SFC=y && MTD=m) |
| 34 | 34 | default y |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | This exposes the on-board flash and/or EEPROM as MTD devices |
| 37 | 37 | (e.g. /dev/mtd1). This is required to update the firmware or |
| 38 | 38 | the boot configuration under Linux. |
| @@ -40,14 +40,14 @@ config SFC_MCDI_MON · 1 unmodified line | ||
| 40 | 40 | bool "Solarflare SFC9000/SFC9100-family hwmon support" |
| 41 | 41 | depends on SFC && HWMON && !(SFC=y && HWMON=m) |
| 42 | 42 | default y |
| 43 | − ---help--- | |
| 43 | + help | |
| 44 | 44 | This exposes the on-board firmware-managed sensors as a |
| 45 | 45 | hardware monitor device. |
| 46 | 46 | config SFC_SRIOV |
| 47 | 47 | bool "Solarflare SFC9000-family SR-IOV support" |
| 48 | 48 | depends on SFC && PCI_IOV |
| 49 | 49 | default y |
| 50 | − ---help--- | |
| 50 | + help | |
| 51 | 51 | This enables support for the SFC9000 I/O Virtualization |
| 52 | 52 | features, allowing accelerated network performance in |
| 53 | 53 | virtualized environments. |
| @@ -55,7 +55,7 @@ config SFC_MCDI_LOGGING · 1 unmodified line | ||
| 55 | 55 | bool "Solarflare SFC9000/SFC9100-family MCDI logging support" |
| 56 | 56 | depends on SFC |
| 57 | 57 | default y |
| 58 | − ---help--- | |
| 58 | + help | |
| 59 | 59 | This enables support for tracing of MCDI (Management-Controller-to- |
| 60 | 60 | Driver-Interface) commands and responses, allowing debugging of |
| 61 | 61 | driver/firmware interaction. The tracing is actually enabled by |
| @@ -6,7 +6,7 @@ config SFC_FALCON · 5 unmodified lines | ||
| 6 | 6 | select CRC32 |
| 7 | 7 | select I2C |
| 8 | 8 | select I2C_ALGOBIT |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This driver supports 10-gigabit Ethernet cards based on |
| 11 | 11 | the Solarflare SFC4000 controller. |
| 12 | 12 | |
| @@ -16,7 +16,7 @@ config SFC_FALCON_MTD · 3 unmodified lines | ||
| 16 | 16 | bool "Solarflare SFC4000 MTD support" |
| 17 | 17 | depends on SFC_FALCON && MTD && !(SFC_FALCON=y && MTD=m) |
| 18 | 18 | default y |
| 19 | − ---help--- | |
| 19 | + help | |
| 20 | 20 | This exposes the on-board flash and/or EEPROM as MTD devices |
| 21 | 21 | (e.g. /dev/mtd1). This is required to update the boot |
| 22 | 22 | configuration under Linux. |
| @@ -7,7 +7,7 @@ config NET_VENDOR_SGI · 6 unmodified lines | ||
| 7 | 7 | bool "SGI devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on (PCI && SGI_MFD_IOC3) || SGI_IP32 |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -23,7 +23,7 @@ config SGI_IOC3_ETH · 9 unmodified lines | ||
| 23 | 23 | select CRC16 |
| 24 | 24 | select CRC32 |
| 25 | 25 | select MII |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | If you have a network (Ethernet) card of this type, say Y here. |
| 28 | 28 | |
| 29 | 29 | config SGI_O2MACE_ETH |
| @@ -7,7 +7,7 @@ config NET_VENDOR_SILAN · 6 unmodified lines | ||
| 7 | 7 | bool "Silan devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -21,7 +21,7 @@ config SC92031 · 7 unmodified lines | ||
| 21 | 21 | tristate "Silan SC92031 PCI Fast Ethernet Adapter driver" |
| 22 | 22 | depends on PCI |
| 23 | 23 | select CRC32 |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | This is a driver for the Fast Ethernet PCI network cards based on |
| 26 | 26 | the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you |
| 27 | 27 | have one of these, say Y here. |
| @@ -7,7 +7,7 @@ config NET_VENDOR_SIS · 6 unmodified lines | ||
| 7 | 7 | bool "Silicon Integrated Systems (SiS) devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -22,7 +22,7 @@ config SIS900 · 8 unmodified lines | ||
| 22 | 22 | depends on PCI |
| 23 | 23 | select CRC32 |
| 24 | 24 | select MII |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | This is a driver for the Fast Ethernet PCI network cards based on |
| 27 | 27 | the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in |
| 28 | 28 | SiS 630 and SiS 540 chipsets. |
| @@ -38,7 +38,7 @@ config SIS190 · 9 unmodified lines | ||
| 38 | 38 | depends on PCI |
| 39 | 39 | select CRC32 |
| 40 | 40 | select MII |
| 41 | − ---help--- | |
| 41 | + help | |
| 42 | 42 | Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or |
| 43 | 43 | a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to |
| 44 | 44 | appear in lan on motherboard designs which are based on SiS 965 |
| @@ -9,7 +9,7 @@ config NET_VENDOR_SMSC · 8 unmodified lines | ||
| 9 | 9 | depends on ARM || ARM64 || ATARI_ETHERNAT || COLDFIRE || \ |
| 10 | 10 | ISA || MAC || MIPS || NIOS2 || PCI || \ |
| 11 | 11 | PCMCIA || SUPERH || XTENSA || H8300 |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 14 | 14 | |
| 15 | 15 | Note that the answer to this question doesn't directly affect the |
| @@ -23,7 +23,7 @@ config SMC9194 · 7 unmodified lines | ||
| 23 | 23 | tristate "SMC 9194 support" |
| 24 | 24 | depends on ISA |
| 25 | 25 | select CRC32 |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | This is support for the SMC9xxx based Ethernet cards. Choose this |
| 28 | 28 | option if you have a DELL laptop with the docking station, or |
| 29 | 29 | another SMC9192/9194 based chipset. Say Y if you want it compiled |
| @@ -40,7 +40,7 @@ config SMC91X · 10 unmodified lines | ||
| 40 | 40 | depends on !OF || GPIOLIB |
| 41 | 41 | depends on ARM || ARM64 || ATARI_ETHERNAT || COLDFIRE || \ |
| 42 | 42 | MIPS || NIOS2 || SUPERH || XTENSA || H8300 |
| 43 | − ---help--- | |
| 43 | + help | |
| 44 | 44 | This is a driver for SMC's 91x series of Ethernet chipsets, |
| 45 | 45 | including the SMC91C94 and the SMC91C111. Say Y if you want it |
| 46 | 46 | compiled into the kernel, and read the file |
| @@ -56,7 +56,7 @@ config PCMCIA_SMC91C92 · 9 unmodified lines | ||
| 56 | 56 | depends on PCMCIA |
| 57 | 57 | select CRC32 |
| 58 | 58 | select MII |
| 59 | − ---help--- | |
| 59 | + help | |
| 60 | 60 | Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA |
| 61 | 61 | (PC-card) Ethernet or Fast Ethernet card to your computer. |
| 62 | 62 | |
| @@ -68,7 +68,7 @@ config EPIC100 · 5 unmodified lines | ||
| 68 | 68 | depends on PCI |
| 69 | 69 | select CRC32 |
| 70 | 70 | select MII |
| 71 | − ---help--- | |
| 71 | + help | |
| 72 | 72 | This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC, |
| 73 | 73 | which is based on the SMC83c17x (EPIC/100). |
| 74 | 74 | More specific information and updates are available from |
| @@ -79,7 +79,7 @@ config SMC911X · 4 unmodified lines | ||
| 79 | 79 | select CRC32 |
| 80 | 80 | select MII |
| 81 | 81 | depends on (ARM || SUPERH) |
| 82 | − ---help--- | |
| 82 | + help | |
| 83 | 83 | This is a driver for SMSC's LAN911x series of Ethernet chipsets |
| 84 | 84 | including the new LAN9115, LAN9116, LAN9117, and LAN9118. |
| 85 | 85 | Say Y here if you want it compiled into the kernel. |
| @@ -94,7 +94,7 @@ config SMSC911X · 8 unmodified lines | ||
| 94 | 94 | select CRC32 |
| 95 | 95 | select MII |
| 96 | 96 | select PHYLIB |
| 97 | − ---help--- | |
| 97 | + help | |
| 98 | 98 | Say Y here if you want support for SMSC LAN911x and LAN921x families |
| 99 | 99 | of ethernet controllers. |
| 100 | 100 | |
| @@ -104,7 +104,7 @@ config SMSC911X · 3 unmodified lines | ||
| 104 | 104 | config SMSC911X_ARCH_HOOKS |
| 105 | 105 | def_bool n |
| 106 | 106 | depends on SMSC911X |
| 107 | − ---help--- | |
| 107 | + help | |
| 108 | 108 | If the arch enables this, it allows the arch to implement various |
| 109 | 109 | hooks for more comprehensive interrupt control and also to override |
| 110 | 110 | the source of the MAC address. |
| @@ -115,7 +115,7 @@ config SMSC9420 · 4 unmodified lines | ||
| 115 | 115 | select CRC32 |
| 116 | 116 | select PHYLIB |
| 117 | 117 | select SMSC_PHY |
| 118 | − ---help--- | |
| 118 | + help | |
| 119 | 119 | This is a driver for SMSC's LAN9420 PCI ethernet adapter. |
| 120 | 120 | Say Y here if you want it compiled into the kernel. |
| 121 | 121 | |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config NET_VENDOR_SOCIONEXT |
| 3 | 3 | bool "Socionext ethernet drivers" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | Option to select ethernet drivers for Socionext platforms. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -18,7 +18,7 @@ config SNI_AVE · 9 unmodified lines | ||
| 18 | 18 | depends on HAS_IOMEM |
| 19 | 19 | select MFD_SYSCON |
| 20 | 20 | select PHYLIB |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | Driver for gigabit ethernet MACs, called AVE, in the |
| 23 | 23 | Socionext UniPhier family. |
| 24 | 24 | |
| @@ -28,7 +28,7 @@ config SNI_NETSEC · 3 unmodified lines | ||
| 28 | 28 | select PHYLIB |
| 29 | 29 | select PAGE_POOL |
| 30 | 30 | select MII |
| 31 | − ---help--- | |
| 31 | + help | |
| 32 | 32 | Enable to add support for the SocioNext NetSec Gigabit Ethernet |
| 33 | 33 | controller + PHY, as found on the Synquacer SC2A11 SoC |
| 34 | 34 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_STMICRO · 6 unmodified lines | ||
| 7 | 7 | bool "STMicroelectronics devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on HAS_IOMEM |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card based on Synopsys Ethernet IP |
| 12 | 12 | Cores, say Y. |
| 13 | 13 | |
| @@ -9,7 +9,7 @@ config STMMAC_ETH · 8 unmodified lines | ||
| 9 | 9 | select CRC32 |
| 10 | 10 | imply PTP_1588_CLOCK |
| 11 | 11 | select RESET_CONTROLLER |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | This is the driver for the Ethernet IPs built around a |
| 14 | 14 | Synopsys IP Core. |
| 15 | 15 | |
| @@ -20,7 +20,7 @@ config STMMAC_SELFTESTS · 4 unmodified lines | ||
| 20 | 20 | depends on INET |
| 21 | 21 | depends on STMMAC_ETH |
| 22 | 22 | default n |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | This adds support for STMMAC Selftests using ethtool. Enable this |
| 25 | 25 | feature if you are facing problems with your HW and submit the test |
| 26 | 26 | results to the netdev Mailing List. |
| @@ -30,7 +30,7 @@ config STMMAC_PLATFORM · 3 unmodified lines | ||
| 30 | 30 | depends on STMMAC_ETH |
| 31 | 31 | select MFD_SYSCON |
| 32 | 32 | default y |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | This selects the platform specific bus support for the stmmac driver. |
| 35 | 35 | This is the driver used on several SoCs: |
| 36 | 36 | STi, Allwinner, Amlogic Meson, Altera SOCFPGA. |
| @@ -52,7 +52,7 @@ config DWMAC_DWC_QOS_ETH · 15 unmodified lines | ||
| 52 | 52 | config DWMAC_GENERIC |
| 53 | 53 | tristate "Generic driver for DWMAC" |
| 54 | 54 | default STMMAC_PLATFORM |
| 55 | − ---help--- | |
| 55 | + help | |
| 56 | 56 | Generic DWMAC driver for platforms that don't require any |
| 57 | 57 | platform specific code to function or is using platform |
| 58 | 58 | data for setup. |
| @@ -84,7 +84,7 @@ config DWMAC_LPC18XX · 25 unmodified lines | ||
| 84 | 84 | default ARCH_LPC18XX |
| 85 | 85 | depends on OF && (ARCH_LPC18XX || COMPILE_TEST) |
| 86 | 86 | select MFD_SYSCON |
| 87 | − ---help--- | |
| 87 | + help | |
| 88 | 88 | Support for NXP LPC18xx/43xx DWMAC Ethernet. |
| 89 | 89 | |
| 90 | 90 | config DWMAC_MEDIATEK |
| @@ -155,7 +155,7 @@ config DWMAC_STI · 64 unmodified lines | ||
| 155 | 155 | default ARCH_STI |
| 156 | 156 | depends on OF && (ARCH_STI || COMPILE_TEST) |
| 157 | 157 | select MFD_SYSCON |
| 158 | − ---help--- | |
| 158 | + help | |
| 159 | 159 | Support for ethernet controller on STi SOCs. |
| 160 | 160 | |
| 161 | 161 | This selects STi SoC glue layer support for the stmmac |
| @@ -167,7 +167,7 @@ config DWMAC_STM32 · 5 unmodified lines | ||
| 167 | 167 | default ARCH_STM32 |
| 168 | 168 | depends on OF && HAS_IOMEM && (ARCH_STM32 || COMPILE_TEST) |
| 169 | 169 | select MFD_SYSCON |
| 170 | − ---help--- | |
| 170 | + help | |
| 171 | 171 | Support for ethernet controller on STM32 SOCs. |
| 172 | 172 | |
| 173 | 173 | This selects STM32 SoC glue layer support for the stmmac |
| @@ -178,7 +178,7 @@ config DWMAC_SUNXI · 4 unmodified lines | ||
| 178 | 178 | tristate "Allwinner GMAC support" |
| 179 | 179 | default ARCH_SUNXI |
| 180 | 180 | depends on OF && (ARCH_SUNXI || COMPILE_TEST) |
| 181 | − ---help--- | |
| 181 | + help | |
| 182 | 182 | Support for Allwinner A20/A31 GMAC ethernet controllers. |
| 183 | 183 | |
| 184 | 184 | This selects Allwinner SoC glue layer support for the |
| @@ -190,7 +190,7 @@ config DWMAC_SUN8I · 5 unmodified lines | ||
| 190 | 190 | default ARCH_SUNXI |
| 191 | 191 | depends on OF && (ARCH_SUNXI || COMPILE_TEST) |
| 192 | 192 | select MDIO_BUS_MUX |
| 193 | − ---help--- | |
| 193 | + help | |
| 194 | 194 | Support for Allwinner H3 A83T A64 EMAC ethernet controllers. |
| 195 | 195 | |
| 196 | 196 | This selects Allwinner SoC glue layer support for the |
| @@ -202,7 +202,7 @@ config DWMAC_IMX8 · 5 unmodified lines | ||
| 202 | 202 | default ARCH_MXC |
| 203 | 203 | depends on OF && (ARCH_MXC || COMPILE_TEST) |
| 204 | 204 | select MFD_SYSCON |
| 205 | − ---help--- | |
| 205 | + help | |
| 206 | 206 | Support for ethernet controller on NXP i.MX8 SOCs. |
| 207 | 207 | |
| 208 | 208 | This selects NXP SoC glue layer support for the stmmac |
| @@ -216,7 +216,7 @@ config DWMAC_INTEL · 7 unmodified lines | ||
| 216 | 216 | default X86 |
| 217 | 217 | depends on X86 && STMMAC_ETH && PCI |
| 218 | 218 | depends on COMMON_CLK |
| 219 | − ---help--- | |
| 219 | + help | |
| 220 | 220 | This selects the Intel platform specific bus support for the |
| 221 | 221 | stmmac driver. This driver is used for Intel Quark/EHL/TGL. |
| 222 | 222 | |
| @@ -224,7 +224,7 @@ config STMMAC_PCI · 1 unmodified line | ||
| 224 | 224 | tristate "STMMAC PCI bus support" |
| 225 | 225 | depends on STMMAC_ETH && PCI |
| 226 | 226 | depends on COMMON_CLK |
| 227 | − ---help--- | |
| 227 | + help | |
| 228 | 228 | This selects the platform specific bus support for the stmmac driver. |
| 229 | 229 | This driver was tested on XLINX XC2V3000 FF1152AMT0221 |
| 230 | 230 | D1215994A VIRTEX FPGA board and SNPS QoS IPK Prototyping Kit. |
| @@ -7,7 +7,7 @@ config NET_VENDOR_SUN · 6 unmodified lines | ||
| 7 | 7 | bool "Sun devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on SUN3 || SBUS || PCI || SUN_LDOMS |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -21,7 +21,7 @@ config HAPPYMEAL · 7 unmodified lines | ||
| 21 | 21 | tristate "Sun Happy Meal 10/100baseT support" |
| 22 | 22 | depends on (SBUS || PCI) |
| 23 | 23 | select CRC32 |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | This driver supports the "hme" interface present on most Ultra |
| 26 | 26 | systems and as an option on older Sbus systems. This driver supports |
| 27 | 27 | both PCI and Sbus devices. This driver also supports the "qfe" quad |
| @@ -34,7 +34,7 @@ config SUNBMAC · 6 unmodified lines | ||
| 34 | 34 | tristate "Sun BigMAC 10/100baseT support" |
| 35 | 35 | depends on SBUS |
| 36 | 36 | select CRC32 |
| 37 | − ---help--- | |
| 37 | + help | |
| 38 | 38 | This driver supports the "be" interface available as an Sbus option. |
| 39 | 39 | This is Sun's older 100baseT Ethernet device. |
| 40 | 40 | |
| @@ -45,7 +45,7 @@ config SUNQE · 4 unmodified lines | ||
| 45 | 45 | tristate "Sun QuadEthernet support" |
| 46 | 46 | depends on SBUS |
| 47 | 47 | select CRC32 |
| 48 | − ---help--- | |
| 48 | + help | |
| 49 | 49 | This driver supports the "qe" 10baseT Ethernet device, available as |
| 50 | 50 | an Sbus option. Note that this is not the same as Quad FastEthernet |
| 51 | 51 | "qfe" which is supported by the Happy Meal driver instead. |
| @@ -58,7 +58,7 @@ config SUNGEM · 6 unmodified lines | ||
| 58 | 58 | depends on PCI |
| 59 | 59 | select CRC32 |
| 60 | 60 | select SUNGEM_PHY |
| 61 | − ---help--- | |
| 61 | + help | |
| 62 | 62 | Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also |
| 63 | 63 | <http://docs.oracle.com/cd/E19455-01/806-3985-10/806-3985-10.pdf>. |
| 64 | 64 | |
| @@ -66,7 +66,7 @@ config CASSINI · 1 unmodified line | ||
| 66 | 66 | tristate "Sun Cassini support" |
| 67 | 67 | depends on PCI |
| 68 | 68 | select CRC32 |
| 69 | − ---help--- | |
| 69 | + help | |
| 70 | 70 | Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also |
| 71 | 71 | <http://docs.oracle.com/cd/E19113-01/giga.ether.pci/817-4341-10/817-4341-10.pdf>. |
| 72 | 72 | |
| @@ -80,7 +80,7 @@ config SUNVNET · 7 unmodified lines | ||
| 80 | 80 | default m |
| 81 | 81 | depends on SUN_LDOMS |
| 82 | 82 | depends on SUNVNET_COMMON |
| 83 | − ---help--- | |
| 83 | + help | |
| 84 | 84 | Support for virtual network devices under Sun Logical Domains. |
| 85 | 85 | |
| 86 | 86 | config LDMVSW |
| @@ -88,7 +88,7 @@ config LDMVSW · 1 unmodified line | ||
| 88 | 88 | default m |
| 89 | 89 | depends on SUN_LDOMS |
| 90 | 90 | depends on SUNVNET_COMMON |
| 91 | − ---help--- | |
| 91 | + help | |
| 92 | 92 | Support for virtual switch devices under Sun4v Logical Domains. |
| 93 | 93 | This driver adds a network interface for every vsw-port node |
| 94 | 94 | found in the machine description of a service domain. |
| @@ -100,7 +100,7 @@ config NIU · 5 unmodified lines | ||
| 100 | 100 | tristate "Sun Neptune 10Gbit Ethernet support" |
| 101 | 101 | depends on PCI |
| 102 | 102 | select CRC32 |
| 103 | − ---help--- | |
| 103 | + help | |
| 104 | 104 | This enables support for cards based upon Sun's |
| 105 | 105 | Neptune chipset. |
| 106 | 106 | |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_SYNOPSYS |
| 7 | 7 | bool "Synopsys devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) device belonging to this class, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -21,7 +21,7 @@ config DWC_XLGMAC · 8 unmodified lines | ||
| 21 | 21 | depends on HAS_IOMEM && HAS_DMA |
| 22 | 22 | select BITREVERSE |
| 23 | 23 | select CRC32 |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | This driver supports the Synopsys DesignWare Cores Enterprise |
| 26 | 26 | Ethernet (dwc-xlgmac). |
| 27 | 27 | |
| @@ -30,7 +30,7 @@ if DWC_XLGMAC · 2 unmodified lines | ||
| 30 | 30 | config DWC_XLGMAC_PCI |
| 31 | 31 | tristate "XLGMAC PCI bus support" |
| 32 | 32 | depends on DWC_XLGMAC && PCI |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | This selects the pci bus support for the dwc-xlgmac driver. |
| 35 | 35 | This driver was tested on Synopsys XLGMAC IP Prototyping Kit. |
| 36 | 36 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_TEHUTI · 6 unmodified lines | ||
| 7 | 7 | bool "Tehuti devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ if NET_VENDOR_TEHUTI · 6 unmodified lines | ||
| 20 | 20 | config TEHUTI |
| 21 | 21 | tristate "Tehuti Networks 10G Ethernet" |
| 22 | 22 | depends on PCI |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | Tehuti Networks 10G Ethernet NIC |
| 25 | 25 | |
| 26 | 26 | endif # NET_VENDOR_TEHUTI |
| @@ -7,7 +7,7 @@ config NET_VENDOR_TI · 6 unmodified lines | ||
| 7 | 7 | bool "Texas Instruments (TI) devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI || EISA || AR7 || ARCH_DAVINCI || ARCH_OMAP2PLUS || ARCH_KEYSTONE || ARCH_K3 |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -23,7 +23,7 @@ config TI_DAVINCI_EMAC · 9 unmodified lines | ||
| 23 | 23 | select TI_DAVINCI_MDIO |
| 24 | 24 | select PHYLIB |
| 25 | 25 | select GENERIC_ALLOCATOR |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | This driver supports TI's DaVinci Ethernet . |
| 28 | 28 | |
| 29 | 29 | To compile this driver as a module, choose M here: the module |
| @@ -33,7 +33,7 @@ config TI_DAVINCI_MDIO · 3 unmodified lines | ||
| 33 | 33 | tristate "TI DaVinci MDIO Support" |
| 34 | 34 | depends on ARCH_DAVINCI || ARCH_OMAP2PLUS || ARCH_KEYSTONE || ARCH_K3 || COMPILE_TEST |
| 35 | 35 | select PHYLIB |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | This driver supports TI's DaVinci MDIO module. |
| 38 | 38 | |
| 39 | 39 | To compile this driver as a module, choose M here: the module |
| @@ -42,7 +42,7 @@ config TI_DAVINCI_MDIO · 2 unmodified lines | ||
| 42 | 42 | config TI_CPSW_PHY_SEL |
| 43 | 43 | bool "TI CPSW Phy mode Selection (DEPRECATED)" |
| 44 | 44 | default n |
| 45 | − ---help--- | |
| 45 | + help | |
| 46 | 46 | This driver supports configuring of the phy mode connected to |
| 47 | 47 | the CPSW. DEPRECATED: use PHY_TI_GMII_SEL. |
| 48 | 48 | |
| @@ -55,7 +55,7 @@ config TI_CPSW · 6 unmodified lines | ||
| 55 | 55 | select PAGE_POOL |
| 56 | 56 | select REGMAP |
| 57 | 57 | imply PHY_TI_GMII_SEL |
| 58 | − ---help--- | |
| 58 | + help | |
| 59 | 59 | This driver supports TI's CPSW Ethernet Switch. |
| 60 | 60 | |
| 61 | 61 | To compile this driver as a module, choose M here: the module |
| @@ -83,7 +83,7 @@ config TI_CPTS · 21 unmodified lines | ||
| 83 | 83 | depends on ARCH_OMAP2PLUS || ARCH_KEYSTONE || COMPILE_TEST |
| 84 | 84 | depends on COMMON_CLK |
| 85 | 85 | depends on PTP_1588_CLOCK |
| 86 | − ---help--- | |
| 86 | + help | |
| 87 | 87 | This driver supports the Common Platform Time Sync unit of |
| 88 | 88 | the CPSW Ethernet Switch and Keystone 2 1g/10g Switch Subsystem. |
| 89 | 89 | The unit can time stamp PTP UDP/IPv4 and Layer 2 packets, and the |
| @@ -133,7 +133,7 @@ config TI_KEYSTONE_NETCP · 43 unmodified lines | ||
| 133 | 133 | depends on OF |
| 134 | 134 | depends on KEYSTONE_NAVIGATOR_DMA && KEYSTONE_NAVIGATOR_QMSS |
| 135 | 135 | depends on TI_CPTS || !TI_CPTS |
| 136 | − ---help--- | |
| 136 | + help | |
| 137 | 137 | This driver supports TI's Keystone NETCP Core. |
| 138 | 138 | |
| 139 | 139 | To compile this driver as a module, choose M here: the module |
| @@ -142,7 +142,7 @@ config TI_KEYSTONE_NETCP · 2 unmodified lines | ||
| 142 | 142 | config TI_KEYSTONE_NETCP_ETHSS |
| 143 | 143 | depends on TI_KEYSTONE_NETCP |
| 144 | 144 | tristate "TI Keystone NETCP Ethernet subsystem Support" |
| 145 | − ---help--- | |
| 145 | + help | |
| 146 | 146 | |
| 147 | 147 | To compile this driver as a module, choose M here: the module |
| 148 | 148 | will be called keystone_netcp_ethss. |
| @@ -150,7 +150,7 @@ config TI_KEYSTONE_NETCP_ETHSS · 1 unmodified line | ||
| 150 | 150 | config TLAN |
| 151 | 151 | tristate "TI ThunderLAN support" |
| 152 | 152 | depends on (PCI || EISA) |
| 153 | − ---help--- | |
| 153 | + help | |
| 154 | 154 | If you have a PCI Ethernet network card based on the ThunderLAN chip |
| 155 | 155 | which is supported by this driver, say Y here. |
| 156 | 156 | |
| @@ -168,7 +168,7 @@ config CPMAC · 11 unmodified lines | ||
| 168 | 168 | tristate "TI AR7 CPMAC Ethernet support" |
| 169 | 169 | depends on AR7 |
| 170 | 170 | select PHYLIB |
| 171 | − ---help--- | |
| 171 | + help | |
| 172 | 172 | TI AR7 CPMAC Ethernet support |
| 173 | 173 | |
| 174 | 174 | endif # NET_VENDOR_TI |
| @@ -7,7 +7,7 @@ config NET_VENDOR_TOSHIBA · 6 unmodified lines | ||
| 7 | 7 | bool "Toshiba devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCI && (PPC_IBM_CELL_BLADE || MIPS) || PPC_PS3 |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -21,7 +21,7 @@ config GELIC_NET · 7 unmodified lines | ||
| 21 | 21 | tristate "PS3 Gigabit Ethernet driver" |
| 22 | 22 | depends on PPC_PS3 |
| 23 | 23 | select PS3_SYS_MANAGER |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | This driver supports the network device on the PS3 game |
| 26 | 26 | console. This driver has built-in support for Ethernet. |
| 27 | 27 | |
| @@ -32,7 +32,7 @@ config GELIC_WIRELESS · 4 unmodified lines | ||
| 32 | 32 | bool "PS3 Wireless support" |
| 33 | 33 | depends on GELIC_NET && WLAN |
| 34 | 34 | select WIRELESS_EXT |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | This option adds the support for the wireless feature of PS3. |
| 37 | 37 | If you have the wireless-less model of PS3 or have no plan to |
| 38 | 38 | use wireless feature, disabling this option saves memory. As |
| @@ -44,7 +44,7 @@ config SPIDER_NET · 5 unmodified lines | ||
| 44 | 44 | depends on PCI && PPC_IBM_CELL_BLADE |
| 45 | 45 | select FW_LOADER |
| 46 | 46 | select SUNGEM_PHY |
| 47 | − ---help--- | |
| 47 | + help | |
| 48 | 48 | This driver supports the Gigabit Ethernet chips present on the |
| 49 | 49 | Cell Processor-Based Blades from IBM. |
| 50 | 50 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_TUNDRA · 6 unmodified lines | ||
| 7 | 7 | bool "Tundra devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on TSI108_BRIDGE |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ if NET_VENDOR_TUNDRA · 6 unmodified lines | ||
| 20 | 20 | config TSI108_ETH |
| 21 | 21 | tristate "Tundra TSI108 gigabit Ethernet support" |
| 22 | 22 | depends on TSI108_BRIDGE |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | This driver supports Tundra TSI108 gigabit Ethernet ports. |
| 25 | 25 | To compile this driver as a module, choose M here: the module |
| 26 | 26 | will be called tsi108_eth. |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_VIA |
| 7 | 7 | bool "VIA devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -23,7 +23,7 @@ config VIA_RHINE · 10 unmodified lines | ||
| 23 | 23 | depends on HAS_DMA |
| 24 | 24 | select CRC32 |
| 25 | 25 | select MII |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A), |
| 28 | 28 | Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type |
| 29 | 29 | Ethernet functions can also be found integrated on South Bridges |
| @@ -35,7 +35,7 @@ config VIA_RHINE · 5 unmodified lines | ||
| 35 | 35 | config VIA_RHINE_MMIO |
| 36 | 36 | bool "Use MMIO instead of PIO" |
| 37 | 37 | depends on VIA_RHINE |
| 38 | − ---help--- | |
| 38 | + help | |
| 39 | 39 | This instructs the driver to use PCI shared memory (MMIO) instead of |
| 40 | 40 | programmed I/O ports (PIO). Enabling this gives an improvement in |
| 41 | 41 | processing time in parts of the driver. |
| @@ -49,7 +49,7 @@ config VIA_VELOCITY · 7 unmodified lines | ||
| 49 | 49 | select CRC32 |
| 50 | 50 | select CRC_CCITT |
| 51 | 51 | select MII |
| 52 | − ---help--- | |
| 52 | + help | |
| 53 | 53 | If you have a VIA "Velocity" based network card say Y here. |
| 54 | 54 | |
| 55 | 55 | To compile this driver as a module, choose M here. The module |
| @@ -7,7 +7,7 @@ config NET_VENDOR_WIZNET · 6 unmodified lines | ||
| 7 | 7 | bool "WIZnet devices" |
| 8 | 8 | depends on HAS_IOMEM |
| 9 | 9 | default y |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ if NET_VENDOR_WIZNET · 6 unmodified lines | ||
| 20 | 20 | config WIZNET_W5100 |
| 21 | 21 | tristate "WIZnet W5100 Ethernet support" |
| 22 | 22 | depends on HAS_IOMEM |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | Support for WIZnet W5100 chips. |
| 25 | 25 | |
| 26 | 26 | W5100 is a single chip with integrated 10/100 Ethernet MAC, |
| @@ -33,7 +33,7 @@ config WIZNET_W5100 · 6 unmodified lines | ||
| 33 | 33 | config WIZNET_W5300 |
| 34 | 34 | tristate "WIZnet W5300 Ethernet support" |
| 35 | 35 | depends on HAS_IOMEM |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | Support for WIZnet W5300 chips. |
| 38 | 38 | |
| 39 | 39 | W5300 is a single chip with integrated 10/100 Ethernet MAC, |
| @@ -50,20 +50,20 @@ choice · 10 unmodified lines | ||
| 50 | 50 | |
| 51 | 51 | config WIZNET_BUS_DIRECT |
| 52 | 52 | bool "Direct address bus mode" |
| 53 | − ---help--- | |
| 53 | + help | |
| 54 | 54 | In direct address mode host system can directly access all registers |
| 55 | 55 | after mapping to Memory-Mapped I/O space. |
| 56 | 56 | |
| 57 | 57 | config WIZNET_BUS_INDIRECT |
| 58 | 58 | bool "Indirect address bus mode" |
| 59 | − ---help--- | |
| 59 | + help | |
| 60 | 60 | In indirect address mode host system indirectly accesses registers |
| 61 | 61 | using Indirect Mode Address Register and Indirect Mode Data Register, |
| 62 | 62 | which are directly mapped to Memory-Mapped I/O space. |
| 63 | 63 | |
| 64 | 64 | config WIZNET_BUS_ANY |
| 65 | 65 | bool "Select interface mode in runtime" |
| 66 | − ---help--- | |
| 66 | + help | |
| 67 | 67 | If interface mode is unknown in compile time, it can be selected |
| 68 | 68 | in runtime from board/platform resources configuration. |
| 69 | 69 | |
| @@ -74,7 +74,7 @@ config WIZNET_W5100_SPI · 4 unmodified lines | ||
| 74 | 74 | tristate "WIZnet W5100/W5200/W5500 Ethernet support for SPI mode" |
| 75 | 75 | depends on WIZNET_BUS_ANY && WIZNET_W5100 |
| 76 | 76 | depends on SPI |
| 77 | − ---help--- | |
| 77 | + help | |
| 78 | 78 | In SPI mode host system accesses registers using SPI protocol |
| 79 | 79 | (mode 0) on the SPI bus. |
| 80 | 80 | |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_VENDOR_XILINX |
| 7 | 7 | bool "Xilinx devices" |
| 8 | 8 | default y |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 11 | 11 | |
| 12 | 12 | Note that the answer to this question doesn't directly affect the |
| @@ -20,20 +20,20 @@ config XILINX_EMACLITE · 7 unmodified lines | ||
| 20 | 20 | tristate "Xilinx 10/100 Ethernet Lite support" |
| 21 | 21 | depends on PPC32 || MICROBLAZE || ARCH_ZYNQ || MIPS |
| 22 | 22 | select PHYLIB |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | This driver supports the 10/100 Ethernet Lite from Xilinx. |
| 25 | 25 | |
| 26 | 26 | config XILINX_AXI_EMAC |
| 27 | 27 | tristate "Xilinx 10/100/1000 AXI Ethernet support" |
| 28 | 28 | select PHYLINK |
| 29 | − ---help--- | |
| 29 | + help | |
| 30 | 30 | This driver supports the 10/100/1000 Ethernet from Xilinx for the |
| 31 | 31 | AXI bus interface used in Xilinx Virtex FPGAs and Soc's. |
| 32 | 32 | |
| 33 | 33 | config XILINX_LL_TEMAC |
| 34 | 34 | tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver" |
| 35 | 35 | select PHYLIB |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | This driver supports the Xilinx 10/100/1000 LocalLink TEMAC |
| 38 | 38 | core used in Xilinx Spartan and Virtex FPGAs |
| 39 | 39 | |
| @@ -7,7 +7,7 @@ config NET_VENDOR_XIRCOM · 6 unmodified lines | ||
| 7 | 7 | bool "Xircom devices" |
| 8 | 8 | default y |
| 9 | 9 | depends on PCMCIA |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 12 | 12 | |
| 13 | 13 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ if NET_VENDOR_XIRCOM · 6 unmodified lines | ||
| 20 | 20 | config PCMCIA_XIRC2PS |
| 21 | 21 | tristate "Xircom 16-bit PCMCIA support" |
| 22 | 22 | depends on PCMCIA |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | Say Y here if you intend to attach a Xircom 16-bit PCMCIA (PC-card) |
| 25 | 25 | Ethernet or Fast Ethernet card to your computer. |
| 26 | 26 | |
| @@ -8,7 +8,7 @@ config NET_VENDOR_XSCALE · 7 unmodified lines | ||
| 8 | 8 | default y |
| 9 | 9 | depends on NET_VENDOR_INTEL && (ARM && ARCH_IXP4XX && \ |
| 10 | 10 | IXP4XX_NPE && IXP4XX_QMGR) |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | If you have a network (Ethernet) card belonging to this class, say Y. |
| 13 | 13 | |
| 14 | 14 | Note that the answer to this question does not directly affect the |
| @@ -23,7 +23,7 @@ config IXP4XX_ETH · 8 unmodified lines | ||
| 23 | 23 | depends on ARM && ARCH_IXP4XX && IXP4XX_NPE && IXP4XX_QMGR |
| 24 | 24 | select PHYLIB |
| 25 | 25 | select NET_PTP_CLASSIFY |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | Say Y here if you want to use built-in Ethernet ports |
| 28 | 28 | on IXP4xx processor. |
| 29 | 29 | |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config FDDI |
| 7 | 7 | tristate "FDDI driver support" |
| 8 | 8 | depends on PCI || EISA || TC |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Fiber Distributed Data Interface is a high speed local area network |
| 11 | 11 | design; essentially a replacement for high speed Ethernet. FDDI can |
| 12 | 12 | run over copper or fiber. If you are connected to such a network and |
| @@ -30,7 +30,7 @@ config DEFZA · 17 unmodified lines | ||
| 30 | 30 | config DEFXX |
| 31 | 31 | tristate "Digital DEFTA/DEFEA/DEFPA adapter support" |
| 32 | 32 | depends on FDDI && (PCI || EISA || TC) |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | This is support for the DIGITAL series of TURBOchannel (DEFTA), |
| 35 | 35 | EISA (DEFEA) and PCI (DEFPA) controllers which can connect you |
| 36 | 36 | to a local FDDI network. |
| @@ -44,7 +44,7 @@ config DEFXX_MMIO · 7 unmodified lines | ||
| 44 | 44 | depends on DEFXX |
| 45 | 45 | default n if PCI || EISA |
| 46 | 46 | default y |
| 47 | − ---help--- | |
| 47 | + help | |
| 48 | 48 | This instructs the driver to use EISA or PCI memory-mapped I/O |
| 49 | 49 | (MMIO) as appropriate instead of programmed I/O ports (PIO). |
| 50 | 50 | Enabling this gives an improvement in processing time in parts |
| @@ -58,7 +58,7 @@ config SKFP · 7 unmodified lines | ||
| 58 | 58 | tristate "SysKonnect FDDI PCI support" |
| 59 | 59 | depends on FDDI && PCI |
| 60 | 60 | select BITREVERSE |
| 61 | − ---help--- | |
| 61 | + help | |
| 62 | 62 | Say Y here if you have a SysKonnect FDDI PCI adapter. |
| 63 | 63 | The following adapters are supported by this driver: |
| 64 | 64 | - SK-5521 (SK-NET FDDI-UP) |
| @@ -3,7 +3,7 @@ config MKISS · 2 unmodified lines | ||
| 3 | 3 | tristate "Serial port KISS driver" |
| 4 | 4 | depends on AX25 && TTY |
| 5 | 5 | select CRC16 |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | KISS is a protocol used for the exchange of data between a computer |
| 8 | 8 | and a Terminal Node Controller (a small embedded system commonly |
| 9 | 9 | used for networking over AX.25 amateur radio connections; it |
| @@ -20,7 +20,7 @@ config MKISS · 10 unmodified lines | ||
| 20 | 20 | config 6PACK |
| 21 | 21 | tristate "Serial port 6PACK driver" |
| 22 | 22 | depends on AX25 && TTY |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | 6pack is a transmission protocol for the data exchange between your |
| 25 | 25 | PC and your TNC (the Terminal Node Controller acts as a kind of |
| 26 | 26 | modem connecting your computer's serial port to your radio's |
| @@ -48,7 +48,7 @@ config BPQETHER · 21 unmodified lines | ||
| 48 | 48 | config DMASCC |
| 49 | 49 | tristate "High-speed (DMA) SCC driver for AX.25" |
| 50 | 50 | depends on ISA && AX25 && BROKEN_ON_SMP && ISA_DMA_API |
| 51 | − ---help--- | |
| 51 | + help | |
| 52 | 52 | This is a driver for high-speed SCC boards, i.e. those supporting |
| 53 | 53 | DMA on one port. You usually use those boards to connect your |
| 54 | 54 | computer to an amateur radio modem (such as the WA4DSY 56kbps |
| @@ -81,7 +81,7 @@ config DMASCC · 26 unmodified lines | ||
| 81 | 81 | config SCC |
| 82 | 82 | tristate "Z8530 SCC driver" |
| 83 | 83 | depends on ISA && AX25 && ISA_DMA_API |
| 84 | − ---help--- | |
| 84 | + help | |
| 85 | 85 | These cards are used to connect your Linux box to an amateur radio |
| 86 | 86 | in order to communicate with other computers. If you want to use |
| 87 | 87 | this, read <file:Documentation/networking/z8530drv.rst> and the |
| @@ -116,7 +116,7 @@ config BAYCOM_SER_FDX · 28 unmodified lines | ||
| 116 | 116 | tristate "BAYCOM ser12 fullduplex driver for AX.25" |
| 117 | 117 | depends on AX25 && !S390 |
| 118 | 118 | select CRC_CCITT |
| 119 | − ---help--- | |
| 119 | + help | |
| 120 | 120 | This is one of two drivers for Baycom style simple amateur radio |
| 121 | 121 | modems that connect to a serial interface. The driver supports the |
| 122 | 122 | ser12 design in full-duplex mode. In addition, it allows the |
| @@ -136,7 +136,7 @@ config BAYCOM_SER_HDX · 13 unmodified lines | ||
| 136 | 136 | tristate "BAYCOM ser12 halfduplex driver for AX.25" |
| 137 | 137 | depends on AX25 && !S390 |
| 138 | 138 | select CRC_CCITT |
| 139 | − ---help--- | |
| 139 | + help | |
| 140 | 140 | This is one of two drivers for Baycom style simple amateur radio |
| 141 | 141 | modems that connect to a serial interface. The driver supports the |
| 142 | 142 | ser12 design in half-duplex mode. This is the old driver. It is |
| @@ -154,7 +154,7 @@ config BAYCOM_PAR · 11 unmodified lines | ||
| 154 | 154 | tristate "BAYCOM picpar and par96 driver for AX.25" |
| 155 | 155 | depends on PARPORT && AX25 |
| 156 | 156 | select CRC_CCITT |
| 157 | − ---help--- | |
| 157 | + help | |
| 158 | 158 | This is a driver for Baycom style simple amateur radio modems that |
| 159 | 159 | connect to a parallel interface. The driver supports the picpar and |
| 160 | 160 | par96 designs. To configure the driver, use the sethdlc utility |
| @@ -169,7 +169,7 @@ config BAYCOM_EPP · 8 unmodified lines | ||
| 169 | 169 | tristate "BAYCOM epp driver for AX.25" |
| 170 | 170 | depends on PARPORT && AX25 && !64BIT |
| 171 | 171 | select CRC_CCITT |
| 172 | − ---help--- | |
| 172 | + help | |
| 173 | 173 | This is a driver for Baycom style simple amateur radio modems that |
| 174 | 174 | connect to a parallel interface. The driver supports the EPP |
| 175 | 175 | designs. To configure the driver, use the sethdlc utility available |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config HIPPI |
| 7 | 7 | bool "HIPPI driver support" |
| 8 | 8 | depends on INET && PCI |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and |
| 11 | 11 | 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI |
| 12 | 12 | can run over copper (25m) or fiber (300m on multi-mode or 10km on |
| @@ -21,7 +21,7 @@ if HIPPI · 8 unmodified lines | ||
| 21 | 21 | config ROADRUNNER |
| 22 | 22 | tristate "Essential RoadRunner HIPPI PCI adapter support" |
| 23 | 23 | depends on PCI |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | Say Y here if this is your PCI HIPPI network card. |
| 26 | 26 | |
| 27 | 27 | To compile this driver as a module, choose M here: the module |
| @@ -30,7 +30,7 @@ config ROADRUNNER · 2 unmodified lines | ||
| 30 | 30 | config ROADRUNNER_LARGE_RINGS |
| 31 | 31 | bool "Use large TX/RX rings" |
| 32 | 32 | depends on ROADRUNNER |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | If you say Y here, the RoadRunner driver will preallocate up to 2 MB |
| 35 | 35 | of additional memory to allow for fastest operation, both for |
| 36 | 36 | transmitting and receiving. This memory cannot be used by any other |
| @@ -3,7 +3,7 @@ menuconfig IEEE802154_DRIVERS · 2 unmodified lines | ||
| 3 | 3 | tristate "IEEE 802.15.4 drivers" |
| 4 | 4 | depends on NETDEVICES && IEEE802154 |
| 5 | 5 | default y |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | Say Y here to get to see options for IEEE 802.15.4 Low-Rate |
| 8 | 8 | Wireless Personal Area Network device drivers. This option alone |
| 9 | 9 | does not add any kernel code. |
| @@ -14,7 +14,7 @@ menuconfig IEEE802154_DRIVERS · 4 unmodified lines | ||
| 14 | 14 | config IEEE802154_FAKELB |
| 15 | 15 | depends on IEEE802154_DRIVERS && MAC802154 |
| 16 | 16 | tristate "IEEE 802.15.4 loopback driver" |
| 17 | − ---help--- | |
| 17 | + help | |
| 18 | 18 | Say Y here to enable the fake driver that can emulate a net |
| 19 | 19 | of several interconnected radio devices. |
| 20 | 20 | |
| @@ -26,7 +26,7 @@ config IEEE802154_AT86RF230 · 5 unmodified lines | ||
| 26 | 26 | tristate "AT86RF230/231/233/212 transceiver driver" |
| 27 | 27 | depends on SPI |
| 28 | 28 | select REGMAP_SPI |
| 29 | − ---help--- | |
| 29 | + help | |
| 30 | 30 | Say Y here to enable the at86rf230/231/233/212 SPI 802.15.4 wireless |
| 31 | 31 | controller. |
| 32 | 32 | |
| @@ -37,7 +37,7 @@ config IEEE802154_AT86RF230_DEBUGFS · 4 unmodified lines | ||
| 37 | 37 | depends on IEEE802154_AT86RF230 |
| 38 | 38 | bool "AT86RF230 debugfs interface" |
| 39 | 39 | depends on DEBUG_FS |
| 40 | − ---help--- | |
| 40 | + help | |
| 41 | 41 | This option compiles debugfs code for the at86rf230 driver. |
| 42 | 42 | |
| 43 | 43 | config IEEE802154_MRF24J40 |
| @@ -45,7 +45,7 @@ config IEEE802154_MRF24J40 · 1 unmodified line | ||
| 45 | 45 | depends on IEEE802154_DRIVERS && MAC802154 |
| 46 | 46 | depends on SPI |
| 47 | 47 | select REGMAP_SPI |
| 48 | − ---help--- | |
| 48 | + help | |
| 49 | 49 | Say Y here to enable the MRF24J20 SPI 802.15.4 wireless |
| 50 | 50 | controller. |
| 51 | 51 | |
| @@ -56,7 +56,7 @@ config IEEE802154_CC2520 · 4 unmodified lines | ||
| 56 | 56 | depends on IEEE802154_DRIVERS && MAC802154 |
| 57 | 57 | tristate "CC2520 transceiver driver" |
| 58 | 58 | depends on SPI |
| 59 | − ---help--- | |
| 59 | + help | |
| 60 | 60 | Say Y here to enable the CC2520 SPI 802.15.4 wireless |
| 61 | 61 | controller. |
| 62 | 62 | |
| @@ -66,7 +66,7 @@ config IEEE802154_CC2520 · 3 unmodified lines | ||
| 66 | 66 | config IEEE802154_ATUSB |
| 67 | 67 | tristate "ATUSB transceiver driver" |
| 68 | 68 | depends on IEEE802154_DRIVERS && MAC802154 && USB |
| 69 | − ---help--- | |
| 69 | + help | |
| 70 | 70 | Say Y here to enable the ATUSB IEEE 802.15.4 wireless |
| 71 | 71 | controller. |
| 72 | 72 | |
| @@ -77,7 +77,7 @@ config IEEE802154_ADF7242 · 4 unmodified lines | ||
| 77 | 77 | tristate "ADF7242 transceiver driver" |
| 78 | 78 | depends on IEEE802154_DRIVERS && MAC802154 |
| 79 | 79 | depends on SPI |
| 80 | − ---help--- | |
| 80 | + help | |
| 81 | 81 | Say Y here to enable the ADF7242 SPI 802.15.4 wireless |
| 82 | 82 | controller. |
| 83 | 83 | |
| @@ -89,7 +89,7 @@ config IEEE802154_CA8210 · 5 unmodified lines | ||
| 89 | 89 | depends on IEEE802154_DRIVERS && MAC802154 |
| 90 | 90 | depends on COMMON_CLK |
| 91 | 91 | depends on SPI |
| 92 | − ---help--- | |
| 92 | + help | |
| 93 | 93 | Say Y here to enable the CA8210 SPI 802.15.4 wireless |
| 94 | 94 | controller. |
| 95 | 95 | |
| @@ -100,7 +100,7 @@ config IEEE802154_CA8210_DEBUGFS · 4 unmodified lines | ||
| 100 | 100 | bool "CA8210 debugfs interface" |
| 101 | 101 | depends on IEEE802154_CA8210 |
| 102 | 102 | depends on DEBUG_FS |
| 103 | − ---help--- | |
| 103 | + help | |
| 104 | 104 | This option compiles debugfs code for the ca8210 driver. This |
| 105 | 105 | exposes a debugfs node for each CA8210 instance which allows |
| 106 | 106 | direct use of the Cascoda API, exposing the 802.15.4 MAC |
| @@ -110,7 +110,7 @@ config IEEE802154_MCR20A · 3 unmodified lines | ||
| 110 | 110 | tristate "MCR20A transceiver driver" |
| 111 | 111 | depends on IEEE802154_DRIVERS && MAC802154 |
| 112 | 112 | depends on SPI |
| 113 | − ---help--- | |
| 113 | + help | |
| 114 | 114 | Say Y here to enable the MCR20A SPI 802.15.4 wireless |
| 115 | 115 | controller. |
| 116 | 116 | |
| @@ -120,7 +120,7 @@ config IEEE802154_MCR20A · 3 unmodified lines | ||
| 120 | 120 | config IEEE802154_HWSIM |
| 121 | 121 | depends on IEEE802154_DRIVERS && MAC802154 |
| 122 | 122 | tristate "Simulated radio testing tool for mac802154" |
| 123 | − ---help--- | |
| 123 | + help | |
| 124 | 124 | This driver is a developer testing tool that can be used to test |
| 125 | 125 | IEEE 802.15.4 networking stack (mac802154) functionality. This is not |
| 126 | 126 | needed for normal wpan usage and is only for testing. |
| @@ -134,7 +134,7 @@ config MDIO_GPIO · 133 unmodified lines | ||
| 134 | 134 | tristate "GPIO lib-based bitbanged MDIO buses" |
| 135 | 135 | depends on MDIO_BITBANG |
| 136 | 136 | depends on GPIOLIB || COMPILE_TEST |
| 137 | − ---help--- | |
| 137 | + help | |
| 138 | 138 | Supports GPIO lib-based MDIO busses. |
| 139 | 139 | |
| 140 | 140 | To compile this driver as a module, choose M here: the module |
| @@ -265,7 +265,7 @@ config SWPHY · 124 unmodified lines | ||
| 265 | 265 | config LED_TRIGGER_PHY |
| 266 | 266 | bool "Support LED triggers for tracking link state" |
| 267 | 267 | depends on LEDS_TRIGGERS |
| 268 | − ---help--- | |
| 268 | + help | |
| 269 | 269 | Adds support for a set of LED trigger events per-PHY. Link |
| 270 | 270 | state change will trigger the events, for consumption by an |
| 271 | 271 | LED class driver. There are triggers for each link speed currently |
| @@ -298,12 +298,12 @@ config ADIN_PHY · 26 unmodified lines | ||
| 298 | 298 | |
| 299 | 299 | config AMD_PHY |
| 300 | 300 | tristate "AMD PHYs" |
| 301 | − ---help--- | |
| 301 | + help | |
| 302 | 302 | Currently supports the am79c874 |
| 303 | 303 | |
| 304 | 304 | config AQUANTIA_PHY |
| 305 | 305 | tristate "Aquantia PHYs" |
| 306 | − ---help--- | |
| 306 | + help | |
| 307 | 307 | Currently supports the Aquantia AQ1202, AQ2104, AQR105, AQR405 |
| 308 | 308 | |
| 309 | 309 | config AX88796B_PHY |
| @@ -316,13 +316,13 @@ config BCM63XX_PHY · 6 unmodified lines | ||
| 316 | 316 | tristate "Broadcom 63xx SOCs internal PHY" |
| 317 | 317 | depends on BCM63XX || COMPILE_TEST |
| 318 | 318 | select BCM_NET_PHYLIB |
| 319 | − ---help--- | |
| 319 | + help | |
| 320 | 320 | Currently supports the 6348 and 6358 PHYs. |
| 321 | 321 | |
| 322 | 322 | config BCM7XXX_PHY |
| 323 | 323 | tristate "Broadcom 7xxx SOCs internal PHYs" |
| 324 | 324 | select BCM_NET_PHYLIB |
| 325 | − ---help--- | |
| 325 | + help | |
| 326 | 326 | Currently supports the BCM7366, BCM7439, BCM7445, and |
| 327 | 327 | 40nm and 65nm generation of BCM7xxx Set Top Box SoCs. |
| 328 | 328 | |
| @@ -336,7 +336,7 @@ config BCM_CYGNUS_PHY · 7 unmodified lines | ||
| 336 | 336 | depends on ARCH_BCM_IPROC || COMPILE_TEST |
| 337 | 337 | depends on MDIO_BCM_IPROC |
| 338 | 338 | select BCM_NET_PHYLIB |
| 339 | − ---help--- | |
| 339 | + help | |
| 340 | 340 | This PHY driver is for the 1G internal PHYs of the Broadcom |
| 341 | 341 | Cygnus and Omega Family SoC. |
| 342 | 342 | |
| @@ -350,7 +350,7 @@ config BCM_NET_PHYLIB · 7 unmodified lines | ||
| 350 | 350 | config BROADCOM_PHY |
| 351 | 351 | tristate "Broadcom PHYs" |
| 352 | 352 | select BCM_NET_PHYLIB |
| 353 | − ---help--- | |
| 353 | + help | |
| 354 | 354 | Currently supports the BCM5411, BCM5421, BCM5461, BCM54616S, BCM5464, |
| 355 | 355 | BCM5481, BCM54810 and BCM5482 PHYs. |
| 356 | 356 | |
| @@ -368,48 +368,48 @@ config BCM54140_PHY · 11 unmodified lines | ||
| 368 | 368 | config BCM84881_PHY |
| 369 | 369 | tristate "Broadcom BCM84881 PHY" |
| 370 | 370 | depends on PHYLIB |
| 371 | − ---help--- | |
| 371 | + help | |
| 372 | 372 | Support the Broadcom BCM84881 PHY. |
| 373 | 373 | |
| 374 | 374 | config CICADA_PHY |
| 375 | 375 | tristate "Cicada PHYs" |
| 376 | − ---help--- | |
| 376 | + help | |
| 377 | 377 | Currently supports the cis8204 |
| 378 | 378 | |
| 379 | 379 | config CORTINA_PHY |
| 380 | 380 | tristate "Cortina EDC CDR 10G Ethernet PHY" |
| 381 | − ---help--- | |
| 381 | + help | |
| 382 | 382 | Currently supports the CS4340 phy. |
| 383 | 383 | |
| 384 | 384 | config DAVICOM_PHY |
| 385 | 385 | tristate "Davicom PHYs" |
| 386 | − ---help--- | |
| 386 | + help | |
| 387 | 387 | Currently supports dm9161e and dm9131 |
| 388 | 388 | |
| 389 | 389 | config DP83822_PHY |
| 390 | 390 | tristate "Texas Instruments DP83822/825/826 PHYs" |
| 391 | − ---help--- | |
| 391 | + help | |
| 392 | 392 | Supports the DP83822, DP83825I, DP83825CM, DP83825CS, DP83825S, |
| 393 | 393 | DP83826C and DP83826NC PHYs. |
| 394 | 394 | |
| 395 | 395 | config DP83TC811_PHY |
| 396 | 396 | tristate "Texas Instruments DP83TC811 PHY" |
| 397 | − ---help--- | |
| 397 | + help | |
| 398 | 398 | Supports the DP83TC811 PHY. |
| 399 | 399 | |
| 400 | 400 | config DP83848_PHY |
| 401 | 401 | tristate "Texas Instruments DP83848 PHY" |
| 402 | − ---help--- | |
| 402 | + help | |
| 403 | 403 | Supports the DP83848 PHY. |
| 404 | 404 | |
| 405 | 405 | config DP83867_PHY |
| 406 | 406 | tristate "Texas Instruments DP83867 Gigabit PHY" |
| 407 | − ---help--- | |
| 407 | + help | |
| 408 | 408 | Currently supports the DP83867 PHY. |
| 409 | 409 | |
| 410 | 410 | config DP83869_PHY |
| 411 | 411 | tristate "Texas Instruments DP83869 Gigabit PHY" |
| 412 | − ---help--- | |
| 412 | + help | |
| 413 | 413 | Currently supports the DP83869 PHY. This PHY supports copper and |
| 414 | 414 | fiber connections. |
| 415 | 415 | |
| @@ -417,7 +417,7 @@ config FIXED_PHY · 1 unmodified line | ||
| 417 | 417 | tristate "MDIO Bus/PHY emulation with fixed speed/link PHYs" |
| 418 | 418 | depends on PHYLIB |
| 419 | 419 | select SWPHY |
| 420 | − ---help--- | |
| 420 | + help | |
| 421 | 421 | Adds the platform "fixed" MDIO Bus to cover the boards that use |
| 422 | 422 | PHYs that are not connected to the real MDIO bus. |
| 423 | 423 | |
| @@ -425,12 +425,12 @@ config FIXED_PHY · 1 unmodified line | ||
| 425 | 425 | |
| 426 | 426 | config ICPLUS_PHY |
| 427 | 427 | tristate "ICPlus PHYs" |
| 428 | − ---help--- | |
| 428 | + help | |
| 429 | 429 | Currently supports the IP175C and IP1001 PHYs. |
| 430 | 430 | |
| 431 | 431 | config INTEL_XWAY_PHY |
| 432 | 432 | tristate "Intel XWAY PHYs" |
| 433 | − ---help--- | |
| 433 | + help | |
| 434 | 434 | Supports the Intel XWAY (former Lantiq) 11G and 22E PHYs. |
| 435 | 435 | These PHYs are marked as standalone chips under the names |
| 436 | 436 | PEF 7061, PEF 7071 and PEF 7072 or integrated into the Intel |
| @@ -438,33 +438,33 @@ config INTEL_XWAY_PHY · 1 unmodified line | ||
| 438 | 438 | |
| 439 | 439 | config LSI_ET1011C_PHY |
| 440 | 440 | tristate "LSI ET1011C PHY" |
| 441 | − ---help--- | |
| 441 | + help | |
| 442 | 442 | Supports the LSI ET1011C PHY. |
| 443 | 443 | |
| 444 | 444 | config LXT_PHY |
| 445 | 445 | tristate "Intel LXT PHYs" |
| 446 | − ---help--- | |
| 446 | + help | |
| 447 | 447 | Currently supports the lxt970, lxt971 |
| 448 | 448 | |
| 449 | 449 | config MARVELL_PHY |
| 450 | 450 | tristate "Marvell PHYs" |
| 451 | − ---help--- | |
| 451 | + help | |
| 452 | 452 | Currently has a driver for the 88E1011S |
| 453 | 453 | |
| 454 | 454 | config MARVELL_10G_PHY |
| 455 | 455 | tristate "Marvell Alaska 10Gbit PHYs" |
| 456 | − ---help--- | |
| 456 | + help | |
| 457 | 457 | Support for the Marvell Alaska MV88X3310 and compatible PHYs. |
| 458 | 458 | |
| 459 | 459 | config MESON_GXL_PHY |
| 460 | 460 | tristate "Amlogic Meson GXL Internal PHY" |
| 461 | 461 | depends on ARCH_MESON || COMPILE_TEST |
| 462 | − ---help--- | |
| 462 | + help | |
| 463 | 463 | Currently has a driver for the Amlogic Meson GXL Internal PHY |
| 464 | 464 | |
| 465 | 465 | config MICREL_PHY |
| 466 | 466 | tristate "Micrel PHYs" |
| 467 | − ---help--- | |
| 467 | + help | |
| 468 | 468 | Supports the KSZ9021, VSC8201, KS8001 PHYs. |
| 469 | 469 | |
| 470 | 470 | config MICROCHIP_PHY |
| @@ -474,7 +474,7 @@ config MICROCHIP_PHY · 3 unmodified lines | ||
| 474 | 474 | |
| 475 | 475 | config MICROCHIP_T1_PHY |
| 476 | 476 | tristate "Microchip T1 PHYs" |
| 477 | − ---help--- | |
| 477 | + help | |
| 478 | 478 | Supports the LAN87XX PHYs. |
| 479 | 479 | |
| 480 | 480 | config MICROSEMI_PHY |
| @@ -482,18 +482,18 @@ config MICROSEMI_PHY · 1 unmodified line | ||
| 482 | 482 | depends on MACSEC || MACSEC=n |
| 483 | 483 | select CRYPTO_AES |
| 484 | 484 | select CRYPTO_ECB |
| 485 | − ---help--- | |
| 485 | + help | |
| 486 | 486 | Currently supports VSC8514, VSC8530, VSC8531, VSC8540 and VSC8541 PHYs |
| 487 | 487 | |
| 488 | 488 | config NATIONAL_PHY |
| 489 | 489 | tristate "National Semiconductor PHYs" |
| 490 | − ---help--- | |
| 490 | + help | |
| 491 | 491 | Currently supports the DP83865 PHY. |
| 492 | 492 | |
| 493 | 493 | config NXP_TJA11XX_PHY |
| 494 | 494 | tristate "NXP TJA11xx PHYs support" |
| 495 | 495 | depends on HWMON |
| 496 | − ---help--- | |
| 496 | + help | |
| 497 | 497 | Currently supports the NXP TJA1100 and TJA1101 PHY. |
| 498 | 498 | |
| 499 | 499 | config AT803X_PHY |
| @@ -504,47 +504,47 @@ config AT803X_PHY · 4 unmodified lines | ||
| 504 | 504 | |
| 505 | 505 | config QSEMI_PHY |
| 506 | 506 | tristate "Quality Semiconductor PHYs" |
| 507 | − ---help--- | |
| 507 | + help | |
| 508 | 508 | Currently supports the qs6612 |
| 509 | 509 | |
| 510 | 510 | config REALTEK_PHY |
| 511 | 511 | tristate "Realtek PHYs" |
| 512 | − ---help--- | |
| 512 | + help | |
| 513 | 513 | Supports the Realtek 821x PHY. |
| 514 | 514 | |
| 515 | 515 | config RENESAS_PHY |
| 516 | 516 | tristate "Driver for Renesas PHYs" |
| 517 | − ---help--- | |
| 517 | + help | |
| 518 | 518 | Supports the Renesas PHYs uPD60620 and uPD60620A. |
| 519 | 519 | |
| 520 | 520 | config ROCKCHIP_PHY |
| 521 | 521 | tristate "Driver for Rockchip Ethernet PHYs" |
| 522 | − ---help--- | |
| 522 | + help | |
| 523 | 523 | Currently supports the integrated Ethernet PHY. |
| 524 | 524 | |
| 525 | 525 | config SMSC_PHY |
| 526 | 526 | tristate "SMSC PHYs" |
| 527 | − ---help--- | |
| 527 | + help | |
| 528 | 528 | Currently supports the LAN83C185, LAN8187 and LAN8700 PHYs |
| 529 | 529 | |
| 530 | 530 | config STE10XP |
| 531 | 531 | tristate "STMicroelectronics STe10Xp PHYs" |
| 532 | − ---help--- | |
| 532 | + help | |
| 533 | 533 | This is the driver for the STe100p and STe101p PHYs. |
| 534 | 534 | |
| 535 | 535 | config TERANETICS_PHY |
| 536 | 536 | tristate "Teranetics PHYs" |
| 537 | − ---help--- | |
| 537 | + help | |
| 538 | 538 | Currently supports the Teranetics TN2020 |
| 539 | 539 | |
| 540 | 540 | config VITESSE_PHY |
| 541 | 541 | tristate "Vitesse PHYs" |
| 542 | − ---help--- | |
| 542 | + help | |
| 543 | 543 | Currently supports the vsc8244 |
| 544 | 544 | |
| 545 | 545 | config XILINX_GMII2RGMII |
| 546 | 546 | tristate "Xilinx GMII2RGMII converter driver" |
| 547 | − ---help--- | |
| 547 | + help | |
| 548 | 548 | This driver support xilinx GMII to RGMII IP core it provides |
| 549 | 549 | the Reduced Gigabit Media Independent Interface(RGMII) between |
| 550 | 550 | Ethernet physical media devices and the Gigabit Ethernet controller. |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config PLIP |
| 7 | 7 | tristate "PLIP (parallel port) support" |
| 8 | 8 | depends on PARPORT |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | PLIP (Parallel Line Internet Protocol) is used to create a |
| 11 | 11 | reasonably fast mini network consisting of two (or, rarely, more) |
| 12 | 12 | local machines. A PLIP link from a Linux box is a popular means to |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config PPP |
| 7 | 7 | tristate "PPP (point-to-point protocol) support" |
| 8 | 8 | select SLHC |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | PPP (Point to Point Protocol) is a newer and better SLIP. It serves |
| 11 | 11 | the same purpose: sending Internet traffic over telephone (and other |
| 12 | 12 | serial) lines. Ask your access provider if they support it, because |
| @@ -38,7 +38,7 @@ if PPP · 25 unmodified lines | ||
| 38 | 38 | config PPP_BSDCOMP |
| 39 | 39 | tristate "PPP BSD-Compress compression" |
| 40 | 40 | depends on PPP |
| 41 | − ---help--- | |
| 41 | + help | |
| 42 | 42 | Support for the BSD-Compress compression method for PPP, which uses |
| 43 | 43 | the LZW compression method to compress each PPP packet before it is |
| 44 | 44 | sent over the wire. The machine at the other end of the PPP link |
| @@ -59,7 +59,7 @@ config PPP_DEFLATE · 14 unmodified lines | ||
| 59 | 59 | depends on PPP |
| 60 | 60 | select ZLIB_INFLATE |
| 61 | 61 | select ZLIB_DEFLATE |
| 62 | − ---help--- | |
| 62 | + help | |
| 63 | 63 | Support for the Deflate compression method for PPP, which uses the |
| 64 | 64 | Deflate algorithm (the same algorithm that gzip uses) to compress |
| 65 | 65 | each PPP packet before it is sent over the wire. The machine at the |
| @@ -72,7 +72,7 @@ config PPP_DEFLATE · 6 unmodified lines | ||
| 72 | 72 | config PPP_FILTER |
| 73 | 73 | bool "PPP filtering" |
| 74 | 74 | depends on PPP |
| 75 | − ---help--- | |
| 75 | + help | |
| 76 | 76 | Say Y here if you want to be able to filter the packets passing over |
| 77 | 77 | PPP interfaces. This allows you to control which packets count as |
| 78 | 78 | activity (i.e. which packets will reset the idle timer or bring up |
| @@ -88,7 +88,7 @@ config PPP_MPPE · 9 unmodified lines | ||
| 88 | 88 | select CRYPTO |
| 89 | 89 | select CRYPTO_SHA1 |
| 90 | 90 | select CRYPTO_LIB_ARC4 |
| 91 | − ---help--- | |
| 91 | + help | |
| 92 | 92 | Support for the MPPE Encryption protocol, as employed by the |
| 93 | 93 | Microsoft Point-to-Point Tunneling Protocol. |
| 94 | 94 | |
| @@ -98,7 +98,7 @@ config PPP_MPPE · 3 unmodified lines | ||
| 98 | 98 | config PPP_MULTILINK |
| 99 | 99 | bool "PPP multilink support" |
| 100 | 100 | depends on PPP |
| 101 | − ---help--- | |
| 101 | + help | |
| 102 | 102 | PPP multilink is a protocol (defined in RFC 1990) which allows you |
| 103 | 103 | to combine several (logical or physical) lines into one logical PPP |
| 104 | 104 | connection, so that you can utilize your full bandwidth. |
| @@ -111,7 +111,7 @@ config PPP_MULTILINK · 6 unmodified lines | ||
| 111 | 111 | config PPPOATM |
| 112 | 112 | tristate "PPP over ATM" |
| 113 | 113 | depends on ATM && PPP |
| 114 | − ---help--- | |
| 114 | + help | |
| 115 | 115 | Support PPP (Point to Point Protocol) encapsulated in ATM frames. |
| 116 | 116 | This implementation does not yet comply with section 8 of RFC2364, |
| 117 | 117 | which can lead to bad results if the ATM peer loses state and |
| @@ -120,7 +120,7 @@ config PPPOATM · 2 unmodified lines | ||
| 120 | 120 | config PPPOE |
| 121 | 121 | tristate "PPP over Ethernet" |
| 122 | 122 | depends on PPP |
| 123 | − ---help--- | |
| 123 | + help | |
| 124 | 124 | Support for PPP over Ethernet. |
| 125 | 125 | |
| 126 | 126 | This driver requires the latest version of pppd from the CVS |
| @@ -132,7 +132,7 @@ config PPPOE · 5 unmodified lines | ||
| 132 | 132 | config PPTP |
| 133 | 133 | tristate "PPP over IPv4 (PPTP)" |
| 134 | 134 | depends on PPP && NET_IPGRE_DEMUX |
| 135 | − ---help--- | |
| 135 | + help | |
| 136 | 136 | Support for PPP over IPv4.(Point-to-Point Tunneling Protocol) |
| 137 | 137 | |
| 138 | 138 | This driver requires pppd plugin to work in client mode or |
| @@ -143,7 +143,7 @@ config PPTP · 4 unmodified lines | ||
| 143 | 143 | config PPPOL2TP |
| 144 | 144 | tristate "PPP over L2TP" |
| 145 | 145 | depends on L2TP && PPP |
| 146 | − ---help--- | |
| 146 | + help | |
| 147 | 147 | Support for PPP-over-L2TP socket family. L2TP is a protocol |
| 148 | 148 | used by ISPs and enterprises to tunnel PPP traffic over UDP |
| 149 | 149 | tunnels. L2TP is replacing PPTP for VPN uses. |
| @@ -153,7 +153,7 @@ config PPP_ASYNC · 3 unmodified lines | ||
| 153 | 153 | tristate "PPP support for async serial ports" |
| 154 | 154 | depends on PPP |
| 155 | 155 | select CRC_CCITT |
| 156 | − ---help--- | |
| 156 | + help | |
| 157 | 157 | Say Y (or M) here if you want to be able to use PPP over standard |
| 158 | 158 | asynchronous serial ports, such as COM1 or COM2 on a PC. If you use |
| 159 | 159 | a modem (not a synchronous or ISDN modem) to contact your ISP, you |
| @@ -166,7 +166,7 @@ config PPP_ASYNC · 6 unmodified lines | ||
| 166 | 166 | config PPP_SYNC_TTY |
| 167 | 167 | tristate "PPP support for sync tty ports" |
| 168 | 168 | depends on PPP |
| 169 | − ---help--- | |
| 169 | + help | |
| 170 | 170 | Say Y (or M) here if you want to be able to use PPP over synchronous |
| 171 | 171 | (HDLC) tty devices, such as the SyncLink adapter. These devices |
| 172 | 172 | are often used for high-speed leased lines like T1/E1. |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config SLIP |
| 7 | 7 | tristate "SLIP (serial line) support" |
| 8 | 8 | depends on TTY |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to |
| 11 | 11 | connect to your Internet service provider or to connect to some |
| 12 | 12 | other local Unix box or if you want to configure your Linux box as a |
| @@ -36,7 +36,7 @@ config SLIP · 23 unmodified lines | ||
| 36 | 36 | |
| 37 | 37 | config SLHC |
| 38 | 38 | tristate |
| 39 | − ---help--- | |
| 39 | + help | |
| 40 | 40 | This option enables Van Jacobsen serial line header compression |
| 41 | 41 | routines. |
| 42 | 42 | |
| @@ -46,7 +46,7 @@ config SLIP_COMPRESSED · 3 unmodified lines | ||
| 46 | 46 | bool "CSLIP compressed headers" |
| 47 | 47 | depends on SLIP |
| 48 | 48 | select SLHC |
| 49 | − ---help--- | |
| 49 | + help | |
| 50 | 50 | This protocol is faster than SLIP because it uses compression on the |
| 51 | 51 | TCP/IP headers (not on the data itself), but it has to be supported |
| 52 | 52 | on both ends. Ask your access provider if you are not sure and |
| @@ -61,7 +61,7 @@ config SLIP_COMPRESSED · 8 unmodified lines | ||
| 61 | 61 | config SLIP_SMART |
| 62 | 62 | bool "Keepalive and linefill" |
| 63 | 63 | depends on SLIP |
| 64 | − ---help--- | |
| 64 | + help | |
| 65 | 65 | Adds additional capabilities to the SLIP driver to support the |
| 66 | 66 | RELCOM line fill and keepalive monitoring. Ideal on poor quality |
| 67 | 67 | analogue lines. |
| @@ -69,7 +69,7 @@ config SLIP_SMART · 1 unmodified line | ||
| 69 | 69 | config SLIP_MODE_SLIP6 |
| 70 | 70 | bool "Six bit SLIP encapsulation" |
| 71 | 71 | depends on SLIP |
| 72 | − ---help--- | |
| 72 | + help | |
| 73 | 73 | Just occasionally you may need to run IP over hostile serial |
| 74 | 74 | networks that don't pass all control characters or are only seven |
| 75 | 75 | bit. Saying Y here adds an extra mode you can use with SLIP: |
| @@ -1,7 +1,7 @@ | ||
| 1 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | 2 | menuconfig NET_TEAM |
| 3 | 3 | tristate "Ethernet team driver support" |
| 4 | − ---help--- | |
| 4 | + help | |
| 5 | 5 | This allows one to create virtual interfaces that teams together |
| 6 | 6 | multiple ethernet devices. |
| 7 | 7 | |
| @@ -18,7 +18,7 @@ if NET_TEAM · 10 unmodified lines | ||
| 18 | 18 | config NET_TEAM_MODE_BROADCAST |
| 19 | 19 | tristate "Broadcast mode support" |
| 20 | 20 | depends on NET_TEAM |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | Basic mode where packets are transmitted always by all suitable ports. |
| 23 | 23 | |
| 24 | 24 | All added ports are setup to have team's device address. |
| @@ -29,7 +29,7 @@ config NET_TEAM_MODE_BROADCAST · 4 unmodified lines | ||
| 29 | 29 | config NET_TEAM_MODE_ROUNDROBIN |
| 30 | 30 | tristate "Round-robin mode support" |
| 31 | 31 | depends on NET_TEAM |
| 32 | − ---help--- | |
| 32 | + help | |
| 33 | 33 | Basic mode where port used for transmitting packets is selected in |
| 34 | 34 | round-robin fashion using packet counter. |
| 35 | 35 | |
| @@ -41,7 +41,7 @@ config NET_TEAM_MODE_ROUNDROBIN · 5 unmodified lines | ||
| 41 | 41 | config NET_TEAM_MODE_RANDOM |
| 42 | 42 | tristate "Random mode support" |
| 43 | 43 | depends on NET_TEAM |
| 44 | − ---help--- | |
| 44 | + help | |
| 45 | 45 | Basic mode where port used for transmitting packets is selected |
| 46 | 46 | randomly. |
| 47 | 47 | |
| @@ -53,7 +53,7 @@ config NET_TEAM_MODE_RANDOM · 5 unmodified lines | ||
| 53 | 53 | config NET_TEAM_MODE_ACTIVEBACKUP |
| 54 | 54 | tristate "Active-backup mode support" |
| 55 | 55 | depends on NET_TEAM |
| 56 | − ---help--- | |
| 56 | + help | |
| 57 | 57 | Only one port is active at a time and the rest of ports are used |
| 58 | 58 | for backup. |
| 59 | 59 | |
| @@ -66,7 +66,7 @@ config NET_TEAM_MODE_ACTIVEBACKUP · 6 unmodified lines | ||
| 66 | 66 | config NET_TEAM_MODE_LOADBALANCE |
| 67 | 67 | tristate "Load-balance mode support" |
| 68 | 68 | depends on NET_TEAM |
| 69 | − ---help--- | |
| 69 | + help | |
| 70 | 70 | This mode provides load balancing functionality. Tx port selection |
| 71 | 71 | is done using BPF function set up from userspace (bpf_hash_func |
| 72 | 72 | option) |
| @@ -15,7 +15,7 @@ if USB_NET_DRIVERS · 14 unmodified lines | ||
| 15 | 15 | config USB_CATC |
| 16 | 16 | tristate "USB CATC NetMate-based Ethernet device support" |
| 17 | 17 | select CRC32 |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | Say Y if you want to use one of the following 10Mbps USB Ethernet |
| 20 | 20 | device based on the EL1210A chip. Supported devices are: |
| 21 | 21 | Belkin F5U011 |
| @@ -33,7 +33,7 @@ config USB_CATC · 11 unmodified lines | ||
| 33 | 33 | |
| 34 | 34 | config USB_KAWETH |
| 35 | 35 | tristate "USB KLSI KL5USB101-based ethernet device support" |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | Say Y here if you want to use one of the following 10Mbps only |
| 38 | 38 | USB Ethernet adapters based on the KLSI KL5KUSB101B chipset: |
| 39 | 39 | 3Com 3C19250 |
| @@ -73,7 +73,7 @@ config USB_KAWETH · 33 unmodified lines | ||
| 73 | 73 | config USB_PEGASUS |
| 74 | 74 | tristate "USB Pegasus/Pegasus-II based ethernet device support" |
| 75 | 75 | select MII |
| 76 | − ---help--- | |
| 76 | + help | |
| 77 | 77 | Say Y here if you know you have Pegasus or Pegasus-II based adapter. |
| 78 | 78 | If in doubt then look at <file:drivers/net/usb/pegasus.h> for the |
| 79 | 79 | complete list of supported devices. |
| @@ -128,7 +128,7 @@ config USB_LAN78XX · 48 unmodified lines | ||
| 128 | 128 | config USB_USBNET |
| 129 | 129 | tristate "Multi-purpose USB Networking Framework" |
| 130 | 130 | select MII |
| 131 | − ---help--- | |
| 131 | + help | |
| 132 | 132 | This driver supports several kinds of network links over USB, |
| 133 | 133 | with "minidrivers" built around a common network driver core |
| 134 | 134 | that supports deep queues for efficient transfers. (This gives |
| @@ -321,7 +321,7 @@ config USB_NET_SR9800 · 186 unmodified lines | ||
| 321 | 321 | tristate "CoreChip-sz SR9800 based USB 2.0 10/100 ethernet devices" |
| 322 | 322 | depends on USB_USBNET |
| 323 | 323 | select CRC32 |
| 324 | − ---help--- | |
| 324 | + help | |
| 325 | 325 | Say Y if you want to use one of the following 100Mbps USB Ethernet |
| 326 | 326 | device based on the CoreChip-sz SR9800 chip. |
| 327 | 327 | |
| @@ -570,7 +570,7 @@ config USB_CDC_PHONET · 242 unmodified lines | ||
| 570 | 570 | config USB_IPHETH |
| 571 | 571 | tristate "Apple iPhone USB Ethernet driver" |
| 572 | 572 | default n |
| 573 | − ---help--- | |
| 573 | + help | |
| 574 | 574 | Module used to share Internet connection (tethering) from your |
| 575 | 575 | iPhone (Original, 3G and 3GS) to your system. |
| 576 | 576 | Note that you need userspace libraries and programs that are needed |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | |
| 6 | 6 | menuconfig WAN |
| 7 | 7 | bool "Wan interfaces support" |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | Wide Area Networks (WANs), such as X.25, Frame Relay and leased |
| 10 | 10 | lines, are used to interconnect Local Area Networks (LANs) over vast |
| 11 | 11 | distances with data transfer rates significantly higher than those |
| @@ -39,7 +39,7 @@ config HOSTESS_SV11 · 27 unmodified lines | ||
| 39 | 39 | config COSA |
| 40 | 40 | tristate "COSA/SRP sync serial boards support" |
| 41 | 41 | depends on ISA && m && ISA_DMA_API && HDLC && VIRT_TO_BUS |
| 42 | − ---help--- | |
| 42 | + help | |
| 43 | 43 | Driver for COSA and SRP synchronous serial boards. |
| 44 | 44 | |
| 45 | 45 | These boards allow to connect synchronous serial devices (for example |
| @@ -63,7 +63,7 @@ config COSA · 17 unmodified lines | ||
| 63 | 63 | config LANMEDIA |
| 64 | 64 | tristate "LanMedia Corp. SSI/V.35, T1/E1, HSSI, T3 boards" |
| 65 | 65 | depends on PCI && VIRT_TO_BUS && HDLC |
| 66 | − ---help--- | |
| 66 | + help | |
| 67 | 67 | Driver for the following Lan Media family of serial boards: |
| 68 | 68 | |
| 69 | 69 | - LMC 1000 board allows you to connect synchronous serial devices |
| @@ -251,7 +251,7 @@ config C101 · 181 unmodified lines | ||
| 251 | 251 | config FARSYNC |
| 252 | 252 | tristate "FarSync T-Series support" |
| 253 | 253 | depends on HDLC && PCI |
| 254 | − ---help--- | |
| 254 | + help | |
| 255 | 255 | Support for the FarSync T-Series X.21 (and V.35/V.24) cards by |
| 256 | 256 | FarSite Communications Ltd. |
| 257 | 257 | |
| @@ -323,7 +323,7 @@ config IXP4XX_HSS · 65 unmodified lines | ||
| 323 | 323 | |
| 324 | 324 | config DLCI |
| 325 | 325 | tristate "Frame Relay DLCI support" |
| 326 | − ---help--- | |
| 326 | + help | |
| 327 | 327 | Support for the Frame Relay protocol. |
| 328 | 328 | |
| 329 | 329 | Frame Relay is a fast low-cost way to connect to a remote Internet |
| @@ -370,7 +370,7 @@ config SDLA · 40 unmodified lines | ||
| 370 | 370 | config LAPBETHER |
| 371 | 371 | tristate "LAPB over Ethernet driver" |
| 372 | 372 | depends on LAPB && X25 |
| 373 | − ---help--- | |
| 373 | + help | |
| 374 | 374 | Driver for a pseudo device (typically called /dev/lapb0) which allows |
| 375 | 375 | you to open an LAPB point-to-point connection to some other computer |
| 376 | 376 | on your Ethernet network. |
| @@ -386,7 +386,7 @@ config LAPBETHER · 9 unmodified lines | ||
| 386 | 386 | config X25_ASY |
| 387 | 387 | tristate "X.25 async driver" |
| 388 | 388 | depends on LAPB && X25 && TTY |
| 389 | − ---help--- | |
| 389 | + help | |
| 390 | 390 | Send and receive X.25 frames over regular asynchronous serial |
| 391 | 391 | lines such as telephone lines equipped with ordinary modems. |
| 392 | 392 | |
| @@ -401,7 +401,7 @@ config X25_ASY · 8 unmodified lines | ||
| 401 | 401 | config SBNI |
| 402 | 402 | tristate "Granch SBNI12 Leased Line adapter support" |
| 403 | 403 | depends on X86 |
| 404 | − ---help--- | |
| 404 | + help | |
| 405 | 405 | Driver for ISA SBNI12-xx cards which are low cost alternatives to |
| 406 | 406 | leased line modems. |
| 407 | 407 | |
| @@ -9,7 +9,7 @@ menuconfig WLAN · 8 unmodified lines | ||
| 9 | 9 | depends on NET |
| 10 | 10 | select WIRELESS |
| 11 | 11 | default y |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | This section contains all the pre 802.11 and 802.11 wireless |
| 14 | 14 | device drivers. For a complete list of drivers and documentation |
| 15 | 15 | on them refer to the wireless wiki: |
| @@ -54,7 +54,7 @@ config PCMCIA_RAYCS · 38 unmodified lines | ||
| 54 | 54 | select WIRELESS_EXT |
| 55 | 55 | select WEXT_SPY |
| 56 | 56 | select WEXT_PRIV |
| 57 | − ---help--- | |
| 57 | + help | |
| 58 | 58 | Say Y here if you intend to attach an Aviator/Raytheon PCMCIA |
| 59 | 59 | (PC-card) wireless Ethernet networking card to your computer. |
| 60 | 60 | Please read the file <file:Documentation/networking/ray_cs.rst> for |
| @@ -76,7 +76,7 @@ config PCMCIA_WL3501 · 15 unmodified lines | ||
| 76 | 76 | config MAC80211_HWSIM |
| 77 | 77 | tristate "Simulated radio testing tool for mac80211" |
| 78 | 78 | depends on MAC80211 |
| 79 | − ---help--- | |
| 79 | + help | |
| 80 | 80 | This driver is a developer testing tool that can be used to test |
| 81 | 81 | IEEE 802.11 networking stack (mac80211) functionality. This is not |
| 82 | 82 | needed for normal wireless LAN usage and is only for testing. See |
| @@ -94,7 +94,7 @@ config USB_NET_RNDIS_WLAN · 11 unmodified lines | ||
| 94 | 94 | select USB_USBNET |
| 95 | 95 | select USB_NET_CDCETHER |
| 96 | 96 | select USB_NET_RNDIS_HOST |
| 97 | − ---help--- | |
| 97 | + help | |
| 98 | 98 | This is a driver for wireless RNDIS devices. |
| 99 | 99 | These are USB based adapters found in devices such as: |
| 100 | 100 | |
| @@ -118,7 +118,7 @@ config USB_NET_RNDIS_WLAN · 17 unmodified lines | ||
| 118 | 118 | config VIRT_WIFI |
| 119 | 119 | tristate "Wifi wrapper for ethernet drivers" |
| 120 | 120 | depends on CFG80211 |
| 121 | − ---help--- | |
| 121 | + help | |
| 122 | 122 | This option adds support for ethernet connections to appear as if they |
| 123 | 123 | are wifi connections through a special rtnetlink device. |
| 124 | 124 | |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_ADMTEK |
| 3 | 3 | bool "ADMtek devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -17,7 +17,7 @@ config ADM8211 · 8 unmodified lines | ||
| 17 | 17 | depends on MAC80211 && PCI |
| 18 | 18 | select CRC32 |
| 19 | 19 | select EEPROM_93CX6 |
| 20 | − ---help--- | |
| 20 | + help | |
| 21 | 21 | This driver is for ADM8211A, ADM8211B, and ADM8211C based cards. |
| 22 | 22 | These are PCI/mini-PCI/Cardbus 802.11b chips found in cards such as: |
| 23 | 23 | |
| @@ -5,7 +5,7 @@ config ATH_COMMON · 4 unmodified lines | ||
| 5 | 5 | config WLAN_VENDOR_ATH |
| 6 | 6 | bool "Atheros/Qualcomm devices" |
| 7 | 7 | default y |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | If you have a wireless card belonging to this class, say Y. |
| 10 | 10 | |
| 11 | 11 | Note that the answer to this question doesn't directly affect the |
| @@ -25,7 +25,7 @@ if WLAN_VENDOR_ATH · 13 unmodified lines | ||
| 25 | 25 | |
| 26 | 26 | config ATH_DEBUG |
| 27 | 27 | bool "Atheros wireless debugging" |
| 28 | − ---help--- | |
| 28 | + help | |
| 29 | 29 | Say Y, if you want to debug atheros wireless drivers. |
| 30 | 30 | Right now only ath9k makes use of this. |
| 31 | 31 | |
| @@ -33,7 +33,7 @@ config ATH_TRACEPOINTS · 1 unmodified line | ||
| 33 | 33 | bool "Atheros wireless tracing" |
| 34 | 34 | depends on ATH_DEBUG |
| 35 | 35 | depends on EVENT_TRACING |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | This option enables tracepoints for atheros wireless drivers. |
| 38 | 38 | Currently, ath9k makes use of this facility. |
| 39 | 39 | |
| @@ -41,7 +41,7 @@ config ATH_REG_DYNAMIC_USER_REG_HINTS · 1 unmodified line | ||
| 41 | 41 | bool "Atheros dynamic user regulatory hints" |
| 42 | 42 | depends on CFG80211_CERTIFICATION_ONUS |
| 43 | 43 | default n |
| 44 | − ---help--- | |
| 44 | + help | |
| 45 | 45 | Say N. This should only be enabled in countries where |
| 46 | 46 | this feature is explicitly allowed and only on cards that |
| 47 | 47 | specifically have been tested for this. |
| @@ -50,7 +50,7 @@ config ATH_REG_DYNAMIC_USER_CERT_TESTING · 2 unmodified lines | ||
| 50 | 50 | bool "Atheros dynamic user regulatory testing" |
| 51 | 51 | depends on ATH_REG_DYNAMIC_USER_REG_HINTS && CFG80211_CERTIFICATION_ONUS |
| 52 | 52 | default n |
| 53 | − ---help--- | |
| 53 | + help | |
| 54 | 54 | Say N. This should only be enabled on systems |
| 55 | 55 | undergoing certification testing. |
| 56 | 56 | |
| @@ -4,6 +4,6 @@ config AR5523 · 3 unmodified lines | ||
| 4 | 4 | depends on MAC80211 && USB |
| 5 | 5 | select ATH_COMMON |
| 6 | 6 | select FW_LOADER |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | This module add support for AR5523 based USB dongles such as D-Link |
| 9 | 9 | DWL-G132, Netgear WPN111 and many more. |
| @@ -6,7 +6,7 @@ config ATH10K · 5 unmodified lines | ||
| 6 | 6 | select CRC32 |
| 7 | 7 | select WANT_DEV_COREDUMP |
| 8 | 8 | select ATH10K_CE |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This module adds support for wireless adapters based on |
| 11 | 11 | Atheros IEEE 802.11ac family of chipsets. |
| 12 | 12 | |
| @@ -18,25 +18,25 @@ config ATH10K_CE · 5 unmodified lines | ||
| 18 | 18 | config ATH10K_PCI |
| 19 | 19 | tristate "Atheros ath10k PCI support" |
| 20 | 20 | depends on ATH10K && PCI |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | This module adds support for PCIE bus |
| 23 | 23 | |
| 24 | 24 | config ATH10K_AHB |
| 25 | 25 | bool "Atheros ath10k AHB support" |
| 26 | 26 | depends on ATH10K_PCI && OF && RESET_CONTROLLER |
| 27 | − ---help--- | |
| 27 | + help | |
| 28 | 28 | This module adds support for AHB bus |
| 29 | 29 | |
| 30 | 30 | config ATH10K_SDIO |
| 31 | 31 | tristate "Atheros ath10k SDIO support" |
| 32 | 32 | depends on ATH10K && MMC |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | This module adds support for SDIO/MMC bus. |
| 35 | 35 | |
| 36 | 36 | config ATH10K_USB |
| 37 | 37 | tristate "Atheros ath10k USB support (EXPERIMENTAL)" |
| 38 | 38 | depends on ATH10K && USB |
| 39 | − ---help--- | |
| 39 | + help | |
| 40 | 40 | This module adds experimental support for USB bus. Currently |
| 41 | 41 | work in progress and will not fully work. |
| 42 | 42 | |
| @@ -45,14 +45,14 @@ config ATH10K_SNOC · 2 unmodified lines | ||
| 45 | 45 | depends on ATH10K |
| 46 | 46 | depends on ARCH_QCOM || COMPILE_TEST |
| 47 | 47 | select QCOM_QMI_HELPERS |
| 48 | − ---help--- | |
| 48 | + help | |
| 49 | 49 | This module adds support for integrated WCN3990 chip connected |
| 50 | 50 | to system NOC(SNOC). |
| 51 | 51 | |
| 52 | 52 | config ATH10K_DEBUG |
| 53 | 53 | bool "Atheros ath10k debugging" |
| 54 | 54 | depends on ATH10K |
| 55 | − ---help--- | |
| 55 | + help | |
| 56 | 56 | Enables debug support |
| 57 | 57 | |
| 58 | 58 | If unsure, say Y to make it easier to debug problems. |
| @@ -60,7 +60,7 @@ config ATH10K_DEBUG · 1 unmodified line | ||
| 60 | 60 | config ATH10K_DEBUGFS |
| 61 | 61 | bool "Atheros ath10k debugfs support" |
| 62 | 62 | depends on ATH10K && DEBUG_FS |
| 63 | − ---help--- | |
| 63 | + help | |
| 64 | 64 | Enabled debugfs support |
| 65 | 65 | |
| 66 | 66 | If unsure, say Y to make it easier to debug problems. |
| @@ -70,20 +70,20 @@ config ATH10K_SPECTRAL · 3 unmodified lines | ||
| 70 | 70 | depends on ATH10K_DEBUGFS |
| 71 | 71 | select RELAY |
| 72 | 72 | default n |
| 73 | − ---help--- | |
| 73 | + help | |
| 74 | 74 | Say Y to enable access to the FFT/spectral data via debugfs. |
| 75 | 75 | |
| 76 | 76 | config ATH10K_TRACING |
| 77 | 77 | bool "Atheros ath10k tracing support" |
| 78 | 78 | depends on ATH10K |
| 79 | 79 | depends on EVENT_TRACING |
| 80 | − ---help--- | |
| 80 | + help | |
| 81 | 81 | Select this to ath10k use tracing infrastructure. |
| 82 | 82 | |
| 83 | 83 | config ATH10K_DFS_CERTIFIED |
| 84 | 84 | bool "Atheros DFS support for certified platforms" |
| 85 | 85 | depends on ATH10K && CFG80211_CERTIFICATION_ONUS |
| 86 | 86 | default n |
| 87 | − ---help--- | |
| 87 | + help | |
| 88 | 88 | This option enables DFS support for initiating radiation on |
| 89 | 89 | ath10k. |
| @@ -7,7 +7,7 @@ config ATH11K · 6 unmodified lines | ||
| 7 | 7 | depends on ARCH_QCOM || COMPILE_TEST |
| 8 | 8 | select ATH_COMMON |
| 9 | 9 | select QCOM_QMI_HELPERS |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | This module adds support for Qualcomm Technologies 802.11ax family of |
| 12 | 12 | chipsets. |
| 13 | 13 | |
| @@ -16,7 +16,7 @@ config ATH11K · 2 unmodified lines | ||
| 16 | 16 | config ATH11K_DEBUG |
| 17 | 17 | bool "QCA ath11k debugging" |
| 18 | 18 | depends on ATH11K |
| 19 | − ---help--- | |
| 19 | + help | |
| 20 | 20 | Enables debug support |
| 21 | 21 | |
| 22 | 22 | If unsure, say Y to make it easier to debug problems. |
| @@ -24,7 +24,7 @@ config ATH11K_DEBUG · 1 unmodified line | ||
| 24 | 24 | config ATH11K_DEBUGFS |
| 25 | 25 | bool "QCA ath11k debugfs support" |
| 26 | 26 | depends on ATH11K && DEBUG_FS && MAC80211_DEBUGFS |
| 27 | − ---help--- | |
| 27 | + help | |
| 28 | 28 | Enable ath11k debugfs support |
| 29 | 29 | |
| 30 | 30 | If unsure, say Y to make it easier to debug problems. |
| @@ -32,5 +32,5 @@ config ATH11K_DEBUGFS · 1 unmodified line | ||
| 32 | 32 | config ATH11K_TRACING |
| 33 | 33 | bool "ath11k tracing support" |
| 34 | 34 | depends on ATH11K && EVENT_TRACING |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | Select this to use ath11k tracing infrastructure. |
| @@ -8,7 +8,7 @@ config ATH5K · 7 unmodified lines | ||
| 8 | 8 | select NEW_LEDS |
| 9 | 9 | select ATH5K_AHB if ATH25 |
| 10 | 10 | select ATH5K_PCI if !ATH25 |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | This module adds support for wireless adapters based on |
| 13 | 13 | Atheros 5xxx chipset. |
| 14 | 14 | |
| @@ -25,7 +25,7 @@ config ATH5K · 10 unmodified lines | ||
| 25 | 25 | config ATH5K_DEBUG |
| 26 | 26 | bool "Atheros 5xxx debugging" |
| 27 | 27 | depends on ATH5K |
| 28 | − ---help--- | |
| 28 | + help | |
| 29 | 29 | Atheros 5xxx debugging messages. |
| 30 | 30 | |
| 31 | 31 | Say Y, if and you will get debug options for ath5k. |
| @@ -45,7 +45,7 @@ config ATH5K_TRACER · 13 unmodified lines | ||
| 45 | 45 | bool "Atheros 5xxx tracer" |
| 46 | 46 | depends on ATH5K |
| 47 | 47 | depends on EVENT_TRACING |
| 48 | − ---help--- | |
| 48 | + help | |
| 49 | 49 | Say Y here to enable tracepoints for the ath5k driver |
| 50 | 50 | using the kernel tracing infrastructure. Select this |
| 51 | 51 | option if you are interested in debugging the driver. |
| @@ -55,21 +55,21 @@ config ATH5K_TRACER · 3 unmodified lines | ||
| 55 | 55 | config ATH5K_AHB |
| 56 | 56 | bool "Atheros 5xxx AHB bus support" |
| 57 | 57 | depends on ATH25 && ATH5K |
| 58 | − ---help--- | |
| 58 | + help | |
| 59 | 59 | This adds support for WiSoC type chipsets of the 5xxx Atheros |
| 60 | 60 | family. |
| 61 | 61 | |
| 62 | 62 | config ATH5K_PCI |
| 63 | 63 | bool "Atheros 5xxx PCI bus support" |
| 64 | 64 | depends on (!ATH25 && PCI) |
| 65 | − ---help--- | |
| 65 | + help | |
| 66 | 66 | This adds support for PCI type chipsets of the 5xxx Atheros |
| 67 | 67 | family. |
| 68 | 68 | |
| 69 | 69 | config ATH5K_TEST_CHANNELS |
| 70 | 70 | bool "Enables testing channels on ath5k" |
| 71 | 71 | depends on ATH5K && CFG80211_CERTIFICATION_ONUS |
| 72 | − ---help--- | |
| 72 | + help | |
| 73 | 73 | This enables non-standard IEEE 802.11 channels on ath5k, which |
| 74 | 74 | can be used for research purposes. This option should be disabled |
| 75 | 75 | unless doing research. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config ATH6KL |
| 3 | 3 | tristate "Atheros mobile chipsets support" |
| 4 | 4 | depends on CFG80211 |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This module adds core support for wireless adapters based on |
| 7 | 7 | Atheros AR6003 and AR6004 chipsets. You still need separate |
| 8 | 8 | bus drivers for USB and SDIO to be able to use real devices. |
| @@ -15,7 +15,7 @@ config ATH6KL_SDIO · 6 unmodified lines | ||
| 15 | 15 | tristate "Atheros ath6kl SDIO support" |
| 16 | 16 | depends on ATH6KL |
| 17 | 17 | depends on MMC |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | This module adds support for wireless adapters based on |
| 20 | 20 | Atheros AR6003 and AR6004 chipsets running over SDIO. If you |
| 21 | 21 | choose to build it as a module, it will be called ath6kl_sdio. |
| @@ -26,7 +26,7 @@ config ATH6KL_USB · 4 unmodified lines | ||
| 26 | 26 | tristate "Atheros ath6kl USB support" |
| 27 | 27 | depends on ATH6KL |
| 28 | 28 | depends on USB |
| 29 | − ---help--- | |
| 29 | + help | |
| 30 | 30 | This module adds support for wireless adapters based on |
| 31 | 31 | Atheros AR6004 chipset and chipsets based on it running over |
| 32 | 32 | USB. If you choose to build it as a module, it will be |
| @@ -35,7 +35,7 @@ config ATH6KL_USB · 2 unmodified lines | ||
| 35 | 35 | config ATH6KL_DEBUG |
| 36 | 36 | bool "Atheros ath6kl debugging" |
| 37 | 37 | depends on ATH6KL |
| 38 | − ---help--- | |
| 38 | + help | |
| 39 | 39 | Enables ath6kl debug support, including debug messages |
| 40 | 40 | enabled with debug_mask module parameter and debugfs |
| 41 | 41 | interface. |
| @@ -46,7 +46,7 @@ config ATH6KL_TRACING · 4 unmodified lines | ||
| 46 | 46 | bool "Atheros ath6kl tracing support" |
| 47 | 47 | depends on ATH6KL |
| 48 | 48 | depends on EVENT_TRACING |
| 49 | − ---help--- | |
| 49 | + help | |
| 50 | 50 | Select this to ath6kl use tracing infrastructure which, for |
| 51 | 51 | example, can be enabled with help of trace-cmd. All debug |
| 52 | 52 | messages and commands are delivered to using individually |
| @@ -58,7 +58,7 @@ config ATH6KL_REGDOMAIN · 5 unmodified lines | ||
| 58 | 58 | bool "Atheros ath6kl regdomain support" |
| 59 | 59 | depends on ATH6KL |
| 60 | 60 | depends on CFG80211_CERTIFICATION_ONUS |
| 61 | − ---help--- | |
| 61 | + help | |
| 62 | 62 | Enabling this makes it possible to change the regdomain in |
| 63 | 63 | the firmware. This can be only enabled if regulatory requirements |
| 64 | 64 | are taken into account. |
| @@ -14,7 +14,7 @@ config ATH9K_BTCOEX_SUPPORT · 13 unmodified lines | ||
| 14 | 14 | bool "Atheros bluetooth coexistence support" |
| 15 | 15 | depends on (ATH9K || ATH9K_HTC) |
| 16 | 16 | default y |
| 17 | − ---help--- | |
| 17 | + help | |
| 18 | 18 | Say Y, if you want to use the ath9k/ath9k_htc radios together with |
| 19 | 19 | Bluetooth modules in the same system. |
| 20 | 20 | |
| @@ -26,7 +26,7 @@ config ATH9K · 5 unmodified lines | ||
| 26 | 26 | select LEDS_CLASS |
| 27 | 27 | select NEW_LEDS |
| 28 | 28 | select ATH9K_COMMON |
| 29 | − ---help--- | |
| 29 | + help | |
| 30 | 30 | This module adds support for wireless adapters based on |
| 31 | 31 | Atheros IEEE 802.11n AR5008, AR9001 and AR9002 family |
| 32 | 32 | of chipsets. For a specific list of supported external |
| @@ -42,7 +42,7 @@ config ATH9K_PCI · 9 unmodified lines | ||
| 42 | 42 | bool "Atheros ath9k PCI/PCIe bus support" |
| 43 | 43 | default y |
| 44 | 44 | depends on ATH9K && PCI |
| 45 | − ---help--- | |
| 45 | + help | |
| 46 | 46 | This option enables the PCI bus support in ath9k. |
| 47 | 47 | |
| 48 | 48 | Say Y, if you have a compatible PCI/PCIe wireless card. |
| @@ -51,7 +51,7 @@ config ATH9K_AHB · 2 unmodified lines | ||
| 51 | 51 | bool "Atheros ath9k AHB bus support" |
| 52 | 52 | depends on ATH9K |
| 53 | 53 | default n |
| 54 | − ---help--- | |
| 54 | + help | |
| 55 | 55 | This option enables the AHB bus support in ath9k. |
| 56 | 56 | |
| 57 | 57 | Say Y, if you have a SoC with a compatible built-in |
| @@ -62,7 +62,7 @@ config ATH9K_DEBUGFS · 4 unmodified lines | ||
| 62 | 62 | depends on ATH9K && DEBUG_FS |
| 63 | 63 | select MAC80211_DEBUGFS |
| 64 | 64 | select ATH9K_COMMON_DEBUG |
| 65 | − ---help--- | |
| 65 | + help | |
| 66 | 66 | Say Y, if you need access to ath9k's statistics for |
| 67 | 67 | interrupts, rate control, etc. |
| 68 | 68 | |
| @@ -74,14 +74,14 @@ config ATH9K_STATION_STATISTICS · 5 unmodified lines | ||
| 74 | 74 | depends on ATH9K && ATH9K_DEBUGFS && DEBUG_FS |
| 75 | 75 | select MAC80211_DEBUGFS |
| 76 | 76 | default n |
| 77 | − ---help--- | |
| 77 | + help | |
| 78 | 78 | This option enables detailed statistics for association stations. |
| 79 | 79 | |
| 80 | 80 | config ATH9K_TX99 |
| 81 | 81 | bool "Atheros ath9k TX99 testing support" |
| 82 | 82 | depends on ATH9K_DEBUGFS && CFG80211_CERTIFICATION_ONUS |
| 83 | 83 | default n |
| 84 | − ---help--- | |
| 84 | + help | |
| 85 | 85 | Say N. This should only be enabled on systems undergoing |
| 86 | 86 | certification testing and evaluation in a controlled environment. |
| 87 | 87 | Enabling this will only enable TX99 support, all other modes of |
| @@ -101,7 +101,7 @@ config ATH9K_DFS_CERTIFIED · 13 unmodified lines | ||
| 101 | 101 | bool "Atheros DFS support for certified platforms" |
| 102 | 102 | depends on ATH9K && CFG80211_CERTIFICATION_ONUS |
| 103 | 103 | default n |
| 104 | − ---help--- | |
| 104 | + help | |
| 105 | 105 | This option enables DFS support for initiating radiation on |
| 106 | 106 | ath9k. There is no way to dynamically detect if a card was DFS |
| 107 | 107 | certified and as such this is left as a build time option. This |
| @@ -120,7 +120,7 @@ config ATH9K_DYNACK · 12 unmodified lines | ||
| 120 | 120 | bool "Atheros ath9k ACK timeout estimation algorithm" |
| 121 | 121 | depends on ATH9K |
| 122 | 122 | default n |
| 123 | − ---help--- | |
| 123 | + help | |
| 124 | 124 | This option enables ath9k dynamic ACK timeout estimation algorithm |
| 125 | 125 | based on ACK frame RX timestamp, TX frame timestamp and frame |
| 126 | 126 | duration |
| @@ -129,7 +129,7 @@ config ATH9K_WOW · 2 unmodified lines | ||
| 129 | 129 | bool "Wake on Wireless LAN support (EXPERIMENTAL)" |
| 130 | 130 | depends on ATH9K && PM |
| 131 | 131 | default n |
| 132 | − ---help--- | |
| 132 | + help | |
| 133 | 133 | This option enables Wake on Wireless LAN support for certain cards. |
| 134 | 134 | Currently, AR9462 is supported. |
| 135 | 135 | |
| @@ -147,7 +147,7 @@ config ATH9K_CHANNEL_CONTEXT · 11 unmodified lines | ||
| 147 | 147 | bool "Channel Context support" |
| 148 | 148 | depends on ATH9K |
| 149 | 149 | default n |
| 150 | − ---help--- | |
| 150 | + help | |
| 151 | 151 | This option enables channel context support in ath9k, which is needed |
| 152 | 152 | for multi-channel concurrency. Enable this if P2P PowerSave support |
| 153 | 153 | is required. |
| @@ -181,7 +181,7 @@ config ATH9K_HTC · 27 unmodified lines | ||
| 181 | 181 | select LEDS_CLASS |
| 182 | 182 | select NEW_LEDS |
| 183 | 183 | select ATH9K_COMMON |
| 184 | − ---help--- | |
| 184 | + help | |
| 185 | 185 | Support for Atheros HTC based cards. |
| 186 | 186 | Chipsets supported: AR9271 |
| 187 | 187 | |
| @@ -193,7 +193,7 @@ config ATH9K_HTC_DEBUGFS · 5 unmodified lines | ||
| 193 | 193 | bool "Atheros ath9k_htc debugging" |
| 194 | 194 | depends on ATH9K_HTC && DEBUG_FS |
| 195 | 195 | select ATH9K_COMMON_DEBUG |
| 196 | − ---help--- | |
| 196 | + help | |
| 197 | 197 | Say Y, if you need access to ath9k_htc's statistics. |
| 198 | 198 | As well as access to the FFT/spectral data. |
| 199 | 199 | |
| @@ -201,7 +201,7 @@ config ATH9K_HWRNG · 1 unmodified line | ||
| 201 | 201 | bool "Random number generator support" |
| 202 | 202 | depends on ATH9K && (HW_RANDOM = y || HW_RANDOM = ATH9K) |
| 203 | 203 | default n |
| 204 | − ---help--- | |
| 204 | + help | |
| 205 | 205 | This option incorporates the ADC register output as a source of |
| 206 | 206 | randomness into Linux entropy pool (/dev/urandom and /dev/random) |
| 207 | 207 | |
| @@ -213,5 +213,5 @@ config ATH9K_COMMON_SPECTRAL · 5 unmodified lines | ||
| 213 | 213 | depends on ATH9K_DEBUGFS || ATH9K_HTC_DEBUGFS |
| 214 | 214 | select RELAY |
| 215 | 215 | default n |
| 216 | − ---help--- | |
| 216 | + help | |
| 217 | 217 | Say Y to enable access to the FFT/spectral data via debugfs. |
| @@ -4,7 +4,7 @@ config WCN36XX · 3 unmodified lines | ||
| 4 | 4 | depends on MAC80211 && HAS_DMA |
| 5 | 5 | depends on QCOM_WCNSS_CTRL || QCOM_WCNSS_CTRL=n |
| 6 | 6 | depends on RPMSG || RPMSG=n |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | This module adds support for wireless adapters based on |
| 9 | 9 | Qualcomm Atheros WCN3660 and WCN3680 mobile chipsets. |
| 10 | 10 | |
| @@ -13,7 +13,7 @@ config WCN36XX · 2 unmodified lines | ||
| 13 | 13 | config WCN36XX_DEBUGFS |
| 14 | 14 | bool "WCN36XX debugfs support" |
| 15 | 15 | depends on WCN36XX |
| 16 | − ---help--- | |
| 16 | + help | |
| 17 | 17 | Enabled debugfs support |
| 18 | 18 | |
| 19 | 19 | If unsure, say Y to make it easier to debug problems. |
| @@ -5,7 +5,7 @@ config WIL6210 · 4 unmodified lines | ||
| 5 | 5 | depends on CFG80211 |
| 6 | 6 | depends on PCI |
| 7 | 7 | default n |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | This module adds support for wireless adapter based on |
| 10 | 10 | wil6210 chip by Wilocity. It supports operation on the |
| 11 | 11 | 60 GHz band, covered by the IEEE802.11ad standard. |
| @@ -19,7 +19,7 @@ config WIL6210_ISR_COR · 7 unmodified lines | ||
| 19 | 19 | bool "Use Clear-On-Read mode for ISR registers for wil6210" |
| 20 | 20 | depends on WIL6210 |
| 21 | 21 | default y |
| 22 | − ---help--- | |
| 22 | + help | |
| 23 | 23 | ISR registers on wil6210 chip may operate in either |
| 24 | 24 | COR (Clear-On-Read) or W1C (Write-1-to-Clear) mode. |
| 25 | 25 | For production code, use COR (say y); is default since |
| @@ -35,7 +35,7 @@ config WIL6210_TRACING · 9 unmodified lines | ||
| 35 | 35 | depends on WIL6210 |
| 36 | 36 | depends on EVENT_TRACING |
| 37 | 37 | default n |
| 38 | − ---help--- | |
| 38 | + help | |
| 39 | 39 | Say Y here to enable tracepoints for the wil6210 driver |
| 40 | 40 | using the kernel tracing infrastructure. Select this |
| 41 | 41 | option if you are interested in debugging the driver. |
| @@ -47,7 +47,7 @@ config WIL6210_DEBUGFS · 5 unmodified lines | ||
| 47 | 47 | depends on WIL6210 |
| 48 | 48 | depends on DEBUG_FS |
| 49 | 49 | default y |
| 50 | − ---help--- | |
| 50 | + help | |
| 51 | 51 | Say Y here to enable wil6210 debugfs support, using the |
| 52 | 52 | kernel debugfs infrastructure. Select this |
| 53 | 53 | option if you are interested in debugging the driver. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_ATMEL |
| 3 | 3 | bool "Atmel devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -19,7 +19,7 @@ config ATMEL · 10 unmodified lines | ||
| 19 | 19 | select WEXT_PRIV |
| 20 | 20 | select FW_LOADER |
| 21 | 21 | select CRC32 |
| 22 | − ---help--- | |
| 22 | + help | |
| 23 | 23 | A driver 802.11b wireless cards based on the Atmel fast-vnet |
| 24 | 24 | chips. This driver supports standard Linux wireless extensions. |
| 25 | 25 | |
| @@ -33,7 +33,7 @@ config ATMEL · 7 unmodified lines | ||
| 33 | 33 | config PCI_ATMEL |
| 34 | 34 | tristate "Atmel at76c506 PCI cards" |
| 35 | 35 | depends on ATMEL && PCI |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | Enable support for PCI and mini-PCI cards containing the |
| 38 | 38 | Atmel at76c506 chip. |
| 39 | 39 | |
| @@ -43,7 +43,7 @@ config PCMCIA_ATMEL · 3 unmodified lines | ||
| 43 | 43 | select WIRELESS_EXT |
| 44 | 44 | select FW_LOADER |
| 45 | 45 | select CRC32 |
| 46 | − ---help--- | |
| 46 | + help | |
| 47 | 47 | Enable support for PCMCIA cards containing the |
| 48 | 48 | Atmel at76c502 and at76c504 chips. |
| 49 | 49 | |
| @@ -51,7 +51,7 @@ config AT76C50X_USB · 1 unmodified line | ||
| 51 | 51 | tristate "Atmel at76c503/at76c505/at76c505a USB cards" |
| 52 | 52 | depends on MAC80211 && USB |
| 53 | 53 | select FW_LOADER |
| 54 | − ---help--- | |
| 54 | + help | |
| 55 | 55 | Enable support for USB Wireless devices using Atmel at76c503, |
| 56 | 56 | at76c505 or at76c505a chips. |
| 57 | 57 | |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_BROADCOM |
| 3 | 3 | bool "Broadcom devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -6,7 +6,7 @@ config B43 · 5 unmodified lines | ||
| 6 | 6 | select SSB if B43_SSB |
| 7 | 7 | select FW_LOADER |
| 8 | 8 | select CORDIC |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | b43 is a driver for the Broadcom 43xx series wireless devices. |
| 11 | 11 | |
| 12 | 12 | Check "lspci" for something like |
| @@ -77,7 +77,7 @@ config B43_SDIO · 64 unmodified lines | ||
| 77 | 77 | bool "Broadcom 43xx SDIO device support" |
| 78 | 78 | depends on B43 && B43_SSB && SSB_SDIOHOST_POSSIBLE |
| 79 | 79 | select SSB_SDIOHOST |
| 80 | − ---help--- | |
| 80 | + help | |
| 81 | 81 | Broadcom 43xx device support for Soft-MAC SDIO devices. |
| 82 | 82 | |
| 83 | 83 | With this config option you can drive Soft-MAC b43 cards with a |
| @@ -108,7 +108,7 @@ config B43_PHY_G · 24 unmodified lines | ||
| 108 | 108 | bool "Support for G-PHY (802.11g) devices" |
| 109 | 109 | depends on B43 && B43_SSB |
| 110 | 110 | default y |
| 111 | − ---help--- | |
| 111 | + help | |
| 112 | 112 | This PHY type can be found in the following chipsets: |
| 113 | 113 | PCI: BCM4306, BCM4311, BCM4318 |
| 114 | 114 | SoC: BCM4712, BCM5352E |
| @@ -117,7 +117,7 @@ config B43_PHY_N · 2 unmodified lines | ||
| 117 | 117 | bool "Support for N-PHY (the main 802.11n series) devices" |
| 118 | 118 | depends on B43 |
| 119 | 119 | default y |
| 120 | − ---help--- | |
| 120 | + help | |
| 121 | 121 | This PHY type can be found in the following chipsets: |
| 122 | 122 | PCI: BCM4321, BCM4322, |
| 123 | 123 | BCM43222, BCM43224, BCM43225, |
| @@ -128,7 +128,7 @@ config B43_PHY_LP · 4 unmodified lines | ||
| 128 | 128 | bool "Support for LP-PHY (low-power 802.11g) devices" |
| 129 | 129 | depends on B43 && B43_SSB |
| 130 | 130 | default y |
| 131 | − ---help--- | |
| 131 | + help | |
| 132 | 132 | The LP-PHY is a low-power PHY built into some notebooks |
| 133 | 133 | and embedded devices. It supports 802.11a/b/g |
| 134 | 134 | (802.11a support is optional, and currently disabled). |
| @@ -137,13 +137,13 @@ config B43_PHY_HT · 2 unmodified lines | ||
| 137 | 137 | bool "Support for HT-PHY (high throughput 802.11n) devices" |
| 138 | 138 | depends on B43 && B43_BCMA |
| 139 | 139 | default y |
| 140 | − ---help--- | |
| 140 | + help | |
| 141 | 141 | This PHY type with 3x3:3 MIMO can be found in the BCM4331 PCI chipset. |
| 142 | 142 | |
| 143 | 143 | config B43_PHY_LCN |
| 144 | 144 | bool "Support for LCN-PHY devices (BROKEN)" |
| 145 | 145 | depends on B43 && BROKEN |
| 146 | − ---help--- | |
| 146 | + help | |
| 147 | 147 | Support for the LCN-PHY. |
| 148 | 148 | |
| 149 | 149 | Say N, this is BROKEN and crashes driver. |
| @@ -151,7 +151,7 @@ config B43_PHY_LCN · 1 unmodified line | ||
| 151 | 151 | config B43_PHY_AC |
| 152 | 152 | bool "Support for AC-PHY (802.11ac) devices (BROKEN)" |
| 153 | 153 | depends on B43 && B43_BCMA && BROKEN |
| 154 | − ---help--- | |
| 154 | + help | |
| 155 | 155 | This PHY type can be found in the following chipsets: |
| 156 | 156 | PCI: BCM4352, BCM4360 |
| 157 | 157 | |
| @@ -174,7 +174,7 @@ config B43_HWRNG · 16 unmodified lines | ||
| 174 | 174 | config B43_DEBUG |
| 175 | 175 | bool "Broadcom 43xx debugging" |
| 176 | 176 | depends on B43 |
| 177 | − ---help--- | |
| 177 | + help | |
| 178 | 178 | Broadcom 43xx debugging. |
| 179 | 179 | |
| 180 | 180 | This adds additional runtime sanity checks and statistics to the driver. |
| @@ -4,7 +4,7 @@ config B43LEGACY · 3 unmodified lines | ||
| 4 | 4 | depends on SSB_POSSIBLE && MAC80211 && HAS_DMA |
| 5 | 5 | select SSB |
| 6 | 6 | select FW_LOADER |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | b43legacy is a driver for 802.11b devices from Broadcom (BCM4301 and |
| 9 | 9 | BCM4303) and early model 802.11g chips (BCM4306 Ver. 2) used in the |
| 10 | 10 | Linksys WPC54G V1 PCMCIA devices. |
| @@ -54,7 +54,7 @@ config B43LEGACY_DEBUG · 43 unmodified lines | ||
| 54 | 54 | bool "Broadcom 43xx-legacy debugging" |
| 55 | 55 | depends on B43LEGACY |
| 56 | 56 | default y |
| 57 | − ---help--- | |
| 57 | + help | |
| 58 | 58 | Say Y, because this information will help you get the driver running. |
| 59 | 59 | This option generates a minimum of log output. |
| 60 | 60 | |
| @@ -75,7 +75,7 @@ config B43LEGACY_DMA_AND_PIO_MODE · 14 unmodified lines | ||
| 75 | 75 | bool "DMA + PIO" |
| 76 | 76 | select B43LEGACY_DMA |
| 77 | 77 | select B43LEGACY_PIO |
| 78 | − ---help--- | |
| 78 | + help | |
| 79 | 79 | Include both, Direct Memory Access (DMA) and Programmed I/O (PIO) |
| 80 | 80 | data transfer modes. The mode actually used is selectable through |
| 81 | 81 | the module parameter "pio". With pio=0 as a module parameter, the |
| @@ -86,14 +86,14 @@ config B43LEGACY_DMA_AND_PIO_MODE · 4 unmodified lines | ||
| 86 | 86 | config B43LEGACY_DMA_MODE |
| 87 | 87 | bool "DMA (Direct Memory Access) only" |
| 88 | 88 | select B43LEGACY_DMA |
| 89 | − ---help--- | |
| 89 | + help | |
| 90 | 90 | Only include Direct Memory Access (DMA). |
| 91 | 91 | This reduces the size of the driver module, by omitting the PIO code. |
| 92 | 92 | |
| 93 | 93 | config B43LEGACY_PIO_MODE |
| 94 | 94 | bool "PIO (Programmed I/O) only" |
| 95 | 95 | select B43LEGACY_PIO |
| 96 | − ---help--- | |
| 96 | + help | |
| 97 | 97 | Only include Programmed I/O (PIO). |
| 98 | 98 | This reduces the size of the driver module, by omitting the DMA code. |
| 99 | 99 | Please note that PIO transfers are slow (compared to DMA). |
| @@ -12,7 +12,7 @@ config BRCMSMAC · 11 unmodified lines | ||
| 12 | 12 | select BRCMUTIL |
| 13 | 13 | select FW_LOADER |
| 14 | 14 | select CORDIC |
| 15 | − ---help--- | |
| 15 | + help | |
| 16 | 16 | This module adds support for PCIe wireless adapters based on Broadcom |
| 17 | 17 | IEEE802.11n SoftMAC chipsets. It also has WLAN led support, which will |
| 18 | 18 | be available if you select BCMA_DRIVER_GPIO. If you choose to build a |
| @@ -23,7 +23,7 @@ source "drivers/net/wireless/broadcom/brcm80211/brcmfmac/Kconfig" · 4 unmodified lines | ||
| 23 | 23 | config BRCM_TRACING |
| 24 | 24 | bool "Broadcom device tracing" |
| 25 | 25 | depends on BRCMSMAC || BRCMFMAC |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | If you say Y here, the Broadcom wireless drivers will register |
| 28 | 28 | with ftrace to dump event information into the trace ringbuffer. |
| 29 | 29 | Tracing can be enabled at runtime to aid in debugging wireless |
| @@ -35,5 +35,5 @@ config BRCMDBG · 5 unmodified lines | ||
| 35 | 35 | bool "Broadcom driver debug functions" |
| 36 | 36 | depends on BRCMSMAC || BRCMFMAC |
| 37 | 37 | select WANT_DEV_COREDUMP if BRCMFMAC |
| 38 | − ---help--- | |
| 38 | + help | |
| 39 | 39 | Selecting this enables additional code for debug purposes. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_CISCO |
| 3 | 3 | bool "Cisco devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -20,7 +20,7 @@ config AIRO · 11 unmodified lines | ||
| 20 | 20 | select CRYPTO_SKCIPHER |
| 21 | 21 | select WEXT_SPY |
| 22 | 22 | select WEXT_PRIV |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | This is the standard Linux driver to support Cisco/Aironet ISA and |
| 25 | 25 | PCI 802.11 wireless cards. |
| 26 | 26 | It supports the new 802.11b cards from Cisco (Cisco 34X, Cisco 35X |
| @@ -42,7 +42,7 @@ config AIRO_CS · 15 unmodified lines | ||
| 42 | 42 | select CRYPTO |
| 43 | 43 | select CRYPTO_AES |
| 44 | 44 | select CRYPTO_CTR |
| 45 | − ---help--- | |
| 45 | + help | |
| 46 | 46 | This is the standard Linux driver to support Cisco/Aironet PCMCIA |
| 47 | 47 | 802.11 wireless cards. This driver is the same as the Aironet |
| 48 | 48 | driver part of the Linux Pcmcia package. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_INTEL |
| 3 | 3 | bool "Intel devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -12,7 +12,7 @@ config IPW2100 · 11 unmodified lines | ||
| 12 | 12 | select FW_LOADER |
| 13 | 13 | select LIB80211 |
| 14 | 14 | select LIBIPW |
| 15 | − ---help--- | |
| 15 | + help | |
| 16 | 16 | A driver for the Intel PRO/Wireless 2100 Network |
| 17 | 17 | Connection 802.11b wireless network adapter. |
| 18 | 18 | |
| @@ -41,7 +41,7 @@ config IPW2100 · 22 unmodified lines | ||
| 41 | 41 | config IPW2100_MONITOR |
| 42 | 42 | bool "Enable promiscuous mode" |
| 43 | 43 | depends on IPW2100 |
| 44 | − ---help--- | |
| 44 | + help | |
| 45 | 45 | Enables promiscuous/monitor mode support for the ipw2100 driver. |
| 46 | 46 | With this feature compiled into the driver, you can switch to |
| 47 | 47 | promiscuous mode via the Wireless Tool's Monitor mode. While in this |
| @@ -50,7 +50,7 @@ config IPW2100_MONITOR · 2 unmodified lines | ||
| 50 | 50 | config IPW2100_DEBUG |
| 51 | 51 | bool "Enable full debugging output in IPW2100 module." |
| 52 | 52 | depends on IPW2100 |
| 53 | − ---help--- | |
| 53 | + help | |
| 54 | 54 | This option will enable debug tracing output for the IPW2100. |
| 55 | 55 | |
| 56 | 56 | This will result in the kernel module being ~60k larger. You can |
| @@ -74,7 +74,7 @@ config IPW2200 · 17 unmodified lines | ||
| 74 | 74 | select FW_LOADER |
| 75 | 75 | select LIB80211 |
| 76 | 76 | select LIBIPW |
| 77 | − ---help--- | |
| 77 | + help | |
| 78 | 78 | A driver for the Intel PRO/Wireless 2200BG and 2915ABG Network |
| 79 | 79 | Connection adapters. |
| 80 | 80 | |
| @@ -103,7 +103,7 @@ config IPW2200 · 22 unmodified lines | ||
| 103 | 103 | config IPW2200_MONITOR |
| 104 | 104 | bool "Enable promiscuous mode" |
| 105 | 105 | depends on IPW2200 |
| 106 | − ---help--- | |
| 106 | + help | |
| 107 | 107 | Enables promiscuous/monitor mode support for the ipw2200 driver. |
| 108 | 108 | With this feature compiled into the driver, you can switch to |
| 109 | 109 | promiscuous mode via the Wireless Tool's Monitor mode. While in this |
| @@ -117,7 +117,7 @@ config IPW2200_PROMISCUOUS · 7 unmodified lines | ||
| 117 | 117 | bool "Enable creation of a RF radiotap promiscuous interface" |
| 118 | 118 | depends on IPW2200_MONITOR |
| 119 | 119 | select IPW2200_RADIOTAP |
| 120 | − ---help--- | |
| 120 | + help | |
| 121 | 121 | Enables the creation of a second interface prefixed 'rtap'. |
| 122 | 122 | This second interface will provide every received in radiotap |
| 123 | 123 | format. |
| @@ -144,7 +144,7 @@ config IPW2200_QOS · 20 unmodified lines | ||
| 144 | 144 | config IPW2200_DEBUG |
| 145 | 145 | bool "Enable full debugging output in IPW2200 module." |
| 146 | 146 | depends on IPW2200 |
| 147 | − ---help--- | |
| 147 | + help | |
| 148 | 148 | This option will enable low level debug tracing output for IPW2200. |
| 149 | 149 | |
| 150 | 150 | Note, normal debug code is already compiled in. This low level |
| @@ -170,7 +170,7 @@ config LIBIPW · 19 unmodified lines | ||
| 170 | 170 | select LIB80211_CRYPT_WEP |
| 171 | 171 | select LIB80211_CRYPT_TKIP |
| 172 | 172 | select LIB80211_CRYPT_CCMP |
| 173 | − ---help--- | |
| 173 | + help | |
| 174 | 174 | This option enables the hardware independent IEEE 802.11 |
| 175 | 175 | networking stack. This component is deprecated in favor of the |
| 176 | 176 | mac80211 component. |
| @@ -178,7 +178,7 @@ config LIBIPW · 1 unmodified line | ||
| 178 | 178 | config LIBIPW_DEBUG |
| 179 | 179 | bool "Full debugging output for the LIBIPW component" |
| 180 | 180 | depends on LIBIPW |
| 181 | − ---help--- | |
| 181 | + help | |
| 182 | 182 | This option will enable debug tracing output for the |
| 183 | 183 | libipw component. |
| 184 | 184 | |
| @@ -11,7 +11,7 @@ config IWL4965 · 10 unmodified lines | ||
| 11 | 11 | tristate "Intel Wireless WiFi 4965AGN (iwl4965)" |
| 12 | 12 | depends on PCI && MAC80211 |
| 13 | 13 | select IWLEGACY |
| 14 | − ---help--- | |
| 14 | + help | |
| 15 | 15 | This option enables support for |
| 16 | 16 | |
| 17 | 17 | Select to build the driver supporting the: |
| @@ -39,7 +39,7 @@ config IWL3945 · 21 unmodified lines | ||
| 39 | 39 | tristate "Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945)" |
| 40 | 40 | depends on PCI && MAC80211 |
| 41 | 41 | select IWLEGACY |
| 42 | − ---help--- | |
| 42 | + help | |
| 43 | 43 | Select to build the driver supporting the: |
| 44 | 44 | |
| 45 | 45 | Intel PRO/Wireless 3945ABG/BG Network Connection |
| @@ -67,7 +67,7 @@ menu "iwl3945 / iwl4965 Debugging Options" · 21 unmodified lines | ||
| 67 | 67 | config IWLEGACY_DEBUG |
| 68 | 68 | bool "Enable full debugging output in iwlegacy (iwl 3945/4965) drivers" |
| 69 | 69 | depends on IWLEGACY |
| 70 | − ---help--- | |
| 70 | + help | |
| 71 | 71 | This option will enable debug tracing output for the iwlegacy |
| 72 | 72 | drivers. |
| 73 | 73 | |
| @@ -93,7 +93,7 @@ config IWLEGACY_DEBUG · 19 unmodified lines | ||
| 93 | 93 | config IWLEGACY_DEBUGFS |
| 94 | 94 | bool "iwlegacy (iwl 3945/4965) debugfs support" |
| 95 | 95 | depends on IWLEGACY && MAC80211_DEBUGFS |
| 96 | − ---help--- | |
| 96 | + help | |
| 97 | 97 | Enable creation of debugfs files for the iwlegacy drivers. This |
| 98 | 98 | is a low-impact option that allows getting insight into the |
| 99 | 99 | driver's state at runtime. |
| @@ -3,7 +3,7 @@ config IWLWIFI · 2 unmodified lines | ||
| 3 | 3 | tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi) " |
| 4 | 4 | depends on PCI && HAS_IOMEM && CFG80211 |
| 5 | 5 | select FW_LOADER |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | Select to build the driver supporting the: |
| 8 | 8 | |
| 9 | 9 | Intel Wireless WiFi Link Next-Gen AGN |
| @@ -96,7 +96,7 @@ menu "Debugging Options" · 86 unmodified lines | ||
| 96 | 96 | |
| 97 | 97 | config IWLWIFI_DEBUG |
| 98 | 98 | bool "Enable full debugging output in the iwlwifi driver" |
| 99 | − ---help--- | |
| 99 | + help | |
| 100 | 100 | This option will enable debug tracing output for the iwlwifi drivers |
| 101 | 101 | |
| 102 | 102 | This will result in the kernel module being ~100k larger. You can |
| @@ -121,7 +121,7 @@ config IWLWIFI_DEBUG · 18 unmodified lines | ||
| 121 | 121 | config IWLWIFI_DEBUGFS |
| 122 | 122 | bool "iwlwifi debugfs support" |
| 123 | 123 | depends on MAC80211_DEBUGFS |
| 124 | − ---help--- | |
| 124 | + help | |
| 125 | 125 | Enable creation of debugfs files for the iwlwifi drivers. This |
| 126 | 126 | is a low-impact option that allows getting insight into the |
| 127 | 127 | driver's state at runtime. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_INTERSIL |
| 3 | 3 | bool "Intersil devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -23,7 +23,7 @@ config PRISM54 · 14 unmodified lines | ||
| 23 | 23 | select WEXT_SPY |
| 24 | 24 | select WEXT_PRIV |
| 25 | 25 | select FW_LOADER |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | This enables support for FullMAC PCI/Cardbus prism54 devices. This |
| 28 | 28 | driver is now deprecated in favor for the SoftMAC driver, p54pci. |
| 29 | 29 | p54pci supports FullMAC PCI/Cardbus devices as well. |
| @@ -15,7 +15,7 @@ config HOSTAP · 14 unmodified lines | ||
| 15 | 15 | select LIB80211_CRYPT_WEP |
| 16 | 16 | select LIB80211_CRYPT_TKIP |
| 17 | 17 | select LIB80211_CRYPT_CCMP |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | Shared driver code for IEEE 802.11b wireless cards based on |
| 20 | 20 | Intersil Prism2/2.5/3 chipset. This driver supports so called |
| 21 | 21 | Host AP mode that allows the card to act as an IEEE 802.11 |
| @@ -36,7 +36,7 @@ config HOSTAP · 14 unmodified lines | ||
| 36 | 36 | config HOSTAP_FIRMWARE |
| 37 | 37 | bool "Support downloading firmware images with Host AP driver" |
| 38 | 38 | depends on HOSTAP |
| 39 | − ---help--- | |
| 39 | + help | |
| 40 | 40 | Configure Host AP driver to include support for firmware image |
| 41 | 41 | download. This option by itself only enables downloading to the |
| 42 | 42 | volatile memory, i.e. the card RAM. This option is required to |
| @@ -49,7 +49,7 @@ config HOSTAP_FIRMWARE · 6 unmodified lines | ||
| 49 | 49 | config HOSTAP_FIRMWARE_NVRAM |
| 50 | 50 | bool "Support for non-volatile firmware download" |
| 51 | 51 | depends on HOSTAP_FIRMWARE |
| 52 | − ---help--- | |
| 52 | + help | |
| 53 | 53 | Allow Host AP driver to write firmware images to the non-volatile |
| 54 | 54 | card memory, i.e. flash memory that survives power cycling. |
| 55 | 55 | Enable this option if you want to be able to change card firmware |
| @@ -61,7 +61,7 @@ config HOSTAP_FIRMWARE_NVRAM · 5 unmodified lines | ||
| 61 | 61 | config HOSTAP_PLX |
| 62 | 62 | tristate "Host AP driver for Prism2/2.5/3 in PLX9052 PCI adaptors" |
| 63 | 63 | depends on PCI && HOSTAP |
| 64 | − ---help--- | |
| 64 | + help | |
| 65 | 65 | Host AP driver's version for Prism2/2.5/3 PC Cards in PLX9052 based |
| 66 | 66 | PCI adaptors. |
| 67 | 67 | |
| @@ -75,7 +75,7 @@ config HOSTAP_PLX · 7 unmodified lines | ||
| 75 | 75 | config HOSTAP_PCI |
| 76 | 76 | tristate "Host AP driver for Prism2.5 PCI adaptors" |
| 77 | 77 | depends on PCI && HOSTAP |
| 78 | − ---help--- | |
| 78 | + help | |
| 79 | 79 | Host AP driver's version for Prism2.5 PCI adaptors. |
| 80 | 80 | |
| 81 | 81 | "Host AP support for Prism2/2.5/3 IEEE 802.11b" is required for this |
| @@ -88,7 +88,7 @@ config HOSTAP_PCI · 6 unmodified lines | ||
| 88 | 88 | config HOSTAP_CS |
| 89 | 89 | tristate "Host AP driver for Prism2/2.5/3 PC Cards" |
| 90 | 90 | depends on PCMCIA && HOSTAP |
| 91 | − ---help--- | |
| 91 | + help | |
| 92 | 92 | Host AP driver's version for Prism2/2.5/3 PC Cards. |
| 93 | 93 | |
| 94 | 94 | "Host AP support for Prism2/2.5/3 IEEE 802.11b" is required for this |
| @@ -10,7 +10,7 @@ config HERMES · 9 unmodified lines | ||
| 10 | 10 | select FW_LOADER |
| 11 | 11 | select CRYPTO |
| 12 | 12 | select CRYPTO_MICHAEL_MIC |
| 13 | − ---help--- | |
| 13 | + help | |
| 14 | 14 | A driver for 802.11b wireless cards based on the "Hermes" or |
| 15 | 15 | Intersil HFA384x (Prism 2) MAC controller. This includes the vast |
| 16 | 16 | majority of the PCMCIA 802.11b cards (which are nearly all rebadges) |
| @@ -32,7 +32,7 @@ config HERMES · 15 unmodified lines | ||
| 32 | 32 | config HERMES_PRISM |
| 33 | 33 | bool "Support Prism 2/2.5 chipset" |
| 34 | 34 | depends on HERMES |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | |
| 37 | 37 | Say Y to enable support for Prism 2 and 2.5 chipsets. These |
| 38 | 38 | chipsets are better handled by the hostap driver. This driver |
| @@ -44,7 +44,7 @@ config HERMES_CACHE_FW_ON_INIT · 5 unmodified lines | ||
| 44 | 44 | bool "Cache Hermes firmware on driver initialisation" |
| 45 | 45 | depends on HERMES |
| 46 | 46 | default y |
| 47 | − ---help--- | |
| 47 | + help | |
| 48 | 48 | Say Y to cache any firmware required by the Hermes drivers |
| 49 | 49 | on startup. The firmware will remain cached until the |
| 50 | 50 | driver is unloaded. The cache uses 64K of RAM. |
| @@ -110,7 +110,7 @@ config PCI_HERMES · 59 unmodified lines | ||
| 110 | 110 | config PCMCIA_HERMES |
| 111 | 111 | tristate "Hermes PCMCIA card support" |
| 112 | 112 | depends on PCMCIA && HERMES && HAS_IOPORT_MAP |
| 113 | − ---help--- | |
| 113 | + help | |
| 114 | 114 | A driver for "Hermes" chipset based PCMCIA wireless adaptors, such |
| 115 | 115 | as the Lucent WavelanIEEE/Orinoco cards and their OEM (Cabletron/ |
| 116 | 116 | EnteraSys RoamAbout 802.11, ELSA Airlancer, Melco Buffalo and |
| @@ -125,7 +125,7 @@ config PCMCIA_HERMES · 8 unmodified lines | ||
| 125 | 125 | config PCMCIA_SPECTRUM |
| 126 | 126 | tristate "Symbol Spectrum24 Trilogy PCMCIA card support" |
| 127 | 127 | depends on PCMCIA && HERMES && HAS_IOPORT_MAP |
| 128 | − ---help--- | |
| 128 | + help | |
| 129 | 129 | |
| 130 | 130 | This is a driver for 802.11b cards using RAM-loadable Symbol |
| 131 | 131 | firmware, such as Symbol Wireless Networker LA4100, CompactFlash |
| @@ -139,5 +139,5 @@ config ORINOCO_USB · 7 unmodified lines | ||
| 139 | 139 | tristate "Agere Orinoco USB support" |
| 140 | 140 | depends on USB && HERMES |
| 141 | 141 | select FW_LOADER |
| 142 | − ---help--- | |
| 142 | + help | |
| 143 | 143 | This driver is for USB versions of the Agere Orinoco card. |
| @@ -4,7 +4,7 @@ config P54_COMMON · 3 unmodified lines | ||
| 4 | 4 | depends on MAC80211 |
| 5 | 5 | select FW_LOADER |
| 6 | 6 | select CRC_CCITT |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | This is common code for isl38xx/stlc45xx based modules. |
| 9 | 9 | This module does nothing by itself - the USB/PCI/SPI front-ends |
| 10 | 10 | also need to be enabled in order to support any devices. |
| @@ -18,7 +18,7 @@ config P54_USB · 7 unmodified lines | ||
| 18 | 18 | tristate "Prism54 USB support" |
| 19 | 19 | depends on P54_COMMON && USB |
| 20 | 20 | select CRC32 |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | This driver is for USB isl38xx based wireless cards. |
| 23 | 23 | |
| 24 | 24 | These devices require softmac firmware which can be found at |
| @@ -29,7 +29,7 @@ config P54_USB · 4 unmodified lines | ||
| 29 | 29 | config P54_PCI |
| 30 | 30 | tristate "Prism54 PCI support" |
| 31 | 31 | depends on P54_COMMON && PCI |
| 32 | − ---help--- | |
| 32 | + help | |
| 33 | 33 | This driver is for PCI isl38xx based wireless cards. |
| 34 | 34 | This driver supports most devices that are supported by the |
| 35 | 35 | fullmac prism54 driver plus many devices which are not |
| @@ -43,7 +43,7 @@ config P54_PCI · 7 unmodified lines | ||
| 43 | 43 | config P54_SPI |
| 44 | 44 | tristate "Prism54 SPI (stlc45xx) support" |
| 45 | 45 | depends on P54_COMMON && SPI_MASTER |
| 46 | − ---help--- | |
| 46 | + help | |
| 47 | 47 | This driver is for stlc4550 or stlc4560 based wireless chips |
| 48 | 48 | such as Nokia's N800/N810 Portable Internet Tablet. |
| 49 | 49 | |
| @@ -53,7 +53,7 @@ config P54_SPI_DEFAULT_EEPROM · 3 unmodified lines | ||
| 53 | 53 | bool "Include fallback EEPROM blob" |
| 54 | 54 | depends on P54_SPI |
| 55 | 55 | default n |
| 56 | − ---help--- | |
| 56 | + help | |
| 57 | 57 | Unlike the PCI or USB devices, the SPI variants don't have |
| 58 | 58 | a dedicated EEPROM chip to store all device specific values |
| 59 | 59 | for calibration, country and interface settings. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_MARVELL |
| 3 | 3 | bool "Marvell devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -19,7 +19,7 @@ source "drivers/net/wireless/marvell/mwifiex/Kconfig" · 10 unmodified lines | ||
| 19 | 19 | config MWL8K |
| 20 | 20 | tristate "Marvell 88W8xxx PCI/PCIe Wireless support" |
| 21 | 21 | depends on MAC80211 && PCI |
| 22 | − ---help--- | |
| 22 | + help | |
| 23 | 23 | This driver supports Marvell TOPDOG 802.11 wireless cards. |
| 24 | 24 | |
| 25 | 25 | To compile this driver as a module, choose M here: the module |
| @@ -6,37 +6,37 @@ config LIBERTAS · 5 unmodified lines | ||
| 6 | 6 | select WEXT_SPY |
| 7 | 7 | select LIB80211 |
| 8 | 8 | select FW_LOADER |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | A library for Marvell Libertas 8xxx devices. |
| 11 | 11 | |
| 12 | 12 | config LIBERTAS_USB |
| 13 | 13 | tristate "Marvell Libertas 8388 USB 802.11b/g cards" |
| 14 | 14 | depends on LIBERTAS && USB |
| 15 | − ---help--- | |
| 15 | + help | |
| 16 | 16 | A driver for Marvell Libertas 8388 USB devices. |
| 17 | 17 | |
| 18 | 18 | config LIBERTAS_CS |
| 19 | 19 | tristate "Marvell Libertas 8385 CompactFlash 802.11b/g cards" |
| 20 | 20 | depends on LIBERTAS && PCMCIA && HAS_IOPORT_MAP |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | A driver for Marvell Libertas 8385 CompactFlash devices. |
| 23 | 23 | |
| 24 | 24 | config LIBERTAS_SDIO |
| 25 | 25 | tristate "Marvell Libertas 8385/8686/8688 SDIO 802.11b/g cards" |
| 26 | 26 | depends on LIBERTAS && MMC |
| 27 | − ---help--- | |
| 27 | + help | |
| 28 | 28 | A driver for Marvell Libertas 8385/8686/8688 SDIO devices. |
| 29 | 29 | |
| 30 | 30 | config LIBERTAS_SPI |
| 31 | 31 | tristate "Marvell Libertas 8686 SPI 802.11b/g cards" |
| 32 | 32 | depends on LIBERTAS && SPI |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | A driver for Marvell Libertas 8686 SPI devices. |
| 35 | 35 | |
| 36 | 36 | config LIBERTAS_DEBUG |
| 37 | 37 | bool "Enable full debugging output in the Libertas module." |
| 38 | 38 | depends on LIBERTAS |
| 39 | − ---help--- | |
| 39 | + help | |
| 40 | 40 | Debugging support. |
| 41 | 41 | |
| 42 | 42 | config LIBERTAS_MESH |
| @@ -3,17 +3,17 @@ config LIBERTAS_THINFIRM · 2 unmodified lines | ||
| 3 | 3 | tristate "Marvell 8xxx Libertas WLAN driver support with thin firmware" |
| 4 | 4 | depends on MAC80211 |
| 5 | 5 | select FW_LOADER |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | A library for Marvell Libertas 8xxx devices using thinfirm. |
| 8 | 8 | |
| 9 | 9 | config LIBERTAS_THINFIRM_DEBUG |
| 10 | 10 | bool "Enable full debugging output in the Libertas thin firmware module." |
| 11 | 11 | depends on LIBERTAS_THINFIRM |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | Debugging support. |
| 14 | 14 | |
| 15 | 15 | config LIBERTAS_THINFIRM_USB |
| 16 | 16 | tristate "Marvell Libertas 8388 USB 802.11b/g cards with thin firmware" |
| 17 | 17 | depends on LIBERTAS_THINFIRM && USB |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | A driver for Marvell Libertas 8388 USB devices using thinfirm. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config MWIFIEX |
| 3 | 3 | tristate "Marvell WiFi-Ex Driver" |
| 4 | 4 | depends on CFG80211 |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This adds support for wireless adapters based on Marvell |
| 7 | 7 | 802.11n/ac chipsets. |
| 8 | 8 | |
| @@ -14,7 +14,7 @@ config MWIFIEX_SDIO · 5 unmodified lines | ||
| 14 | 14 | depends on MWIFIEX && MMC |
| 15 | 15 | select FW_LOADER |
| 16 | 16 | select WANT_DEV_COREDUMP |
| 17 | − ---help--- | |
| 17 | + help | |
| 18 | 18 | This adds support for wireless adapters based on Marvell |
| 19 | 19 | 8786/8787/8797/8887/8897/8977/8987/8997 chipsets with SDIO interface. |
| 20 | 20 | |
| @@ -26,7 +26,7 @@ config MWIFIEX_PCIE · 5 unmodified lines | ||
| 26 | 26 | depends on MWIFIEX && PCI |
| 27 | 27 | select FW_LOADER |
| 28 | 28 | select WANT_DEV_COREDUMP |
| 29 | − ---help--- | |
| 29 | + help | |
| 30 | 30 | This adds support for wireless adapters based on Marvell |
| 31 | 31 | 8766/8897/8997 chipsets with PCIe interface. |
| 32 | 32 | |
| @@ -37,7 +37,7 @@ config MWIFIEX_USB · 4 unmodified lines | ||
| 37 | 37 | tristate "Marvell WiFi-Ex Driver for USB8766/8797/8997" |
| 38 | 38 | depends on MWIFIEX && USB |
| 39 | 39 | select FW_LOADER |
| 40 | − ---help--- | |
| 40 | + help | |
| 41 | 41 | This adds support for wireless adapters based on Marvell |
| 42 | 42 | 8797/8997 chipset with USB interface. |
| 43 | 43 | |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_MEDIATEK |
| 3 | 3 | bool "MediaTek devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -3,5 +3,5 @@ config MT7601U · 2 unmodified lines | ||
| 3 | 3 | tristate "MediaTek MT7601U (USB) support" |
| 4 | 4 | depends on MAC80211 |
| 5 | 5 | depends on USB |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | This adds support for MT7601U-based wireless USB dongles. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_RALINK |
| 3 | 3 | bool "Ralink devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | menuconfig RT2X00 |
| 3 | 3 | tristate "Ralink driver support" |
| 4 | 4 | depends on MAC80211 && HAS_DMA |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This will enable the support for the Ralink drivers, |
| 7 | 7 | developed in the rt2x00 project <http://rt2x00.serialmonkey.com>. |
| 8 | 8 | |
| @@ -24,7 +24,7 @@ config RT2400PCI · 15 unmodified lines | ||
| 24 | 24 | select RT2X00_LIB_MMIO |
| 25 | 25 | select RT2X00_LIB_PCI |
| 26 | 26 | select EEPROM_93CX6 |
| 27 | − ---help--- | |
| 27 | + help | |
| 28 | 28 | This adds support for rt2400 wireless chipset family. |
| 29 | 29 | Supported chips: RT2460. |
| 30 | 30 | |
| @@ -36,7 +36,7 @@ config RT2500PCI · 5 unmodified lines | ||
| 36 | 36 | select RT2X00_LIB_MMIO |
| 37 | 37 | select RT2X00_LIB_PCI |
| 38 | 38 | select EEPROM_93CX6 |
| 39 | − ---help--- | |
| 39 | + help | |
| 40 | 40 | This adds support for rt2500 wireless chipset family. |
| 41 | 41 | Supported chips: RT2560. |
| 42 | 42 | |
| @@ -51,7 +51,7 @@ config RT61PCI · 8 unmodified lines | ||
| 51 | 51 | select RT2X00_LIB_CRYPTO |
| 52 | 52 | select CRC_ITU_T |
| 53 | 53 | select EEPROM_93CX6 |
| 54 | − ---help--- | |
| 54 | + help | |
| 55 | 55 | This adds support for rt2501 wireless chipset family. |
| 56 | 56 | Supported chips: RT2561, RT2561S & RT2661. |
| 57 | 57 | |
| @@ -68,7 +68,7 @@ config RT2800PCI · 10 unmodified lines | ||
| 68 | 68 | select RT2X00_LIB_CRYPTO |
| 69 | 69 | select CRC_CCITT |
| 70 | 70 | select EEPROM_93CX6 |
| 71 | − ---help--- | |
| 71 | + help | |
| 72 | 72 | This adds support for rt27xx/rt28xx/rt30xx wireless chipset family. |
| 73 | 73 | Supported chips: RT2760, RT2790, RT2860, RT2880, RT2890, RT3052, |
| 74 | 74 | RT3090, RT3091 & RT3092 |
| @@ -80,7 +80,7 @@ if RT2800PCI · 5 unmodified lines | ||
| 80 | 80 | config RT2800PCI_RT33XX |
| 81 | 81 | bool "rt2800pci - Include support for rt33xx devices" |
| 82 | 82 | default y |
| 83 | − ---help--- | |
| 83 | + help | |
| 84 | 84 | This adds support for rt33xx wireless chipset family to the |
| 85 | 85 | rt2800pci driver. |
| 86 | 86 | Supported chips: RT3390 |
| @@ -88,7 +88,7 @@ config RT2800PCI_RT33XX · 1 unmodified line | ||
| 88 | 88 | config RT2800PCI_RT35XX |
| 89 | 89 | bool "rt2800pci - Include support for rt35xx devices (EXPERIMENTAL)" |
| 90 | 90 | default y |
| 91 | − ---help--- | |
| 91 | + help | |
| 92 | 92 | This adds support for rt35xx wireless chipset family to the |
| 93 | 93 | rt2800pci driver. |
| 94 | 94 | Supported chips: RT3060, RT3062, RT3562, RT3592 |
| @@ -97,7 +97,7 @@ config RT2800PCI_RT35XX · 2 unmodified lines | ||
| 97 | 97 | config RT2800PCI_RT53XX |
| 98 | 98 | bool "rt2800pci - Include support for rt53xx devices (EXPERIMENTAL)" |
| 99 | 99 | default y |
| 100 | − ---help--- | |
| 100 | + help | |
| 101 | 101 | This adds support for rt53xx wireless chipset family to the |
| 102 | 102 | rt2800pci driver. |
| 103 | 103 | Supported chips: RT5390 |
| @@ -105,7 +105,7 @@ config RT2800PCI_RT53XX · 1 unmodified line | ||
| 105 | 105 | config RT2800PCI_RT3290 |
| 106 | 106 | bool "rt2800pci - Include support for rt3290 devices (EXPERIMENTAL)" |
| 107 | 107 | default y |
| 108 | − ---help--- | |
| 108 | + help | |
| 109 | 109 | This adds support for rt3290 wireless chipset family to the |
| 110 | 110 | rt2800pci driver. |
| 111 | 111 | Supported chips: RT3290 |
| @@ -116,7 +116,7 @@ config RT2500USB · 4 unmodified lines | ||
| 116 | 116 | depends on USB |
| 117 | 117 | select RT2X00_LIB_USB |
| 118 | 118 | select RT2X00_LIB_CRYPTO |
| 119 | − ---help--- | |
| 119 | + help | |
| 120 | 120 | This adds support for rt2500 wireless chipset family. |
| 121 | 121 | Supported chips: RT2571 & RT2572. |
| 122 | 122 | |
| @@ -129,7 +129,7 @@ config RT73USB · 6 unmodified lines | ||
| 129 | 129 | select RT2X00_LIB_FIRMWARE |
| 130 | 130 | select RT2X00_LIB_CRYPTO |
| 131 | 131 | select CRC_ITU_T |
| 132 | − ---help--- | |
| 132 | + help | |
| 133 | 133 | This adds support for rt2501 wireless chipset family. |
| 134 | 134 | Supported chips: RT2571W, RT2573 & RT2671. |
| 135 | 135 | |
| @@ -143,7 +143,7 @@ config RT2800USB · 7 unmodified lines | ||
| 143 | 143 | select RT2X00_LIB_FIRMWARE |
| 144 | 144 | select RT2X00_LIB_CRYPTO |
| 145 | 145 | select CRC_CCITT |
| 146 | − ---help--- | |
| 146 | + help | |
| 147 | 147 | This adds support for rt27xx/rt28xx/rt30xx wireless chipset family. |
| 148 | 148 | Supported chips: RT2770, RT2870 & RT3070, RT3071 & RT3072 |
| 149 | 149 | |
| @@ -154,7 +154,7 @@ if RT2800USB · 4 unmodified lines | ||
| 154 | 154 | config RT2800USB_RT33XX |
| 155 | 155 | bool "rt2800usb - Include support for rt33xx devices" |
| 156 | 156 | default y |
| 157 | − ---help--- | |
| 157 | + help | |
| 158 | 158 | This adds support for rt33xx wireless chipset family to the |
| 159 | 159 | rt2800usb driver. |
| 160 | 160 | Supported chips: RT3370 |
| @@ -162,27 +162,27 @@ config RT2800USB_RT33XX · 1 unmodified line | ||
| 162 | 162 | config RT2800USB_RT35XX |
| 163 | 163 | bool "rt2800usb - Include support for rt35xx devices (EXPERIMENTAL)" |
| 164 | 164 | default y |
| 165 | − ---help--- | |
| 165 | + help | |
| 166 | 166 | This adds support for rt35xx wireless chipset family to the |
| 167 | 167 | rt2800usb driver. |
| 168 | 168 | Supported chips: RT3572 |
| 169 | 169 | |
| 170 | 170 | config RT2800USB_RT3573 |
| 171 | 171 | bool "rt2800usb - Include support for rt3573 devices (EXPERIMENTAL)" |
| 172 | − ---help--- | |
| 172 | + help | |
| 173 | 173 | This enables support for RT3573 chipset based wireless USB devices |
| 174 | 174 | in the rt2800usb driver. |
| 175 | 175 | |
| 176 | 176 | config RT2800USB_RT53XX |
| 177 | 177 | bool "rt2800usb - Include support for rt53xx devices (EXPERIMENTAL)" |
| 178 | − ---help--- | |
| 178 | + help | |
| 179 | 179 | This adds support for rt53xx wireless chipset family to the |
| 180 | 180 | rt2800usb driver. |
| 181 | 181 | Supported chips: RT5370 |
| 182 | 182 | |
| 183 | 183 | config RT2800USB_RT55XX |
| 184 | 184 | bool "rt2800usb - Include support for rt55xx devices (EXPERIMENTAL)" |
| 185 | − ---help--- | |
| 185 | + help | |
| 186 | 186 | This adds support for rt55xx wireless chipset family to the |
| 187 | 187 | rt2800usb driver. |
| 188 | 188 | Supported chips: RT5572 |
| @@ -190,7 +190,7 @@ config RT2800USB_RT55XX · 1 unmodified line | ||
| 190 | 190 | config RT2800USB_UNKNOWN |
| 191 | 191 | bool "rt2800usb - Include support for unknown (USB) devices" |
| 192 | 192 | default n |
| 193 | − ---help--- | |
| 193 | + help | |
| 194 | 194 | This adds support for rt2800usb devices that are known to |
| 195 | 195 | have a rt28xx family compatible chipset, but for which the exact |
| 196 | 196 | chipset is unknown. |
| @@ -209,7 +209,7 @@ config RT2800SOC · 12 unmodified lines | ||
| 209 | 209 | select RT2X00_LIB_FIRMWARE |
| 210 | 210 | select RT2800_LIB |
| 211 | 211 | select RT2800_LIB_MMIO |
| 212 | − ---help--- | |
| 212 | + help | |
| 213 | 213 | This adds support for Ralink WiSoC devices. |
| 214 | 214 | Supported chips: RT2880, RT3050, RT3052, RT3350, RT3352. |
| 215 | 215 | |
| @@ -256,7 +256,7 @@ config RT2X00_LIB_LEDS · 40 unmodified lines | ||
| 256 | 256 | config RT2X00_LIB_DEBUGFS |
| 257 | 257 | bool "Ralink debugfs support" |
| 258 | 258 | depends on RT2X00_LIB && MAC80211_DEBUGFS |
| 259 | − ---help--- | |
| 259 | + help | |
| 260 | 260 | Enable creation of debugfs files for the rt2x00 drivers. |
| 261 | 261 | These debugfs files support both reading and writing of the |
| 262 | 262 | most important register types of the rt2x00 hardware. |
| @@ -264,7 +264,7 @@ config RT2X00_LIB_DEBUGFS · 1 unmodified line | ||
| 264 | 264 | config RT2X00_DEBUG |
| 265 | 265 | bool "Ralink debug output" |
| 266 | 266 | depends on RT2X00_LIB |
| 267 | − ---help--- | |
| 267 | + help | |
| 268 | 268 | Enable debugging output for all rt2x00 modules |
| 269 | 269 | |
| 270 | 270 | endif |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_REALTEK |
| 3 | 3 | bool "Realtek devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -6,7 +6,7 @@ config RTL8180 · 5 unmodified lines | ||
| 6 | 6 | tristate "Realtek 8180/8185/8187SE PCI support" |
| 7 | 7 | depends on MAC80211 && PCI |
| 8 | 8 | select EEPROM_93CX6 |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This is a driver for RTL8180, RTL8185 and RTL8187SE based cards. |
| 11 | 11 | These are PCI based chips found in cards such as: |
| 12 | 12 | |
| @@ -62,7 +62,7 @@ config RTL8187 · 49 unmodified lines | ||
| 62 | 62 | tristate "Realtek 8187 and 8187B USB support" |
| 63 | 63 | depends on MAC80211 && USB |
| 64 | 64 | select EEPROM_93CX6 |
| 65 | − ---help--- | |
| 65 | + help | |
| 66 | 66 | This is a driver for RTL8187 and RTL8187B based cards. |
| 67 | 67 | These are USB based chips found in devices such as: |
| 68 | 68 | |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | config RTL8XXXU |
| 6 | 6 | tristate "RTL8723AU/RTL8188[CR]U/RTL819[12]CU (mac80211) support" |
| 7 | 7 | depends on MAC80211 && USB |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | This is an alternative driver for various Realtek RTL8XXX |
| 10 | 10 | parts written to utilize the Linux mac80211 stack. |
| 11 | 11 | The driver is known to work with a number of RTL8723AU, |
| @@ -27,7 +27,7 @@ config RTL8XXXU · 15 unmodified lines | ||
| 27 | 27 | config RTL8XXXU_UNTESTED |
| 28 | 28 | bool "Include support for untested Realtek 8xxx USB devices (EXPERIMENTAL)" |
| 29 | 29 | depends on RTL8XXXU |
| 30 | − ---help--- | |
| 30 | + help | |
| 31 | 31 | This option enables detection of Realtek 8723/8188/8191/8192 WiFi |
| 32 | 32 | USB devices which have not been tested directly by the driver |
| 33 | 33 | author or reported to be working by third parties. |
| @@ -3,7 +3,7 @@ menuconfig RTL_CARDS · 2 unmodified lines | ||
| 3 | 3 | tristate "Realtek rtlwifi family of devices" |
| 4 | 4 | depends on MAC80211 && (PCI || USB) |
| 5 | 5 | default y |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | This option will enable support for the Realtek mac80211-based |
| 8 | 8 | wireless drivers. Drivers rtl8192ce, rtl8192cu, rtl8192se, rtl8192de, |
| 9 | 9 | rtl8723ae, rtl8723be, rtl8188ee, rtl8192ee, and rtl8821ae share |
| @@ -17,7 +17,7 @@ config RTL8192CE · 7 unmodified lines | ||
| 17 | 17 | select RTL8192C_COMMON |
| 18 | 18 | select RTLWIFI |
| 19 | 19 | select RTLWIFI_PCI |
| 20 | − ---help--- | |
| 20 | + help | |
| 21 | 21 | This is the driver for Realtek RTL8192CE/RTL8188CE 802.11n PCIe |
| 22 | 22 | wireless network adapters. |
| 23 | 23 | |
| @@ -28,7 +28,7 @@ config RTL8192SE · 4 unmodified lines | ||
| 28 | 28 | depends on PCI |
| 29 | 29 | select RTLWIFI |
| 30 | 30 | select RTLWIFI_PCI |
| 31 | − ---help--- | |
| 31 | + help | |
| 32 | 32 | This is the driver for Realtek RTL8192SE/RTL8191SE 802.11n PCIe |
| 33 | 33 | wireless network adapters. |
| 34 | 34 | |
| @@ -39,7 +39,7 @@ config RTL8192DE · 4 unmodified lines | ||
| 39 | 39 | depends on PCI |
| 40 | 40 | select RTLWIFI |
| 41 | 41 | select RTLWIFI_PCI |
| 42 | − ---help--- | |
| 42 | + help | |
| 43 | 43 | This is the driver for Realtek RTL8192DE/RTL8188DE 802.11n PCIe |
| 44 | 44 | wireless network adapters. |
| 45 | 45 | |
| @@ -52,7 +52,7 @@ config RTL8723AE · 6 unmodified lines | ||
| 52 | 52 | select RTLWIFI_PCI |
| 53 | 53 | select RTL8723_COMMON |
| 54 | 54 | select RTLBTCOEXIST |
| 55 | − ---help--- | |
| 55 | + help | |
| 56 | 56 | This is the driver for Realtek RTL8723AE 802.11n PCIe |
| 57 | 57 | wireless network adapters. |
| 58 | 58 | |
| @@ -65,7 +65,7 @@ config RTL8723BE · 6 unmodified lines | ||
| 65 | 65 | select RTLWIFI_PCI |
| 66 | 66 | select RTL8723_COMMON |
| 67 | 67 | select RTLBTCOEXIST |
| 68 | − ---help--- | |
| 68 | + help | |
| 69 | 69 | This is the driver for Realtek RTL8723BE 802.11n PCIe |
| 70 | 70 | wireless network adapters. |
| 71 | 71 | |
| @@ -76,7 +76,7 @@ config RTL8188EE · 4 unmodified lines | ||
| 76 | 76 | depends on PCI |
| 77 | 77 | select RTLWIFI |
| 78 | 78 | select RTLWIFI_PCI |
| 79 | − ---help--- | |
| 79 | + help | |
| 80 | 80 | This is the driver for Realtek RTL8188EE 802.11n PCIe |
| 81 | 81 | wireless network adapters. |
| 82 | 82 | |
| @@ -88,7 +88,7 @@ config RTL8192EE · 5 unmodified lines | ||
| 88 | 88 | select RTLWIFI |
| 89 | 89 | select RTLWIFI_PCI |
| 90 | 90 | select RTLBTCOEXIST |
| 91 | − ---help--- | |
| 91 | + help | |
| 92 | 92 | This is the driver for Realtek RTL8192EE 802.11n PCIe |
| 93 | 93 | wireless network adapters. |
| 94 | 94 | |
| @@ -100,7 +100,7 @@ config RTL8821AE · 5 unmodified lines | ||
| 100 | 100 | select RTLWIFI |
| 101 | 101 | select RTLWIFI_PCI |
| 102 | 102 | select RTLBTCOEXIST |
| 103 | − ---help--- | |
| 103 | + help | |
| 104 | 104 | This is the driver for Realtek RTL8821AE/RTL8812AE 802.11ac PCIe |
| 105 | 105 | wireless network adapters. |
| 106 | 106 | |
| @@ -112,7 +112,7 @@ config RTL8192CU · 5 unmodified lines | ||
| 112 | 112 | select RTLWIFI |
| 113 | 113 | select RTLWIFI_USB |
| 114 | 114 | select RTL8192C_COMMON |
| 115 | − ---help--- | |
| 115 | + help | |
| 116 | 116 | This is the driver for Realtek RTL8192CU/RTL8188CU 802.11n USB |
| 117 | 117 | wireless network adapters. |
| 118 | 118 | |
| @@ -132,7 +132,7 @@ config RTLWIFI_DEBUG · 13 unmodified lines | ||
| 132 | 132 | bool "Debugging output for rtlwifi driver family" |
| 133 | 133 | depends on RTLWIFI |
| 134 | 134 | default y |
| 135 | − ---help--- | |
| 135 | + help | |
| 136 | 136 | To use the module option that sets the dynamic-debugging level for, |
| 137 | 137 | the front-end driver, this parameter must be "Y". For memory-limited |
| 138 | 138 | systems, choose "N". If in doubt, choose "Y". |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_RSI |
| 3 | 3 | bool "Redpine Signals Inc devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -16,7 +16,7 @@ config RSI_91X · 7 unmodified lines | ||
| 16 | 16 | tristate "Redpine Signals Inc 91x WLAN driver support" |
| 17 | 17 | select BT_HCIRSI if RSI_COEX |
| 18 | 18 | depends on MAC80211 |
| 19 | − ---help--- | |
| 19 | + help | |
| 20 | 20 | This option enabes support for RSI 1x1 devices. |
| 21 | 21 | Select M (recommended), if you have a RSI 1x1 wireless module. |
| 22 | 22 | |
| @@ -24,7 +24,7 @@ config RSI_DEBUGFS · 1 unmodified line | ||
| 24 | 24 | bool "Redpine Signals Inc debug support" |
| 25 | 25 | depends on RSI_91X |
| 26 | 26 | default y |
| 27 | − ---help--- | |
| 27 | + help | |
| 28 | 28 | Say Y, if you would like to enable debug support. This option |
| 29 | 29 | creates debugfs entries |
| 30 | 30 | |
| @@ -32,7 +32,7 @@ config RSI_SDIO · 1 unmodified line | ||
| 32 | 32 | tristate "Redpine Signals SDIO bus support" |
| 33 | 33 | depends on MMC && RSI_91X |
| 34 | 34 | default m |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | This option enables the SDIO bus support in rsi drivers. |
| 37 | 37 | Select M (recommended), if you have a RSI 1x1 wireless module. |
| 38 | 38 | |
| @@ -40,7 +40,7 @@ config RSI_USB · 1 unmodified line | ||
| 40 | 40 | tristate "Redpine Signals USB bus support" |
| 41 | 41 | depends on USB && RSI_91X |
| 42 | 42 | default m |
| 43 | − ---help--- | |
| 43 | + help | |
| 44 | 44 | This option enables the USB bus support in rsi drivers. |
| 45 | 45 | Select M (recommended), if you have a RSI 1x1 wireless module. |
| 46 | 46 | |
| @@ -49,7 +49,7 @@ config RSI_COEX · 2 unmodified lines | ||
| 49 | 49 | depends on BT && RSI_91X |
| 50 | 50 | depends on !(BT=m && RSI_91X=y) |
| 51 | 51 | default y |
| 52 | − ---help--- | |
| 52 | + help | |
| 53 | 53 | This option enables the WLAN BT coex support in rsi drivers. |
| 54 | 54 | Select M (recommended), if you have want to use this feature |
| 55 | 55 | and you have RS9113 module. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_ST |
| 3 | 3 | bool "STMicroelectronics devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_TI |
| 3 | 3 | bool "Texas Instrument devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -22,7 +22,7 @@ config WILINK_PLATFORM_DATA · 13 unmodified lines | ||
| 22 | 22 | bool "TI WiLink platform data" |
| 23 | 23 | depends on WLCORE_SDIO || WL1251_SDIO |
| 24 | 24 | default y |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | Small platform data bit needed to pass data to the sdio modules. |
| 27 | 27 | |
| 28 | 28 | |
| @@ -4,7 +4,7 @@ config WL1251 · 3 unmodified lines | ||
| 4 | 4 | depends on MAC80211 |
| 5 | 5 | select FW_LOADER |
| 6 | 6 | select CRC7 |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | This will enable TI wl1251 driver support. The drivers make |
| 9 | 9 | use of the mac80211 stack. |
| 10 | 10 | |
| @@ -14,7 +14,7 @@ config WL1251 · 3 unmodified lines | ||
| 14 | 14 | config WL1251_SPI |
| 15 | 15 | tristate "TI wl1251 SPI support" |
| 16 | 16 | depends on WL1251 && SPI_MASTER |
| 17 | − ---help--- | |
| 17 | + help | |
| 18 | 18 | This module adds support for the SPI interface of adapters using |
| 19 | 19 | TI wl1251 chipset. Select this if your platform is using |
| 20 | 20 | the SPI bus. |
| @@ -25,7 +25,7 @@ config WL1251_SPI · 4 unmodified lines | ||
| 25 | 25 | config WL1251_SDIO |
| 26 | 26 | tristate "TI wl1251 SDIO support" |
| 27 | 27 | depends on WL1251 && MMC |
| 28 | − ---help--- | |
| 28 | + help | |
| 29 | 29 | This module adds support for the SDIO interface of adapters using |
| 30 | 30 | TI wl1251 chipset. Select this if your platform is using |
| 31 | 31 | the SDIO bus. |
| @@ -3,7 +3,7 @@ config WL12XX · 2 unmodified lines | ||
| 3 | 3 | tristate "TI wl12xx support" |
| 4 | 4 | depends on MAC80211 |
| 5 | 5 | select WLCORE |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | This module adds support for wireless adapters based on TI wl1271, |
| 8 | 8 | wl1273, wl1281 and wl1283 chipsets. This module does *not* include |
| 9 | 9 | support for wl1251. For wl1251 support, use the separate homonymous |
| @@ -3,6 +3,6 @@ config WL18XX · 2 unmodified lines | ||
| 3 | 3 | tristate "TI wl18xx support" |
| 4 | 4 | depends on MAC80211 |
| 5 | 5 | select WLCORE |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | This module adds support for wireless adapters based on TI |
| 8 | 8 | WiLink 8 chipsets. |
| @@ -3,7 +3,7 @@ config WLCORE · 2 unmodified lines | ||
| 3 | 3 | tristate "TI wlcore support" |
| 4 | 4 | depends on MAC80211 |
| 5 | 5 | select FW_LOADER |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | This module contains the main code for TI WLAN chips. It abstracts |
| 8 | 8 | hardware-specific differences among different chipset families. |
| 9 | 9 | Each chipset family needs to implement its own lower-level module |
| @@ -16,7 +16,7 @@ config WLCORE_SPI · 6 unmodified lines | ||
| 16 | 16 | tristate "TI wlcore SPI support" |
| 17 | 17 | depends on WLCORE && SPI_MASTER && OF |
| 18 | 18 | select CRC7 |
| 19 | − ---help--- | |
| 19 | + help | |
| 20 | 20 | This module adds support for the SPI interface of adapters using |
| 21 | 21 | TI WLAN chipsets. Select this if your platform is using |
| 22 | 22 | the SPI bus. |
| @@ -27,7 +27,7 @@ config WLCORE_SPI · 4 unmodified lines | ||
| 27 | 27 | config WLCORE_SDIO |
| 28 | 28 | tristate "TI wlcore SDIO support" |
| 29 | 29 | depends on WLCORE && MMC |
| 30 | − ---help--- | |
| 30 | + help | |
| 31 | 31 | This module adds support for the SDIO interface of adapters using |
| 32 | 32 | TI WLAN chipsets. Select this if your platform is using |
| 33 | 33 | the SDIO bus. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config WLAN_VENDOR_ZYDAS |
| 3 | 3 | bool "ZyDAS devices" |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | If you have a wireless card belonging to this class, say Y. |
| 7 | 7 | |
| 8 | 8 | Note that the answer to this question doesn't directly affect the |
| @@ -18,7 +18,7 @@ config USB_ZD1201 · 9 unmodified lines | ||
| 18 | 18 | select WIRELESS_EXT |
| 19 | 19 | select WEXT_PRIV |
| 20 | 20 | select FW_LOADER |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | Say Y if you want to use wireless LAN adapters based on the ZyDAS |
| 23 | 23 | ZD1201 chip. |
| 24 | 24 | |
| @@ -3,7 +3,7 @@ config ZD1211RW · 2 unmodified lines | ||
| 3 | 3 | tristate "ZyDAS ZD1211/ZD1211B USB-wireless support" |
| 4 | 4 | depends on USB && MAC80211 |
| 5 | 5 | select FW_LOADER |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | This is a driver for the ZyDAS ZD1211/ZD1211B wireless |
| 8 | 8 | chip, present in many USB-wireless adapters. |
| 9 | 9 | |
| @@ -13,7 +13,7 @@ config ZD1211RW · 3 unmodified lines | ||
| 13 | 13 | config ZD1211RW_DEBUG |
| 14 | 14 | bool "ZyDAS ZD1211 debugging" |
| 15 | 15 | depends on ZD1211RW |
| 16 | − ---help--- | |
| 16 | + help | |
| 17 | 17 | ZD1211 debugging messages. Choosing Y will result in additional debug |
| 18 | 18 | messages being saved to your kernel logs, which may help debug any |
| 19 | 19 | problems. |
| @@ -4,7 +4,7 @@ config NFC_FDP · 3 unmodified lines | ||
| 4 | 4 | depends on NFC_NCI |
| 5 | 5 | select CRC_CCITT |
| 6 | 6 | default n |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | Intel Fields Peak NFC controller core driver. |
| 9 | 9 | This is a driver based on the NCI NFC kernel layers. |
| 10 | 10 | |
| @@ -15,7 +15,7 @@ config NFC_FDP · 4 unmodified lines | ||
| 15 | 15 | config NFC_FDP_I2C |
| 16 | 16 | tristate "NFC FDP i2c support" |
| 17 | 17 | depends on NFC_FDP && I2C |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | This module adds support for the Intel Fields Peak NFC controller |
| 20 | 20 | i2c interface. |
| 21 | 21 | Select this if your platform is using the i2c bus. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config NFC_MICROREAD |
| 3 | 3 | tristate |
| 4 | 4 | select CRC_CCITT |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This module contains the main code for Inside Secure microread |
| 7 | 7 | NFC chipsets. It implements the chipset HCI logic and hooks into |
| 8 | 8 | the NFC kernel APIs. Physical layers will register against it. |
| @@ -11,7 +11,7 @@ config NFC_MICROREAD_I2C · 2 unmodified lines | ||
| 11 | 11 | tristate "Inside Secure Microread device support (I2C)" |
| 12 | 12 | depends on NFC_HCI && I2C && NFC_SHDLC |
| 13 | 13 | select NFC_MICROREAD |
| 14 | − ---help--- | |
| 14 | + help | |
| 15 | 15 | This module adds support for the i2c interface of adapters using |
| 16 | 16 | Inside microread chipsets. Select this if your platform is using |
| 17 | 17 | the i2c bus. |
| @@ -23,7 +23,7 @@ config NFC_MICROREAD_MEI · 5 unmodified lines | ||
| 23 | 23 | tristate "Inside Secure Microread device support (MEI)" |
| 24 | 24 | depends on NFC_HCI && NFC_MEI_PHY |
| 25 | 25 | select NFC_MICROREAD |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | This module adds support for the mei interface of adapters using |
| 28 | 28 | Inside microread chipsets. Select this if your microread chipset |
| 29 | 29 | is handled by Intel's Management Engine Interface on your platform. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config NFC_NXP_NCI |
| 3 | 3 | tristate "NXP-NCI NFC driver" |
| 4 | 4 | depends on NFC_NCI |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | Generic core driver for NXP NCI chips such as the NPC100 (PN547), |
| 7 | 7 | NPC300 (PN548) or PN7150 families. |
| 8 | 8 | This is a driver based on the NCI NFC kernel layers and |
| @@ -15,7 +15,7 @@ config NFC_NXP_NCI · 6 unmodified lines | ||
| 15 | 15 | config NFC_NXP_NCI_I2C |
| 16 | 16 | tristate "NXP-NCI I2C support" |
| 17 | 17 | depends on NFC_NXP_NCI && I2C |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | This module adds support for an I2C interface to the NXP NCI |
| 20 | 20 | chips. |
| 21 | 21 | Select this if your platform is using the I2C bus. |
| @@ -9,7 +9,7 @@ config NFC_PN533_USB · 8 unmodified lines | ||
| 9 | 9 | tristate "NFC PN533 device support (USB)" |
| 10 | 10 | depends on USB |
| 11 | 11 | select NFC_PN533 |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | This module adds support for the NXP pn533 USB interface. |
| 14 | 14 | Select this if your platform is using the USB bus. |
| 15 | 15 | |
| @@ -20,7 +20,7 @@ config NFC_PN533_I2C · 4 unmodified lines | ||
| 20 | 20 | tristate "NFC PN533 device support (I2C)" |
| 21 | 21 | depends on I2C |
| 22 | 22 | select NFC_PN533 |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | This module adds support for the NXP pn533 I2C interface. |
| 25 | 25 | Select this if your platform is using the I2C bus. |
| 26 | 26 | |
| @@ -31,7 +31,7 @@ config NFC_PN532_UART · 4 unmodified lines | ||
| 31 | 31 | tristate "NFC PN532 device support (UART)" |
| 32 | 32 | depends on SERIAL_DEV_BUS |
| 33 | 33 | select NFC_PN533 |
| 34 | − ---help--- | |
| 34 | + help | |
| 35 | 35 | This module adds support for the NXP pn532 UART interface. |
| 36 | 36 | Select this if your platform is using the UART bus. |
| 37 | 37 | |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config NFC_PN544 |
| 3 | 3 | tristate |
| 4 | 4 | select CRC_CCITT |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | NXP PN544 core driver. |
| 7 | 7 | This is a driver based on the HCI NFC kernel layers and |
| 8 | 8 | will thus not work with NXP libnfc library. |
| @@ -11,7 +11,7 @@ config NFC_PN544_I2C · 2 unmodified lines | ||
| 11 | 11 | tristate "NXP PN544 device support (I2C)" |
| 12 | 12 | depends on NFC_HCI && I2C && NFC_SHDLC |
| 13 | 13 | select NFC_PN544 |
| 14 | − ---help--- | |
| 14 | + help | |
| 15 | 15 | This module adds support for the NXP pn544 i2c interface. |
| 16 | 16 | Select this if your platform is using the i2c bus. |
| 17 | 17 | |
| @@ -22,7 +22,7 @@ config NFC_PN544_MEI · 4 unmodified lines | ||
| 22 | 22 | tristate "NXP PN544 device support (MEI)" |
| 23 | 23 | depends on NFC_HCI && NFC_MEI_PHY |
| 24 | 24 | select NFC_PN544 |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | This module adds support for the mei interface of adapters using |
| 27 | 27 | NXP pn544 chipsets. Select this if your pn544 chipset |
| 28 | 28 | is handled by Intel's Management Engine Interface on your platform. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config NFC_S3FWRN5 |
| 3 | 3 | tristate |
| 4 | 4 | select CRYPTO |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | Core driver for Samsung S3FWRN5 NFC chip. Contains core utilities |
| 7 | 7 | of chip. It's intended to be used by PHYs to avoid duplicating lots |
| 8 | 8 | of common code. |
| @@ -12,7 +12,7 @@ config NFC_S3FWRN5_I2C · 3 unmodified lines | ||
| 12 | 12 | depends on NFC_NCI && I2C |
| 13 | 13 | select NFC_S3FWRN5 |
| 14 | 14 | default n |
| 15 | − ---help--- | |
| 15 | + help | |
| 16 | 16 | This module adds support for an I2C interface to the S3FWRN5 chip. |
| 17 | 17 | Select this if your platform is using the I2C bus. |
| 18 | 18 | |
| @@ -1,7 +1,7 @@ | ||
| 1 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | 2 | config NFC_ST_NCI |
| 3 | 3 | tristate |
| 4 | − ---help--- | |
| 4 | + help | |
| 5 | 5 | STMicroelectronics NFC NCI chips core driver. It implements the chipset |
| 6 | 6 | NCI logic and hooks into the NFC kernel APIs. Physical layers will |
| 7 | 7 | register against it. |
| @@ -10,7 +10,7 @@ config NFC_ST_NCI_I2C · 2 unmodified lines | ||
| 10 | 10 | tristate "STMicroelectronics ST NCI NFC driver (I2C)" |
| 11 | 11 | depends on NFC_NCI && I2C |
| 12 | 12 | select NFC_ST_NCI |
| 13 | − ---help--- | |
| 13 | + help | |
| 14 | 14 | This module adds support for an I2C interface to the |
| 15 | 15 | STMicroelectronics NFC NCI chips family. |
| 16 | 16 | Select this if your platform is using the i2c bus. |
| @@ -22,7 +22,7 @@ config NFC_ST_NCI_SPI · 5 unmodified lines | ||
| 22 | 22 | tristate "STMicroelectronics ST NCI NFC driver (SPI)" |
| 23 | 23 | depends on NFC_NCI && SPI |
| 24 | 24 | select NFC_ST_NCI |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | This module adds support for an SPI interface to the |
| 27 | 27 | STMicroelectronics NFC NCI chips family. |
| 28 | 28 | Select this if your platform is using the spi bus. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config NFC_ST21NFCA |
| 3 | 3 | tristate |
| 4 | 4 | select CRC_CCITT |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | STMicroelectronics ST21NFCA core driver. It implements the chipset |
| 7 | 7 | HCI logic and hooks into the NFC kernel APIs. Physical layers will |
| 8 | 8 | register against it. |
| @@ -11,7 +11,7 @@ config NFC_ST21NFCA_I2C · 2 unmodified lines | ||
| 11 | 11 | tristate "STMicroelectronics ST21NFCA NFC driver (I2C)" |
| 12 | 12 | depends on NFC_HCI && I2C && NFC_SHDLC |
| 13 | 13 | select NFC_ST21NFCA |
| 14 | − ---help--- | |
| 14 | + help | |
| 15 | 15 | This module adds support for the STMicroelectronics st21nfca i2c interface. |
| 16 | 16 | Select this if your platform is using the i2c bus. |
| 17 | 17 | |
| @@ -7,7 +7,7 @@ config BLK_DEV_NVME · 6 unmodified lines | ||
| 7 | 7 | tristate "NVM Express block device" |
| 8 | 8 | depends on PCI && BLOCK |
| 9 | 9 | select NVME_CORE |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | The NVM Express driver is for solid state drives directly |
| 12 | 12 | connected to the PCI or PCI Express bus. If you know you |
| 13 | 13 | don't have one of these, it is safe to answer N. |
| @@ -18,7 +18,7 @@ config BLK_DEV_NVME · 4 unmodified lines | ||
| 18 | 18 | config NVME_MULTIPATH |
| 19 | 19 | bool "NVMe multipath support" |
| 20 | 20 | depends on NVME_CORE |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | This option enables support for multipath access to NVMe |
| 23 | 23 | subsystems. If this option is enabled only a single |
| 24 | 24 | /dev/nvmeXnY device will show up for each NVMe namespaces, |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config PM_OPP |
| 3 | 3 | bool |
| 4 | 4 | select SRCU |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | SOCs have a standard set of tuples consisting of frequency and |
| 7 | 7 | voltage pairs that the device will support per voltage domain. This |
| 8 | 8 | is called Operating Performance Point or OPP. The actual definitions |
| @@ -15,7 +15,7 @@ config ARCH_MIGHT_HAVE_PC_PARPORT · 14 unmodified lines | ||
| 15 | 15 | menuconfig PARPORT |
| 16 | 16 | tristate "Parallel port support" |
| 17 | 17 | depends on HAS_IOMEM |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | If you want to use devices connected to your machine's parallel port |
| 20 | 20 | (the connector at the computer with 25 holes), e.g. printer, ZIP |
| 21 | 21 | drive, PLIP link (Parallel Line Internet Protocol is mainly used to |
| @@ -248,7 +248,7 @@ config PCIE_TANGO_SMP8759 · 247 unmodified lines | ||
| 248 | 248 | config VMD |
| 249 | 249 | depends on PCI_MSI && X86_64 && SRCU |
| 250 | 250 | tristate "Intel Volume Management Device Driver" |
| 251 | − ---help--- | |
| 251 | + help | |
| 252 | 252 | Adds support for the Intel Volume Management Device (VMD). VMD is a |
| 253 | 253 | secondary PCI host bridge that allows PCI Express root ports, |
| 254 | 254 | and devices attached to them, to be removed from the default |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | menuconfig HOTPLUG_PCI |
| 7 | 7 | bool "Support for PCI Hotplug" |
| 8 | 8 | depends on PCI && SYSFS |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Say Y here if you have a motherboard with a PCI Hotplug controller. |
| 11 | 11 | This allows you to add and remove PCI cards while the machine is |
| 12 | 12 | powered up and running. |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | menuconfig PCCARD |
| 7 | 7 | tristate "PCCard (PCMCIA/CardBus) support" |
| 8 | 8 | depends on !UML |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Say Y here if you want to attach PCMCIA- or PC-cards to your Linux |
| 11 | 11 | computer. These are credit-card size devices such as network cards, |
| 12 | 12 | modems or hard drives often used with laptops computers. There are |
| @@ -22,7 +22,7 @@ config PCMCIA · 9 unmodified lines | ||
| 22 | 22 | tristate "16-bit PCMCIA support" |
| 23 | 23 | select CRC32 |
| 24 | 24 | default y |
| 25 | − ---help--- | |
| 25 | + help | |
| 26 | 26 | This option enables support for 16-bit PCMCIA cards. Most older |
| 27 | 27 | PC-cards are such 16-bit PCMCIA cards, so unless you know you're |
| 28 | 28 | only using 32-bit CardBus cards, say Y or M here. |
| @@ -54,7 +54,7 @@ config CARDBUS · 25 unmodified lines | ||
| 54 | 54 | bool "32-bit CardBus support" |
| 55 | 55 | depends on PCI |
| 56 | 56 | default y |
| 57 | − ---help--- | |
| 57 | + help | |
| 58 | 58 | CardBus is a bus mastering architecture for PC-cards, which allows |
| 59 | 59 | for 32 bit PC-cards (the original PCMCIA standard specifies only |
| 60 | 60 | a 16 bit wide bus). Many newer PC-cards are actually CardBus cards. |
| @@ -75,7 +75,7 @@ config YENTA · 14 unmodified lines | ||
| 75 | 75 | depends on PCI |
| 76 | 76 | select CARDBUS if !EXPERT |
| 77 | 77 | select PCCARD_NONSTATIC if PCMCIA != n |
| 78 | − ---help--- | |
| 78 | + help | |
| 79 | 79 | This option enables support for CardBus host bridges. Virtually |
| 80 | 80 | all modern PCMCIA bridges are CardBus compatible. A "bridge" is |
| 81 | 81 | the hardware inside your computer that PCMCIA cards are plugged |
| @@ -16,7 +16,7 @@ config MFD_CROS_EC · 15 unmodified lines | ||
| 16 | 16 | menuconfig CHROME_PLATFORMS |
| 17 | 17 | bool "Platform support for Chrome hardware" |
| 18 | 18 | depends on X86 || ARM || ARM64 || COMPILE_TEST |
| 19 | − ---help--- | |
| 19 | + help | |
| 20 | 20 | Say Y here to get to see options for platform support for |
| 21 | 21 | various Chromebooks and Chromeboxes. This option alone does |
| 22 | 22 | not add any kernel code. |
| @@ -28,7 +28,7 @@ if CHROME_PLATFORMS · 5 unmodified lines | ||
| 28 | 28 | config CHROMEOS_LAPTOP |
| 29 | 29 | tristate "Chrome OS Laptop" |
| 30 | 30 | depends on I2C && DMI && X86 |
| 31 | − ---help--- | |
| 31 | + help | |
| 32 | 32 | This driver instantiates i2c and smbus devices such as |
| 33 | 33 | light sensors and touchpads. |
| 34 | 34 | |
| @@ -38,7 +38,7 @@ config CHROMEOS_LAPTOP · 3 unmodified lines | ||
| 38 | 38 | config CHROMEOS_PSTORE |
| 39 | 39 | tristate "Chrome OS pstore support" |
| 40 | 40 | depends on X86 |
| 41 | − ---help--- | |
| 41 | + help | |
| 42 | 42 | This module instantiates the persistent storage on x86 ChromeOS |
| 43 | 43 | devices. It can be used to store away console logs and crash |
| 44 | 44 | information across reboots. |
| @@ -112,7 +112,7 @@ config CROS_EC_SPI · 67 unmodified lines | ||
| 112 | 112 | tristate "ChromeOS Embedded Controller (SPI)" |
| 113 | 113 | depends on CROS_EC && SPI |
| 114 | 114 | |
| 115 | − ---help--- | |
| 115 | + help | |
| 116 | 116 | If you say Y here, you get support for talking to the ChromeOS EC |
| 117 | 117 | through a SPI bus, using a byte-level protocol. Since the EC's |
| 118 | 118 | response time cannot be guaranteed, we support ignoring |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | menuconfig MELLANOX_PLATFORM |
| 7 | 7 | bool "Platform support for Mellanox hardware" |
| 8 | 8 | depends on X86 || ARM || ARM64 || COMPILE_TEST |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Say Y here to get to see options for platform support for |
| 11 | 11 | Mellanox systems. This option alone does not add any kernel code. |
| 12 | 12 | |
| @@ -19,7 +19,7 @@ config MLXREG_HOTPLUG · 6 unmodified lines | ||
| 19 | 19 | depends on REGMAP |
| 20 | 20 | depends on HWMON |
| 21 | 21 | depends on I2C |
| 22 | − ---help--- | |
| 22 | + help | |
| 23 | 23 | This driver handles hot-plug events for the power suppliers, power |
| 24 | 24 | cables and fans on the wide range Mellanox IB and Ethernet systems. |
| 25 | 25 | |
| @@ -7,7 +7,7 @@ menuconfig X86_PLATFORM_DEVICES · 6 unmodified lines | ||
| 7 | 7 | bool "X86 Platform Specific Device Drivers" |
| 8 | 8 | default y |
| 9 | 9 | depends on X86 |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Say Y here to get to see options for device drivers for various |
| 12 | 12 | x86 platforms, including vendor-specific laptop extension drivers. |
| 13 | 13 | This option alone does not add any kernel code. |
| @@ -41,7 +41,7 @@ config WMI_BMOF · 27 unmodified lines | ||
| 41 | 41 | tristate "WMI embedded Binary MOF driver" |
| 42 | 42 | depends on ACPI_WMI |
| 43 | 43 | default ACPI_WMI |
| 44 | − ---help--- | |
| 44 | + help | |
| 45 | 45 | Say Y here if you want to be able to read a firmware-embedded |
| 46 | 46 | WMI Binary MOF data. Using this requires userspace tools and may be |
| 47 | 47 | rather tedious. |
| @@ -55,7 +55,7 @@ config ALIENWARE_WMI · 7 unmodified lines | ||
| 55 | 55 | depends on LEDS_CLASS |
| 56 | 56 | depends on NEW_LEDS |
| 57 | 57 | depends on ACPI_WMI |
| 58 | − ---help--- | |
| 58 | + help | |
| 59 | 59 | This is a driver for controlling Alienware BIOS driven |
| 60 | 60 | features. It exposes an interface for controlling the AlienFX |
| 61 | 61 | zones on Alienware machines that don't contain a dedicated AlienFX |
| @@ -91,7 +91,7 @@ config INTEL_WMI_SBL_FW_UPDATE · 29 unmodified lines | ||
| 91 | 91 | config INTEL_WMI_THUNDERBOLT |
| 92 | 92 | tristate "Intel WMI thunderbolt force power driver" |
| 93 | 93 | depends on ACPI_WMI |
| 94 | − ---help--- | |
| 94 | + help | |
| 95 | 95 | Say Y here if you want to be able to use the WMI interface on select |
| 96 | 96 | systems to force the power control of Intel Thunderbolt controllers. |
| 97 | 97 | This is useful for updating the firmware when devices are not plugged |
| @@ -103,7 +103,7 @@ config INTEL_WMI_THUNDERBOLT · 5 unmodified lines | ||
| 103 | 103 | config MXM_WMI |
| 104 | 104 | tristate "WMI support for MXM Laptop Graphics" |
| 105 | 105 | depends on ACPI_WMI |
| 106 | − ---help--- | |
| 106 | + help | |
| 107 | 107 | MXM is a standard for laptop graphics cards, the WMI interface |
| 108 | 108 | is required for switchable nvidia graphics machines |
| 109 | 109 | |
| @@ -128,7 +128,7 @@ config ACERHDF · 18 unmodified lines | ||
| 128 | 128 | tristate "Acer Aspire One temperature and fan driver" |
| 129 | 129 | depends on ACPI && THERMAL |
| 130 | 130 | select THERMAL_GOV_BANG_BANG |
| 131 | − ---help--- | |
| 131 | + help | |
| 132 | 132 | This is a driver for Acer Aspire One netbooks. It allows to access |
| 133 | 133 | the temperature sensor and to control the fan. |
| 134 | 134 | |
| @@ -149,7 +149,7 @@ config ACER_WIRELESS · 14 unmodified lines | ||
| 149 | 149 | tristate "Acer Wireless Radio Control Driver" |
| 150 | 150 | depends on ACPI |
| 151 | 151 | depends on INPUT |
| 152 | − ---help--- | |
| 152 | + help | |
| 153 | 153 | The Acer Wireless Radio Control handles the airplane mode hotkey |
| 154 | 154 | present on new Acer laptops. |
| 155 | 155 | |
| @@ -172,7 +172,7 @@ config ACER_WMI · 16 unmodified lines | ||
| 172 | 172 | select INPUT_SPARSEKMAP |
| 173 | 173 | # Acer WMI depends on ACPI_VIDEO when ACPI is enabled |
| 174 | 174 | select ACPI_VIDEO if ACPI |
| 175 | − ---help--- | |
| 175 | + help | |
| 176 | 176 | This is a driver for newer Acer (and Wistron) laptops. It adds |
| 177 | 177 | wireless radio and bluetooth control, and on some laptops, |
| 178 | 178 | exposes the mail LED and LCD backlight. |
| @@ -187,7 +187,7 @@ config APPLE_GMUX · 8 unmodified lines | ||
| 187 | 187 | depends on BACKLIGHT_CLASS_DEVICE |
| 188 | 188 | depends on BACKLIGHT_APPLE=n || BACKLIGHT_APPLE |
| 189 | 189 | depends on ACPI_VIDEO=n || ACPI_VIDEO |
| 190 | − ---help--- | |
| 190 | + help | |
| 191 | 191 | This driver provides support for the gmux device found on many |
| 192 | 192 | Apple laptops, which controls the display mux for the hybrid |
| 193 | 193 | graphics as well as the backlight. Currently only backlight |
| @@ -203,7 +203,7 @@ config ASUS_LAPTOP · 9 unmodified lines | ||
| 203 | 203 | depends on RFKILL || RFKILL = n |
| 204 | 204 | depends on ACPI_VIDEO || ACPI_VIDEO = n |
| 205 | 205 | select INPUT_SPARSEKMAP |
| 206 | − ---help--- | |
| 206 | + help | |
| 207 | 207 | This is a driver for Asus laptops, Lenovo SL and the Pegatron |
| 208 | 208 | Lucid tablet. It may also support some MEDION, JVC or VICTOR |
| 209 | 209 | laptops. It makes all the extra buttons generate standard |
| @@ -223,7 +223,7 @@ config ASUS_WIRELESS · 13 unmodified lines | ||
| 223 | 223 | depends on INPUT |
| 224 | 224 | select NEW_LEDS |
| 225 | 225 | select LEDS_CLASS |
| 226 | − ---help--- | |
| 226 | + help | |
| 227 | 227 | The Asus Wireless Radio Control handles the airplane mode hotkey |
| 228 | 228 | present on some Asus laptops. |
| 229 | 229 | |
| @@ -246,7 +246,7 @@ config ASUS_WMI · 16 unmodified lines | ||
| 246 | 246 | select INPUT_SPARSEKMAP |
| 247 | 247 | select LEDS_CLASS |
| 248 | 248 | select NEW_LEDS |
| 249 | − ---help--- | |
| 249 | + help | |
| 250 | 250 | Say Y here if you have a WMI aware Asus laptop (like Eee PCs or new |
| 251 | 251 | Asus Notebooks). |
| 252 | 252 | |
| @@ -257,7 +257,7 @@ config ASUS_NB_WMI · 4 unmodified lines | ||
| 257 | 257 | tristate "Asus Notebook WMI Driver" |
| 258 | 258 | depends on ASUS_WMI |
| 259 | 259 | depends on SERIO_I8042 || SERIO_I8042 = n |
| 260 | − ---help--- | |
| 260 | + help | |
| 261 | 261 | This is a driver for newer Asus notebooks. It adds extra features |
| 262 | 262 | like wireless radio and bluetooth control, leds, hotkeys, backlight... |
| 263 | 263 | |
| @@ -279,7 +279,7 @@ config EEEPC_LAPTOP · 15 unmodified lines | ||
| 279 | 279 | select LEDS_CLASS |
| 280 | 280 | select NEW_LEDS |
| 281 | 281 | select INPUT_SPARSEKMAP |
| 282 | − ---help--- | |
| 282 | + help | |
| 283 | 283 | This driver supports the Fn-Fx keys on Eee PC laptops. |
| 284 | 284 | |
| 285 | 285 | It also gives access to some extra laptop functionalities like |
| @@ -292,7 +292,7 @@ config EEEPC_LAPTOP · 6 unmodified lines | ||
| 292 | 292 | config EEEPC_WMI |
| 293 | 293 | tristate "Eee PC WMI Driver" |
| 294 | 294 | depends on ASUS_WMI |
| 295 | − ---help--- | |
| 295 | + help | |
| 296 | 296 | This is a driver for newer Eee PC laptops. It adds extra features |
| 297 | 297 | like wireless radio and bluetooth control, leds, hotkeys, backlight... |
| 298 | 298 | |
| @@ -327,7 +327,7 @@ config DELL_SMBIOS · 28 unmodified lines | ||
| 327 | 327 | tristate "Dell SMBIOS driver" |
| 328 | 328 | depends on DCDBAS || DCDBAS=n |
| 329 | 329 | depends on ACPI_WMI || ACPI_WMI=n |
| 330 | − ---help--- | |
| 330 | + help | |
| 331 | 331 | This provides support for the Dell SMBIOS calling interface. |
| 332 | 332 | If you have a Dell computer you should enable this option. |
| 333 | 333 | |
| @@ -339,7 +339,7 @@ config DELL_SMBIOS_WMI · 5 unmodified lines | ||
| 339 | 339 | depends on ACPI_WMI |
| 340 | 340 | select DELL_WMI_DESCRIPTOR |
| 341 | 341 | depends on DELL_SMBIOS |
| 342 | − ---help--- | |
| 342 | + help | |
| 343 | 343 | This provides an implementation for the Dell SMBIOS calling interface |
| 344 | 344 | communicated over ACPI-WMI. |
| 345 | 345 | |
| @@ -352,7 +352,7 @@ config DELL_SMBIOS_SMM · 6 unmodified lines | ||
| 352 | 352 | default y |
| 353 | 353 | depends on DCDBAS |
| 354 | 354 | depends on DELL_SMBIOS |
| 355 | − ---help--- | |
| 355 | + help | |
| 356 | 356 | This provides an implementation for the Dell SMBIOS calling interface |
| 357 | 357 | communicated over SMI/SMM. |
| 358 | 358 | |
| @@ -373,7 +373,7 @@ config DELL_LAPTOP · 14 unmodified lines | ||
| 373 | 373 | select NEW_LEDS |
| 374 | 374 | select LEDS_TRIGGERS |
| 375 | 375 | select LEDS_TRIGGER_AUDIO |
| 376 | − ---help--- | |
| 376 | + help | |
| 377 | 377 | This driver adds support for rfkill and backlight control to Dell |
| 378 | 378 | laptops (except for some models covered by the Compal driver). |
| 379 | 379 | |
| @@ -382,7 +382,7 @@ config DELL_RBTN · 2 unmodified lines | ||
| 382 | 382 | depends on ACPI |
| 383 | 383 | depends on INPUT |
| 384 | 384 | depends on RFKILL |
| 385 | − ---help--- | |
| 385 | + help | |
| 386 | 386 | Say Y here if you want to support Dell Airplane Mode Switch ACPI |
| 387 | 387 | device on Dell laptops. Sometimes it has names: DELLABCE or DELRBTN. |
| 388 | 388 | This driver register rfkill device or input hotkey device depending |
| @@ -408,7 +408,7 @@ config DELL_RBU · 19 unmodified lines | ||
| 408 | 408 | config DELL_SMO8800 |
| 409 | 409 | tristate "Dell Latitude freefall driver (ACPI SMO88XX)" |
| 410 | 410 | depends on ACPI |
| 411 | − ---help--- | |
| 411 | + help | |
| 412 | 412 | Say Y here if you want to support SMO88XX freefall devices |
| 413 | 413 | on Dell Latitude laptops. |
| 414 | 414 | |
| @@ -424,7 +424,7 @@ config DELL_WMI · 9 unmodified lines | ||
| 424 | 424 | depends on DELL_SMBIOS |
| 425 | 425 | select DELL_WMI_DESCRIPTOR |
| 426 | 426 | select INPUT_SPARSEKMAP |
| 427 | − ---help--- | |
| 427 | + help | |
| 428 | 428 | Say Y here if you want to support WMI-based hotkeys on Dell laptops. |
| 429 | 429 | |
| 430 | 430 | To compile this driver as a module, choose M here: the module will |
| @@ -439,7 +439,7 @@ config DELL_WMI_AIO · 8 unmodified lines | ||
| 439 | 439 | depends on ACPI_WMI |
| 440 | 440 | depends on INPUT |
| 441 | 441 | select INPUT_SPARSEKMAP |
| 442 | − ---help--- | |
| 442 | + help | |
| 443 | 443 | Say Y here if you want to support WMI-based hotkeys on Dell |
| 444 | 444 | All-In-One machines. |
| 445 | 445 | |
| @@ -458,7 +458,7 @@ config AMILO_RFKILL · 12 unmodified lines | ||
| 458 | 458 | tristate "Fujitsu-Siemens Amilo rfkill support" |
| 459 | 459 | depends on RFKILL |
| 460 | 460 | depends on SERIO_I8042 |
| 461 | − ---help--- | |
| 461 | + help | |
| 462 | 462 | This is a driver for enabling wifi on some Fujitsu-Siemens Amilo |
| 463 | 463 | laptops. |
| 464 | 464 | |
| @@ -470,7 +470,7 @@ config FUJITSU_LAPTOP · 5 unmodified lines | ||
| 470 | 470 | depends on ACPI_VIDEO || ACPI_VIDEO = n |
| 471 | 471 | select INPUT_SPARSEKMAP |
| 472 | 472 | select LEDS_CLASS |
| 473 | − ---help--- | |
| 473 | + help | |
| 474 | 474 | This is a driver for laptops built by Fujitsu: |
| 475 | 475 | |
| 476 | 476 | * P2xxx/P5xxx/S6xxx/S7xxx series Lifebooks |
| @@ -485,7 +485,7 @@ config FUJITSU_TABLET · 8 unmodified lines | ||
| 485 | 485 | tristate "Fujitsu Tablet Extras" |
| 486 | 486 | depends on ACPI |
| 487 | 487 | depends on INPUT |
| 488 | − ---help--- | |
| 488 | + help | |
| 489 | 489 | This is a driver for tablets built by Fujitsu: |
| 490 | 490 | |
| 491 | 491 | * Lifebook P1510/P1610/P1620/Txxxx |
| @@ -502,7 +502,7 @@ config GPD_POCKET_FAN · 10 unmodified lines | ||
| 502 | 502 | tristate "GPD Pocket Fan Controller support" |
| 503 | 503 | depends on ACPI |
| 504 | 504 | depends on THERMAL |
| 505 | − ---help--- | |
| 505 | + help | |
| 506 | 506 | Driver for the GPD Pocket vendor specific FAN02501 ACPI device |
| 507 | 507 | which controls the fan speed on the GPD Pocket. |
| 508 | 508 | |
| @@ -558,14 +558,14 @@ config TC1100_WMI · 49 unmodified lines | ||
| 558 | 558 | depends on !X86_64 |
| 559 | 559 | depends on ACPI |
| 560 | 560 | depends on ACPI_WMI |
| 561 | − ---help--- | |
| 561 | + help | |
| 562 | 562 | This is a driver for the WMI extensions (wireless and bluetooth power |
| 563 | 563 | control) of the HP Compaq TC1100 tablet. |
| 564 | 564 | |
| 565 | 565 | config IBM_RTL |
| 566 | 566 | tristate "Device driver to enable PRTL support" |
| 567 | 567 | depends on PCI |
| 568 | − ---help--- | |
| 568 | + help | |
| 569 | 569 | Enable support for IBM Premium Real Time Mode (PRTM). |
| 570 | 570 | This module will allow you the enter and exit PRTM in the BIOS via |
| 571 | 571 | sysfs on platforms that support this feature. System in PRTM will |
| @@ -623,7 +623,7 @@ config THINKPAD_ACPI · 51 unmodified lines | ||
| 623 | 623 | select LEDS_CLASS |
| 624 | 624 | select LEDS_TRIGGERS |
| 625 | 625 | select LEDS_TRIGGER_AUDIO |
| 626 | − ---help--- | |
| 626 | + help | |
| 627 | 627 | This is a driver for the IBM and Lenovo ThinkPad laptops. It adds |
| 628 | 628 | support for Fn-Fx key combinations, Bluetooth control, video |
| 629 | 629 | output switching, ThinkLight control, UltraBay eject and more. |
| @@ -646,7 +646,7 @@ config THINKPAD_ACPI_ALSA_SUPPORT · 16 unmodified lines | ||
| 646 | 646 | depends on SND |
| 647 | 647 | depends on SND = y || THINKPAD_ACPI = SND |
| 648 | 648 | default y |
| 649 | − ---help--- | |
| 649 | + help | |
| 650 | 650 | Enables monitoring of the built-in console audio output control |
| 651 | 651 | (headphone and speakers), which is operated by the mute and (in |
| 652 | 652 | some ThinkPad models) volume hotkeys. |
| @@ -666,7 +666,7 @@ config THINKPAD_ACPI_ALSA_SUPPORT · 13 unmodified lines | ||
| 666 | 666 | config THINKPAD_ACPI_DEBUGFACILITIES |
| 667 | 667 | bool "Maintainer debug facilities" |
| 668 | 668 | depends on THINKPAD_ACPI |
| 669 | − ---help--- | |
| 669 | + help | |
| 670 | 670 | Enables extra stuff in the thinkpad-acpi which is completely useless |
| 671 | 671 | for normal use. Read the driver source to find out what it does. |
| 672 | 672 | |
| @@ -676,7 +676,7 @@ config THINKPAD_ACPI_DEBUGFACILITIES · 3 unmodified lines | ||
| 676 | 676 | config THINKPAD_ACPI_DEBUG |
| 677 | 677 | bool "Verbose debug mode" |
| 678 | 678 | depends on THINKPAD_ACPI |
| 679 | − ---help--- | |
| 679 | + help | |
| 680 | 680 | Enables extra debugging information, at the expense of a slightly |
| 681 | 681 | increase in driver size. |
| 682 | 682 | |
| @@ -685,7 +685,7 @@ config THINKPAD_ACPI_DEBUG · 2 unmodified lines | ||
| 685 | 685 | config THINKPAD_ACPI_UNSAFE_LEDS |
| 686 | 686 | bool "Allow control of important LEDs (unsafe)" |
| 687 | 687 | depends on THINKPAD_ACPI |
| 688 | − ---help--- | |
| 688 | + help | |
| 689 | 689 | Overriding LED state on ThinkPads can mask important |
| 690 | 690 | firmware alerts (like critical battery condition), or misled |
| 691 | 691 | the user into damaging the hardware (undocking or ejecting |
| @@ -709,7 +709,7 @@ config THINKPAD_ACPI_VIDEO · 17 unmodified lines | ||
| 709 | 709 | bool "Video output control support" |
| 710 | 710 | depends on THINKPAD_ACPI |
| 711 | 711 | default y |
| 712 | − ---help--- | |
| 712 | + help | |
| 713 | 713 | Allows the thinkpad_acpi driver to provide an interface to control |
| 714 | 714 | the various video output ports. |
| 715 | 715 | |
| @@ -732,7 +732,7 @@ config THINKPAD_ACPI_HOTKEY_POLL · 16 unmodified lines | ||
| 732 | 732 | bool "Support NVRAM polling for hot keys" |
| 733 | 733 | depends on THINKPAD_ACPI |
| 734 | 734 | default y |
| 735 | − ---help--- | |
| 735 | + help | |
| 736 | 736 | Some thinkpad models benefit from NVRAM polling to detect a few of |
| 737 | 737 | the hot key press events. If you know your ThinkPad model does not |
| 738 | 738 | need to do NVRAM polling to support any of the hot keys you use, |
| @@ -767,7 +767,7 @@ config INTEL_CHT_INT33FE · 28 unmodified lines | ||
| 767 | 767 | depends on CHARGER_BQ24190=y || (CHARGER_BQ24190=m && m) |
| 768 | 768 | depends on USB_ROLES_INTEL_XHCI=y || (USB_ROLES_INTEL_XHCI=m && m) |
| 769 | 769 | depends on TYPEC_MUX_PI3USB30532=y || (TYPEC_MUX_PI3USB30532=m && m) |
| 770 | − ---help--- | |
| 770 | + help | |
| 771 | 771 | This driver add support for the INT33FE ACPI device found on |
| 772 | 772 | some Intel Cherry Trail devices. |
| 773 | 773 | |
| @@ -801,7 +801,7 @@ config INTEL_INT0002_VGPIO · 27 unmodified lines | ||
| 801 | 801 | tristate "Intel ACPI INT0002 Virtual GPIO driver" |
| 802 | 802 | depends on GPIOLIB && ACPI |
| 803 | 803 | select GPIOLIB_IRQCHIP |
| 804 | − ---help--- | |
| 804 | + help | |
| 805 | 805 | Some peripherals on Bay Trail and Cherry Trail platforms signal a |
| 806 | 806 | Power Management Event (PME) to the Power Management Controller (PMC) |
| 807 | 807 | to wakeup the system. When this happens software needs to explicitly |
| @@ -820,7 +820,7 @@ config INTEL_MENLOW · 12 unmodified lines | ||
| 820 | 820 | tristate "Thermal Management driver for Intel menlow platform" |
| 821 | 821 | depends on ACPI_THERMAL |
| 822 | 822 | select THERMAL |
| 823 | − ---help--- | |
| 823 | + help | |
| 824 | 824 | ACPI thermal management enhancement driver on |
| 825 | 825 | Intel Menlow platform. |
| 826 | 826 | |
| @@ -831,7 +831,7 @@ config INTEL_OAKTRAIL · 4 unmodified lines | ||
| 831 | 831 | depends on ACPI |
| 832 | 832 | depends on ACPI_VIDEO || ACPI_VIDEO = n |
| 833 | 833 | depends on RFKILL && BACKLIGHT_CLASS_DEVICE && ACPI |
| 834 | − ---help--- | |
| 834 | + help | |
| 835 | 835 | Intel Oaktrail platform need this driver to provide interfaces to |
| 836 | 836 | enable/disable the Camera, WiFi, BT etc. devices. If in doubt, say Y |
| 837 | 837 | here; it will only load on supported platforms. |
| @@ -854,7 +854,7 @@ config SURFACE3_WMI · 16 unmodified lines | ||
| 854 | 854 | depends on DMI |
| 855 | 855 | depends on INPUT |
| 856 | 856 | depends on SPI |
| 857 | − ---help--- | |
| 857 | + help | |
| 858 | 858 | Say Y here if you have a Surface 3. |
| 859 | 859 | |
| 860 | 860 | To compile this driver as a module, choose M here: the module will |
| @@ -863,7 +863,7 @@ config SURFACE3_WMI · 2 unmodified lines | ||
| 863 | 863 | config SURFACE_3_BUTTON |
| 864 | 864 | tristate "Power/home/volume buttons driver for Microsoft Surface 3 tablet" |
| 865 | 865 | depends on ACPI && KEYBOARD_GPIO && I2C |
| 866 | − ---help--- | |
| 866 | + help | |
| 867 | 867 | This driver handles the power/home/volume buttons on the Microsoft Surface 3 tablet. |
| 868 | 868 | |
| 869 | 869 | config SURFACE_3_POWER_OPREGION |
| @@ -876,7 +876,7 @@ config SURFACE_3_POWER_OPREGION · 6 unmodified lines | ||
| 876 | 876 | config SURFACE_PRO3_BUTTON |
| 877 | 877 | tristate "Power/home/volume buttons driver for Microsoft Surface Pro 3/4 tablet" |
| 878 | 878 | depends on ACPI && INPUT |
| 879 | − ---help--- | |
| 879 | + help | |
| 880 | 880 | This driver handles the power/home/volume buttons on the Microsoft Surface Pro 3/4 tablet. |
| 881 | 881 | |
| 882 | 882 | config MSI_LAPTOP |
| @@ -887,7 +887,7 @@ config MSI_LAPTOP · 4 unmodified lines | ||
| 887 | 887 | depends on RFKILL |
| 888 | 888 | depends on INPUT && SERIO_I8042 |
| 889 | 889 | select INPUT_SPARSEKMAP |
| 890 | − ---help--- | |
| 890 | + help | |
| 891 | 891 | This is a driver for laptops built by MSI (MICRO-STAR |
| 892 | 892 | INTERNATIONAL): |
| 893 | 893 | |
| @@ -918,7 +918,7 @@ config XO15_EBOOK · 24 unmodified lines | ||
| 918 | 918 | tristate "OLPC XO-1.5 ebook switch" |
| 919 | 919 | depends on OLPC || COMPILE_TEST |
| 920 | 920 | depends on ACPI && INPUT |
| 921 | − ---help--- | |
| 921 | + help | |
| 922 | 922 | Support for the ebook switch on the OLPC XO-1.5 laptop. |
| 923 | 923 | |
| 924 | 924 | This switch is triggered as the screen is rotated and folded down to |
| @@ -928,7 +928,7 @@ config XO1_RFKILL · 3 unmodified lines | ||
| 928 | 928 | tristate "OLPC XO-1 software RF kill switch" |
| 929 | 929 | depends on OLPC || COMPILE_TEST |
| 930 | 930 | depends on RFKILL |
| 931 | − ---help--- | |
| 931 | + help | |
| 932 | 932 | Support for enabling/disabling the WLAN interface on the OLPC XO-1 |
| 933 | 933 | laptop. |
| 934 | 934 | |
| @@ -953,7 +953,7 @@ config SAMSUNG_LAPTOP · 18 unmodified lines | ||
| 953 | 953 | depends on BACKLIGHT_CLASS_DEVICE |
| 954 | 954 | select LEDS_CLASS |
| 955 | 955 | select NEW_LEDS |
| 956 | − ---help--- | |
| 956 | + help | |
| 957 | 957 | This module implements a driver for a wide range of different |
| 958 | 958 | Samsung laptops. It offers control over the different |
| 959 | 959 | function keys, wireless LED, LCD backlight level. |
| @@ -968,7 +968,7 @@ config SAMSUNG_Q10 · 8 unmodified lines | ||
| 968 | 968 | tristate "Samsung Q10 Extras" |
| 969 | 969 | depends on ACPI |
| 970 | 970 | select BACKLIGHT_CLASS_DEVICE |
| 971 | − ---help--- | |
| 971 | + help | |
| 972 | 972 | This driver provides support for backlight control on Samsung Q10 |
| 973 | 973 | and related laptops, including Dell Latitude X200. |
| 974 | 974 | |
| @@ -985,7 +985,7 @@ config ACPI_TOSHIBA · 10 unmodified lines | ||
| 985 | 985 | depends on RFKILL || RFKILL = n |
| 986 | 986 | depends on IIO |
| 987 | 987 | select INPUT_SPARSEKMAP |
| 988 | − ---help--- | |
| 988 | + help | |
| 989 | 989 | This driver adds support for access to certain system settings |
| 990 | 990 | on "legacy free" Toshiba laptops. These laptops can be recognized by |
| 991 | 991 | their lack of a BIOS setup menu and APM support. |
| @@ -1012,7 +1012,7 @@ config TOSHIBA_BT_RFKILL · 20 unmodified lines | ||
| 1012 | 1012 | tristate "Toshiba Bluetooth RFKill switch support" |
| 1013 | 1013 | depends on ACPI |
| 1014 | 1014 | depends on RFKILL || RFKILL = n |
| 1015 | − ---help--- | |
| 1015 | + help | |
| 1016 | 1016 | This driver adds support for Bluetooth events for the RFKill |
| 1017 | 1017 | switch on modern Toshiba laptops with full ACPI support and |
| 1018 | 1018 | an RFKill switch. |
| @@ -1027,7 +1027,7 @@ config TOSHIBA_BT_RFKILL · 8 unmodified lines | ||
| 1027 | 1027 | config TOSHIBA_HAPS |
| 1028 | 1028 | tristate "Toshiba HDD Active Protection Sensor" |
| 1029 | 1029 | depends on ACPI |
| 1030 | − ---help--- | |
| 1030 | + help | |
| 1031 | 1031 | This driver adds support for the built-in accelerometer |
| 1032 | 1032 | found on recent Toshiba laptops equipped with HID TOS620A |
| 1033 | 1033 | device. |
| @@ -1048,7 +1048,7 @@ config TOSHIBA_WMI · 14 unmodified lines | ||
| 1048 | 1048 | depends on ACPI_WMI |
| 1049 | 1049 | depends on INPUT |
| 1050 | 1050 | select INPUT_SPARSEKMAP |
| 1051 | − ---help--- | |
| 1051 | + help | |
| 1052 | 1052 | This driver adds hotkey monitoring support to some Toshiba models |
| 1053 | 1053 | that manage the hotkeys via WMI events. |
| 1054 | 1054 | |
| @@ -1078,7 +1078,7 @@ config COMPAL_LAPTOP · 23 unmodified lines | ||
| 1078 | 1078 | depends on RFKILL |
| 1079 | 1079 | depends on HWMON |
| 1080 | 1080 | depends on POWER_SUPPLY |
| 1081 | − ---help--- | |
| 1081 | + help | |
| 1082 | 1082 | This is a driver for laptops built by Compal, and some models by |
| 1083 | 1083 | other brands (e.g. Dell, Toshiba). |
| 1084 | 1084 | |
| @@ -1104,7 +1104,7 @@ config PANASONIC_LAPTOP · 19 unmodified lines | ||
| 1104 | 1104 | depends on INPUT && ACPI |
| 1105 | 1105 | depends on BACKLIGHT_CLASS_DEVICE |
| 1106 | 1106 | select INPUT_SPARSEKMAP |
| 1107 | − ---help--- | |
| 1107 | + help | |
| 1108 | 1108 | This driver adds support for access to backlight control and hotkeys |
| 1109 | 1109 | on Panasonic Let's Note laptops. |
| 1110 | 1110 | |
| @@ -1118,7 +1118,7 @@ config SONY_LAPTOP · 7 unmodified lines | ||
| 1118 | 1118 | depends on BACKLIGHT_CLASS_DEVICE |
| 1119 | 1119 | depends on INPUT |
| 1120 | 1120 | depends on RFKILL |
| 1121 | − ---help--- | |
| 1121 | + help | |
| 1122 | 1122 | This mini-driver drives the SNC and SPIC devices present in the ACPI |
| 1123 | 1123 | BIOS of the Sony Vaio laptops. |
| 1124 | 1124 | |
| @@ -1131,7 +1131,7 @@ config SONY_LAPTOP · 6 unmodified lines | ||
| 1131 | 1131 | config SONYPI_COMPAT |
| 1132 | 1132 | bool "Sonypi compatibility" |
| 1133 | 1133 | depends on SONY_LAPTOP |
| 1134 | − ---help--- | |
| 1134 | + help | |
| 1135 | 1135 | Build the sonypi driver compatibility code into the sony-laptop driver. |
| 1136 | 1136 | |
| 1137 | 1137 | config SYSTEM76_ACPI |
| @@ -1154,7 +1154,7 @@ config TOPSTAR_LAPTOP · 16 unmodified lines | ||
| 1154 | 1154 | select INPUT_SPARSEKMAP |
| 1155 | 1155 | select LEDS_CLASS |
| 1156 | 1156 | select NEW_LEDS |
| 1157 | − ---help--- | |
| 1157 | + help | |
| 1158 | 1158 | This driver adds support for hotkeys found on Topstar laptops. |
| 1159 | 1159 | |
| 1160 | 1160 | If you have a Topstar laptop, say Y or M here. |
| @@ -1173,7 +1173,7 @@ config I2C_MULTI_INSTANTIATE · 12 unmodified lines | ||
| 1173 | 1173 | config MLX_PLATFORM |
| 1174 | 1174 | tristate "Mellanox Technologies platform support" |
| 1175 | 1175 | depends on I2C && REGMAP |
| 1176 | − ---help--- | |
| 1176 | + help | |
| 1177 | 1177 | This option enables system support for the Mellanox Technologies |
| 1178 | 1178 | platform. The Mellanox systems provide data center networking |
| 1179 | 1179 | solutions based on Virtual Protocol Interconnect (VPI) technology |
| @@ -1186,7 +1186,7 @@ config TOUCHSCREEN_DMI · 6 unmodified lines | ||
| 1186 | 1186 | bool "DMI based touchscreen configuration info" |
| 1187 | 1187 | depends on ACPI && DMI && I2C=y && TOUCHSCREEN_SILEAD |
| 1188 | 1188 | select EFI_EMBEDDED_FIRMWARE if EFI |
| 1189 | − ---help--- | |
| 1189 | + help | |
| 1190 | 1190 | Certain ACPI based tablets with e.g. Silead or Chipone touchscreens |
| 1191 | 1191 | do not have enough data in ACPI tables for the touchscreen driver to |
| 1192 | 1192 | handle the touchscreen properly, as OEMs expect the data to be baked |
| @@ -1197,7 +1197,7 @@ config TOUCHSCREEN_DMI · 4 unmodified lines | ||
| 1197 | 1197 | config INTEL_IMR |
| 1198 | 1198 | bool "Intel Isolated Memory Region support" |
| 1199 | 1199 | depends on X86_INTEL_QUARK && IOSF_MBI |
| 1200 | − ---help--- | |
| 1200 | + help | |
| 1201 | 1201 | This option provides a means to manipulate Isolated Memory Regions. |
| 1202 | 1202 | IMRs are a set of registers that define read and write access masks |
| 1203 | 1203 | to prohibit certain system agents from accessing memory with 1 KiB |
| @@ -1221,7 +1221,7 @@ config INTEL_IMR · 17 unmodified lines | ||
| 1221 | 1221 | config INTEL_IPS |
| 1222 | 1222 | tristate "Intel Intelligent Power Sharing" |
| 1223 | 1223 | depends on ACPI && PCI |
| 1224 | − ---help--- | |
| 1224 | + help | |
| 1225 | 1225 | Intel Calpella platforms support dynamic power sharing between the |
| 1226 | 1226 | CPU and GPU, maximizing performance in a given TDP. This driver, |
| 1227 | 1227 | along with the CPU frequency and i915 drivers, provides that |
| @@ -1231,7 +1231,7 @@ config INTEL_IPS · 3 unmodified lines | ||
| 1231 | 1231 | config INTEL_RST |
| 1232 | 1232 | tristate "Intel Rapid Start Technology Driver" |
| 1233 | 1233 | depends on ACPI |
| 1234 | − ---help--- | |
| 1234 | + help | |
| 1235 | 1235 | This driver provides support for modifying parameters on systems |
| 1236 | 1236 | equipped with Intel's Rapid Start Technology. When put in an ACPI |
| 1237 | 1237 | sleep state, these devices will wake after either a configured |
| @@ -1243,7 +1243,7 @@ config INTEL_RST · 5 unmodified lines | ||
| 1243 | 1243 | config INTEL_SMARTCONNECT |
| 1244 | 1244 | tristate "Intel Smart Connect disabling driver" |
| 1245 | 1245 | depends on ACPI |
| 1246 | − ---help--- | |
| 1246 | + help | |
| 1247 | 1247 | Intel Smart Connect is a technology intended to permit devices to |
| 1248 | 1248 | update state by resuming for a short period of time at regular |
| 1249 | 1249 | intervals. If a user enables this functionality under Windows and |
| @@ -1259,7 +1259,7 @@ source "drivers/platform/x86/intel_speed_select_if/Kconfig" · 9 unmodified lines | ||
| 1259 | 1259 | config INTEL_TURBO_MAX_3 |
| 1260 | 1260 | bool "Intel Turbo Boost Max Technology 3.0 enumeration driver" |
| 1261 | 1261 | depends on X86_64 && SCHED_MC_PRIO |
| 1262 | − ---help--- | |
| 1262 | + help | |
| 1263 | 1263 | This driver reads maximum performance ratio of each CPU and set up |
| 1264 | 1264 | the scheduler priority metrics. In this way scheduler can prefer |
| 1265 | 1265 | CPU with higher performance to schedule tasks. |
| @@ -1282,7 +1282,7 @@ config INTEL_BXTWC_PMIC_TMU · 16 unmodified lines | ||
| 1282 | 1282 | depends on REGMAP |
| 1283 | 1283 | depends on MFD_INTEL_PMC_BXT |
| 1284 | 1284 | depends on INTEL_SOC_PMIC_BXTWC |
| 1285 | − ---help--- | |
| 1285 | + help | |
| 1286 | 1286 | Select this driver to use Intel BXT Whiskey Cove PMIC TMU feature. |
| 1287 | 1287 | This driver enables the alarm wakeup functionality in the TMU unit |
| 1288 | 1288 | of Whiskey Cove PMIC. |
| @@ -1291,7 +1291,7 @@ config INTEL_CHTDC_TI_PWRBTN · 2 unmodified lines | ||
| 1291 | 1291 | tristate "Intel Cherry Trail Dollar Cove TI power button driver" |
| 1292 | 1292 | depends on INTEL_SOC_PMIC_CHTDC_TI |
| 1293 | 1293 | depends on INPUT |
| 1294 | − ---help--- | |
| 1294 | + help | |
| 1295 | 1295 | This option adds a power button driver driver for Dollar Cove TI |
| 1296 | 1296 | PMIC on Intel Cherry Trail devices. |
| 1297 | 1297 | |
| @@ -1317,7 +1317,7 @@ config INTEL_MRFLD_PWRBTN · 19 unmodified lines | ||
| 1317 | 1317 | tristate "Intel Merrifield Basin Cove power button driver" |
| 1318 | 1318 | depends on INTEL_SOC_PMIC_MRFLD |
| 1319 | 1319 | depends on INPUT |
| 1320 | − ---help--- | |
| 1320 | + help | |
| 1321 | 1321 | This option adds a power button driver for Basin Cove PMIC |
| 1322 | 1322 | on Intel Merrifield devices. |
| 1323 | 1323 | |
| @@ -1327,7 +1327,7 @@ config INTEL_MRFLD_PWRBTN · 3 unmodified lines | ||
| 1327 | 1327 | config INTEL_PMC_CORE |
| 1328 | 1328 | tristate "Intel PMC Core driver" |
| 1329 | 1329 | depends on PCI |
| 1330 | − ---help--- | |
| 1330 | + help | |
| 1331 | 1331 | The Intel Platform Controller Hub for Intel Core SoCs provides access |
| 1332 | 1332 | to Power Management Controller registers via a PCI interface. This |
| 1333 | 1333 | driver can utilize debugging capabilities and supported features as |
| @@ -1341,7 +1341,7 @@ config INTEL_PMC_CORE · 7 unmodified lines | ||
| 1341 | 1341 | |
| 1342 | 1342 | config INTEL_PUNIT_IPC |
| 1343 | 1343 | tristate "Intel P-Unit IPC Driver" |
| 1344 | − ---help--- | |
| 1344 | + help | |
| 1345 | 1345 | This driver provides support for Intel P-Unit Mailbox IPC mechanism, |
| 1346 | 1346 | which is used to bridge the communications between kernel and P-Unit. |
| 1347 | 1347 | |
| @@ -1379,7 +1379,7 @@ config INTEL_SCU_PLATFORM · 31 unmodified lines | ||
| 1379 | 1379 | config INTEL_SCU_IPC_UTIL |
| 1380 | 1380 | tristate "Intel SCU IPC utility driver" |
| 1381 | 1381 | depends on INTEL_SCU |
| 1382 | − ---help--- | |
| 1382 | + help | |
| 1383 | 1383 | The IPC Util driver provides an interface with the SCU enabling |
| 1384 | 1384 | low level access for debug work and updating the firmware. Say |
| 1385 | 1385 | N unless you will be doing this on an Intel MID platform. |
| @@ -1389,7 +1389,7 @@ config INTEL_TELEMETRY · 3 unmodified lines | ||
| 1389 | 1389 | depends on X86_64 |
| 1390 | 1390 | depends on MFD_INTEL_PMC_BXT |
| 1391 | 1391 | depends on INTEL_PUNIT_IPC |
| 1392 | − ---help--- | |
| 1392 | + help | |
| 1393 | 1393 | This driver provides interfaces to configure and use |
| 1394 | 1394 | telemetry for INTEL SoC from APL onwards. It is also |
| 1395 | 1395 | used to get various SoC events and parameters |
| @@ -7,7 +7,7 @@ menuconfig PNP · 6 unmodified lines | ||
| 7 | 7 | bool "Plug and Play support" |
| 8 | 8 | depends on HAS_IOMEM |
| 9 | 9 | depends on ISA || ACPI |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Plug and Play (PnP) is a standard for peripherals which allows those |
| 12 | 12 | peripherals to be configured by software, e.g. assign IRQ's or other |
| 13 | 13 | parameters. No jumpers on the cards are needed, instead the values |
| @@ -6,7 +6,7 @@ config PNPBIOS · 5 unmodified lines | ||
| 6 | 6 | bool "Plug and Play BIOS support" |
| 7 | 7 | depends on ISA && X86_32 |
| 8 | 8 | default n |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Linux uses the PNPBIOS as defined in "Plug and Play BIOS |
| 11 | 11 | Specification Version 1.0A May 5, 1994" to autodetect built-in |
| 12 | 12 | mainboard resources (e.g. parallel port resources). |
| @@ -26,7 +26,7 @@ config PNPBIOS · 13 unmodified lines | ||
| 26 | 26 | config PNPBIOS_PROC_FS |
| 27 | 27 | bool "Plug and Play BIOS /proc interface" |
| 28 | 28 | depends on PNPBIOS && PROC_FS |
| 29 | − ---help--- | |
| 29 | + help | |
| 30 | 30 | If you say Y here and to "/proc file system support", you will be |
| 31 | 31 | able to directly access the PNPBIOS. This includes resource |
| 32 | 32 | allocation, ESCD, and other PNPBIOS services. Using this |
| @@ -23,7 +23,7 @@ config INTEL_RAPL · 22 unmodified lines | ||
| 23 | 23 | tristate "Intel RAPL Support via MSR Interface" |
| 24 | 24 | depends on X86 && IOSF_MBI |
| 25 | 25 | select INTEL_RAPL_CORE |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | This enables support for the Intel Running Average Power Limit (RAPL) |
| 28 | 28 | technology via MSR interface, which allows power limits to be enforced |
| 29 | 29 | and monitored on modern Intel processors (Sandy Bridge and later). |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | |
| 6 | 6 | menuconfig PPS |
| 7 | 7 | tristate "PPS support" |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | PPS (Pulse Per Second) is a special pulse provided by some GPS |
| 10 | 10 | antennae. Userland can use it to get a high-precision time |
| 11 | 11 | reference. |
| @@ -64,7 +64,7 @@ config DP83640_PHY · 63 unmodified lines | ||
| 64 | 64 | depends on NETWORK_PHY_TIMESTAMPING |
| 65 | 65 | depends on PHYLIB |
| 66 | 66 | depends on PTP_1588_CLOCK |
| 67 | − ---help--- | |
| 67 | + help | |
| 68 | 68 | Supports the DP83640 PHYTER with IEEE 1588 features. |
| 69 | 69 | |
| 70 | 70 | This driver adds support for using the DP83640 as a PTP |
| @@ -19,14 +19,14 @@ config RAPIDIO_DISC_TIMEOUT · 18 unmodified lines | ||
| 19 | 19 | int "Discovery timeout duration (seconds)" |
| 20 | 20 | depends on RAPIDIO |
| 21 | 21 | default "30" |
| 22 | − ---help--- | |
| 22 | + help | |
| 23 | 23 | Amount of time a discovery node waits for a host to complete |
| 24 | 24 | enumeration before giving up. |
| 25 | 25 | |
| 26 | 26 | config RAPIDIO_ENABLE_RX_TX_PORTS |
| 27 | 27 | bool "Enable RapidIO Input/Output Ports" |
| 28 | 28 | depends on RAPIDIO |
| 29 | − ---help--- | |
| 29 | + help | |
| 30 | 30 | The RapidIO specification describes a Output port transmit |
| 31 | 31 | enable and a Input port receive enable. The recommended state |
| 32 | 32 | for Input ports and Output ports should be disabled. When |
| @@ -7,5 +7,5 @@ config RAPIDIO_TSI721 · 6 unmodified lines | ||
| 7 | 7 | tristate "IDT Tsi721 PCI Express SRIO Controller support" |
| 8 | 8 | depends on RAPIDIO && PCIEPORTBUS |
| 9 | 9 | default "n" |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Include support for IDT Tsi721 PCI Express Serial RapidIO controller. |
| @@ -4,28 +4,28 @@ · 3 unmodified lines | ||
| 4 | 4 | # |
| 5 | 5 | config RAPIDIO_TSI57X |
| 6 | 6 | tristate "IDT Tsi57x SRIO switches support" |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | Includes support for IDT Tsi57x family of serial RapidIO switches. |
| 9 | 9 | |
| 10 | 10 | config RAPIDIO_CPS_XX |
| 11 | 11 | tristate "IDT CPS-xx SRIO switches support" |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | Includes support for IDT CPS-16/12/10/8 serial RapidIO switches. |
| 14 | 14 | |
| 15 | 15 | config RAPIDIO_TSI568 |
| 16 | 16 | tristate "Tsi568 SRIO switch support" |
| 17 | 17 | default n |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | Includes support for IDT Tsi568 serial RapidIO switch. |
| 20 | 20 | |
| 21 | 21 | config RAPIDIO_CPS_GEN2 |
| 22 | 22 | tristate "IDT CPS Gen.2 SRIO switch support" |
| 23 | 23 | default n |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | Includes support for ITD CPS Gen.2 serial RapidIO switches. |
| 26 | 26 | |
| 27 | 27 | config RAPIDIO_RXS_GEN3 |
| 28 | 28 | tristate "IDT RXS Gen.3 SRIO switch support" |
| 29 | 29 | default n |
| 30 | − ---help--- | |
| 30 | + help | |
| 31 | 31 | Includes support for ITD RXS Gen.3 serial RapidIO switches. |
| @@ -53,7 +53,7 @@ config ENVCTRL · 52 unmodified lines | ||
| 53 | 53 | config DISPLAY7SEG |
| 54 | 54 | tristate "7-Segment Display support" |
| 55 | 55 | depends on PCI && SPARC64 |
| 56 | − ---help--- | |
| 56 | + help | |
| 57 | 57 | This is the driver for the 7-segment display and LED present on |
| 58 | 58 | Sun Microsystems CompactPCI models CP1400 and CP1500. |
| 59 | 59 | |
| @@ -11,7 +11,7 @@ config RAID_ATTRS · 10 unmodified lines | ||
| 11 | 11 | default n |
| 12 | 12 | depends on BLOCK |
| 13 | 13 | depends on SCSI_MOD |
| 14 | − ---help--- | |
| 14 | + help | |
| 15 | 15 | Provides RAID |
| 16 | 16 | |
| 17 | 17 | config SCSI |
| @@ -20,7 +20,7 @@ config SCSI · 2 unmodified lines | ||
| 20 | 20 | select SCSI_DMA if HAS_DMA |
| 21 | 21 | select SG_POOL |
| 22 | 22 | select BLK_SCSI_REQUEST |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or |
| 25 | 25 | any other SCSI device under Linux, say Y and make sure that you know |
| 26 | 26 | the name of your SCSI host adapter (the card inside your computer |
| @@ -55,7 +55,7 @@ config SCSI_PROC_FS · 28 unmodified lines | ||
| 55 | 55 | bool "legacy /proc/scsi/ support" |
| 56 | 56 | depends on SCSI && PROC_FS |
| 57 | 57 | default y |
| 58 | − ---help--- | |
| 58 | + help | |
| 59 | 59 | This option enables support for the various files in |
| 60 | 60 | /proc/scsi. In Linux 2.6 this has been superseded by |
| 61 | 61 | files in sysfs but many legacy applications rely on this. |
| @@ -69,7 +69,7 @@ config BLK_DEV_SD · 7 unmodified lines | ||
| 69 | 69 | tristate "SCSI disk support" |
| 70 | 70 | depends on SCSI |
| 71 | 71 | select BLK_DEV_INTEGRITY_T10 if BLK_DEV_INTEGRITY |
| 72 | − ---help--- | |
| 72 | + help | |
| 73 | 73 | If you want to use SCSI hard disks, Fibre Channel disks, |
| 74 | 74 | Serial ATA (SATA) or Parallel ATA (PATA) hard disks, |
| 75 | 75 | USB storage or the SCSI or parallel port version of |
| @@ -90,7 +90,7 @@ config BLK_DEV_SD · 14 unmodified lines | ||
| 90 | 90 | config CHR_DEV_ST |
| 91 | 91 | tristate "SCSI tape support" |
| 92 | 92 | depends on SCSI |
| 93 | − ---help--- | |
| 93 | + help | |
| 94 | 94 | If you want to use a SCSI tape drive under Linux, say Y and read the |
| 95 | 95 | SCSI-HOWTO, available from |
| 96 | 96 | <http://www.tldp.org/docs.html#howto>, and |
| @@ -104,7 +104,7 @@ config BLK_DEV_SR · 7 unmodified lines | ||
| 104 | 104 | tristate "SCSI CDROM support" |
| 105 | 105 | depends on SCSI && BLK_DEV |
| 106 | 106 | select CDROM |
| 107 | − ---help--- | |
| 107 | + help | |
| 108 | 108 | If you want to use a CD or DVD drive attached to your computer |
| 109 | 109 | by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO |
| 110 | 110 | and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>. |
| @@ -118,7 +118,7 @@ config BLK_DEV_SR · 7 unmodified lines | ||
| 118 | 118 | config CHR_DEV_SG |
| 119 | 119 | tristate "SCSI generic support" |
| 120 | 120 | depends on SCSI |
| 121 | − ---help--- | |
| 121 | + help | |
| 122 | 122 | If you want to use SCSI scanners, synthesizers or CD-writers or just |
| 123 | 123 | about anything having "SCSI" in its name other than hard disks, |
| 124 | 124 | CD-ROMs or tapes, say Y here. These won't be supported by the kernel |
| @@ -143,7 +143,7 @@ config CHR_DEV_SG · 18 unmodified lines | ||
| 143 | 143 | config CHR_DEV_SCH |
| 144 | 144 | tristate "SCSI media changer support" |
| 145 | 145 | depends on SCSI |
| 146 | − ---help--- | |
| 146 | + help | |
| 147 | 147 | This is a driver for SCSI media changers. Most common devices are |
| 148 | 148 | tape libraries and MOD/CDROM jukeboxes. *Real* jukeboxes, you |
| 149 | 149 | don't need this for those tiny 6-slot cdrom changers. Media |
| @@ -178,7 +178,7 @@ config SCSI_CONSTANTS · 28 unmodified lines | ||
| 178 | 178 | config SCSI_LOGGING |
| 179 | 179 | bool "SCSI logging facility" |
| 180 | 180 | depends on SCSI |
| 181 | − ---help--- | |
| 181 | + help | |
| 182 | 182 | This turns on a logging facility that can be used to debug a number |
| 183 | 183 | of SCSI related problems. |
| 184 | 184 | |
| @@ -376,7 +376,7 @@ config SCSI_AHA152X · 191 unmodified lines | ||
| 376 | 376 | depends on ISA && SCSI |
| 377 | 377 | select SCSI_SPI_ATTRS |
| 378 | 378 | select CHECK_SIGNATURE |
| 379 | − ---help--- | |
| 379 | + help | |
| 380 | 380 | This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825 |
| 381 | 381 | SCSI host adapters. It also works for the AVA-1505, but the IRQ etc. |
| 382 | 382 | must be manually specified in this case. |
| @@ -391,7 +391,7 @@ config SCSI_AHA152X · 8 unmodified lines | ||
| 391 | 391 | config SCSI_AHA1542 |
| 392 | 392 | tristate "Adaptec AHA1542 support" |
| 393 | 393 | depends on ISA && SCSI && ISA_DMA_API |
| 394 | − ---help--- | |
| 394 | + help | |
| 395 | 395 | This is support for a SCSI host adapter. It is explained in section |
| 396 | 396 | 3.4 of the SCSI-HOWTO, available from |
| 397 | 397 | <http://www.tldp.org/docs.html#howto>. Note that Trantor was |
| @@ -405,7 +405,7 @@ config SCSI_AHA1542 · 7 unmodified lines | ||
| 405 | 405 | config SCSI_AHA1740 |
| 406 | 406 | tristate "Adaptec AHA1740 support" |
| 407 | 407 | depends on EISA && SCSI |
| 408 | − ---help--- | |
| 408 | + help | |
| 409 | 409 | This is support for a SCSI host adapter. It is explained in section |
| 410 | 410 | 3.5 of the SCSI-HOWTO, available from |
| 411 | 411 | <http://www.tldp.org/docs.html#howto>. If it doesn't work out |
| @@ -498,7 +498,7 @@ config SCSI_HPTIOP · 86 unmodified lines | ||
| 498 | 498 | config SCSI_BUSLOGIC |
| 499 | 499 | tristate "BusLogic SCSI support" |
| 500 | 500 | depends on (PCI || ISA) && SCSI && ISA_DMA_API && VIRT_TO_BUS |
| 501 | − ---help--- | |
| 501 | + help | |
| 502 | 502 | This is support for BusLogic MultiMaster and FlashPoint SCSI Host |
| 503 | 503 | Adapters. Consult the SCSI-HOWTO, available from |
| 504 | 504 | <http://www.tldp.org/docs.html#howto>, and the files |
| @@ -580,20 +580,20 @@ config LIBFC · 75 unmodified lines | ||
| 580 | 580 | tristate "LibFC module" |
| 581 | 581 | depends on SCSI_FC_ATTRS |
| 582 | 582 | select CRC32 |
| 583 | − ---help--- | |
| 583 | + help | |
| 584 | 584 | Fibre Channel library module |
| 585 | 585 | |
| 586 | 586 | config LIBFCOE |
| 587 | 587 | tristate "LibFCoE module" |
| 588 | 588 | depends on LIBFC |
| 589 | − ---help--- | |
| 589 | + help | |
| 590 | 590 | Library for Fibre Channel over Ethernet module |
| 591 | 591 | |
| 592 | 592 | config FCOE |
| 593 | 593 | tristate "FCoE module" |
| 594 | 594 | depends on PCI |
| 595 | 595 | depends on LIBFCOE |
| 596 | − ---help--- | |
| 596 | + help | |
| 597 | 597 | Fibre Channel over Ethernet module |
| 598 | 598 | |
| 599 | 599 | config FCOE_FNIC |
| @@ -672,7 +672,7 @@ config SCSI_FDOMAIN_ISA · 72 unmodified lines | ||
| 672 | 672 | config SCSI_GDTH |
| 673 | 673 | tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support" |
| 674 | 674 | depends on PCI && SCSI |
| 675 | − ---help--- | |
| 675 | + help | |
| 676 | 676 | Formerly called GDT SCSI Disk Array Controller Support. |
| 677 | 677 | |
| 678 | 678 | This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) |
| @@ -688,7 +688,7 @@ config SCSI_ISCI · 9 unmodified lines | ||
| 688 | 688 | depends on PCI && SCSI |
| 689 | 689 | depends on X86 |
| 690 | 690 | select SCSI_SAS_LIBSAS |
| 691 | − ---help--- | |
| 691 | + help | |
| 692 | 692 | This driver supports the 6Gb/s SAS capabilities of the storage |
| 693 | 693 | control unit found in the Intel(R) C600 series chipset. |
| 694 | 694 | |
| @@ -696,7 +696,7 @@ config SCSI_GENERIC_NCR5380 · 1 unmodified line | ||
| 696 | 696 | tristate "Generic NCR5380/53c400 SCSI ISA card support" |
| 697 | 697 | depends on ISA && SCSI && HAS_IOPORT_MAP |
| 698 | 698 | select SCSI_SPI_ATTRS |
| 699 | − ---help--- | |
| 699 | + help | |
| 700 | 700 | This is a driver for old ISA card SCSI controllers based on a |
| 701 | 701 | NCR 5380, 53C80, 53C400, 53C400A, or DTC 436 device. |
| 702 | 702 | Most boards such as the Trantor T130 fit this category, as do |
| @@ -708,7 +708,7 @@ config SCSI_GENERIC_NCR5380 · 5 unmodified lines | ||
| 708 | 708 | config SCSI_IPS |
| 709 | 709 | tristate "IBM ServeRAID support" |
| 710 | 710 | depends on PCI && SCSI |
| 711 | − ---help--- | |
| 711 | + help | |
| 712 | 712 | This is support for the IBM ServeRAID hardware RAID controllers. |
| 713 | 713 | See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html> |
| 714 | 714 | and <http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=SERV-RAID> |
| @@ -790,7 +790,7 @@ config SCSI_INIA100 · 75 unmodified lines | ||
| 790 | 790 | config SCSI_PPA |
| 791 | 791 | tristate "IOMEGA parallel port (ppa - older drives)" |
| 792 | 792 | depends on SCSI && PARPORT_PC |
| 793 | − ---help--- | |
| 793 | + help | |
| 794 | 794 | This driver supports older versions of IOMEGA's parallel port ZIP |
| 795 | 795 | drive (a 100 MB removable media device). |
| 796 | 796 | |
| @@ -817,7 +817,7 @@ config SCSI_PPA · 20 unmodified lines | ||
| 817 | 817 | config SCSI_IMM |
| 818 | 818 | tristate "IOMEGA parallel port (imm - newer drives)" |
| 819 | 819 | depends on SCSI && PARPORT_PC |
| 820 | − ---help--- | |
| 820 | + help | |
| 821 | 821 | This driver supports newer versions of IOMEGA's parallel port ZIP |
| 822 | 822 | drive (a 100 MB removable media device). |
| 823 | 823 | |
| @@ -844,7 +844,7 @@ config SCSI_IMM · 20 unmodified lines | ||
| 844 | 844 | config SCSI_IZIP_EPP16 |
| 845 | 845 | bool "ppa/imm option - Use slow (but safe) EPP-16" |
| 846 | 846 | depends on SCSI_PPA || SCSI_IMM |
| 847 | − ---help--- | |
| 847 | + help | |
| 848 | 848 | EPP (Enhanced Parallel Port) is a standard for parallel ports which |
| 849 | 849 | allows them to act as expansion buses that can handle up to 64 |
| 850 | 850 | peripheral devices. |
| @@ -896,7 +896,7 @@ config 53C700_LE_ON_BE · 45 unmodified lines | ||
| 896 | 896 | config SCSI_STEX |
| 897 | 897 | tristate "Promise SuperTrak EX Series support" |
| 898 | 898 | depends on PCI && SCSI |
| 899 | − ---help--- | |
| 899 | + help | |
| 900 | 900 | This driver supports Promise SuperTrak EX series storage controllers. |
| 901 | 901 | |
| 902 | 902 | Promise provides Linux RAID configuration utility for these |
| @@ -914,7 +914,7 @@ config SCSI_SYM53C8XX_2 · 11 unmodified lines | ||
| 914 | 914 | tristate "SYM53C8XX Version 2 SCSI support" |
| 915 | 915 | depends on PCI && SCSI |
| 916 | 916 | select SCSI_SPI_ATTRS |
| 917 | − ---help--- | |
| 917 | + help | |
| 918 | 918 | This driver supports the whole NCR53C8XX/SYM53C8XX family of |
| 919 | 919 | PCI-SCSI controllers. It also supports the subset of LSI53C10XX |
| 920 | 920 | Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS |
| @@ -928,7 +928,7 @@ config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE · 7 unmodified lines | ||
| 928 | 928 | int "DMA addressing mode" |
| 929 | 929 | depends on SCSI_SYM53C8XX_2 |
| 930 | 930 | default "1" |
| 931 | − ---help--- | |
| 931 | + help | |
| 932 | 932 | This option only applies to PCI-SCSI chips that are PCI DAC |
| 933 | 933 | capable (875A, 895A, 896, 1010-33, 1010-66, 1000). |
| 934 | 934 | |
| @@ -984,7 +984,7 @@ config SCSI_IPR · 49 unmodified lines | ||
| 984 | 984 | select FW_LOADER |
| 985 | 985 | select IRQ_POLL |
| 986 | 986 | select SGL_ALLOC |
| 987 | − ---help--- | |
| 987 | + help | |
| 988 | 988 | This driver supports the IBM Power Linux family RAID adapters. |
| 989 | 989 | This includes IBM pSeries 5712, 5703, 5709, and 570A, as well |
| 990 | 990 | as IBM iSeries 5702, 5703, 5709, and 570A. |
| @@ -1022,7 +1022,7 @@ config SCSI_NCR53C8XX_DEFAULT_TAGS · 31 unmodified lines | ||
| 1022 | 1022 | int "default tagged command queue depth" |
| 1023 | 1023 | depends on SCSI_ZALON |
| 1024 | 1024 | default "8" |
| 1025 | − ---help--- | |
| 1025 | + help | |
| 1026 | 1026 | "Tagged command queuing" is a feature of SCSI-2 which improves |
| 1027 | 1027 | performance: the host adapter can send several SCSI commands to a |
| 1028 | 1028 | device's queue even if previous commands haven't finished yet. |
| @@ -1048,7 +1048,7 @@ config SCSI_NCR53C8XX_MAX_TAGS · 19 unmodified lines | ||
| 1048 | 1048 | int "maximum number of queued commands" |
| 1049 | 1049 | depends on SCSI_ZALON |
| 1050 | 1050 | default "32" |
| 1051 | − ---help--- | |
| 1051 | + help | |
| 1052 | 1052 | This option allows you to specify the maximum number of commands |
| 1053 | 1053 | that can be queued to any device, when tagged command queuing is |
| 1054 | 1054 | possible. The default value is 32. Minimum is 2, maximum is 64. |
| @@ -1065,7 +1065,7 @@ config SCSI_NCR53C8XX_SYNC · 10 unmodified lines | ||
| 1065 | 1065 | int "synchronous transfers frequency in MHz" |
| 1066 | 1066 | depends on SCSI_ZALON |
| 1067 | 1067 | default "20" |
| 1068 | − ---help--- | |
| 1068 | + help | |
| 1069 | 1069 | The SCSI Parallel Interface-2 Standard defines 5 classes of transfer |
| 1070 | 1070 | rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers |
| 1071 | 1071 | are respectively the maximum data transfer rates in mega-transfers |
| @@ -1108,7 +1108,7 @@ config SCSI_NCR53C8XX_NO_DISCONNECT · 36 unmodified lines | ||
| 1108 | 1108 | config SCSI_QLOGIC_FAS |
| 1109 | 1109 | tristate "Qlogic FAS SCSI support" |
| 1110 | 1110 | depends on ISA && SCSI |
| 1111 | − ---help--- | |
| 1111 | + help | |
| 1112 | 1112 | This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic |
| 1113 | 1113 | FastSCSI! cards as well as any other card based on the FASXX chip |
| 1114 | 1114 | (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards). |
| @@ -1158,14 +1158,14 @@ config SCSI_LPFC · 43 unmodified lines | ||
| 1158 | 1158 | depends on NVME_TARGET_FC || NVME_TARGET_FC=n |
| 1159 | 1159 | depends on NVME_FC || NVME_FC=n |
| 1160 | 1160 | select CRC_T10DIF |
| 1161 | − ---help--- | |
| 1161 | + help | |
| 1162 | 1162 | This lpfc driver supports the Emulex LightPulse |
| 1163 | 1163 | Family of Fibre Channel PCI host adapters. |
| 1164 | 1164 | |
| 1165 | 1165 | config SCSI_LPFC_DEBUG_FS |
| 1166 | 1166 | bool "Emulex LightPulse Fibre Channel debugfs Support" |
| 1167 | 1167 | depends on SCSI_LPFC && DEBUG_FS |
| 1168 | − ---help--- | |
| 1168 | + help | |
| 1169 | 1169 | This makes debugging information from the lpfc driver |
| 1170 | 1170 | available via the debugfs filesystem. |
| 1171 | 1171 | |
| @@ -1173,7 +1173,7 @@ config SCSI_SIM710 · 1 unmodified line | ||
| 1173 | 1173 | tristate "Simple 53c710 SCSI support (Compaq, NCR machines)" |
| 1174 | 1174 | depends on EISA && SCSI |
| 1175 | 1175 | select SCSI_SPI_ATTRS |
| 1176 | − ---help--- | |
| 1176 | + help | |
| 1177 | 1177 | This driver is for NCR53c710 based SCSI host adapters. |
| 1178 | 1178 | |
| 1179 | 1179 | It currently supports Compaq EISA cards. |
| @@ -1181,7 +1181,7 @@ config SCSI_SIM710 · 1 unmodified line | ||
| 1181 | 1181 | config SCSI_DC395x |
| 1182 | 1182 | tristate "Tekram DC395(U/UW/F) and DC315(U) SCSI support" |
| 1183 | 1183 | depends on PCI && SCSI |
| 1184 | − ---help--- | |
| 1184 | + help | |
| 1185 | 1185 | This driver supports PCI SCSI host adapters based on the ASIC |
| 1186 | 1186 | TRM-S1040 chip, e.g Tekram DC395(U/UW/F) and DC315(U) variants. |
| 1187 | 1187 | |
| @@ -1197,7 +1197,7 @@ config SCSI_AM53C974 · 9 unmodified lines | ||
| 1197 | 1197 | tristate "Tekram DC390(T) and Am53/79C974 SCSI support (new driver)" |
| 1198 | 1198 | depends on PCI && SCSI |
| 1199 | 1199 | select SCSI_SPI_ATTRS |
| 1200 | − ---help--- | |
| 1200 | + help | |
| 1201 | 1201 | This driver supports PCI SCSI host adapters based on the Am53C974A |
| 1202 | 1202 | chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard |
| 1203 | 1203 | PCscsi/PCnet (Am53/79C974) solutions. |
| @@ -1224,7 +1224,7 @@ config SCSI_WD719X · 20 unmodified lines | ||
| 1224 | 1224 | tristate "Western Digital WD7193/7197/7296 support" |
| 1225 | 1225 | depends on PCI && SCSI |
| 1226 | 1226 | select EEPROM_93CX6 |
| 1227 | − ---help--- | |
| 1227 | + help | |
| 1228 | 1228 | This is a driver for Western Digital WD7193, WD7197 and WD7296 PCI |
| 1229 | 1229 | SCSI controllers (based on WD33C296A chip). |
| 1230 | 1230 | |
| @@ -1318,7 +1318,7 @@ config A2091_SCSI · 87 unmodified lines | ||
| 1318 | 1318 | config GVP11_SCSI |
| 1319 | 1319 | tristate "GVP Series II WD33C93A support" |
| 1320 | 1320 | depends on ZORRO && SCSI |
| 1321 | − ---help--- | |
| 1321 | + help | |
| 1322 | 1322 | If you have a Great Valley Products Series II SCSI controller, |
| 1323 | 1323 | answer Y. Also say Y if you have a later model of GVP SCSI |
| 1324 | 1324 | controller (such as the GVP A4008 or a Combo board). Otherwise, |
| @@ -1374,7 +1374,7 @@ config ATARI_SCSI · 49 unmodified lines | ||
| 1374 | 1374 | tristate "Atari native SCSI support" |
| 1375 | 1375 | depends on ATARI && SCSI |
| 1376 | 1376 | select SCSI_SPI_ATTRS |
| 1377 | − ---help--- | |
| 1377 | + help | |
| 1378 | 1378 | If you have an Atari with built-in NCR5380 SCSI controller (TT, |
| 1379 | 1379 | Falcon, ...) say Y to get it supported. Of course also, if you have |
| 1380 | 1380 | a compatible SCSI controller (e.g. for Medusa). |
| @@ -1486,7 +1486,7 @@ config SCSI_PMCRAID · 105 unmodified lines | ||
| 1486 | 1486 | tristate "PMC SIERRA Linux MaxRAID adapter support" |
| 1487 | 1487 | depends on PCI && SCSI && NET |
| 1488 | 1488 | select SGL_ALLOC |
| 1489 | − ---help--- | |
| 1489 | + help | |
| 1490 | 1490 | This driver supports the PMC SIERRA MaxRAID adapters. |
| 1491 | 1491 | |
| 1492 | 1492 | config SCSI_PM8001 |
| @@ -15,7 +15,7 @@ config AIC79XX_CMDS_PER_DEVICE · 14 unmodified lines | ||
| 15 | 15 | int "Maximum number of TCQ commands per device" |
| 16 | 16 | depends on SCSI_AIC79XX |
| 17 | 17 | default "32" |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | Specify the number of commands you would like to allocate per SCSI |
| 20 | 20 | device when Tagged Command Queueing (TCQ) is enabled on that device. |
| 21 | 21 | |
| @@ -38,7 +38,7 @@ config AIC79XX_RESET_DELAY_MS · 16 unmodified lines | ||
| 38 | 38 | int "Initial bus reset delay in milli-seconds" |
| 39 | 39 | depends on SCSI_AIC79XX |
| 40 | 40 | default "5000" |
| 41 | − ---help--- | |
| 41 | + help | |
| 42 | 42 | The number of milliseconds to delay after an initial bus reset. |
| 43 | 43 | The bus settle delay following all error recovery actions is |
| 44 | 44 | dictated by the SCSI layer and is not affected by this value. |
| @@ -7,7 +7,7 @@ config SCSI_AIC7XXX · 6 unmodified lines | ||
| 7 | 7 | tristate "Adaptec AIC7xxx Fast -> U160 support" |
| 8 | 8 | depends on (PCI || EISA) && SCSI |
| 9 | 9 | select SCSI_SPI_ATTRS |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | This driver supports all of Adaptec's Fast through Ultra 160 PCI |
| 12 | 12 | based SCSI controllers as well as the aic7770 based EISA and VLB |
| 13 | 13 | SCSI controllers (the 274x and 284x series). For AAA and ARO based |
| @@ -20,7 +20,7 @@ config AIC7XXX_CMDS_PER_DEVICE · 6 unmodified lines | ||
| 20 | 20 | int "Maximum number of TCQ commands per device" |
| 21 | 21 | depends on SCSI_AIC7XXX |
| 22 | 22 | default "32" |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | Specify the number of commands you would like to allocate per SCSI |
| 25 | 25 | device when Tagged Command Queueing (TCQ) is enabled on that device. |
| 26 | 26 | |
| @@ -43,7 +43,7 @@ config AIC7XXX_RESET_DELAY_MS · 16 unmodified lines | ||
| 43 | 43 | int "Initial bus reset delay in milli-seconds" |
| 44 | 44 | depends on SCSI_AIC7XXX |
| 45 | 45 | default "5000" |
| 46 | − ---help--- | |
| 46 | + help | |
| 47 | 47 | The number of milliseconds to delay after an initial bus reset. |
| 48 | 48 | The bus settle delay following all error recovery actions is |
| 49 | 49 | dictated by the SCSI layer and is not affected by this value. |
| @@ -9,5 +9,5 @@ config SCSI_BNX2X_FCOE · 8 unmodified lines | ||
| 9 | 9 | select ETHERNET |
| 10 | 10 | select NET_VENDOR_BROADCOM |
| 11 | 11 | select CNIC |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | This driver supports FCoE offload for the QLogic devices. |
| @@ -9,6 +9,6 @@ config SCSI_BNX2_ISCSI · 8 unmodified lines | ||
| 9 | 9 | select ETHERNET |
| 10 | 10 | select NET_VENDOR_BROADCOM |
| 11 | 11 | select CNIC |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | This driver supports iSCSI offload for the QLogic NetXtreme II |
| 14 | 14 | devices. |
| @@ -8,5 +8,5 @@ config SCSI_CXGB3_ISCSI · 7 unmodified lines | ||
| 8 | 8 | select CHELSIO_T3 |
| 9 | 9 | select CHELSIO_LIB |
| 10 | 10 | select SCSI_ISCSI_ATTRS |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | This driver supports iSCSI offload for the Chelsio T3 devices. |
| @@ -8,5 +8,5 @@ config SCSI_CXGB4_ISCSI · 7 unmodified lines | ||
| 8 | 8 | select CHELSIO_T4 |
| 9 | 9 | select CHELSIO_LIB |
| 10 | 10 | select SCSI_ISCSI_ATTRS |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | This driver supports iSCSI offload for the Chelsio T4 devices. |
| @@ -2,5 +2,5 @@ · 1 unmodified line | ||
| 2 | 2 | config SCSI_ESAS2R |
| 3 | 3 | tristate "ATTO Technology's ExpressSAS RAID adapter driver" |
| 4 | 4 | depends on PCI && SCSI |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This driver supports the ATTO ExpressSAS R6xx SAS/SATA RAID controllers. |
| @@ -46,7 +46,7 @@ config SCSI_MPT3SAS · 45 unmodified lines | ||
| 46 | 46 | select SCSI_SAS_ATTRS |
| 47 | 47 | select RAID_ATTRS |
| 48 | 48 | select IRQ_POLL |
| 49 | − ---help--- | |
| 49 | + help | |
| 50 | 50 | This driver supports PCI-Express SAS 12Gb/s Host Adapters. |
| 51 | 51 | |
| 52 | 52 | config SCSI_MPT2SAS_MAX_SGE |
| @@ -54,7 +54,7 @@ config SCSI_MPT2SAS_MAX_SGE · 1 unmodified line | ||
| 54 | 54 | depends on PCI && SCSI && SCSI_MPT3SAS |
| 55 | 55 | default "128" |
| 56 | 56 | range 16 256 |
| 57 | − ---help--- | |
| 57 | + help | |
| 58 | 58 | This option allows you to specify the maximum number of scatter- |
| 59 | 59 | gather entries per I/O. The driver default is 128, which matches |
| 60 | 60 | MAX_PHYS_SEGMENTS in most kernels. However in SuSE kernels this |
| @@ -66,7 +66,7 @@ config SCSI_MPT3SAS_MAX_SGE · 5 unmodified lines | ||
| 66 | 66 | depends on PCI && SCSI && SCSI_MPT3SAS |
| 67 | 67 | default "128" |
| 68 | 68 | range 16 256 |
| 69 | − ---help--- | |
| 69 | + help | |
| 70 | 70 | This option allows you to specify the maximum number of scatter- |
| 71 | 71 | gather entries per I/O. The driver default is 128, which matches |
| 72 | 72 | MAX_PHYS_SEGMENTS in most kernels. However in SuSE kernels this |
| @@ -78,6 +78,6 @@ config SCSI_MPT2SAS · 5 unmodified lines | ||
| 78 | 78 | default n |
| 79 | 79 | select SCSI_MPT3SAS |
| 80 | 80 | depends on PCI && SCSI |
| 81 | − ---help--- | |
| 81 | + help | |
| 82 | 82 | Dummy config option for backwards compatiblity: configure the MPT3SAS |
| 83 | 83 | driver instead. |
| @@ -7,6 +7,6 @@ config QEDF · 6 unmodified lines | ||
| 7 | 7 | depends on LIBFCOE |
| 8 | 8 | select QED_LL2 |
| 9 | 9 | select QED_FCOE |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | This driver supports FCoE offload for the QLogic FastLinQ |
| 12 | 12 | 41000 Series Converged Network Adapters. |
| @@ -8,6 +8,6 @@ config QEDI · 7 unmodified lines | ||
| 8 | 8 | select QED_OOO |
| 9 | 9 | select QED_ISCSI |
| 10 | 10 | select ISCSI_BOOT_SYSFS |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | This driver supports iSCSI offload for the QLogic FastLinQ |
| 13 | 13 | 41000 Series Converged Network Adapters. |
| @@ -6,7 +6,7 @@ config SCSI_QLA_FC · 5 unmodified lines | ||
| 6 | 6 | depends on NVME_FC || !NVME_FC |
| 7 | 7 | select FW_LOADER |
| 8 | 8 | select BTREE |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This qla2xxx driver supports all QLogic Fibre Channel |
| 11 | 11 | PCI and PCIe host adapters. |
| 12 | 12 | |
| @@ -37,14 +37,14 @@ config TCM_QLA2XXX · 24 unmodified lines | ||
| 37 | 37 | depends on LIBFC |
| 38 | 38 | select BTREE |
| 39 | 39 | default n |
| 40 | − ---help--- | |
| 40 | + help | |
| 41 | 41 | Say Y here to enable the TCM_QLA2XXX fabric module for QLogic 24xx+ series target mode HBAs |
| 42 | 42 | |
| 43 | 43 | if TCM_QLA2XXX |
| 44 | 44 | config TCM_QLA2XXX_DEBUG |
| 45 | 45 | bool "TCM_QLA2XXX fabric module DEBUG mode for QLogic 24xx+ series target mode HBAs" |
| 46 | 46 | default n |
| 47 | − ---help--- | |
| 47 | + help | |
| 48 | 48 | Say Y here to enable the TCM_QLA2XXX fabric module DEBUG for QLogic 24xx+ series target mode HBAs |
| 49 | 49 | This will include code to enable the SCSI command jammer |
| 50 | 50 | endif |
| @@ -4,6 +4,6 @@ config SCSI_QLA_ISCSI · 3 unmodified lines | ||
| 4 | 4 | depends on PCI && SCSI && NET |
| 5 | 5 | select SCSI_ISCSI_ATTRS |
| 6 | 6 | select ISCSI_BOOT_SYSFS |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | This driver supports the QLogic 40xx (ISP4XXX), 8022 (ISP82XX) |
| 9 | 9 | and 8032 (ISP83XX) iSCSI host adapter family. |
| @@ -42,7 +42,7 @@ config SCSI_SMARTPQI · 41 unmodified lines | ||
| 42 | 42 | depends on PCI && SCSI && !S390 |
| 43 | 43 | select SCSI_SAS_ATTRS |
| 44 | 44 | select RAID_ATTRS |
| 45 | − ---help--- | |
| 45 | + help | |
| 46 | 46 | This driver supports Microsemi PQI controllers. |
| 47 | 47 | |
| 48 | 48 | <http://www.microsemi.com> |
| @@ -38,7 +38,7 @@ config SCSI_UFSHCD · 37 unmodified lines | ||
| 38 | 38 | select PM_DEVFREQ |
| 39 | 39 | select DEVFREQ_GOV_SIMPLE_ONDEMAND |
| 40 | 40 | select NLS |
| 41 | − ---help--- | |
| 41 | + help | |
| 42 | 42 | This selects the support for UFS devices in Linux, say Y and make |
| 43 | 43 | sure that you know the name of your UFS host adapter (the card |
| 44 | 44 | inside your computer that "speaks" the UFS protocol, also |
| @@ -53,7 +53,7 @@ config SCSI_UFSHCD · 8 unmodified lines | ||
| 53 | 53 | config SCSI_UFSHCD_PCI |
| 54 | 54 | tristate "PCI bus based UFS Controller support" |
| 55 | 55 | depends on SCSI_UFSHCD && PCI |
| 56 | − ---help--- | |
| 56 | + help | |
| 57 | 57 | This selects the PCI UFS Host Controller Interface. Select this if |
| 58 | 58 | you have UFS Host Controller with PCI Interface. |
| 59 | 59 | |
| @@ -64,7 +64,7 @@ config SCSI_UFSHCD_PCI · 4 unmodified lines | ||
| 64 | 64 | config SCSI_UFS_DWC_TC_PCI |
| 65 | 65 | tristate "DesignWare pci support using a G210 Test Chip" |
| 66 | 66 | depends on SCSI_UFSHCD_PCI |
| 67 | − ---help--- | |
| 67 | + help | |
| 68 | 68 | Synopsys Test Chip is a PHY for prototyping purposes. |
| 69 | 69 | |
| 70 | 70 | If unsure, say N. |
| @@ -72,7 +72,7 @@ config SCSI_UFS_DWC_TC_PCI · 1 unmodified line | ||
| 72 | 72 | config SCSI_UFSHCD_PLATFORM |
| 73 | 73 | tristate "Platform bus based UFS Controller support" |
| 74 | 74 | depends on SCSI_UFSHCD |
| 75 | − ---help--- | |
| 75 | + help | |
| 76 | 76 | This selects the UFS host controller support. Select this if |
| 77 | 77 | you have an UFS controller on Platform bus. |
| 78 | 78 | |
| @@ -91,7 +91,7 @@ config SCSI_UFS_CDNS_PLATFORM · 12 unmodified lines | ||
| 91 | 91 | config SCSI_UFS_DWC_TC_PLATFORM |
| 92 | 92 | tristate "DesignWare platform support using a G210 Test Chip" |
| 93 | 93 | depends on SCSI_UFSHCD_PLATFORM |
| 94 | − ---help--- | |
| 94 | + help | |
| 95 | 95 | Synopsys Test Chip is a PHY for prototyping purposes. |
| 96 | 96 | |
| 97 | 97 | If unsure, say N. |
| @@ -126,7 +126,7 @@ config SCSI_UFS_MEDIATEK · 28 unmodified lines | ||
| 126 | 126 | config SCSI_UFS_HISI |
| 127 | 127 | tristate "Hisilicon specific hooks to UFS controller platform driver" |
| 128 | 128 | depends on (ARCH_HISI || COMPILE_TEST) && SCSI_UFSHCD_PLATFORM |
| 129 | − ---help--- | |
| 129 | + help | |
| 130 | 130 | This selects the Hisilicon specific additions to UFSHCD platform driver. |
| 131 | 131 | |
| 132 | 132 | Select this if you have UFS controller on Hisilicon chipset. |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | |
| 6 | 6 | menuconfig SFI |
| 7 | 7 | bool "SFI (Simple Firmware Interface) Support" |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | The Simple Firmware Interface (SFI) provides a lightweight method |
| 10 | 10 | for platform firmware to pass information to the operating system |
| 11 | 11 | via static tables in memory. Kernel SFI support is required to |
| @@ -8,7 +8,7 @@ config SOC_ASPEED · 7 unmodified lines | ||
| 8 | 8 | config ASPEED_LPC_CTRL |
| 9 | 9 | depends on SOC_ASPEED && REGMAP && MFD_SYSCON |
| 10 | 10 | tristate "Aspeed ast2400/2500 HOST LPC to BMC bridge control" |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | Control Aspeed ast2400/2500 HOST LPC to BMC mappings through |
| 13 | 13 | ioctl()s, the driver also provides a read/write interface to a BMC ram |
| 14 | 14 | region where the host LPC read/write region can be buffered. |
| @@ -1,7 +1,7 @@ | ||
| 1 | 1 | # SPDX-License-Identifier: GPL-2.0 |
| 2 | 2 | menuconfig STAGING |
| 3 | 3 | bool "Staging drivers" |
| 4 | − ---help--- | |
| 4 | + help | |
| 5 | 5 | This option allows you to select a number of drivers that are |
| 6 | 6 | not of the "normal" Linux kernel quality level. These drivers |
| 7 | 7 | are placed here in order to get a wider audience to make use of |
| @@ -4,7 +4,7 @@ if GREYBUS · 3 unmodified lines | ||
| 4 | 4 | config GREYBUS_AUDIO |
| 5 | 5 | tristate "Greybus Audio Class driver" |
| 6 | 6 | depends on SOUND |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | Select this option if you have a device that follows the |
| 9 | 9 | Greybus Audio Class specification. |
| 10 | 10 | |
| @@ -13,7 +13,7 @@ config GREYBUS_AUDIO · 2 unmodified lines | ||
| 13 | 13 | |
| 14 | 14 | config GREYBUS_BOOTROM |
| 15 | 15 | tristate "Greybus Bootrom Class driver" |
| 16 | − ---help--- | |
| 16 | + help | |
| 17 | 17 | Select this option if you have a device that follows the |
| 18 | 18 | Greybus Bootrom Class specification. |
| 19 | 19 | |
| @@ -23,7 +23,7 @@ config GREYBUS_BOOTROM · 3 unmodified lines | ||
| 23 | 23 | config GREYBUS_CAMERA |
| 24 | 24 | tristate "Greybus Camera Class driver" |
| 25 | 25 | depends on MEDIA_SUPPORT && LEDS_CLASS_FLASH && BROKEN |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | Select this option if you have a device that follows the |
| 28 | 28 | Greybus Camera Class specification. |
| 29 | 29 | |
| @@ -33,7 +33,7 @@ config GREYBUS_CAMERA · 3 unmodified lines | ||
| 33 | 33 | config GREYBUS_FIRMWARE |
| 34 | 34 | tristate "Greybus Firmware Download Class driver" |
| 35 | 35 | depends on SPI |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | Select this option if you have a device that follows the |
| 38 | 38 | Greybus Firmware Download Class specification. |
| 39 | 39 | |
| @@ -43,7 +43,7 @@ config GREYBUS_FIRMWARE · 3 unmodified lines | ||
| 43 | 43 | config GREYBUS_HID |
| 44 | 44 | tristate "Greybus HID Class driver" |
| 45 | 45 | depends on HID && INPUT |
| 46 | − ---help--- | |
| 46 | + help | |
| 47 | 47 | Select this option if you have a device that follows the |
| 48 | 48 | Greybus HID Class specification. |
| 49 | 49 | |
| @@ -53,7 +53,7 @@ config GREYBUS_HID · 3 unmodified lines | ||
| 53 | 53 | config GREYBUS_LIGHT |
| 54 | 54 | tristate "Greybus LED Class driver" |
| 55 | 55 | depends on LEDS_CLASS |
| 56 | − ---help--- | |
| 56 | + help | |
| 57 | 57 | Select this option if you have a device that follows the |
| 58 | 58 | Greybus LED Class specification. |
| 59 | 59 | |
| @@ -62,7 +62,7 @@ config GREYBUS_LIGHT · 2 unmodified lines | ||
| 62 | 62 | |
| 63 | 63 | config GREYBUS_LOG |
| 64 | 64 | tristate "Greybus Debug Log Class driver" |
| 65 | − ---help--- | |
| 65 | + help | |
| 66 | 66 | Select this option if you have a device that follows the |
| 67 | 67 | Greybus Debug Log Class specification. |
| 68 | 68 | |
| @@ -71,7 +71,7 @@ config GREYBUS_LOG · 2 unmodified lines | ||
| 71 | 71 | |
| 72 | 72 | config GREYBUS_LOOPBACK |
| 73 | 73 | tristate "Greybus Loopback Class driver" |
| 74 | − ---help--- | |
| 74 | + help | |
| 75 | 75 | Select this option if you have a device that follows the |
| 76 | 76 | Greybus Debug Log Class specification. |
| 77 | 77 | |
| @@ -81,7 +81,7 @@ config GREYBUS_LOOPBACK · 3 unmodified lines | ||
| 81 | 81 | config GREYBUS_POWER |
| 82 | 82 | tristate "Greybus Powersupply Class driver" |
| 83 | 83 | depends on POWER_SUPPLY |
| 84 | − ---help--- | |
| 84 | + help | |
| 85 | 85 | Select this option if you have a device that follows the |
| 86 | 86 | Greybus Powersupply Class specification. |
| 87 | 87 | |
| @@ -90,7 +90,7 @@ config GREYBUS_POWER · 2 unmodified lines | ||
| 90 | 90 | |
| 91 | 91 | config GREYBUS_RAW |
| 92 | 92 | tristate "Greybus Raw Class driver" |
| 93 | − ---help--- | |
| 93 | + help | |
| 94 | 94 | Select this option if you have a device that follows the |
| 95 | 95 | Greybus Raw Class specification. |
| 96 | 96 | |
| @@ -99,7 +99,7 @@ config GREYBUS_RAW · 2 unmodified lines | ||
| 99 | 99 | |
| 100 | 100 | config GREYBUS_VIBRATOR |
| 101 | 101 | tristate "Greybus Vibrator Motor Class driver" |
| 102 | − ---help--- | |
| 102 | + help | |
| 103 | 103 | Select this option if you have a device that follows the |
| 104 | 104 | Greybus Vibrator Motor Class specification. |
| 105 | 105 | |
| @@ -108,7 +108,7 @@ config GREYBUS_VIBRATOR · 2 unmodified lines | ||
| 108 | 108 | |
| 109 | 109 | menuconfig GREYBUS_BRIDGED_PHY |
| 110 | 110 | tristate "Greybus Bridged PHY Class drivers" |
| 111 | − ---help--- | |
| 111 | + help | |
| 112 | 112 | Select this option to pick from a variety of Greybus Bridged |
| 113 | 113 | PHY class drivers. These drivers emulate a number of |
| 114 | 114 | different "traditional" busses by tunneling them over Greybus. |
| @@ -123,7 +123,7 @@ config GREYBUS_GPIO · 8 unmodified lines | ||
| 123 | 123 | tristate "Greybus GPIO Bridged PHY driver" |
| 124 | 124 | depends on GPIOLIB |
| 125 | 125 | select GPIOLIB_IRQCHIP |
| 126 | − ---help--- | |
| 126 | + help | |
| 127 | 127 | Select this option if you have a device that follows the |
| 128 | 128 | Greybus GPIO Bridged PHY Class specification. |
| 129 | 129 | |
| @@ -133,7 +133,7 @@ config GREYBUS_GPIO · 3 unmodified lines | ||
| 133 | 133 | config GREYBUS_I2C |
| 134 | 134 | tristate "Greybus I2C Bridged PHY driver" |
| 135 | 135 | depends on I2C |
| 136 | − ---help--- | |
| 136 | + help | |
| 137 | 137 | Select this option if you have a device that follows the |
| 138 | 138 | Greybus I2C Bridged PHY Class specification. |
| 139 | 139 | |
| @@ -143,7 +143,7 @@ config GREYBUS_I2C · 3 unmodified lines | ||
| 143 | 143 | config GREYBUS_PWM |
| 144 | 144 | tristate "Greybus PWM Bridged PHY driver" |
| 145 | 145 | depends on PWM |
| 146 | − ---help--- | |
| 146 | + help | |
| 147 | 147 | Select this option if you have a device that follows the |
| 148 | 148 | Greybus PWM Bridged PHY Class specification. |
| 149 | 149 | |
| @@ -153,7 +153,7 @@ config GREYBUS_PWM · 3 unmodified lines | ||
| 153 | 153 | config GREYBUS_SDIO |
| 154 | 154 | tristate "Greybus SDIO Bridged PHY driver" |
| 155 | 155 | depends on MMC |
| 156 | − ---help--- | |
| 156 | + help | |
| 157 | 157 | Select this option if you have a device that follows the |
| 158 | 158 | Greybus SDIO Bridged PHY Class specification. |
| 159 | 159 | |
| @@ -163,7 +163,7 @@ config GREYBUS_SDIO · 3 unmodified lines | ||
| 163 | 163 | config GREYBUS_SPI |
| 164 | 164 | tristate "Greybus SPI Bridged PHY driver" |
| 165 | 165 | depends on SPI |
| 166 | − ---help--- | |
| 166 | + help | |
| 167 | 167 | Select this option if you have a device that follows the |
| 168 | 168 | Greybus SPI Bridged PHY Class specification. |
| 169 | 169 | |
| @@ -173,7 +173,7 @@ config GREYBUS_SPI · 3 unmodified lines | ||
| 173 | 173 | config GREYBUS_UART |
| 174 | 174 | tristate "Greybus UART Bridged PHY driver" |
| 175 | 175 | depends on TTY |
| 176 | − ---help--- | |
| 176 | + help | |
| 177 | 177 | Select this option if you have a device that follows the |
| 178 | 178 | Greybus UART Bridged PHY Class specification. |
| 179 | 179 | |
| @@ -183,7 +183,7 @@ config GREYBUS_UART · 3 unmodified lines | ||
| 183 | 183 | config GREYBUS_USB |
| 184 | 184 | tristate "Greybus USB Host Bridged PHY driver" |
| 185 | 185 | depends on USB |
| 186 | − ---help--- | |
| 186 | + help | |
| 187 | 187 | Select this option if you have a device that follows the |
| 188 | 188 | Greybus USB Host Bridged PHY Class specification. |
| 189 | 189 | |
| @@ -195,7 +195,7 @@ endif # GREYBUS_BRIDGED_PHY · 5 unmodified lines | ||
| 195 | 195 | config GREYBUS_ARCHE |
| 196 | 196 | tristate "Greybus Arche Platform driver" |
| 197 | 197 | depends on USB_HSIC_USB3613 || COMPILE_TEST |
| 198 | − ---help--- | |
| 198 | + help | |
| 199 | 199 | Select this option if you have an Arche device. |
| 200 | 200 | |
| 201 | 201 | To compile this code as a module, chose M here: the module |
| @@ -15,7 +15,7 @@ config VIDEO_ATOMISP · 14 unmodified lines | ||
| 15 | 15 | depends on PMIC_OPREGION |
| 16 | 16 | select IOSF_MBI |
| 17 | 17 | select VIDEOBUF_VMALLOC |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | Say Y here if your platform supports Intel Atom SoC |
| 20 | 20 | camera imaging subsystem. |
| 21 | 21 | To compile this driver as a module, choose M here: the |
| @@ -9,7 +9,7 @@ config VIDEO_ATOMISP_OV2722 · 8 unmodified lines | ||
| 9 | 9 | tristate "OVT ov2722 sensor support" |
| 10 | 10 | depends on ACPI |
| 11 | 11 | depends on I2C && VIDEO_V4L2 |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | This is a Video4Linux2 sensor-level driver for the OVT |
| 14 | 14 | OV2722 raw camera. |
| 15 | 15 | |
| @@ -21,7 +21,7 @@ config VIDEO_ATOMISP_GC2235 · 5 unmodified lines | ||
| 21 | 21 | tristate "Galaxy gc2235 sensor support" |
| 22 | 22 | depends on ACPI |
| 23 | 23 | depends on I2C && VIDEO_V4L2 |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | This is a Video4Linux2 sensor-level driver for the OVT |
| 26 | 26 | GC2235 raw camera. |
| 27 | 27 | |
| @@ -32,7 +32,7 @@ config VIDEO_ATOMISP_GC2235 · 4 unmodified lines | ||
| 32 | 32 | config VIDEO_ATOMISP_MSRLIST_HELPER |
| 33 | 33 | tristate "Helper library to load, parse and apply large register lists." |
| 34 | 34 | depends on I2C |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | This is a helper library to be used from a sensor driver to load, parse |
| 37 | 37 | and apply large register lists. |
| 38 | 38 | |
| @@ -43,7 +43,7 @@ config VIDEO_ATOMISP_MT9M114 · 4 unmodified lines | ||
| 43 | 43 | tristate "Aptina mt9m114 sensor support" |
| 44 | 44 | depends on ACPI |
| 45 | 45 | depends on I2C && VIDEO_V4L2 |
| 46 | − ---help--- | |
| 46 | + help | |
| 47 | 47 | This is a Video4Linux2 sensor-level driver for the Micron |
| 48 | 48 | mt9m114 1.3 Mpixel camera. |
| 49 | 49 | |
| @@ -55,7 +55,7 @@ config VIDEO_ATOMISP_GC0310 · 5 unmodified lines | ||
| 55 | 55 | tristate "GC0310 sensor support" |
| 56 | 56 | depends on ACPI |
| 57 | 57 | depends on I2C && VIDEO_V4L2 |
| 58 | − ---help--- | |
| 58 | + help | |
| 59 | 59 | This is a Video4Linux2 sensor-level driver for the Galaxycore |
| 60 | 60 | GC0310 0.3MP sensor. |
| 61 | 61 | |
| @@ -63,7 +63,7 @@ config VIDEO_ATOMISP_OV2680 · 1 unmodified line | ||
| 63 | 63 | tristate "Omnivision OV2680 sensor support" |
| 64 | 64 | depends on ACPI |
| 65 | 65 | depends on I2C && VIDEO_V4L2 |
| 66 | − ---help--- | |
| 66 | + help | |
| 67 | 67 | This is a Video4Linux2 sensor-level driver for the Omnivision |
| 68 | 68 | OV2680 raw camera. |
| 69 | 69 | |
| @@ -79,7 +79,7 @@ config VIDEO_ATOMISP_LM3554 · 9 unmodified lines | ||
| 79 | 79 | tristate "LM3554 flash light driver" |
| 80 | 80 | depends on ACPI |
| 81 | 81 | depends on VIDEO_V4L2 && I2C |
| 82 | − ---help--- | |
| 82 | + help | |
| 83 | 83 | This is a Video4Linux2 sub-dev driver for the LM3554 |
| 84 | 84 | flash light driver. |
| 85 | 85 | |
| @@ -3,7 +3,7 @@ config VIDEO_ATOMISP_OV5693 · 2 unmodified lines | ||
| 3 | 3 | tristate "Omnivision ov5693 sensor support" |
| 4 | 4 | depends on ACPI |
| 5 | 5 | depends on I2C && VIDEO_V4L2 |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | This is a Video4Linux2 sensor-level driver for the Micron |
| 8 | 8 | ov5693 5 Mpixel camera. |
| 9 | 9 | |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config MOST_CDEV |
| 7 | 7 | tristate "Cdev" |
| 8 | 8 | |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Say Y here if you want to commumicate via character devices. |
| 11 | 11 | |
| 12 | 12 | To compile this driver as a module, choose M here: the |
| @@ -7,7 +7,7 @@ config MOST_DIM2 · 6 unmodified lines | ||
| 7 | 7 | tristate "DIM2" |
| 8 | 8 | depends on HAS_IOMEM && OF |
| 9 | 9 | |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Say Y here if you want to connect via MediaLB to network transceiver. |
| 12 | 12 | This device driver is platform dependent and needs an additional |
| 13 | 13 | platform driver to be installed. For more information contact |
| @@ -3,6 +3,6 @@ config ISCSI_TARGET_CXGB4 · 2 unmodified lines | ||
| 3 | 3 | tristate "Chelsio iSCSI target offload driver" |
| 4 | 4 | depends on ISCSI_TARGET && CHELSIO_T4 && INET |
| 5 | 5 | select CHELSIO_LIB |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | To compile this driver as module, choose M here: the module |
| 8 | 8 | will be called cxgbit. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config TTY |
| 3 | 3 | bool "Enable TTY" if EXPERT |
| 4 | 4 | default y |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | Allows you to remove TTY support which can save space, and |
| 7 | 7 | blocks features that require TTY from inclusion in the kernel. |
| 8 | 8 | TTY is required for any text terminals or serial port |
| @@ -15,7 +15,7 @@ config VT · 6 unmodified lines | ||
| 15 | 15 | depends on !UML |
| 16 | 16 | select INPUT |
| 17 | 17 | default y |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | If you say Y here, you will get support for terminal devices with |
| 20 | 20 | display and keyboard devices. These are called "virtual" because you |
| 21 | 21 | can run several virtual terminals (also called virtual consoles) on |
| @@ -46,7 +46,7 @@ config CONSOLE_TRANSLATIONS · 24 unmodified lines | ||
| 46 | 46 | depends on VT |
| 47 | 47 | default y |
| 48 | 48 | bool "Enable character translations in console" if EXPERT |
| 49 | − ---help--- | |
| 49 | + help | |
| 50 | 50 | This enables support for font mapping and Unicode translation |
| 51 | 51 | on virtual consoles. |
| 52 | 52 | |
| @@ -54,7 +54,7 @@ config VT_CONSOLE · 1 unmodified line | ||
| 54 | 54 | bool "Support for console on virtual terminal" if EXPERT |
| 55 | 55 | depends on VT |
| 56 | 56 | default y |
| 57 | − ---help--- | |
| 57 | + help | |
| 58 | 58 | The system console is the device which receives all kernel messages |
| 59 | 59 | and warnings and which allows logins in single user mode. If you |
| 60 | 60 | answer Y here, a virtual terminal (the device used to interact with |
| @@ -84,7 +84,7 @@ config HW_CONSOLE · 23 unmodified lines | ||
| 84 | 84 | config VT_HW_CONSOLE_BINDING |
| 85 | 85 | bool "Support for binding and unbinding console drivers" |
| 86 | 86 | depends on HW_CONSOLE |
| 87 | − ---help--- | |
| 87 | + help | |
| 88 | 88 | The virtual terminal is the device that interacts with the physical |
| 89 | 89 | terminal through console drivers. On these systems, at least one |
| 90 | 90 | console driver is loaded. In other configurations, additional console |
| @@ -100,7 +100,7 @@ config VT_HW_CONSOLE_BINDING · 9 unmodified lines | ||
| 100 | 100 | config UNIX98_PTYS |
| 101 | 101 | bool "Unix98 PTY support" if EXPERT |
| 102 | 102 | default y |
| 103 | − ---help--- | |
| 103 | + help | |
| 104 | 104 | A pseudo terminal (PTY) is a software device consisting of two |
| 105 | 105 | halves: a master and a slave. The slave device behaves identical to |
| 106 | 106 | a physical terminal; the master device is used by a process to |
| @@ -123,7 +123,7 @@ config UNIX98_PTYS · 16 unmodified lines | ||
| 123 | 123 | config LEGACY_PTYS |
| 124 | 124 | bool "Legacy (BSD) PTY support" |
| 125 | 125 | default y |
| 126 | − ---help--- | |
| 126 | + help | |
| 127 | 127 | A pseudo terminal (PTY) is a software device consisting of two |
| 128 | 128 | halves: a master and a slave. The slave device behaves identical to |
| 129 | 129 | a physical terminal; the master device is used by a process to |
| @@ -142,7 +142,7 @@ config LEGACY_PTY_COUNT · 12 unmodified lines | ||
| 142 | 142 | depends on LEGACY_PTYS |
| 143 | 143 | range 0 256 |
| 144 | 144 | default "256" |
| 145 | − ---help--- | |
| 145 | + help | |
| 146 | 146 | The maximum number of legacy PTYs that can be used at any one time. |
| 147 | 147 | The default is 256, and should be more than enough. Embedded |
| 148 | 148 | systems may want to reduce this to save memory. |
| @@ -178,7 +178,7 @@ source "drivers/tty/serial/Kconfig" · 29 unmodified lines | ||
| 178 | 178 | config SERIAL_NONSTANDARD |
| 179 | 179 | bool "Non-standard serial port support" |
| 180 | 180 | depends on HAS_IOMEM |
| 181 | − ---help--- | |
| 181 | + help | |
| 182 | 182 | Say Y here if you have any non-standard serial boards -- boards |
| 183 | 183 | which aren't supported using the standard "dumb" serial driver. |
| 184 | 184 | This includes intelligent serial boards such as Cyclades, |
| @@ -211,7 +211,7 @@ config CYCLADES · 26 unmodified lines | ||
| 211 | 211 | tristate "Cyclades async mux support" |
| 212 | 212 | depends on SERIAL_NONSTANDARD && (PCI || ISA) |
| 213 | 213 | select FW_LOADER |
| 214 | − ---help--- | |
| 214 | + help | |
| 215 | 215 | This driver supports Cyclades Z and Y multiserial boards. |
| 216 | 216 | You would need something like this to connect more than two modems to |
| 217 | 217 | your Linux box, for instance in order to become a dial-in server. |
| @@ -9,7 +9,7 @@ config SERIAL_8250 · 8 unmodified lines | ||
| 9 | 9 | depends on !S390 |
| 10 | 10 | select SERIAL_CORE |
| 11 | 11 | select SERIAL_MCTRL_GPIO if GPIOLIB |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | This selects whether you want to include the driver for the standard |
| 14 | 14 | serial ports. The standard answer is Y. People who might say N |
| 15 | 15 | here are those that are setting up dedicated Ethernet WWW/FTP |
| @@ -39,7 +39,7 @@ config SERIAL_8250_DEPRECATED_OPTIONS · 23 unmodified lines | ||
| 39 | 39 | bool "Support 8250_core.* kernel options (DEPRECATED)" |
| 40 | 40 | depends on SERIAL_8250 |
| 41 | 41 | default y |
| 42 | − ---help--- | |
| 42 | + help | |
| 43 | 43 | In 3.7 we renamed 8250 to 8250_core by mistake, so now we have to |
| 44 | 44 | accept kernel parameters in both forms like 8250_core.nr_uarts=4 and |
| 45 | 45 | 8250.nr_uarts=4. We now renamed the module back to 8250, but if |
| @@ -56,7 +56,7 @@ config SERIAL_8250_PNP · 10 unmodified lines | ||
| 56 | 56 | bool "8250/16550 PNP device support" if EXPERT |
| 57 | 57 | depends on SERIAL_8250 && PNP |
| 58 | 58 | default y |
| 59 | − ---help--- | |
| 59 | + help | |
| 60 | 60 | This builds standard PNP serial support. You may be able to |
| 61 | 61 | disable this feature if you only need legacy serial support. |
| 62 | 62 | |
| @@ -74,7 +74,7 @@ config SERIAL_8250_16550A_VARIANTS · 11 unmodified lines | ||
| 74 | 74 | config SERIAL_8250_FINTEK |
| 75 | 75 | bool "Support for Fintek F81216A LPC to 4 UART RS485 API" |
| 76 | 76 | depends on SERIAL_8250 |
| 77 | − ---help--- | |
| 77 | + help | |
| 78 | 78 | Selecting this option will add support for the RS485 capabilities |
| 79 | 79 | of the Fintek F81216A LPC to 4 UART. |
| 80 | 80 | |
| @@ -88,7 +88,7 @@ config SERIAL_8250_CONSOLE · 7 unmodified lines | ||
| 88 | 88 | depends on SERIAL_8250=y |
| 89 | 89 | select SERIAL_CORE_CONSOLE |
| 90 | 90 | select SERIAL_EARLYCON |
| 91 | − ---help--- | |
| 91 | + help | |
| 92 | 92 | If you say Y here, it will be possible to use a serial port as the |
| 93 | 93 | system console (the system console is the device which receives all |
| 94 | 94 | kernel messages and warnings and which allows logins in single user |
| @@ -158,7 +158,7 @@ config SERIAL_8250_HP300 · 63 unmodified lines | ||
| 158 | 158 | config SERIAL_8250_CS |
| 159 | 159 | tristate "8250/16550 PCMCIA device support" |
| 160 | 160 | depends on PCMCIA && SERIAL_8250 |
| 161 | − ---help--- | |
| 161 | + help | |
| 162 | 162 | Say Y here to enable support for 16-bit PCMCIA serial devices, |
| 163 | 163 | including serial port cards, modems, and the modem functions of |
| 164 | 164 | multi-function Ethernet/modem cards. (PCMCIA- or PC-cards are |
| @@ -32,7 +32,7 @@ config SERIAL_AMBA_PL010_CONSOLE · 31 unmodified lines | ||
| 32 | 32 | bool "Support for console on AMBA serial port" |
| 33 | 33 | depends on SERIAL_AMBA_PL010=y |
| 34 | 34 | select SERIAL_CORE_CONSOLE |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | Say Y here if you wish to use an AMBA PrimeCell UART as the system |
| 37 | 37 | console (the system console is the device which receives all kernel |
| 38 | 38 | messages and warnings and which allows logins in single user mode). |
| @@ -60,7 +60,7 @@ config SERIAL_AMBA_PL011_CONSOLE · 21 unmodified lines | ||
| 60 | 60 | depends on SERIAL_AMBA_PL011=y |
| 61 | 61 | select SERIAL_CORE_CONSOLE |
| 62 | 62 | select SERIAL_EARLYCON |
| 63 | − ---help--- | |
| 63 | + help | |
| 64 | 64 | Say Y here if you wish to use an AMBA PrimeCell UART as the system |
| 65 | 65 | console (the system console is the device which receives all kernel |
| 66 | 66 | messages and warnings and which allows logins in single user mode). |
| @@ -101,7 +101,7 @@ config SERIAL_SB1250_DUART · 34 unmodified lines | ||
| 101 | 101 | depends on SIBYTE_SB1xxx_SOC=y |
| 102 | 102 | select SERIAL_CORE |
| 103 | 103 | default y |
| 104 | − ---help--- | |
| 104 | + help | |
| 105 | 105 | Support for the asynchronous serial interface (DUART) included in |
| 106 | 106 | the BCM1250 and derived System-On-a-Chip (SOC) devices. Note that |
| 107 | 107 | the letter D in DUART stands for "dual", which is how the device |
| @@ -116,7 +116,7 @@ config SERIAL_SB1250_DUART_CONSOLE · 8 unmodified lines | ||
| 116 | 116 | depends on SERIAL_SB1250_DUART=y |
| 117 | 117 | select SERIAL_CORE_CONSOLE |
| 118 | 118 | default y |
| 119 | − ---help--- | |
| 119 | + help | |
| 120 | 120 | If you say Y here, it will be possible to use a serial port as the |
| 121 | 121 | system console (the system console is the device which receives all |
| 122 | 122 | kernel messages and warnings and which allows logins in single user |
| @@ -322,7 +322,7 @@ config SERIAL_TEGRA_TCU_CONSOLE · 199 unmodified lines | ||
| 322 | 322 | depends on SERIAL_TEGRA_TCU=y |
| 323 | 323 | select SERIAL_CORE_CONSOLE |
| 324 | 324 | default y |
| 325 | − ---help--- | |
| 325 | + help | |
| 326 | 326 | If you say Y here, it will be possible to use a the Tegra TCU as the |
| 327 | 327 | system console (the system console is the device which receives all |
| 328 | 328 | kernel messages and warnings and which allows logins in single user |
| @@ -355,7 +355,7 @@ config SERIAL_DZ · 26 unmodified lines | ||
| 355 | 355 | depends on MACH_DECSTATION && 32BIT |
| 356 | 356 | select SERIAL_CORE |
| 357 | 357 | default y |
| 358 | − ---help--- | |
| 358 | + help | |
| 359 | 359 | DZ11-family serial controllers for DECstations and VAXstations, |
| 360 | 360 | including the DC7085, M7814, and M7819. |
| 361 | 361 | |
| @@ -364,7 +364,7 @@ config SERIAL_DZ_CONSOLE · 2 unmodified lines | ||
| 364 | 364 | depends on SERIAL_DZ=y |
| 365 | 365 | select SERIAL_CORE_CONSOLE |
| 366 | 366 | default y |
| 367 | − ---help--- | |
| 367 | + help | |
| 368 | 368 | If you say Y here, it will be possible to use a serial port as the |
| 369 | 369 | system console (the system console is the device which receives all |
| 370 | 370 | kernel messages and warnings and which allows logins in single user |
| @@ -380,7 +380,7 @@ config SERIAL_ZS · 9 unmodified lines | ||
| 380 | 380 | depends on MACH_DECSTATION |
| 381 | 381 | select SERIAL_CORE |
| 382 | 382 | default y |
| 383 | − ---help--- | |
| 383 | + help | |
| 384 | 384 | Support for the Zilog 85C350 serial communications controller used |
| 385 | 385 | for serial ports in newer DECstation systems. These include the |
| 386 | 386 | DECsystem 5900 and all models of the DECstation and DECsystem 5000 |
| @@ -394,7 +394,7 @@ config SERIAL_ZS_CONSOLE · 7 unmodified lines | ||
| 394 | 394 | depends on SERIAL_ZS=y |
| 395 | 395 | select SERIAL_CORE_CONSOLE |
| 396 | 396 | default y |
| 397 | − ---help--- | |
| 397 | + help | |
| 398 | 398 | If you say Y here, it will be possible to use a serial port as the |
| 399 | 399 | system console (the system console is the device which receives all |
| 400 | 400 | kernel messages and warnings and which allows logins in single user |
| @@ -588,7 +588,7 @@ config SERIAL_MUX · 187 unmodified lines | ||
| 588 | 588 | depends on GSC |
| 589 | 589 | select SERIAL_CORE |
| 590 | 590 | default y |
| 591 | − ---help--- | |
| 591 | + help | |
| 592 | 592 | Saying Y here will enable the hardware MUX serial driver for |
| 593 | 593 | the Nova, K class systems and D class with a 'remote control card'. |
| 594 | 594 | The hardware MUX is not 8250/16550 compatible therefore the |
| @@ -1116,7 +1116,7 @@ config SERIAL_TIMBERDALE · 521 unmodified lines | ||
| 1116 | 1116 | tristate "Support for timberdale UART" |
| 1117 | 1117 | select SERIAL_CORE |
| 1118 | 1118 | depends on X86_32 || COMPILE_TEST |
| 1119 | − ---help--- | |
| 1119 | + help | |
| 1120 | 1120 | Add support for UART controller on timberdale. |
| 1121 | 1121 | |
| 1122 | 1122 | config SERIAL_BCM63XX |
| @@ -1145,7 +1145,7 @@ config SERIAL_GRLIB_GAISLER_APBUART · 22 unmodified lines | ||
| 1145 | 1145 | tristate "GRLIB APBUART serial support" |
| 1146 | 1146 | depends on OF && SPARC |
| 1147 | 1147 | select SERIAL_CORE |
| 1148 | − ---help--- | |
| 1148 | + help | |
| 1149 | 1149 | Add support for the GRLIB APBUART serial port. |
| 1150 | 1150 | |
| 1151 | 1151 | config SERIAL_GRLIB_GAISLER_APBUART_CONSOLE |
| @@ -30,7 +30,7 @@ menuconfig USB_SUPPORT · 29 unmodified lines | ||
| 30 | 30 | bool "USB support" |
| 31 | 31 | depends on HAS_IOMEM |
| 32 | 32 | default y |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | This option adds core support for Universal Serial Bus (USB). |
| 35 | 35 | You will also need drivers from the following menu to make use of it. |
| 36 | 36 | |
| @@ -47,7 +47,7 @@ config USB · 10 unmodified lines | ||
| 47 | 47 | select GENERIC_ALLOCATOR |
| 48 | 48 | select USB_COMMON |
| 49 | 49 | select NLS # for UTF-8 strings |
| 50 | − ---help--- | |
| 50 | + help | |
| 51 | 51 | Universal Serial Bus (USB) is a specification for a serial bus |
| 52 | 52 | subsystem which offers higher speeds and more features than the |
| 53 | 53 | traditional PC serial port. The bus supplies power to peripherals |
| @@ -83,7 +83,7 @@ config USB_PCI · 29 unmodified lines | ||
| 83 | 83 | bool "PCI based USB host interface" |
| 84 | 84 | depends on PCI |
| 85 | 85 | default y |
| 86 | − ---help--- | |
| 86 | + help | |
| 87 | 87 | Many embedded system SOCs (e.g. freescale T2080) have both |
| 88 | 88 | PCI and USB modules with the USB module directly controlled by |
| 89 | 89 | registers and having no relationship to the PCI module. |
| @@ -133,7 +133,7 @@ config USB_USS720 · 43 unmodified lines | ||
| 133 | 133 | tristate "USS720 parport driver" |
| 134 | 134 | depends on PARPORT |
| 135 | 135 | select PARPORT_NOT_PC |
| 136 | − ---help--- | |
| 136 | + help | |
| 137 | 137 | This driver is for USB parallel port adapters that use the Lucent |
| 138 | 138 | Technologies USS-720 chip. These cables are plugged into your USB |
| 139 | 139 | port and provide USB compatibility to peripherals designed with |
| @@ -7,7 +7,7 @@ comment "USB Device Class drivers" · 6 unmodified lines | ||
| 7 | 7 | config USB_ACM |
| 8 | 8 | tristate "USB Modem (CDC ACM) support" |
| 9 | 9 | depends on TTY |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | This driver supports USB modems and ISDN adapters which support the |
| 12 | 12 | Communication Device Class Abstract Control Model interface. |
| 13 | 13 | Please read <file:Documentation/usb/acm.rst> for details. |
| @@ -30,7 +30,7 @@ config USB_PRINTER · 16 unmodified lines | ||
| 30 | 30 | |
| 31 | 31 | config USB_WDM |
| 32 | 32 | tristate "USB Wireless Device Management support" |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | This driver supports the WMC Device Management functionality |
| 35 | 35 | of cell phones compliant to the CDC WMC specification. You can use |
| 36 | 36 | AT commands over this device. |
| @@ -20,7 +20,7 @@ config USB_C67X00_HCD · 19 unmodified lines | ||
| 20 | 20 | config USB_XHCI_HCD |
| 21 | 21 | tristate "xHCI HCD (USB 3.0) support" |
| 22 | 22 | depends on HAS_DMA && HAS_IOMEM |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | The eXtensible Host Controller Interface (xHCI) is standard for USB 3.0 |
| 25 | 25 | "SuperSpeed" host controller hardware. |
| 26 | 26 | |
| @@ -31,7 +31,7 @@ if USB_XHCI_HCD · 4 unmodified lines | ||
| 31 | 31 | config USB_XHCI_DBGCAP |
| 32 | 32 | bool "xHCI support for debug capability" |
| 33 | 33 | depends on TTY |
| 34 | − ---help--- | |
| 34 | + help | |
| 35 | 35 | Say 'Y' to enable the support for the xHCI debug capability. Make |
| 36 | 36 | sure that your xHCI host supports the extended debug capability and |
| 37 | 37 | you want a TTY serial device based on the xHCI debug capability |
| @@ -45,7 +45,7 @@ config USB_XHCI_PCI · 7 unmodified lines | ||
| 45 | 45 | |
| 46 | 46 | config USB_XHCI_PCI_RENESAS |
| 47 | 47 | tristate "Support for additional Renesas xHCI controller with firwmare" |
| 48 | − ---help--- | |
| 48 | + help | |
| 49 | 49 | Say 'Y' to enable the support for the Renesas xHCI controller with |
| 50 | 50 | firwmare. Make sure you have the firwmare for the device and |
| 51 | 51 | installed on your system for this device to work. |
| @@ -54,7 +54,7 @@ config USB_XHCI_PCI_RENESAS · 2 unmodified lines | ||
| 54 | 54 | config USB_XHCI_PLATFORM |
| 55 | 55 | tristate "Generic xHCI driver for a platform device" |
| 56 | 56 | select USB_XHCI_RCAR if ARCH_RENESAS |
| 57 | − ---help--- | |
| 57 | + help | |
| 58 | 58 | Adds an xHCI host driver for a generic platform device, which |
| 59 | 59 | provides a memory space and an irq. |
| 60 | 60 | It is also a prerequisite for platform specific drivers that |
| @@ -73,7 +73,7 @@ config USB_XHCI_MTK · 12 unmodified lines | ||
| 73 | 73 | tristate "xHCI support for MediaTek SoCs" |
| 74 | 74 | select MFD_SYSCON |
| 75 | 75 | depends on (MIPS && SOC_MT7621) || ARCH_MEDIATEK || COMPILE_TEST |
| 76 | − ---help--- | |
| 76 | + help | |
| 77 | 77 | Say 'Y' to enable the support for the xHCI host controller |
| 78 | 78 | found in MediaTek SoCs. |
| 79 | 79 | If unsure, say N. |
| @@ -83,7 +83,7 @@ config USB_XHCI_MVEBU · 3 unmodified lines | ||
| 83 | 83 | select USB_XHCI_PLATFORM |
| 84 | 84 | depends on HAS_IOMEM |
| 85 | 85 | depends on ARCH_MVEBU || COMPILE_TEST |
| 86 | − ---help--- | |
| 86 | + help | |
| 87 | 87 | Say 'Y' to enable the support for the xHCI host controller |
| 88 | 88 | found in Marvell Armada 375/38x/37xx ARM SOCs. |
| 89 | 89 | |
| @@ -91,7 +91,7 @@ config USB_XHCI_RCAR · 1 unmodified line | ||
| 91 | 91 | tristate "xHCI support for Renesas R-Car SoCs" |
| 92 | 92 | depends on USB_XHCI_PLATFORM |
| 93 | 93 | depends on ARCH_RENESAS || COMPILE_TEST |
| 94 | − ---help--- | |
| 94 | + help | |
| 95 | 95 | Say 'Y' to enable the support for the xHCI host controller |
| 96 | 96 | found in Renesas R-Car ARM SoCs. |
| 97 | 97 | |
| @@ -100,7 +100,7 @@ config USB_XHCI_TEGRA · 2 unmodified lines | ||
| 100 | 100 | depends on PHY_TEGRA_XUSB |
| 101 | 101 | depends on RESET_CONTROLLER |
| 102 | 102 | select FW_LOADER |
| 103 | − ---help--- | |
| 103 | + help | |
| 104 | 104 | Say 'Y' to enable the support for the xHCI host controller |
| 105 | 105 | found in NVIDIA Tegra124 and later SoCs. |
| 106 | 106 | |
| @@ -129,7 +129,7 @@ config USB_BRCMSTB · 22 unmodified lines | ||
| 129 | 129 | config USB_EHCI_HCD |
| 130 | 130 | tristate "EHCI HCD (USB 2.0) support" |
| 131 | 131 | depends on HAS_DMA && HAS_IOMEM |
| 132 | − ---help--- | |
| 132 | + help | |
| 133 | 133 | The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0 |
| 134 | 134 | "high speed" (480 Mbit/sec, 60 Mbyte/sec) host controller hardware. |
| 135 | 135 | If your USB host controller supports USB 2.0, you will likely want to |
| @@ -151,7 +151,7 @@ config USB_EHCI_HCD · 15 unmodified lines | ||
| 151 | 151 | config USB_EHCI_ROOT_HUB_TT |
| 152 | 152 | bool "Root Hub Transaction Translators" |
| 153 | 153 | depends on USB_EHCI_HCD |
| 154 | − ---help--- | |
| 154 | + help | |
| 155 | 155 | Some EHCI chips have vendor-specific extensions to integrate |
| 156 | 156 | transaction translators, so that no OHCI or UHCI companion |
| 157 | 157 | controller is needed. It's safe to say "y" even if your |
| @@ -164,7 +164,7 @@ config USB_EHCI_TT_NEWSCHED · 6 unmodified lines | ||
| 164 | 164 | bool "Improved Transaction Translator scheduling" |
| 165 | 165 | depends on USB_EHCI_HCD |
| 166 | 166 | default y |
| 167 | − ---help--- | |
| 167 | + help | |
| 168 | 168 | This changes the periodic scheduling code to fill more of the low |
| 169 | 169 | and full speed bandwidth available from the Transaction Translator |
| 170 | 170 | (TT) in USB 2.0 hubs. Without this, only one transfer will be |
| @@ -192,7 +192,7 @@ config USB_EHCI_HCD_PMC_MSP · 21 unmodified lines | ||
| 192 | 192 | depends on MSP_HAS_USB |
| 193 | 193 | select USB_EHCI_BIG_ENDIAN_DESC |
| 194 | 194 | select USB_EHCI_BIG_ENDIAN_MMIO |
| 195 | − ---help--- | |
| 195 | + help | |
| 196 | 196 | Enables support for the onchip USB controller on the PMC_MSP7100 Family SoC's. |
| 197 | 197 | If unsure, say N. |
| 198 | 198 | |
| @@ -201,7 +201,7 @@ config XPS_USB_HCD_XILINX · 2 unmodified lines | ||
| 201 | 201 | depends on (PPC32 || MICROBLAZE) |
| 202 | 202 | select USB_EHCI_BIG_ENDIAN_DESC |
| 203 | 203 | select USB_EHCI_BIG_ENDIAN_MMIO |
| 204 | − ---help--- | |
| 204 | + help | |
| 205 | 205 | Xilinx xps USB host controller core is EHCI compliant and has |
| 206 | 206 | transaction translator built-in. It can be configured to either |
| 207 | 207 | support both high speed and full speed devices, or high speed |
| @@ -210,14 +210,14 @@ config XPS_USB_HCD_XILINX · 2 unmodified lines | ||
| 210 | 210 | config USB_EHCI_FSL |
| 211 | 211 | tristate "Support for Freescale on-chip EHCI USB controller" |
| 212 | 212 | select USB_EHCI_ROOT_HUB_TT |
| 213 | − ---help--- | |
| 213 | + help | |
| 214 | 214 | Variation of ARC USB block used in some Freescale chips. |
| 215 | 215 | |
| 216 | 216 | config USB_EHCI_MXC |
| 217 | 217 | tristate "Support for Freescale i.MX on-chip EHCI USB controller" |
| 218 | 218 | depends on ARCH_MXC || COMPILE_TEST |
| 219 | 219 | select USB_EHCI_ROOT_HUB_TT |
| 220 | − ---help--- | |
| 220 | + help | |
| 221 | 221 | Variation of ARC USB block used in some Freescale chips. |
| 222 | 222 | |
| 223 | 223 | config USB_EHCI_HCD_NPCM7XX |
| @@ -233,7 +233,7 @@ config USB_EHCI_HCD_OMAP · 9 unmodified lines | ||
| 233 | 233 | depends on ARCH_OMAP |
| 234 | 234 | depends on NOP_USB_XCEIV |
| 235 | 235 | default y |
| 236 | − ---help--- | |
| 236 | + help | |
| 237 | 237 | Enables support for the on-chip EHCI controller on |
| 238 | 238 | OMAP3 and later chips. |
| 239 | 239 | |
| @@ -241,7 +241,7 @@ config USB_EHCI_HCD_ORION · 1 unmodified line | ||
| 241 | 241 | tristate "Support for Marvell EBU on-chip EHCI USB controller" |
| 242 | 242 | depends on USB_EHCI_HCD && (PLAT_ORION || ARCH_MVEBU || COMPILE_TEST) |
| 243 | 243 | default y if (PLAT_ORION || ARCH_MVEBU) |
| 244 | − ---help--- | |
| 244 | + help | |
| 245 | 245 | Enables support for the on-chip EHCI controller on Marvell's |
| 246 | 246 | embedded ARM SoCs, including Orion, Kirkwood, Dove, Armada XP, |
| 247 | 247 | Armada 370. This is different from the EHCI implementation |
| @@ -252,7 +252,7 @@ config USB_EHCI_HCD_SPEAR · 4 unmodified lines | ||
| 252 | 252 | tristate "Support for ST SPEAr on-chip EHCI USB controller" |
| 253 | 253 | depends on USB_EHCI_HCD && (PLAT_SPEAR || COMPILE_TEST) |
| 254 | 254 | default y if PLAT_SPEAR |
| 255 | − ---help--- | |
| 255 | + help | |
| 256 | 256 | Enables support for the on-chip EHCI controller on |
| 257 | 257 | ST SPEAr chips. |
| 258 | 258 | |
| @@ -269,7 +269,7 @@ config USB_EHCI_HCD_AT91 · 10 unmodified lines | ||
| 269 | 269 | tristate "Support for Atmel on-chip EHCI USB controller" |
| 270 | 270 | depends on USB_EHCI_HCD && (ARCH_AT91 || COMPILE_TEST) |
| 271 | 271 | default y if ARCH_AT91 |
| 272 | − ---help--- | |
| 272 | + help | |
| 273 | 273 | Enables support for the on-chip EHCI controller on |
| 274 | 274 | Atmel chips. |
| 275 | 275 | |
| @@ -286,14 +286,14 @@ config USB_EHCI_HCD_PPC_OF · 10 unmodified lines | ||
| 286 | 286 | bool "EHCI support for PPC USB controller on OF platform bus" |
| 287 | 287 | depends on PPC |
| 288 | 288 | default y |
| 289 | − ---help--- | |
| 289 | + help | |
| 290 | 290 | Enables support for the USB controller present on the PowerPC |
| 291 | 291 | OpenFirmware platform bus. |
| 292 | 292 | |
| 293 | 293 | config USB_EHCI_SH |
| 294 | 294 | bool "EHCI support for SuperH USB controller" |
| 295 | 295 | depends on SUPERH || COMPILE_TEST |
| 296 | − ---help--- | |
| 296 | + help | |
| 297 | 297 | Enables support for the on-chip EHCI controller on the SuperH. |
| 298 | 298 | If you use the PCI EHCI controller, this option is not necessary. |
| 299 | 299 | |
| @@ -307,7 +307,7 @@ config USB_EHCI_MV · 7 unmodified lines | ||
| 307 | 307 | tristate "EHCI support for Marvell PXA/MMP USB controller" |
| 308 | 308 | depends on ARCH_PXA || ARCH_MMP || COMPILE_TEST |
| 309 | 309 | select USB_EHCI_ROOT_HUB_TT |
| 310 | − ---help--- | |
| 310 | + help | |
| 311 | 311 | Enables support for Marvell (including PXA and MMP series) on-chip |
| 312 | 312 | USB SPH and OTG controller. SPH is a single port host, and it can |
| 313 | 313 | only be EHCI host. OTG is controller that can switch to host mode. |
| @@ -320,7 +320,7 @@ config USB_CNS3XXX_EHCI · 6 unmodified lines | ||
| 320 | 320 | bool "Cavium CNS3XXX EHCI Module (DEPRECATED)" |
| 321 | 321 | depends on ARCH_CNS3XXX || COMPILE_TEST |
| 322 | 322 | select USB_EHCI_HCD_PLATFORM |
| 323 | − ---help--- | |
| 323 | + help | |
| 324 | 324 | This option is deprecated now and the driver was removed, use |
| 325 | 325 | USB_EHCI_HCD_PLATFORM instead. |
| 326 | 326 | |
| @@ -330,7 +330,7 @@ config USB_CNS3XXX_EHCI · 3 unmodified lines | ||
| 330 | 330 | |
| 331 | 331 | config USB_EHCI_HCD_PLATFORM |
| 332 | 332 | tristate "Generic EHCI driver for a platform device" |
| 333 | − ---help--- | |
| 333 | + help | |
| 334 | 334 | Adds an EHCI host driver for a generic platform device, which |
| 335 | 335 | provides a memory space and an irq. |
| 336 | 336 | |
| @@ -355,7 +355,7 @@ endif # USB_EHCI_HCD · 18 unmodified lines | ||
| 355 | 355 | config USB_OXU210HP_HCD |
| 356 | 356 | tristate "OXU210HP HCD support" |
| 357 | 357 | depends on HAS_IOMEM |
| 358 | − ---help--- | |
| 358 | + help | |
| 359 | 359 | The OXU210HP is an USB host/OTG/device controller. Enable this |
| 360 | 360 | option if your board has this chip. If unsure, say N. |
| 361 | 361 | |
| @@ -368,7 +368,7 @@ config USB_OXU210HP_HCD · 6 unmodified lines | ||
| 368 | 368 | config USB_ISP116X_HCD |
| 369 | 369 | tristate "ISP116X HCD support" |
| 370 | 370 | depends on HAS_IOMEM |
| 371 | − ---help--- | |
| 371 | + help | |
| 372 | 372 | The ISP1160 and ISP1161 chips are USB host controllers. Enable this |
| 373 | 373 | option if your board has this chip. If unsure, say N. |
| 374 | 374 | |
| @@ -381,7 +381,7 @@ config USB_ISP1362_HCD · 6 unmodified lines | ||
| 381 | 381 | tristate "ISP1362 HCD support" |
| 382 | 382 | depends on HAS_IOMEM |
| 383 | 383 | depends on COMPILE_TEST # nothing uses this |
| 384 | − ---help--- | |
| 384 | + help | |
| 385 | 385 | Supports the Philips ISP1362 chip as a host controller |
| 386 | 386 | |
| 387 | 387 | This driver does not support isochronous transfers. |
| @@ -392,7 +392,7 @@ config USB_ISP1362_HCD · 4 unmodified lines | ||
| 392 | 392 | config USB_FOTG210_HCD |
| 393 | 393 | tristate "FOTG210 HCD support" |
| 394 | 394 | depends on USB && HAS_DMA && HAS_IOMEM |
| 395 | − ---help--- | |
| 395 | + help | |
| 396 | 396 | Faraday FOTG210 is an OTG controller which can be configured as |
| 397 | 397 | an USB2.0 host. It is designed to meet USB2.0 EHCI specification |
| 398 | 398 | with minor modification. |
| @@ -403,7 +403,7 @@ config USB_FOTG210_HCD · 4 unmodified lines | ||
| 403 | 403 | config USB_MAX3421_HCD |
| 404 | 404 | tristate "MAX3421 HCD (USB-over-SPI) support" |
| 405 | 405 | depends on USB && SPI |
| 406 | − ---help--- | |
| 406 | + help | |
| 407 | 407 | The Maxim MAX3421E chip supports standard USB 2.0-compliant |
| 408 | 408 | full-speed devices either in host or peripheral mode. This |
| 409 | 409 | driver supports the host-mode of the MAX3421E only. |
| @@ -414,7 +414,7 @@ config USB_MAX3421_HCD · 4 unmodified lines | ||
| 414 | 414 | config USB_OHCI_HCD |
| 415 | 415 | tristate "OHCI HCD (USB 1.1) support" |
| 416 | 416 | depends on HAS_DMA && HAS_IOMEM |
| 417 | − ---help--- | |
| 417 | + help | |
| 418 | 418 | The Open Host Controller Interface (OHCI) is a standard for accessing |
| 419 | 419 | USB 1.1 host controller hardware. It does more in hardware than Intel's |
| 420 | 420 | UHCI specification. If your USB host controller follows the OHCI spec, |
| @@ -434,14 +434,14 @@ config USB_OHCI_HCD_OMAP1 · 13 unmodified lines | ||
| 434 | 434 | depends on ARCH_OMAP1 |
| 435 | 435 | depends on ISP1301_OMAP || !(MACH_OMAP_H2 || MACH_OMAP_H3) |
| 436 | 436 | default y |
| 437 | − ---help--- | |
| 437 | + help | |
| 438 | 438 | Enables support for the OHCI controller on OMAP1/2 chips. |
| 439 | 439 | |
| 440 | 440 | config USB_OHCI_HCD_SPEAR |
| 441 | 441 | tristate "Support for ST SPEAr on-chip OHCI USB controller" |
| 442 | 442 | depends on USB_OHCI_HCD && (PLAT_SPEAR || COMPILE_TEST) |
| 443 | 443 | default y if PLAT_SPEAR |
| 444 | − ---help--- | |
| 444 | + help | |
| 445 | 445 | Enables support for the on-chip OHCI controller on |
| 446 | 446 | ST SPEAr chips. |
| 447 | 447 | |
| @@ -458,7 +458,7 @@ config USB_OHCI_HCD_S3C2410 · 10 unmodified lines | ||
| 458 | 458 | tristate "OHCI support for Samsung S3C24xx/S3C64xx SoC series" |
| 459 | 459 | depends on USB_OHCI_HCD && (ARCH_S3C24XX || ARCH_S3C64XX || COMPILE_TEST) |
| 460 | 460 | default y if (ARCH_S3C24XX || ARCH_S3C64XX) |
| 461 | − ---help--- | |
| 461 | + help | |
| 462 | 462 | Enables support for the on-chip OHCI controller on |
| 463 | 463 | S3C24xx/S3C64xx chips. |
| 464 | 464 | |
| @@ -468,7 +468,7 @@ config USB_OHCI_HCD_LPC32XX · 3 unmodified lines | ||
| 468 | 468 | depends on ARCH_LPC32XX || COMPILE_TEST |
| 469 | 469 | depends on USB_ISP1301 |
| 470 | 470 | default y |
| 471 | − ---help--- | |
| 471 | + help | |
| 472 | 472 | Enables support for the on-chip OHCI controller on |
| 473 | 473 | NXP chips. |
| 474 | 474 | |
| @@ -476,7 +476,7 @@ config USB_OHCI_HCD_PXA27X · 1 unmodified line | ||
| 476 | 476 | tristate "Support for PXA27X/PXA3XX on-chip OHCI USB controller" |
| 477 | 477 | depends on USB_OHCI_HCD && (PXA27x || PXA3xx) |
| 478 | 478 | default y |
| 479 | − ---help--- | |
| 479 | + help | |
| 480 | 480 | Enables support for the on-chip OHCI controller on |
| 481 | 481 | PXA27x/PXA3xx chips. |
| 482 | 482 | |
| @@ -484,7 +484,7 @@ config USB_OHCI_HCD_AT91 · 1 unmodified line | ||
| 484 | 484 | tristate "Support for Atmel on-chip OHCI USB controller" |
| 485 | 485 | depends on USB_OHCI_HCD && (ARCH_AT91 || COMPILE_TEST) && OF |
| 486 | 486 | default y if ARCH_AT91 |
| 487 | − ---help--- | |
| 487 | + help | |
| 488 | 488 | Enables support for the on-chip OHCI controller on |
| 489 | 489 | Atmel chips. |
| 490 | 490 | |
| @@ -516,7 +516,7 @@ config USB_OHCI_HCD_PPC_OF_BE · 25 unmodified lines | ||
| 516 | 516 | depends on PPC |
| 517 | 517 | select USB_OHCI_BIG_ENDIAN_DESC |
| 518 | 518 | select USB_OHCI_BIG_ENDIAN_MMIO |
| 519 | − ---help--- | |
| 519 | + help | |
| 520 | 520 | Enables support for big-endian USB controllers present on the |
| 521 | 521 | OpenFirmware platform bus. |
| 522 | 522 | |
| @@ -524,7 +524,7 @@ config USB_OHCI_HCD_PPC_OF_LE · 1 unmodified line | ||
| 524 | 524 | bool "OHCI support for OF platform bus (little endian)" |
| 525 | 525 | depends on PPC |
| 526 | 526 | select USB_OHCI_LITTLE_ENDIAN |
| 527 | − ---help--- | |
| 527 | + help | |
| 528 | 528 | Enables support for little-endian USB controllers present on the |
| 529 | 529 | OpenFirmware platform bus. |
| 530 | 530 | |
| @@ -538,7 +538,7 @@ config USB_OHCI_HCD_PCI · 7 unmodified lines | ||
| 538 | 538 | depends on USB_PCI |
| 539 | 539 | default y |
| 540 | 540 | select USB_OHCI_LITTLE_ENDIAN |
| 541 | − ---help--- | |
| 541 | + help | |
| 542 | 542 | Enables support for PCI-bus plug-in USB controller cards. |
| 543 | 543 | If unsure, say Y. |
| 544 | 544 | |
| @@ -547,7 +547,7 @@ config USB_OHCI_HCD_SSB · 2 unmodified lines | ||
| 547 | 547 | depends on (SSB = y || SSB = USB_OHCI_HCD) |
| 548 | 548 | select USB_HCD_SSB |
| 549 | 549 | select USB_OHCI_HCD_PLATFORM |
| 550 | − ---help--- | |
| 550 | + help | |
| 551 | 551 | This option is deprecated now and the driver was removed, use |
| 552 | 552 | USB_HCD_SSB and USB_OHCI_HCD_PLATFORM instead. |
| 553 | 553 | |
| @@ -563,7 +563,7 @@ config USB_OHCI_SH · 9 unmodified lines | ||
| 563 | 563 | bool "OHCI support for SuperH USB controller (DEPRECATED)" |
| 564 | 564 | depends on SUPERH || COMPILE_TEST |
| 565 | 565 | select USB_OHCI_HCD_PLATFORM |
| 566 | − ---help--- | |
| 566 | + help | |
| 567 | 567 | This option is deprecated now and the driver was removed, use |
| 568 | 568 | USB_OHCI_HCD_PLATFORM instead. |
| 569 | 569 | |
| @@ -580,7 +580,7 @@ config USB_CNS3XXX_OHCI · 10 unmodified lines | ||
| 580 | 580 | bool "Cavium CNS3XXX OHCI Module (DEPRECATED)" |
| 581 | 581 | depends on ARCH_CNS3XXX || COMPILE_TEST |
| 582 | 582 | select USB_OHCI_HCD_PLATFORM |
| 583 | − ---help--- | |
| 583 | + help | |
| 584 | 584 | This option is deprecated now and the driver was removed, use |
| 585 | 585 | USB_OHCI_HCD_PLATFORM instead. |
| 586 | 586 | |
| @@ -589,7 +589,7 @@ config USB_CNS3XXX_OHCI · 2 unmodified lines | ||
| 589 | 589 | |
| 590 | 590 | config USB_OHCI_HCD_PLATFORM |
| 591 | 591 | tristate "Generic OHCI driver for a platform device" |
| 592 | − ---help--- | |
| 592 | + help | |
| 593 | 593 | Adds an OHCI host driver for a generic platform device, which |
| 594 | 594 | provides a memory space and an irq. |
| 595 | 595 | |
| @@ -615,7 +615,7 @@ endif # USB_OHCI_HCD · 19 unmodified lines | ||
| 615 | 615 | config USB_UHCI_HCD |
| 616 | 616 | tristate "UHCI HCD (most Intel and VIA) support" |
| 617 | 617 | depends on USB_PCI || USB_UHCI_SUPPORT_NON_PCI_HC |
| 618 | − ---help--- | |
| 618 | + help | |
| 619 | 619 | The Universal Host Controller Interface is a standard by Intel for |
| 620 | 620 | accessing the USB hardware in the PC (which is also called the USB |
| 621 | 621 | host controller). If your USB host controller conforms to this |
| @@ -777,7 +777,7 @@ config USB_HCD_SSB · 155 unmodified lines | ||
| 777 | 777 | |
| 778 | 778 | config USB_HCD_TEST_MODE |
| 779 | 779 | bool "HCD test mode support" |
| 780 | − ---help--- | |
| 780 | + help | |
| 781 | 781 | Say 'Y' to enable additional software test modes that may be |
| 782 | 782 | supported by the host controller drivers. |
| 783 | 783 | |
| @@ -6,7 +6,7 @@ comment "USB Imaging devices" · 5 unmodified lines | ||
| 6 | 6 | |
| 7 | 7 | config USB_MDC800 |
| 8 | 8 | tristate "USB Mustek MDC800 Digital Camera support" |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Say Y here if you want to connect this type of still camera to |
| 11 | 11 | your computer's USB port. This driver can be used with gphoto 0.4.3 |
| 12 | 12 | and higher (look at <http://www.gphoto.org/>). |
| @@ -6,7 +6,7 @@ comment "USB Miscellaneous drivers" · 5 unmodified lines | ||
| 6 | 6 | |
| 7 | 7 | config USB_EMI62 |
| 8 | 8 | tristate "EMI 6|2m USB Audio interface support" |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This driver loads firmware to Emagic EMI 6|2m low latency USB |
| 11 | 11 | Audio and Midi interface. |
| 12 | 12 | |
| @@ -20,7 +20,7 @@ config USB_EMI62 · 7 unmodified lines | ||
| 20 | 20 | |
| 21 | 21 | config USB_EMI26 |
| 22 | 22 | tristate "EMI 2|6 USB Audio interface support" |
| 23 | − ---help--- | |
| 23 | + help | |
| 24 | 24 | This driver loads firmware to Emagic EMI 2|6 low latency USB |
| 25 | 25 | Audio interface. |
| 26 | 26 | |
| @@ -4,7 +4,7 @@ config USB_SISUSBVGA · 3 unmodified lines | ||
| 4 | 4 | tristate "USB 2.0 SVGA dongle support (Net2280/SiS315)" |
| 5 | 5 | depends on (USB_MUSB_HDRC || USB_EHCI_HCD) |
| 6 | 6 | select FONT_SUPPORT if USB_SISUSBVGA_CON |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | Say Y here if you intend to attach a USB2VGA dongle based on a |
| 9 | 9 | Net2280 and a SiS315 chip. |
| 10 | 10 | |
| @@ -18,7 +18,7 @@ config USB_SISUSBVGA_CON · 7 unmodified lines | ||
| 18 | 18 | bool "Text console and mode switching support" if USB_SISUSBVGA |
| 19 | 19 | depends on VT |
| 20 | 20 | select FONT_8x16 |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | Say Y here if you want a VGA text console via the USB dongle or |
| 23 | 23 | want to support userland applications that utilize the driver's |
| 24 | 24 | display mode switching capabilities. |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | menuconfig USB_SERIAL |
| 7 | 7 | tristate "USB Serial Converter support" |
| 8 | 8 | depends on TTY |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Say Y here if you have a USB device that provides normal serial |
| 11 | 11 | ports, or acts like a serial device, and you want to connect it to |
| 12 | 12 | your USB bus. |
| @@ -23,7 +23,7 @@ if USB_SERIAL · 10 unmodified lines | ||
| 23 | 23 | config USB_SERIAL_CONSOLE |
| 24 | 24 | bool "USB Serial Console device support" |
| 25 | 25 | depends on USB_SERIAL=y |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | If you say Y here, it will be possible to use a USB to serial |
| 28 | 28 | converter port as the system console (the system console is the |
| 29 | 29 | device which receives all kernel messages and warnings and which |
| @@ -123,7 +123,7 @@ config USB_SERIAL_WHITEHEAT · 93 unmodified lines | ||
| 123 | 123 | |
| 124 | 124 | config USB_SERIAL_DIGI_ACCELEPORT |
| 125 | 125 | tristate "USB Digi International AccelePort USB Serial Driver" |
| 126 | − ---help--- | |
| 126 | + help | |
| 127 | 127 | Say Y here if you want to use Digi AccelePort USB 2 or 4 devices, |
| 128 | 128 | 2 port (plus parallel port) and 4 port USB serial converters. The |
| 129 | 129 | parallel port on the USB 2 appears as a third serial port on Linux. |
| @@ -168,7 +168,7 @@ config USB_SERIAL_EMPEG · 38 unmodified lines | ||
| 168 | 168 | |
| 169 | 169 | config USB_SERIAL_FTDI_SIO |
| 170 | 170 | tristate "USB FTDI Single Port Serial Driver" |
| 171 | − ---help--- | |
| 171 | + help | |
| 172 | 172 | Say Y here if you want to use a FTDI SIO single port USB to serial |
| 173 | 173 | converter device. The implementation I have is called the USC-1000. |
| 174 | 174 | This driver has also been tested with the 245 and 232 devices. |
| @@ -213,7 +213,7 @@ config USB_SERIAL_IR · 38 unmodified lines | ||
| 213 | 213 | |
| 214 | 214 | config USB_SERIAL_EDGEPORT |
| 215 | 215 | tristate "USB Inside Out Edgeport Serial Driver" |
| 216 | − ---help--- | |
| 216 | + help | |
| 217 | 217 | Say Y here if you want to use any of the following devices from |
| 218 | 218 | Inside Out Networks (Digi): |
| 219 | 219 | Edgeport/4 |
| @@ -311,7 +311,7 @@ config USB_SERIAL_KEYSPAN_PDA · 91 unmodified lines | ||
| 311 | 311 | config USB_SERIAL_KEYSPAN |
| 312 | 312 | tristate "USB Keyspan USA-xxx Serial Driver" |
| 313 | 313 | select USB_EZUSB_FX2 |
| 314 | − ---help--- | |
| 314 | + help | |
| 315 | 315 | Say Y here if you want to use Keyspan USB to serial converter |
| 316 | 316 | devices. This driver makes use of Keyspan's official firmware |
| 317 | 317 | and was developed with their support. You must also include |
| @@ -324,7 +324,7 @@ config USB_SERIAL_KEYSPAN · 6 unmodified lines | ||
| 324 | 324 | |
| 325 | 325 | config USB_SERIAL_KLSI |
| 326 | 326 | tristate "USB KL5KUSB105 (Palmconnect) Driver" |
| 327 | − ---help--- | |
| 327 | + help | |
| 328 | 328 | Say Y here if you want to use a KL5KUSB105 - based single port |
| 329 | 329 | serial adapter. The most widely known -- and currently the only |
| 330 | 330 | tested -- device in this category is the PalmConnect USB Serial |
| @@ -339,7 +339,7 @@ config USB_SERIAL_KLSI · 8 unmodified lines | ||
| 339 | 339 | |
| 340 | 340 | config USB_SERIAL_KOBIL_SCT |
| 341 | 341 | tristate "USB KOBIL chipcard reader" |
| 342 | − ---help--- | |
| 342 | + help | |
| 343 | 343 | Say Y here if you want to use one of the following KOBIL USB chipcard |
| 344 | 344 | readers: |
| 345 | 345 | |
| @@ -356,7 +356,7 @@ config USB_SERIAL_KOBIL_SCT · 10 unmodified lines | ||
| 356 | 356 | |
| 357 | 357 | config USB_SERIAL_MCT_U232 |
| 358 | 358 | tristate "USB MCT Single Port Serial Driver" |
| 359 | − ---help--- | |
| 359 | + help | |
| 360 | 360 | Say Y here if you want to use a USB Serial single port adapter from |
| 361 | 361 | Magic Control Technology Corp. (U232 is one of the model numbers). |
| 362 | 362 | |
| @@ -368,7 +368,7 @@ config USB_SERIAL_MCT_U232 · 5 unmodified lines | ||
| 368 | 368 | |
| 369 | 369 | config USB_SERIAL_METRO |
| 370 | 370 | tristate "USB Metrologic Instruments USB-POS Barcode Scanner Driver" |
| 371 | − ---help--- | |
| 371 | + help | |
| 372 | 372 | Say Y here if you want to use a USB POS Metrologic barcode scanner. |
| 373 | 373 | |
| 374 | 374 | To compile this driver as a module, choose M here: the |
| @@ -376,7 +376,7 @@ config USB_SERIAL_METRO · 1 unmodified line | ||
| 376 | 376 | |
| 377 | 377 | config USB_SERIAL_MOS7720 |
| 378 | 378 | tristate "USB Moschip 7720 Serial Driver" |
| 379 | − ---help--- | |
| 379 | + help | |
| 380 | 380 | Say Y here if you want to use USB Serial single and double |
| 381 | 381 | port adapters from Moschip Semiconductor Tech. |
| 382 | 382 | |
| @@ -388,14 +388,14 @@ config USB_SERIAL_MOS7715_PARPORT · 5 unmodified lines | ||
| 388 | 388 | depends on USB_SERIAL_MOS7720 |
| 389 | 389 | depends on PARPORT=y || PARPORT=USB_SERIAL_MOS7720 |
| 390 | 390 | select PARPORT_NOT_PC |
| 391 | − ---help--- | |
| 391 | + help | |
| 392 | 392 | Say Y if you have a Moschip 7715 device and would like to use |
| 393 | 393 | the parallel port it provides. The port will register with |
| 394 | 394 | the parport subsystem as a low-level driver. |
| 395 | 395 | |
| 396 | 396 | config USB_SERIAL_MOS7840 |
| 397 | 397 | tristate "USB Moschip 7840/7820 USB Serial Driver" |
| 398 | − ---help--- | |
| 398 | + help | |
| 399 | 399 | Say Y here if you want to use a MCS7840 Quad-Serial or MCS7820 |
| 400 | 400 | Dual-Serial port device from MosChip Semiconductor. |
| 401 | 401 | |
| @@ -409,7 +409,7 @@ config USB_SERIAL_MOS7840 · 7 unmodified lines | ||
| 409 | 409 | |
| 410 | 410 | config USB_SERIAL_MXUPORT |
| 411 | 411 | tristate "USB Moxa UPORT Serial Driver" |
| 412 | − ---help--- | |
| 412 | + help | |
| 413 | 413 | Say Y here if you want to use a MOXA UPort Serial hub. |
| 414 | 414 | |
| 415 | 415 | This driver supports: |
| @@ -528,7 +528,7 @@ config USB_SERIAL_TI · 112 unmodified lines | ||
| 528 | 528 | |
| 529 | 529 | config USB_SERIAL_CYBERJACK |
| 530 | 530 | tristate "USB REINER SCT cyberJack pinpad/e-com chipcard reader" |
| 531 | − ---help--- | |
| 531 | + help | |
| 532 | 532 | Say Y here if you want to use a cyberJack pinpad/e-com USB chipcard |
| 533 | 533 | reader. This is an interface to ISO 7816 compatible contact-based |
| 534 | 534 | chipcards, e.g. GSM SIMs. |
| @@ -9,7 +9,7 @@ comment "also be needed; see USB_STORAGE Help for more info" · 8 unmodified lines | ||
| 9 | 9 | config USB_STORAGE |
| 10 | 10 | tristate "USB Mass Storage support" |
| 11 | 11 | depends on SCSI |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | Say Y here if you want to connect USB mass storage devices to your |
| 14 | 14 | computer's USB port. This is the driver you need for USB |
| 15 | 15 | floppy drives, USB hard disks, USB tape drives, USB CD-ROMs, |
| @@ -63,7 +63,7 @@ config USB_STORAGE_FREECOM · 47 unmodified lines | ||
| 63 | 63 | |
| 64 | 64 | config USB_STORAGE_ISD200 |
| 65 | 65 | tristate "ISD-200 USB/ATA Bridge support" |
| 66 | − ---help--- | |
| 66 | + help | |
| 67 | 67 | Say Y here if you want to use USB Mass Store devices based |
| 68 | 68 | on the In-Systems Design ISD-200 USB/ATA bridge. |
| 69 | 69 | |
| @@ -165,7 +165,7 @@ config USB_STORAGE_KARMA · 95 unmodified lines | ||
| 165 | 165 | |
| 166 | 166 | config USB_STORAGE_CYPRESS_ATACB |
| 167 | 167 | tristate "SAT emulation on Cypress USB/ATA Bridge with ATACB" |
| 168 | − ---help--- | |
| 168 | + help | |
| 169 | 169 | Say Y here if you want to use SAT (ata pass through) on devices based |
| 170 | 170 | on the Cypress USB/ATA bridge supporting ATACB. This will allow you |
| 171 | 171 | to use tools to tune and monitor your drive (like hdparm or smartctl). |
| @@ -177,7 +177,7 @@ config USB_STORAGE_CYPRESS_ATACB · 5 unmodified lines | ||
| 177 | 177 | |
| 178 | 178 | config USB_STORAGE_ENE_UB6250 |
| 179 | 179 | tristate "USB ENE card reader support" |
| 180 | − ---help--- | |
| 180 | + help | |
| 181 | 181 | Say Y here if you wish to control a ENE SD/MS Card reader. |
| 182 | 182 | Note that this driver does not support SM cards. |
| 183 | 183 | |
| @@ -5,7 +5,7 @@ config USBIP_CORE · 4 unmodified lines | ||
| 5 | 5 | depends on NET |
| 6 | 6 | select USB_COMMON |
| 7 | 7 | select SGL_ALLOC |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | This enables pushing USB packets over IP to allow remote |
| 10 | 10 | machines direct access to USB devices. It provides the |
| 11 | 11 | USB/IP core that is required by both drivers. |
| @@ -21,7 +21,7 @@ config USBIP_CORE · 9 unmodified lines | ||
| 21 | 21 | config USBIP_VHCI_HCD |
| 22 | 22 | tristate "VHCI hcd" |
| 23 | 23 | depends on USBIP_CORE && USB |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | This enables the USB/IP virtual host controller driver, |
| 26 | 26 | which is run on the remote machine. |
| 27 | 27 | |
| @@ -33,7 +33,7 @@ config USBIP_VHCI_HC_PORTS · 5 unmodified lines | ||
| 33 | 33 | range 1 15 |
| 34 | 34 | default 8 |
| 35 | 35 | depends on USBIP_VHCI_HCD |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | To increase number of ports available for USB/IP virtual |
| 38 | 38 | host controller driver, this defines number of ports per |
| 39 | 39 | USB/IP virtual host controller. |
| @@ -43,7 +43,7 @@ config USBIP_VHCI_NR_HCS · 3 unmodified lines | ||
| 43 | 43 | range 1 128 |
| 44 | 44 | default 1 |
| 45 | 45 | depends on USBIP_VHCI_HCD |
| 46 | − ---help--- | |
| 46 | + help | |
| 47 | 47 | To increase number of ports available for USB/IP virtual |
| 48 | 48 | host controller driver, this defines number of USB/IP |
| 49 | 49 | virtual host controllers as if adding physical host |
| @@ -52,7 +52,7 @@ config USBIP_VHCI_NR_HCS · 2 unmodified lines | ||
| 52 | 52 | config USBIP_HOST |
| 53 | 53 | tristate "Host driver" |
| 54 | 54 | depends on USBIP_CORE && USB |
| 55 | − ---help--- | |
| 55 | + help | |
| 56 | 56 | This enables the USB/IP host driver, which is run on the |
| 57 | 57 | machine that is sharing the USB devices. |
| 58 | 58 | |
| @@ -62,7 +62,7 @@ config USBIP_HOST · 3 unmodified lines | ||
| 62 | 62 | config USBIP_VUDC |
| 63 | 63 | tristate "VUDC driver" |
| 64 | 64 | depends on USBIP_CORE && USB_GADGET |
| 65 | − ---help--- | |
| 65 | + help | |
| 66 | 66 | This enables the USB/IP virtual USB device controller |
| 67 | 67 | driver, which is run on the host machine, allowing the |
| 68 | 68 | machine itself to act as a device. |
| @@ -73,5 +73,5 @@ config USBIP_VUDC · 4 unmodified lines | ||
| 73 | 73 | config USBIP_DEBUG |
| 74 | 74 | bool "Debug messages for USB/IP" |
| 75 | 75 | depends on USBIP_CORE |
| 76 | − ---help--- | |
| 76 | + help | |
| 77 | 77 | This enables the debug messages from the USB/IP drivers. |
| @@ -30,7 +30,7 @@ config VHOST_NET · 29 unmodified lines | ||
| 30 | 30 | tristate "Host kernel accelerator for virtio net" |
| 31 | 31 | depends on NET && EVENTFD && (TUN || !TUN) && (TAP || !TAP) |
| 32 | 32 | select VHOST |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | This kernel module can be loaded in host kernel to accelerate |
| 35 | 35 | guest networking with virtio_net. Not to be confused with virtio_net |
| 36 | 36 | module itself which needs to be loaded in guest kernel. |
| @@ -43,7 +43,7 @@ config VHOST_SCSI · 6 unmodified lines | ||
| 43 | 43 | depends on TARGET_CORE && EVENTFD |
| 44 | 44 | select VHOST |
| 45 | 45 | default n |
| 46 | − ---help--- | |
| 46 | + help | |
| 47 | 47 | Say M here to enable the vhost_scsi TCM fabric module |
| 48 | 48 | for use with virtio-scsi guests |
| 49 | 49 | |
| @@ -53,7 +53,7 @@ config VHOST_VSOCK · 3 unmodified lines | ||
| 53 | 53 | select VHOST |
| 54 | 54 | select VIRTIO_VSOCKETS_COMMON |
| 55 | 55 | default n |
| 56 | − ---help--- | |
| 56 | + help | |
| 57 | 57 | This kernel module can be loaded in the host kernel to provide AF_VSOCK |
| 58 | 58 | sockets for communicating with guests. The guests must have the |
| 59 | 59 | virtio_transport.ko driver loaded to use the virtio-vsock device. |
| @@ -76,7 +76,7 @@ config VHOST_VDPA · 16 unmodified lines | ||
| 76 | 76 | config VHOST_CROSS_ENDIAN_LEGACY |
| 77 | 77 | bool "Cross-endian support for vhost" |
| 78 | 78 | default n |
| 79 | − ---help--- | |
| 79 | + help | |
| 80 | 80 | This option allows vhost to support guests with a different byte |
| 81 | 81 | ordering from host while using legacy virtio. |
| 82 | 82 | |
| @@ -71,7 +71,7 @@ config VGACON_SOFT_SCROLLBACK_PERSISTENT_ENABLE_BY_DEFAULT · 70 unmodified lines | ||
| 71 | 71 | config MDA_CONSOLE |
| 72 | 72 | depends on !M68K && !PARISC && ISA |
| 73 | 73 | tristate "MDA text console (dual-headed)" |
| 74 | − ---help--- | |
| 74 | + help | |
| 75 | 75 | Say Y here if you have an old MDA or monochrome Hercules graphics |
| 76 | 76 | adapter in your system acting as a second head ( = video card). You |
| 77 | 77 | will then be able to use two monitors with your Linux system. Do not |
| @@ -128,7 +128,7 @@ config FRAMEBUFFER_CONSOLE_DETECT_PRIMARY · 50 unmodified lines | ||
| 128 | 128 | bool "Map the console to the primary display device" |
| 129 | 129 | depends on FRAMEBUFFER_CONSOLE |
| 130 | 130 | default n |
| 131 | − ---help--- | |
| 131 | + help | |
| 132 | 132 | If this option is selected, the framebuffer console will |
| 133 | 133 | automatically select the primary display device (if the architecture |
| 134 | 134 | supports this feature). Otherwise, the framebuffer console will |
| @@ -13,7 +13,7 @@ menuconfig FB · 12 unmodified lines | ||
| 13 | 13 | tristate "Support for frame buffer devices" |
| 14 | 14 | select FB_CMDLINE |
| 15 | 15 | select FB_NOTIFY |
| 16 | − ---help--- | |
| 16 | + help | |
| 17 | 17 | The frame buffer device provides an abstraction for the graphics |
| 18 | 18 | hardware. It represents the frame buffer of some video hardware and |
| 19 | 19 | allows application software to access the graphics hardware through |
| @@ -48,7 +48,7 @@ menuconfig FB · 28 unmodified lines | ||
| 48 | 48 | config FIRMWARE_EDID |
| 49 | 49 | bool "Enable firmware EDID" |
| 50 | 50 | depends on FB |
| 51 | − ---help--- | |
| 51 | + help | |
| 52 | 52 | This enables access to the EDID transferred from the firmware. |
| 53 | 53 | On the i386, this is from the Video BIOS. Enable this if DDC/I2C |
| 54 | 54 | transfers do not work for your driver and if you are using |
| @@ -69,14 +69,14 @@ config FB_DDC · 14 unmodified lines | ||
| 69 | 69 | config FB_BOOT_VESA_SUPPORT |
| 70 | 70 | bool |
| 71 | 71 | depends on FB |
| 72 | − ---help--- | |
| 72 | + help | |
| 73 | 73 | If true, at least one selected framebuffer driver can take advantage |
| 74 | 74 | of VESA video modes set at an early boot stage via the vga= parameter. |
| 75 | 75 | |
| 76 | 76 | config FB_CFB_FILLRECT |
| 77 | 77 | tristate |
| 78 | 78 | depends on FB |
| 79 | − ---help--- | |
| 79 | + help | |
| 80 | 80 | Include the cfb_fillrect function for generic software rectangle |
| 81 | 81 | filling. This is used by drivers that don't provide their own |
| 82 | 82 | (accelerated) version. |
| @@ -84,7 +84,7 @@ config FB_CFB_FILLRECT · 1 unmodified line | ||
| 84 | 84 | config FB_CFB_COPYAREA |
| 85 | 85 | tristate |
| 86 | 86 | depends on FB |
| 87 | − ---help--- | |
| 87 | + help | |
| 88 | 88 | Include the cfb_copyarea function for generic software area copying. |
| 89 | 89 | This is used by drivers that don't provide their own (accelerated) |
| 90 | 90 | version. |
| @@ -92,7 +92,7 @@ config FB_CFB_COPYAREA · 1 unmodified line | ||
| 92 | 92 | config FB_CFB_IMAGEBLIT |
| 93 | 93 | tristate |
| 94 | 94 | depends on FB |
| 95 | − ---help--- | |
| 95 | + help | |
| 96 | 96 | Include the cfb_imageblit function for generic software image |
| 97 | 97 | blitting. This is used by drivers that don't provide their own |
| 98 | 98 | (accelerated) version. |
| @@ -100,7 +100,7 @@ config FB_CFB_IMAGEBLIT · 1 unmodified line | ||
| 100 | 100 | config FB_CFB_REV_PIXELS_IN_BYTE |
| 101 | 101 | bool |
| 102 | 102 | depends on FB |
| 103 | − ---help--- | |
| 103 | + help | |
| 104 | 104 | Allow generic frame-buffer functions to work on displays with 1, 2 |
| 105 | 105 | and 4 bits per pixel depths which has opposite order of pixels in |
| 106 | 106 | byte order to bytes in long order. |
| @@ -108,7 +108,7 @@ config FB_CFB_REV_PIXELS_IN_BYTE · 1 unmodified line | ||
| 108 | 108 | config FB_SYS_FILLRECT |
| 109 | 109 | tristate |
| 110 | 110 | depends on FB |
| 111 | − ---help--- | |
| 111 | + help | |
| 112 | 112 | Include the sys_fillrect function for generic software rectangle |
| 113 | 113 | filling. This is used by drivers that don't provide their own |
| 114 | 114 | (accelerated) version and the framebuffer is in system RAM. |
| @@ -116,7 +116,7 @@ config FB_SYS_FILLRECT · 1 unmodified line | ||
| 116 | 116 | config FB_SYS_COPYAREA |
| 117 | 117 | tristate |
| 118 | 118 | depends on FB |
| 119 | − ---help--- | |
| 119 | + help | |
| 120 | 120 | Include the sys_copyarea function for generic software area copying. |
| 121 | 121 | This is used by drivers that don't provide their own (accelerated) |
| 122 | 122 | version and the framebuffer is in system RAM. |
| @@ -124,7 +124,7 @@ config FB_SYS_COPYAREA · 1 unmodified line | ||
| 124 | 124 | config FB_SYS_IMAGEBLIT |
| 125 | 125 | tristate |
| 126 | 126 | depends on FB |
| 127 | − ---help--- | |
| 127 | + help | |
| 128 | 128 | Include the sys_imageblit function for generic software image |
| 129 | 129 | blitting. This is used by drivers that don't provide their own |
| 130 | 130 | (accelerated) version and the framebuffer is in system RAM. |
| @@ -132,14 +132,14 @@ config FB_SYS_IMAGEBLIT · 1 unmodified line | ||
| 132 | 132 | config FB_PROVIDE_GET_FB_UNMAPPED_AREA |
| 133 | 133 | bool |
| 134 | 134 | depends on FB |
| 135 | − ---help--- | |
| 135 | + help | |
| 136 | 136 | Allow generic frame-buffer to provide get_fb_unmapped_area |
| 137 | 137 | function. |
| 138 | 138 | |
| 139 | 139 | menuconfig FB_FOREIGN_ENDIAN |
| 140 | 140 | bool "Framebuffer foreign endianness support" |
| 141 | 141 | depends on FB |
| 142 | − ---help--- | |
| 142 | + help | |
| 143 | 143 | This menu will let you enable support for the framebuffers with |
| 144 | 144 | non-native endianness (e.g. Little-Endian framebuffer on a |
| 145 | 145 | Big-Endian machine). Most probably you don't have such hardware, |
| @@ -176,7 +176,7 @@ config FB_HECUBA · 30 unmodified lines | ||
| 176 | 176 | config FB_SVGALIB |
| 177 | 177 | tristate |
| 178 | 178 | depends on FB |
| 179 | − ---help--- | |
| 179 | + help | |
| 180 | 180 | Common utility functions useful to fbdev drivers of VGA-based |
| 181 | 181 | cards. |
| 182 | 182 | |
| @@ -192,7 +192,7 @@ config FB_BACKLIGHT · 9 unmodified lines | ||
| 192 | 192 | config FB_MODE_HELPERS |
| 193 | 193 | bool "Enable Video Mode Handling Helpers" |
| 194 | 194 | depends on FB |
| 195 | − ---help--- | |
| 195 | + help | |
| 196 | 196 | This enables functions for handling video modes using the |
| 197 | 197 | Generalized Timing Formula and the EDID parser. A few drivers rely |
| 198 | 198 | on this feature such as the radeonfb, rivafb, and the i810fb. If |
| @@ -202,7 +202,7 @@ config FB_MODE_HELPERS · 3 unmodified lines | ||
| 202 | 202 | config FB_TILEBLITTING |
| 203 | 203 | bool "Enable Tile Blitting Support" |
| 204 | 204 | depends on FB |
| 205 | − ---help--- | |
| 205 | + help | |
| 206 | 206 | This enables tile blitting. Tile blitting is a drawing technique |
| 207 | 207 | where the screen is divided into rectangular sections (tiles), whereas |
| 208 | 208 | the standard blitting divides the screen into pixels. Because the |
| @@ -225,7 +225,7 @@ config FB_GRVGA · 16 unmodified lines | ||
| 225 | 225 | select FB_CFB_FILLRECT |
| 226 | 226 | select FB_CFB_COPYAREA |
| 227 | 227 | select FB_CFB_IMAGEBLIT |
| 228 | − ---help--- | |
| 228 | + help | |
| 229 | 229 | This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler. |
| 230 | 230 | |
| 231 | 231 | config FB_CIRRUS |
| @@ -234,7 +234,7 @@ config FB_CIRRUS · 2 unmodified lines | ||
| 234 | 234 | select FB_CFB_FILLRECT |
| 235 | 235 | select FB_CFB_COPYAREA |
| 236 | 236 | select FB_CFB_IMAGEBLIT |
| 237 | − ---help--- | |
| 237 | + help | |
| 238 | 238 | This enables support for Cirrus Logic GD542x/543x based boards on |
| 239 | 239 | Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum. |
| 240 | 240 | |
| @@ -553,7 +553,7 @@ config FB_STI · 312 unmodified lines | ||
| 553 | 553 | select FB_CFB_COPYAREA |
| 554 | 554 | select FB_CFB_IMAGEBLIT |
| 555 | 555 | default y |
| 556 | − ---help--- | |
| 556 | + help | |
| 557 | 557 | STI refers to the HP "Standard Text Interface" which is a set of |
| 558 | 558 | BIOS routines contained in a ROM chip in HP PA-RISC based machines. |
| 559 | 559 | Enabling this option will implement the linux framebuffer device |
| @@ -587,7 +587,7 @@ config FB_TGA · 27 unmodified lines | ||
| 587 | 587 | select FB_CFB_COPYAREA |
| 588 | 588 | select FB_CFB_IMAGEBLIT |
| 589 | 589 | select BITREVERSE |
| 590 | − ---help--- | |
| 590 | + help | |
| 591 | 591 | This is the frame buffer device driver for generic TGA and SFB+ |
| 592 | 592 | graphic cards. These include DEC ZLXp-E1, -E2 and -E3 PCI cards, |
| 593 | 593 | also known as PBXGA-A, -B and -C, and DEC ZLX-E1, -E2 and -E3 |
| @@ -815,7 +815,7 @@ config FB_PVR2 · 221 unmodified lines | ||
| 815 | 815 | select FB_CFB_FILLRECT |
| 816 | 816 | select FB_CFB_COPYAREA |
| 817 | 817 | select FB_CFB_IMAGEBLIT |
| 818 | − ---help--- | |
| 818 | + help | |
| 819 | 819 | Say Y here if you have a PowerVR 2 card in your box. If you plan to |
| 820 | 820 | run linux on your Dreamcast, you will have to say Y here. |
| 821 | 821 | This driver may or may not work on other PowerVR 2 cards, but is |
| @@ -1066,7 +1066,7 @@ config FB_INTEL · 244 unmodified lines | ||
| 1066 | 1066 | config FB_INTEL_DEBUG |
| 1067 | 1067 | bool "Intel driver Debug Messages" |
| 1068 | 1068 | depends on FB_INTEL |
| 1069 | − ---help--- | |
| 1069 | + help | |
| 1070 | 1070 | Say Y here if you want the Intel driver to output all sorts |
| 1071 | 1071 | of debugging information to provide to the maintainer when |
| 1072 | 1072 | something goes wrong. |
| @@ -1087,7 +1087,7 @@ config FB_MATROX · 14 unmodified lines | ||
| 1087 | 1087 | select FB_CFB_IMAGEBLIT |
| 1088 | 1088 | select FB_TILEBLITTING |
| 1089 | 1089 | select FB_MACMODES if PPC_PMAC |
| 1090 | − ---help--- | |
| 1090 | + help | |
| 1091 | 1091 | Say Y here if you have a Matrox Millennium, Matrox Millennium II, |
| 1092 | 1092 | Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox |
| 1093 | 1093 | Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video, |
| @@ -1123,7 +1123,7 @@ config FB_MATROX_MYSTIQUE · 29 unmodified lines | ||
| 1123 | 1123 | config FB_MATROX_G |
| 1124 | 1124 | bool "G100/G200/G400/G450/G550 support" |
| 1125 | 1125 | depends on FB_MATROX |
| 1126 | − ---help--- | |
| 1126 | + help | |
| 1127 | 1127 | Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based |
| 1128 | 1128 | video card. If you select "Advanced lowlevel driver options", you |
| 1129 | 1129 | should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed |
| @@ -1154,7 +1154,7 @@ config FB_MATROX_I2C · 24 unmodified lines | ||
| 1154 | 1154 | tristate "Matrox I2C support" |
| 1155 | 1155 | depends on FB_MATROX |
| 1156 | 1156 | select FB_DDC |
| 1157 | − ---help--- | |
| 1157 | + help | |
| 1158 | 1158 | This drivers creates I2C buses which are needed for accessing the |
| 1159 | 1159 | DDC (I2C) bus present on all Matroxes, an I2C bus which |
| 1160 | 1160 | interconnects Matrox optional devices, like MGA-TVO on G200 and |
| @@ -1170,7 +1170,7 @@ config FB_MATROX_I2C · 9 unmodified lines | ||
| 1170 | 1170 | config FB_MATROX_MAVEN |
| 1171 | 1171 | tristate "G400 second head support" |
| 1172 | 1172 | depends on FB_MATROX_G && FB_MATROX_I2C |
| 1173 | − ---help--- | |
| 1173 | + help | |
| 1174 | 1174 | WARNING !!! This support does not work with G450 !!! |
| 1175 | 1175 | |
| 1176 | 1176 | Say Y or M here if you want to use a secondary head (meaning two |
| @@ -1321,7 +1321,7 @@ config FB_S3 · 144 unmodified lines | ||
| 1321 | 1321 | select FB_SVGALIB |
| 1322 | 1322 | select VGASTATE |
| 1323 | 1323 | select FONT_8x16 if FRAMEBUFFER_CONSOLE |
| 1324 | − ---help--- | |
| 1324 | + help | |
| 1325 | 1325 | Driver for graphics boards with S3 Trio / S3 Virge chip. |
| 1326 | 1326 | |
| 1327 | 1327 | config FB_S3_DDC |
| @@ -1484,7 +1484,7 @@ config FB_3DFX · 156 unmodified lines | ||
| 1484 | 1484 | config FB_3DFX_ACCEL |
| 1485 | 1485 | bool "3Dfx Acceleration functions" |
| 1486 | 1486 | depends on FB_3DFX |
| 1487 | − ---help--- | |
| 1487 | + help | |
| 1488 | 1488 | This will compile the 3Dfx Banshee/Voodoo3/VSA-100 frame buffer |
| 1489 | 1489 | device driver with acceleration functions. |
| 1490 | 1490 | |
| @@ -1502,7 +1502,7 @@ config FB_VOODOO1 · 11 unmodified lines | ||
| 1502 | 1502 | select FB_CFB_FILLRECT |
| 1503 | 1503 | select FB_CFB_COPYAREA |
| 1504 | 1504 | select FB_CFB_IMAGEBLIT |
| 1505 | − ---help--- | |
| 1505 | + help | |
| 1506 | 1506 | Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or |
| 1507 | 1507 | Voodoo2 (cvg) based graphics card. |
| 1508 | 1508 | |
| @@ -1524,7 +1524,7 @@ config FB_VT8623 · 15 unmodified lines | ||
| 1524 | 1524 | select FB_SVGALIB |
| 1525 | 1525 | select VGASTATE |
| 1526 | 1526 | select FONT_8x16 if FRAMEBUFFER_CONSOLE |
| 1527 | − ---help--- | |
| 1527 | + help | |
| 1528 | 1528 | Driver for CastleRock integrated graphics core in the |
| 1529 | 1529 | VIA VT8623 [Apollo CLE266] chipset. |
| 1530 | 1530 | |
| @@ -1536,7 +1536,7 @@ config FB_TRIDENT · 5 unmodified lines | ||
| 1536 | 1536 | select FB_CFB_IMAGEBLIT |
| 1537 | 1537 | select FB_DDC |
| 1538 | 1538 | select FB_MODE_HELPERS |
| 1539 | − ---help--- | |
| 1539 | + help | |
| 1540 | 1540 | This is the frame buffer device driver for Trident PCI/AGP chipsets. |
| 1541 | 1541 | Supported chipset families are TGUI 9440/96XX, 3DImage, Blade3D |
| 1542 | 1542 | and Blade XP. |
| @@ -1560,7 +1560,7 @@ config FB_ARK · 17 unmodified lines | ||
| 1560 | 1560 | select FB_SVGALIB |
| 1561 | 1561 | select VGASTATE |
| 1562 | 1562 | select FONT_8x16 if FRAMEBUFFER_CONSOLE |
| 1563 | − ---help--- | |
| 1563 | + help | |
| 1564 | 1564 | Driver for PCI graphics boards with ARK 2000PV chip |
| 1565 | 1565 | and ICS 5342 RAMDAC. |
| 1566 | 1566 | |
| @@ -1738,7 +1738,7 @@ config FB_PXA168 · 171 unmodified lines | ||
| 1738 | 1738 | select FB_CFB_FILLRECT |
| 1739 | 1739 | select FB_CFB_COPYAREA |
| 1740 | 1740 | select FB_CFB_IMAGEBLIT |
| 1741 | − ---help--- | |
| 1741 | + help | |
| 1742 | 1742 | Frame buffer driver for the built-in LCD controller in the Marvell |
| 1743 | 1743 | MMP processor. |
| 1744 | 1744 | |
| @@ -1750,7 +1750,7 @@ config FB_PXA · 5 unmodified lines | ||
| 1750 | 1750 | select FB_CFB_IMAGEBLIT |
| 1751 | 1751 | select VIDEOMODE_HELPERS if OF |
| 1752 | 1752 | select FB_MODE_HELPERS if OF |
| 1753 | − ---help--- | |
| 1753 | + help | |
| 1754 | 1754 | Frame buffer driver for the built-in LCD controller in the Intel |
| 1755 | 1755 | PXA2x0 processor. |
| 1756 | 1756 | |
| @@ -1772,7 +1772,7 @@ config FB_PXA_SMARTPANEL · 15 unmodified lines | ||
| 1772 | 1772 | config FB_PXA_PARAMETERS |
| 1773 | 1773 | bool "PXA LCD command line parameters" |
| 1774 | 1774 | depends on FB_PXA |
| 1775 | − ---help--- | |
| 1775 | + help | |
| 1776 | 1776 | Enable the use of kernel command line or module parameters |
| 1777 | 1777 | to configure the physical properties of the LCD panel when |
| 1778 | 1778 | using the PXA LCD driver. |
| @@ -1801,14 +1801,14 @@ config FB_MBX · 22 unmodified lines | ||
| 1801 | 1801 | select FB_CFB_FILLRECT |
| 1802 | 1802 | select FB_CFB_COPYAREA |
| 1803 | 1803 | select FB_CFB_IMAGEBLIT |
| 1804 | − ---help--- | |
| 1804 | + help | |
| 1805 | 1805 | Framebuffer driver for the Intel 2700G (Marathon) Graphics |
| 1806 | 1806 | Accelerator |
| 1807 | 1807 | |
| 1808 | 1808 | config FB_MBX_DEBUG |
| 1809 | 1809 | bool "Enable debugging info via debugfs" |
| 1810 | 1810 | depends on FB_MBX && DEBUG_FS |
| 1811 | − ---help--- | |
| 1811 | + help | |
| 1812 | 1812 | Enable this if you want debugging information using the debug |
| 1813 | 1813 | filesystem (debugfs) |
| 1814 | 1814 | |
| @@ -1822,7 +1822,7 @@ config FB_FSL_DIU · 7 unmodified lines | ||
| 1822 | 1822 | select FB_CFB_COPYAREA |
| 1823 | 1823 | select FB_CFB_IMAGEBLIT |
| 1824 | 1824 | select PPC_LIB_RHEAP |
| 1825 | − ---help--- | |
| 1825 | + help | |
| 1826 | 1826 | Framebuffer driver for the Freescale SoC DIU |
| 1827 | 1827 | |
| 1828 | 1828 | config FB_W100 |
| @@ -1831,7 +1831,7 @@ config FB_W100 · 2 unmodified lines | ||
| 1831 | 1831 | select FB_CFB_FILLRECT |
| 1832 | 1832 | select FB_CFB_COPYAREA |
| 1833 | 1833 | select FB_CFB_IMAGEBLIT |
| 1834 | − ---help--- | |
| 1834 | + help | |
| 1835 | 1835 | Frame buffer driver for the w100 as found on the Sharp SL-Cxx series. |
| 1836 | 1836 | It can also drive the w3220 chip found on iPAQ hx4700. |
| 1837 | 1837 | |
| @@ -1852,7 +1852,7 @@ config FB_SH_MOBILE_LCDC · 14 unmodified lines | ||
| 1852 | 1852 | select FB_SYS_FOPS |
| 1853 | 1853 | select FB_DEFERRED_IO |
| 1854 | 1854 | select FB_BACKLIGHT |
| 1855 | − ---help--- | |
| 1855 | + help | |
| 1856 | 1856 | Frame buffer driver for the on-chip SH-Mobile LCD controller. |
| 1857 | 1857 | |
| 1858 | 1858 | config FB_TMIO |
| @@ -1861,7 +1861,7 @@ config FB_TMIO · 2 unmodified lines | ||
| 1861 | 1861 | select FB_CFB_FILLRECT |
| 1862 | 1862 | select FB_CFB_COPYAREA |
| 1863 | 1863 | select FB_CFB_IMAGEBLIT |
| 1864 | − ---help--- | |
| 1864 | + help | |
| 1865 | 1865 | Frame buffer driver for the Toshiba Mobile IO integrated as found |
| 1866 | 1866 | on the Sharp SL-6000 series |
| 1867 | 1867 | |
| @@ -1884,7 +1884,7 @@ config FB_S3C · 16 unmodified lines | ||
| 1884 | 1884 | select FB_CFB_FILLRECT |
| 1885 | 1885 | select FB_CFB_COPYAREA |
| 1886 | 1886 | select FB_CFB_IMAGEBLIT |
| 1887 | − ---help--- | |
| 1887 | + help | |
| 1888 | 1888 | Frame buffer driver for the built-in FB controller in the Samsung |
| 1889 | 1889 | SoC line from the S3C2443 onwards, including the S3C2416, S3C2450, |
| 1890 | 1890 | and the S3C64XX series such as the S3C6400 and S3C6410. |
| @@ -1899,7 +1899,7 @@ config FB_S3C · 8 unmodified lines | ||
| 1899 | 1899 | config FB_S3C_DEBUG_REGWRITE |
| 1900 | 1900 | bool "Debug register writes" |
| 1901 | 1901 | depends on FB_S3C |
| 1902 | − ---help--- | |
| 1902 | + help | |
| 1903 | 1903 | Show all register writes via pr_debug() |
| 1904 | 1904 | |
| 1905 | 1905 | config FB_S3C2410 |
| @@ -1908,7 +1908,7 @@ config FB_S3C2410 · 2 unmodified lines | ||
| 1908 | 1908 | select FB_CFB_FILLRECT |
| 1909 | 1909 | select FB_CFB_COPYAREA |
| 1910 | 1910 | select FB_CFB_IMAGEBLIT |
| 1911 | − ---help--- | |
| 1911 | + help | |
| 1912 | 1912 | Frame buffer driver for the built-in LCD controller in the Samsung |
| 1913 | 1913 | S3C2410 processor. |
| 1914 | 1914 | |
| @@ -1931,7 +1931,7 @@ config FB_SM501 · 16 unmodified lines | ||
| 1931 | 1931 | select FB_CFB_FILLRECT |
| 1932 | 1932 | select FB_CFB_COPYAREA |
| 1933 | 1933 | select FB_CFB_IMAGEBLIT |
| 1934 | − ---help--- | |
| 1934 | + help | |
| 1935 | 1935 | Frame buffer driver for the CRT and LCD controllers in the Silicon |
| 1936 | 1936 | Motion SM501. |
| 1937 | 1937 | |
| @@ -1951,7 +1951,7 @@ config FB_SMSCUFX · 13 unmodified lines | ||
| 1951 | 1951 | select FB_SYS_IMAGEBLIT |
| 1952 | 1952 | select FB_SYS_FOPS |
| 1953 | 1953 | select FB_DEFERRED_IO |
| 1954 | − ---help--- | |
| 1954 | + help | |
| 1955 | 1955 | This is a kernel framebuffer driver for SMSC UFX USB devices. |
| 1956 | 1956 | Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and |
| 1957 | 1957 | mplayer -vo fbdev. Supports both UFX6000 (USB 2.0) and UFX7000 |
| @@ -1967,7 +1967,7 @@ config FB_UDL · 9 unmodified lines | ||
| 1967 | 1967 | select FB_SYS_IMAGEBLIT |
| 1968 | 1968 | select FB_SYS_FOPS |
| 1969 | 1969 | select FB_DEFERRED_IO |
| 1970 | − ---help--- | |
| 1970 | + help | |
| 1971 | 1971 | This is a kernel framebuffer driver for DisplayLink USB devices. |
| 1972 | 1972 | Supports fbdev clients like xf86-video-fbdev, kdrive, fbi, and |
| 1973 | 1973 | mplayer -vo fbdev. Supports all USB 2.0 era DisplayLink devices. |
| @@ -1979,7 +1979,7 @@ config FB_IBM_GXT4500 · 5 unmodified lines | ||
| 1979 | 1979 | select FB_CFB_FILLRECT |
| 1980 | 1980 | select FB_CFB_COPYAREA |
| 1981 | 1981 | select FB_CFB_IMAGEBLIT |
| 1982 | − ---help--- | |
| 1982 | + help | |
| 1983 | 1983 | Say Y here to enable support for the IBM GXT4000P/6000P and |
| 1984 | 1984 | GXT4500P/6500P display adaptor based on Raster Engine RC1000, |
| 1985 | 1985 | found on some IBM System P (pSeries) machines. This driver |
| @@ -1993,14 +1993,14 @@ config FB_PS3 · 7 unmodified lines | ||
| 1993 | 1993 | select FB_SYS_COPYAREA |
| 1994 | 1994 | select FB_SYS_IMAGEBLIT |
| 1995 | 1995 | select FB_SYS_FOPS |
| 1996 | − ---help--- | |
| 1996 | + help | |
| 1997 | 1997 | Include support for the virtual frame buffer in the PS3 platform. |
| 1998 | 1998 | |
| 1999 | 1999 | config FB_PS3_DEFAULT_SIZE_M |
| 2000 | 2000 | int "PS3 default frame buffer size (in MiB)" |
| 2001 | 2001 | depends on FB_PS3 |
| 2002 | 2002 | default 9 |
| 2003 | − ---help--- | |
| 2003 | + help | |
| 2004 | 2004 | This is the default size (in MiB) of the virtual frame buffer in |
| 2005 | 2005 | the PS3. |
| 2006 | 2006 | The default value can be overridden on the kernel command line |
| @@ -2012,7 +2012,7 @@ config FB_XILINX · 5 unmodified lines | ||
| 2012 | 2012 | select FB_CFB_FILLRECT |
| 2013 | 2013 | select FB_CFB_COPYAREA |
| 2014 | 2014 | select FB_CFB_IMAGEBLIT |
| 2015 | − ---help--- | |
| 2015 | + help | |
| 2016 | 2016 | Include support for the Xilinx ML300/ML403 reference design |
| 2017 | 2017 | framebuffer. ML300 carries a 640*480 LCD display on the board, |
| 2018 | 2018 | ML403 uses a standard DB15 VGA connector. |
| @@ -2024,7 +2024,7 @@ config FB_GOLDFISH · 5 unmodified lines | ||
| 2024 | 2024 | select FB_CFB_FILLRECT |
| 2025 | 2025 | select FB_CFB_COPYAREA |
| 2026 | 2026 | select FB_CFB_IMAGEBLIT |
| 2027 | − ---help--- | |
| 2027 | + help | |
| 2028 | 2028 | Framebuffer driver for Goldfish Virtual Platform |
| 2029 | 2029 | |
| 2030 | 2030 | config FB_COBALT |
| @@ -2038,7 +2038,7 @@ config FB_SH7760 · 7 unmodified lines | ||
| 2038 | 2038 | select FB_CFB_FILLRECT |
| 2039 | 2039 | select FB_CFB_COPYAREA |
| 2040 | 2040 | select FB_CFB_IMAGEBLIT |
| 2041 | − ---help--- | |
| 2041 | + help | |
| 2042 | 2042 | Support for the SH7760/SH7763/SH7720/SH7721 integrated |
| 2043 | 2043 | (D)STN/TFT LCD Controller. |
| 2044 | 2044 | Supports display resolutions up to 1024x1024 pixel, grayscale and |
| @@ -2056,7 +2056,7 @@ config FB_DA8XX · 11 unmodified lines | ||
| 2056 | 2056 | select FB_CFB_REV_PIXELS_IN_BYTE |
| 2057 | 2057 | select FB_MODE_HELPERS |
| 2058 | 2058 | select VIDEOMODE_HELPERS |
| 2059 | − ---help--- | |
| 2059 | + help | |
| 2060 | 2060 | This is the frame buffer device driver for the TI LCD controller |
| 2061 | 2061 | found on DA8xx/OMAP-L1xx/AM335x SoCs. |
| 2062 | 2062 | If unsure, say N. |
| @@ -2068,7 +2068,7 @@ config FB_VIRTUAL · 5 unmodified lines | ||
| 2068 | 2068 | select FB_SYS_COPYAREA |
| 2069 | 2069 | select FB_SYS_IMAGEBLIT |
| 2070 | 2070 | select FB_SYS_FOPS |
| 2071 | − ---help--- | |
| 2071 | + help | |
| 2072 | 2072 | This is a `virtual' frame buffer device. It operates on a chunk of |
| 2073 | 2073 | unswappable kernel memory instead of on the memory of a graphics |
| 2074 | 2074 | board. This means you cannot see any output sent to this frame |
| @@ -2119,7 +2119,7 @@ config FB_MB862XX · 44 unmodified lines | ||
| 2119 | 2119 | select FB_CFB_FILLRECT |
| 2120 | 2120 | select FB_CFB_COPYAREA |
| 2121 | 2121 | select FB_CFB_IMAGEBLIT |
| 2122 | − ---help--- | |
| 2122 | + help | |
| 2123 | 2123 | Frame buffer driver for Fujitsu Carmine/Coral-P(A)/Lime controllers. |
| 2124 | 2124 | |
| 2125 | 2125 | choice |
| @@ -2129,7 +2129,7 @@ choice · 3 unmodified lines | ||
| 2129 | 2129 | config FB_MB862XX_PCI_GDC |
| 2130 | 2130 | bool "Carmine/Coral-P(A) GDC" |
| 2131 | 2131 | depends on PCI |
| 2132 | − ---help--- | |
| 2132 | + help | |
| 2133 | 2133 | This enables framebuffer support for Fujitsu Carmine/Coral-P(A) |
| 2134 | 2134 | PCI graphics controller devices. |
| 2135 | 2135 | |
| @@ -2138,7 +2138,7 @@ config FB_MB862XX_LIME · 2 unmodified lines | ||
| 2138 | 2138 | depends on OF && PPC |
| 2139 | 2139 | select FB_FOREIGN_ENDIAN |
| 2140 | 2140 | select FB_LITTLE_ENDIAN |
| 2141 | − ---help--- | |
| 2141 | + help | |
| 2142 | 2142 | Framebuffer support for Fujitsu Lime GDC on host CPU bus. |
| 2143 | 2143 | |
| 2144 | 2144 | endchoice |
| @@ -2159,7 +2159,7 @@ config FB_EP93XX · 14 unmodified lines | ||
| 2159 | 2159 | select FB_CFB_FILLRECT |
| 2160 | 2160 | select FB_CFB_COPYAREA |
| 2161 | 2161 | select FB_CFB_IMAGEBLIT |
| 2162 | − ---help--- | |
| 2162 | + help | |
| 2163 | 2163 | Framebuffer driver for the Cirrus Logic EP93XX series of processors. |
| 2164 | 2164 | This driver is also available as a module. The module will be called |
| 2165 | 2165 | ep93xx-fb. |
| @@ -2167,7 +2167,7 @@ config FB_EP93XX · 1 unmodified line | ||
| 2167 | 2167 | config FB_PRE_INIT_FB |
| 2168 | 2168 | bool "Don't reinitialize, use bootloader's GDC/Display configuration" |
| 2169 | 2169 | depends on FB && FB_MB862XX_LIME |
| 2170 | − ---help--- | |
| 2170 | + help | |
| 2171 | 2171 | Select this option if display contents should be inherited as set by |
| 2172 | 2172 | the bootloader. |
| 2173 | 2173 | |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | config FB_GEODE |
| 6 | 6 | bool "AMD Geode family framebuffer support" |
| 7 | 7 | depends on FB && PCI && (X86_32 || (X86 && COMPILE_TEST)) |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | Say 'Y' here to allow you to select framebuffer drivers for |
| 10 | 10 | the AMD Geode family of processors. |
| 11 | 11 | |
| @@ -15,7 +15,7 @@ config FB_GEODE_LX · 3 unmodified lines | ||
| 15 | 15 | select FB_CFB_FILLRECT |
| 16 | 16 | select FB_CFB_COPYAREA |
| 17 | 17 | select FB_CFB_IMAGEBLIT |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | Framebuffer driver for the display controller integrated into the |
| 20 | 20 | AMD Geode LX processors. |
| 21 | 21 | |
| @@ -30,7 +30,7 @@ config FB_GEODE_GX · 8 unmodified lines | ||
| 30 | 30 | select FB_CFB_FILLRECT |
| 31 | 31 | select FB_CFB_COPYAREA |
| 32 | 32 | select FB_CFB_IMAGEBLIT |
| 33 | − ---help--- | |
| 33 | + help | |
| 34 | 34 | Framebuffer driver for the display controller integrated into the |
| 35 | 35 | AMD Geode GX processors. |
| 36 | 36 | |
| @@ -45,7 +45,7 @@ config FB_GEODE_GX1 · 8 unmodified lines | ||
| 45 | 45 | select FB_CFB_FILLRECT |
| 46 | 46 | select FB_CFB_COPYAREA |
| 47 | 47 | select FB_CFB_IMAGEBLIT |
| 48 | − ---help--- | |
| 48 | + help | |
| 49 | 49 | Framebuffer driver for the display controller integrated into the |
| 50 | 50 | AMD Geode GX1 processor. |
| 51 | 51 | |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | |
| 6 | 6 | menuconfig VIRT_DRIVERS |
| 7 | 7 | bool "Virtualization drivers" |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | Say Y here to get to see options for device drivers that support |
| 10 | 10 | virtualization environments. |
| 11 | 11 | |
| @@ -1,7 +1,7 @@ | ||
| 1 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | 2 | config VIRTIO |
| 3 | 3 | tristate |
| 4 | − ---help--- | |
| 4 | + help | |
| 5 | 5 | This option is selected by any driver which implements the virtio |
| 6 | 6 | bus, such as CONFIG_VIRTIO_PCI, CONFIG_VIRTIO_MMIO, CONFIG_RPMSG |
| 7 | 7 | or CONFIG_S390_GUEST. |
| @@ -16,7 +16,7 @@ config VIRTIO_PCI · 8 unmodified lines | ||
| 16 | 16 | tristate "PCI driver for virtio devices" |
| 17 | 17 | depends on PCI |
| 18 | 18 | select VIRTIO |
| 19 | − ---help--- | |
| 19 | + help | |
| 20 | 20 | This driver provides support for virtio based paravirtual device |
| 21 | 21 | drivers over PCI. This requires that your VMM has appropriate PCI |
| 22 | 22 | virtio backends. Most QEMU based VMMs should support these devices |
| @@ -28,7 +28,7 @@ config VIRTIO_PCI_LEGACY · 5 unmodified lines | ||
| 28 | 28 | bool "Support for legacy virtio draft 0.9.X and older devices" |
| 29 | 29 | default y |
| 30 | 30 | depends on VIRTIO_PCI |
| 31 | − ---help--- | |
| 31 | + help | |
| 32 | 32 | Virtio PCI Card 0.9.X Draft (circa 2014) and older device support. |
| 33 | 33 | |
| 34 | 34 | This option enables building a transitional driver, supporting |
| @@ -72,7 +72,7 @@ config VIRTIO_BALLOON · 37 unmodified lines | ||
| 72 | 72 | depends on VIRTIO |
| 73 | 73 | select MEMORY_BALLOON |
| 74 | 74 | select PAGE_REPORTING |
| 75 | − ---help--- | |
| 75 | + help | |
| 76 | 76 | This driver supports increasing and decreasing the amount |
| 77 | 77 | of memory within a KVM guest. |
| 78 | 78 | |
| @@ -99,7 +99,7 @@ config VIRTIO_INPUT · 20 unmodified lines | ||
| 99 | 99 | tristate "Virtio input driver" |
| 100 | 100 | depends on VIRTIO |
| 101 | 101 | depends on INPUT |
| 102 | − ---help--- | |
| 102 | + help | |
| 103 | 103 | This driver supports virtio input devices such as |
| 104 | 104 | keyboards, mice and tablets. |
| 105 | 105 | |
| @@ -109,7 +109,7 @@ config VIRTIO_MMIO · 3 unmodified lines | ||
| 109 | 109 | tristate "Platform bus driver for memory mapped virtio devices" |
| 110 | 110 | depends on HAS_IOMEM && HAS_DMA |
| 111 | 111 | select VIRTIO |
| 112 | − ---help--- | |
| 112 | + help | |
| 113 | 113 | This drivers provides support for memory mapped virtio |
| 114 | 114 | platform device driver. |
| 115 | 115 | |
| @@ -118,7 +118,7 @@ config VIRTIO_MMIO · 2 unmodified lines | ||
| 118 | 118 | config VIRTIO_MMIO_CMDLINE_DEVICES |
| 119 | 119 | bool "Memory mapped virtio devices parameter parsing" |
| 120 | 120 | depends on VIRTIO_MMIO |
| 121 | − ---help--- | |
| 121 | + help | |
| 122 | 122 | Allow virtio-mmio devices instantiation via the kernel command line |
| 123 | 123 | or module parameters. Be aware that using incorrect parameters (base |
| 124 | 124 | address in particular) can crash your system - you have been warned. |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | config UNISYS_VISORBUS |
| 7 | 7 | tristate "Unisys visorbus driver" |
| 8 | 8 | depends on X86_64 && ACPI |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | The visorbus driver is a virtualized bus for the Unisys s-Par firmware. |
| 11 | 11 | Virtualized devices allow Linux guests on a system to share disks and |
| 12 | 12 | network cards that do not have SR-IOV support, and to be accessed using |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | menuconfig VME_BUS |
| 7 | 7 | bool "VME bridge support" |
| 8 | 8 | depends on PCI |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you say Y here you get support for the VME bridge Framework. |
| 11 | 11 | |
| 12 | 12 | if VME_BUS |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | menuconfig W1 |
| 3 | 3 | tristate "Dallas's 1-wire support" |
| 4 | 4 | depends on HAS_IOMEM |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | Dallas' 1-wire bus is useful to connect slow 1-pin devices |
| 7 | 7 | such as iButtons and thermal sensors. |
| 8 | 8 | |
| @@ -17,7 +17,7 @@ config W1_CON · 8 unmodified lines | ||
| 17 | 17 | depends on CONNECTOR |
| 18 | 18 | bool "Userspace communication over connector" |
| 19 | 19 | default y |
| 20 | − ---help--- | |
| 20 | + help | |
| 21 | 21 | This allows to communicate with userspace using connector. For more |
| 22 | 22 | information see <file:Documentation/driver-api/connector.rst>. |
| 23 | 23 | There are three types of messages between w1 core and userspace: |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | |
| 7 | 7 | menuconfig WATCHDOG |
| 8 | 8 | bool "Watchdog Timer Support" |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | If you say Y here (and to one of the following options) and create a |
| 11 | 11 | character special file /dev/watchdog with major number 10 and minor |
| 12 | 12 | number 130 using mknod ("man mknod"), you will get a watchdog, i.e.: |
| @@ -32,7 +32,7 @@ if WATCHDOG · 19 unmodified lines | ||
| 32 | 32 | |
| 33 | 33 | config WATCHDOG_CORE |
| 34 | 34 | tristate "WatchDog Timer Driver Core" |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | Say Y here if you want to use the new watchdog timer driver core. |
| 37 | 37 | This driver provides a framework for all watchdog timer drivers |
| 38 | 38 | and gives them the /dev/watchdog interface (and later also the |
| @@ -1009,7 +1009,7 @@ config PM8916_WATCHDOG · 970 unmodified lines | ||
| 1009 | 1009 | config ACQUIRE_WDT |
| 1010 | 1010 | tristate "Acquire SBC Watchdog Timer" |
| 1011 | 1011 | depends on X86 |
| 1012 | − ---help--- | |
| 1012 | + help | |
| 1013 | 1013 | This is the driver for the hardware watchdog on Single Board |
| 1014 | 1014 | Computers produced by Acquire Inc (and others). This watchdog |
| 1015 | 1015 | simply watches your kernel to make sure it doesn't freeze, and if |
| @@ -1032,7 +1032,7 @@ config ADVANTECH_WDT · 16 unmodified lines | ||
| 1032 | 1032 | config ALIM1535_WDT |
| 1033 | 1033 | tristate "ALi M1535 PMU Watchdog Timer" |
| 1034 | 1034 | depends on X86 && PCI |
| 1035 | − ---help--- | |
| 1035 | + help | |
| 1036 | 1036 | This is the driver for the hardware watchdog on the ALi M1535 PMU. |
| 1037 | 1037 | |
| 1038 | 1038 | To compile this driver as a module, choose M here: the |
| @@ -1078,7 +1078,7 @@ config SP5100_TCO · 39 unmodified lines | ||
| 1078 | 1078 | tristate "AMD/ATI SP5100 TCO Timer/Watchdog" |
| 1079 | 1079 | depends on X86 && PCI |
| 1080 | 1080 | select WATCHDOG_CORE |
| 1081 | − ---help--- | |
| 1081 | + help | |
| 1082 | 1082 | Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO |
| 1083 | 1083 | (Total Cost of Ownership) timer is a watchdog timer that will reboot |
| 1084 | 1084 | the machine after its expiration. The expiration time can be |
| @@ -1116,7 +1116,7 @@ config SC520_WDT · 31 unmodified lines | ||
| 1116 | 1116 | config SBC_FITPC2_WATCHDOG |
| 1117 | 1117 | tristate "Compulab SBC-FITPC2 watchdog" |
| 1118 | 1118 | depends on X86 |
| 1119 | − ---help--- | |
| 1119 | + help | |
| 1120 | 1120 | This is the driver for the built-in watchdog timer on the fit-PC2, |
| 1121 | 1121 | fit-PC2i, CM-iAM single-board computers made by Compulab. |
| 1122 | 1122 | |
| @@ -1146,7 +1146,7 @@ config EUROTECH_WDT · 23 unmodified lines | ||
| 1146 | 1146 | config IB700_WDT |
| 1147 | 1147 | tristate "IB700 SBC Watchdog Timer" |
| 1148 | 1148 | depends on X86 |
| 1149 | − ---help--- | |
| 1149 | + help | |
| 1150 | 1150 | This is the driver for the hardware watchdog on the IB700 Single |
| 1151 | 1151 | Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog |
| 1152 | 1152 | simply watches your kernel to make sure it doesn't freeze, and if |
| @@ -1184,7 +1184,7 @@ config I6300ESB_WDT · 31 unmodified lines | ||
| 1184 | 1184 | tristate "Intel 6300ESB Timer/Watchdog" |
| 1185 | 1185 | depends on PCI |
| 1186 | 1186 | select WATCHDOG_CORE |
| 1187 | − ---help--- | |
| 1187 | + help | |
| 1188 | 1188 | Hardware driver for the watchdog timer built into the Intel |
| 1189 | 1189 | 6300ESB controller hub. |
| 1190 | 1190 | |
| @@ -1197,7 +1197,7 @@ config IE6XX_WDT · 6 unmodified lines | ||
| 1197 | 1197 | select WATCHDOG_CORE |
| 1198 | 1198 | select MFD_CORE |
| 1199 | 1199 | select LPC_SCH |
| 1200 | − ---help--- | |
| 1200 | + help | |
| 1201 | 1201 | Hardware driver for the watchdog timer built into the Intel |
| 1202 | 1202 | Atom E6XX (TunnelCreek) processor. |
| 1203 | 1203 | |
| @@ -1207,7 +1207,7 @@ config IE6XX_WDT · 3 unmodified lines | ||
| 1207 | 1207 | config INTEL_SCU_WATCHDOG |
| 1208 | 1208 | bool "Intel SCU Watchdog for Mobile Platforms" |
| 1209 | 1209 | depends on X86_INTEL_MID |
| 1210 | − ---help--- | |
| 1210 | + help | |
| 1211 | 1211 | Hardware driver for the watchdog time built into the Intel SCU |
| 1212 | 1212 | for Intel Mobile Platforms. |
| 1213 | 1213 | |
| @@ -1217,7 +1217,7 @@ config INTEL_MID_WATCHDOG · 3 unmodified lines | ||
| 1217 | 1217 | tristate "Intel MID Watchdog Timer" |
| 1218 | 1218 | depends on X86_INTEL_MID |
| 1219 | 1219 | select WATCHDOG_CORE |
| 1220 | − ---help--- | |
| 1220 | + help | |
| 1221 | 1221 | Watchdog timer driver built into the Intel SCU for Intel MID |
| 1222 | 1222 | Platforms. |
| 1223 | 1223 | |
| @@ -1234,7 +1234,7 @@ config ITCO_WDT · 10 unmodified lines | ||
| 1234 | 1234 | depends on MFD_INTEL_PMC_BXT || !MFD_INTEL_PMC_BXT |
| 1235 | 1235 | select LPC_ICH if !EXPERT |
| 1236 | 1236 | select I2C_I801 if !EXPERT && I2C |
| 1237 | − ---help--- | |
| 1237 | + help | |
| 1238 | 1238 | Hardware driver for the intel TCO timer based watchdog devices. |
| 1239 | 1239 | These drivers are included in the Intel 82801 I/O Controller |
| 1240 | 1240 | Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB |
| @@ -1255,7 +1255,7 @@ config ITCO_WDT · 14 unmodified lines | ||
| 1255 | 1255 | config ITCO_VENDOR_SUPPORT |
| 1256 | 1256 | bool "Intel TCO Timer/Watchdog Specific Vendor Support" |
| 1257 | 1257 | depends on ITCO_WDT |
| 1258 | − ---help--- | |
| 1258 | + help | |
| 1259 | 1259 | Add vendor specific support to the intel TCO timer based watchdog |
| 1260 | 1260 | devices. At this moment we only have additional support for some |
| 1261 | 1261 | SuperMicro Inc. motherboards. |
| @@ -1263,7 +1263,7 @@ config ITCO_VENDOR_SUPPORT · 1 unmodified line | ||
| 1263 | 1263 | config IT8712F_WDT |
| 1264 | 1264 | tristate "IT8712F (Smart Guardian) Watchdog Timer" |
| 1265 | 1265 | depends on X86 |
| 1266 | − ---help--- | |
| 1266 | + help | |
| 1267 | 1267 | This is the driver for the built-in watchdog timer on the IT8712F |
| 1268 | 1268 | Super I/0 chipset used on many motherboards. |
| 1269 | 1269 | |
| @@ -1277,7 +1277,7 @@ config IT87_WDT · 7 unmodified lines | ||
| 1277 | 1277 | tristate "IT87 Watchdog Timer" |
| 1278 | 1278 | depends on X86 |
| 1279 | 1279 | select WATCHDOG_CORE |
| 1280 | − ---help--- | |
| 1280 | + help | |
| 1281 | 1281 | This is the driver for the hardware watchdog on the ITE IT8607, |
| 1282 | 1282 | IT8620, IT8622, IT8625, IT8628, IT8655, IT8665, IT8686, IT8702, |
| 1283 | 1283 | IT8712, IT8716, IT8718, IT8720, IT8721, IT8726, IT8728, and |
| @@ -1347,7 +1347,7 @@ config SCx200_WDT · 63 unmodified lines | ||
| 1347 | 1347 | config PC87413_WDT |
| 1348 | 1348 | tristate "NS PC87413 watchdog" |
| 1349 | 1349 | depends on X86 |
| 1350 | − ---help--- | |
| 1350 | + help | |
| 1351 | 1351 | This is the driver for the hardware watchdog on the PC87413 chipset |
| 1352 | 1352 | This watchdog simply watches your kernel to make sure it doesn't |
| 1353 | 1353 | freeze, and if it does, it reboots your computer after a certain |
| @@ -1361,7 +1361,7 @@ config PC87413_WDT · 7 unmodified lines | ||
| 1361 | 1361 | config NV_TCO |
| 1362 | 1362 | tristate "nVidia TCO Timer/Watchdog" |
| 1363 | 1363 | depends on X86 && PCI |
| 1364 | − ---help--- | |
| 1364 | + help | |
| 1365 | 1365 | Hardware driver for the TCO timer built into the nVidia Hub family |
| 1366 | 1366 | (such as the MCP51). The TCO (Total Cost of Ownership) timer is a |
| 1367 | 1367 | watchdog timer that will reboot the machine after its second |
| @@ -1404,7 +1404,7 @@ config 60XX_WDT · 36 unmodified lines | ||
| 1404 | 1404 | config SBC8360_WDT |
| 1405 | 1405 | tristate "SBC8360 Watchdog Timer" |
| 1406 | 1406 | depends on X86_32 |
| 1407 | − ---help--- | |
| 1407 | + help | |
| 1408 | 1408 | |
| 1409 | 1409 | This is the driver for the hardware watchdog on the SBC8360 Single |
| 1410 | 1410 | Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com). |
| @@ -1417,7 +1417,7 @@ config SBC8360_WDT · 6 unmodified lines | ||
| 1417 | 1417 | config SBC7240_WDT |
| 1418 | 1418 | tristate "SBC Nano 7240 Watchdog Timer" |
| 1419 | 1419 | depends on X86_32 && !UML |
| 1420 | − ---help--- | |
| 1420 | + help | |
| 1421 | 1421 | This is the driver for the hardware watchdog found on the IEI |
| 1422 | 1422 | single board computers EPIC Nano 7240 (and likely others). This |
| 1423 | 1423 | watchdog simply watches your kernel to make sure it doesn't freeze, |
| @@ -1430,7 +1430,7 @@ config SBC7240_WDT · 6 unmodified lines | ||
| 1430 | 1430 | config CPU5_WDT |
| 1431 | 1431 | tristate "SMA CPU5 Watchdog" |
| 1432 | 1432 | depends on X86 |
| 1433 | − ---help--- | |
| 1433 | + help | |
| 1434 | 1434 | TBD. |
| 1435 | 1435 | To compile this driver as a module, choose M here: the |
| 1436 | 1436 | module will be called cpu5wdt. |
| @@ -1438,7 +1438,7 @@ config CPU5_WDT · 1 unmodified line | ||
| 1438 | 1438 | config SMSC_SCH311X_WDT |
| 1439 | 1439 | tristate "SMSC SCH311X Watchdog Timer" |
| 1440 | 1440 | depends on X86 |
| 1441 | − ---help--- | |
| 1441 | + help | |
| 1442 | 1442 | This is the driver for the hardware watchdog timer on the |
| 1443 | 1443 | SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset |
| 1444 | 1444 | (LPC IO with 8042 KBC, Reset Generation, HWM and multiple |
| @@ -1450,7 +1450,7 @@ config SMSC_SCH311X_WDT · 5 unmodified lines | ||
| 1450 | 1450 | config SMSC37B787_WDT |
| 1451 | 1451 | tristate "Winbond SMsC37B787 Watchdog Timer" |
| 1452 | 1452 | depends on X86 |
| 1453 | − ---help--- | |
| 1453 | + help | |
| 1454 | 1454 | This is the driver for the hardware watchdog component on the |
| 1455 | 1455 | Winbond SMsC37B787 chipset as used on the NetRunner Mainboard |
| 1456 | 1456 | from Vision Systems and maybe others. |
| @@ -1484,7 +1484,7 @@ config VIA_WDT · 27 unmodified lines | ||
| 1484 | 1484 | tristate "VIA Watchdog Timer" |
| 1485 | 1485 | depends on X86 && PCI |
| 1486 | 1486 | select WATCHDOG_CORE |
| 1487 | − ---help--- | |
| 1487 | + help | |
| 1488 | 1488 | This is the driver for the hardware watchdog timer on VIA |
| 1489 | 1489 | southbridge chipset CX700, VX800/VX820 or VX855/VX875. |
| 1490 | 1490 | |
| @@ -1497,7 +1497,7 @@ config W83627HF_WDT · 6 unmodified lines | ||
| 1497 | 1497 | tristate "Watchdog timer for W83627HF/W83627DHG and compatibles" |
| 1498 | 1498 | depends on X86 |
| 1499 | 1499 | select WATCHDOG_CORE |
| 1500 | − ---help--- | |
| 1500 | + help | |
| 1501 | 1501 | This is the driver for the hardware watchdog on the following |
| 1502 | 1502 | Super I/O chips. |
| 1503 | 1503 | W83627DHG/DHG-P/EHF/EHG/F/G/HF/S/SF/THF/UHG/UG |
| @@ -1526,7 +1526,7 @@ config W83627HF_WDT · 22 unmodified lines | ||
| 1526 | 1526 | config W83877F_WDT |
| 1527 | 1527 | tristate "W83877F (EMACS) Watchdog Timer" |
| 1528 | 1528 | depends on X86 |
| 1529 | − ---help--- | |
| 1529 | + help | |
| 1530 | 1530 | This is the driver for the hardware watchdog on the W83877F chipset |
| 1531 | 1531 | as used in EMACS PC-104 motherboards (and likely others). This |
| 1532 | 1532 | watchdog simply watches your kernel to make sure it doesn't freeze, |
| @@ -1541,7 +1541,7 @@ config W83877F_WDT · 8 unmodified lines | ||
| 1541 | 1541 | config W83977F_WDT |
| 1542 | 1542 | tristate "W83977F (PCM-5335) Watchdog Timer" |
| 1543 | 1543 | depends on X86 |
| 1544 | − ---help--- | |
| 1544 | + help | |
| 1545 | 1545 | This is the driver for the hardware watchdog on the W83977F I/O chip |
| 1546 | 1546 | as used in AAEON's PCM-5335 SBC (and likely others). This |
| 1547 | 1547 | watchdog simply watches your kernel to make sure it doesn't freeze, |
| @@ -1554,7 +1554,7 @@ config W83977F_WDT · 6 unmodified lines | ||
| 1554 | 1554 | config MACHZ_WDT |
| 1555 | 1555 | tristate "ZF MachZ Watchdog" |
| 1556 | 1556 | depends on X86 |
| 1557 | − ---help--- | |
| 1557 | + help | |
| 1558 | 1558 | If you are using a ZF Micro MachZ processor, say Y here, otherwise |
| 1559 | 1559 | N. This is the driver for the watchdog timer built-in on that |
| 1560 | 1560 | processor using ZF-Logic interface. This watchdog simply watches |
| @@ -1567,7 +1567,7 @@ config MACHZ_WDT · 6 unmodified lines | ||
| 1567 | 1567 | config SBC_EPX_C3_WATCHDOG |
| 1568 | 1568 | tristate "Winsystems SBC EPX-C3 watchdog" |
| 1569 | 1569 | depends on X86 |
| 1570 | − ---help--- | |
| 1570 | + help | |
| 1571 | 1571 | This is the driver for the built-in watchdog timer on the EPX-C3 |
| 1572 | 1572 | Single-board computer made by Winsystems, Inc. |
| 1573 | 1573 | |
| @@ -1589,7 +1589,7 @@ config INTEL_MEI_WDT · 15 unmodified lines | ||
| 1589 | 1589 | tristate "Intel MEI iAMT Watchdog" |
| 1590 | 1590 | depends on INTEL_MEI && X86 |
| 1591 | 1591 | select WATCHDOG_CORE |
| 1592 | − ---help--- | |
| 1592 | + help | |
| 1593 | 1593 | A device driver for the Intel MEI iAMT watchdog. |
| 1594 | 1594 | |
| 1595 | 1595 | The Intel AMT Watchdog is an OS Health (Hang/Crash) watchdog. |
| @@ -1604,7 +1604,7 @@ config NI903X_WDT · 8 unmodified lines | ||
| 1604 | 1604 | tristate "NI 903x/913x Watchdog" |
| 1605 | 1605 | depends on X86 && ACPI |
| 1606 | 1606 | select WATCHDOG_CORE |
| 1607 | − ---help--- | |
| 1607 | + help | |
| 1608 | 1608 | This is the driver for the watchdog timer on the National Instruments |
| 1609 | 1609 | 903x/913x real-time controllers. |
| 1610 | 1610 | |
| @@ -1615,7 +1615,7 @@ config NIC7018_WDT · 4 unmodified lines | ||
| 1615 | 1615 | tristate "NIC7018 Watchdog" |
| 1616 | 1616 | depends on X86 && ACPI |
| 1617 | 1617 | select WATCHDOG_CORE |
| 1618 | − ---help--- | |
| 1618 | + help | |
| 1619 | 1619 | Support for National Instruments NIC7018 Watchdog. |
| 1620 | 1620 | |
| 1621 | 1621 | To compile this driver as a module, choose M here: the module will be |
| @@ -1865,7 +1865,7 @@ config PIC32_DMT · 243 unmodified lines | ||
| 1865 | 1865 | config GEF_WDT |
| 1866 | 1866 | tristate "GE Watchdog Timer" |
| 1867 | 1867 | depends on GE_FPGA |
| 1868 | − ---help--- | |
| 1868 | + help | |
| 1869 | 1869 | Watchdog timer found in a number of GE single board computers. |
| 1870 | 1870 | |
| 1871 | 1871 | config MPC5200_WDT |
| @@ -1903,7 +1903,7 @@ config BOOKE_WDT · 31 unmodified lines | ||
| 1903 | 1903 | tristate "PowerPC Book-E Watchdog Timer" |
| 1904 | 1904 | depends on BOOKE || 4xx |
| 1905 | 1905 | select WATCHDOG_CORE |
| 1906 | − ---help--- | |
| 1906 | + help | |
| 1907 | 1907 | Watchdog driver for PowerPC Book-E chips, such as the Freescale |
| 1908 | 1908 | MPC85xx SOCs and the IBM PowerPC 440. |
| 1909 | 1909 | |
| @@ -1994,7 +1994,7 @@ config SH_WDT · 84 unmodified lines | ||
| 1994 | 1994 | config WATCHDOG_CP1XXX |
| 1995 | 1995 | tristate "CP1XXX Hardware Watchdog support" |
| 1996 | 1996 | depends on SPARC64 && PCI |
| 1997 | − ---help--- | |
| 1997 | + help | |
| 1998 | 1998 | This is the driver for the hardware watchdog timers present on |
| 1999 | 1999 | Sun Microsystems CompactPCI models CP1400 and CP1500. |
| 2000 | 2000 | |
| @@ -2051,7 +2051,7 @@ comment "ISA-based Watchdog Cards" · 50 unmodified lines | ||
| 2051 | 2051 | config PCWATCHDOG |
| 2052 | 2052 | tristate "Berkshire Products ISA-PC Watchdog" |
| 2053 | 2053 | depends on ISA |
| 2054 | − ---help--- | |
| 2054 | + help | |
| 2055 | 2055 | This is the driver for the Berkshire Products ISA-PC Watchdog card. |
| 2056 | 2056 | This card simply watches your kernel to make sure it doesn't freeze, |
| 2057 | 2057 | and if it does, it reboots your computer after a certain amount of |
| @@ -2067,7 +2067,7 @@ config PCWATCHDOG · 9 unmodified lines | ||
| 2067 | 2067 | config MIXCOMWD |
| 2068 | 2068 | tristate "Mixcom Watchdog" |
| 2069 | 2069 | depends on ISA |
| 2070 | − ---help--- | |
| 2070 | + help | |
| 2071 | 2071 | This is a driver for the Mixcom hardware watchdog cards. This |
| 2072 | 2072 | watchdog simply watches your kernel to make sure it doesn't freeze, |
| 2073 | 2073 | and if it does, it reboots your computer after a certain amount of |
| @@ -2081,7 +2081,7 @@ config MIXCOMWD · 7 unmodified lines | ||
| 2081 | 2081 | config WDT |
| 2082 | 2082 | tristate "WDT Watchdog timer" |
| 2083 | 2083 | depends on ISA |
| 2084 | − ---help--- | |
| 2084 | + help | |
| 2085 | 2085 | If you have a WDT500P or WDT501P watchdog board, say Y here, |
| 2086 | 2086 | otherwise N. It is not possible to probe for this board, which means |
| 2087 | 2087 | that you have to inform the kernel about the IO port and IRQ that |
| @@ -2100,7 +2100,7 @@ comment "PCI-based Watchdog Cards" · 12 unmodified lines | ||
| 2100 | 2100 | config PCIPCWATCHDOG |
| 2101 | 2101 | tristate "Berkshire Products PCI-PC Watchdog" |
| 2102 | 2102 | depends on PCI |
| 2103 | − ---help--- | |
| 2103 | + help | |
| 2104 | 2104 | This is the driver for the Berkshire Products PCI-PC Watchdog card. |
| 2105 | 2105 | This card simply watches your kernel to make sure it doesn't freeze, |
| 2106 | 2106 | and if it does, it reboots your computer after a certain amount of |
| @@ -2115,7 +2115,7 @@ config PCIPCWATCHDOG · 8 unmodified lines | ||
| 2115 | 2115 | config WDTPCI |
| 2116 | 2116 | tristate "PCI-WDT500/501 Watchdog timer" |
| 2117 | 2117 | depends on PCI |
| 2118 | − ---help--- | |
| 2118 | + help | |
| 2119 | 2119 | If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N. |
| 2120 | 2120 | |
| 2121 | 2121 | If you have a PCI-WDT501 watchdog board then you can enable the |
| @@ -2138,7 +2138,7 @@ comment "USB-based Watchdog Cards" · 16 unmodified lines | ||
| 2138 | 2138 | config USBPCWATCHDOG |
| 2139 | 2139 | tristate "Berkshire Products USB-PC Watchdog" |
| 2140 | 2140 | depends on USB |
| 2141 | − ---help--- | |
| 2141 | + help | |
| 2142 | 2142 | This is the driver for the Berkshire Products USB-PC Watchdog card. |
| 2143 | 2143 | This card simply watches your kernel to make sure it doesn't freeze, |
| 2144 | 2144 | and if it does, it reboots your computer after a certain amount of |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | config ZORRO_NAMES |
| 6 | 6 | bool "Zorro device name database" |
| 7 | 7 | depends on ZORRO |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | By default, the kernel contains a database of all known Zorro device |
| 10 | 10 | names to make the information in /proc/iomem comprehensible to the |
| 11 | 11 | user. This database increases the size of the kernel image by about |
| @@ -229,7 +229,7 @@ endmenu · 228 unmodified lines | ||
| 229 | 229 | menuconfig MISC_FILESYSTEMS |
| 230 | 230 | bool "Miscellaneous filesystems" |
| 231 | 231 | default y |
| 232 | − ---help--- | |
| 232 | + help | |
| 233 | 233 | Say Y here to get to see options for various miscellaneous |
| 234 | 234 | filesystems, such as filesystems that came from other |
| 235 | 235 | operating systems. |
| @@ -274,7 +274,7 @@ menuconfig NETWORK_FILESYSTEMS · 38 unmodified lines | ||
| 274 | 274 | bool "Network File Systems" |
| 275 | 275 | default y |
| 276 | 276 | depends on NET |
| 277 | − ---help--- | |
| 277 | + help | |
| 278 | 278 | Say Y here to get to see options for network filesystems and |
| 279 | 279 | filesystem-related networking code, such as NFS daemon and |
| 280 | 280 | RPCSEC security modules. |
| @@ -7,7 +7,7 @@ config BINFMT_ELF · 6 unmodified lines | ||
| 7 | 7 | depends on MMU |
| 8 | 8 | select ELFCORE |
| 9 | 9 | default y |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | ELF (Executable and Linkable Format) is a format for libraries and |
| 12 | 12 | executables used across different architectures and operating |
| 13 | 13 | systems. Saying Y here will enable your kernel to run ELF binaries |
| @@ -138,7 +138,7 @@ config HAVE_AOUT · 124 unmodified lines | ||
| 138 | 138 | config BINFMT_AOUT |
| 139 | 139 | tristate "Kernel support for a.out and ECOFF binaries" |
| 140 | 140 | depends on HAVE_AOUT |
| 141 | − ---help--- | |
| 141 | + help | |
| 142 | 142 | A.out (Assembler.OUTput) is a set of formats for libraries and |
| 143 | 143 | executables used in the earliest versions of UNIX. Linux used |
| 144 | 144 | the a.out formats QMAGIC and ZMAGIC until they were replaced |
| @@ -168,7 +168,7 @@ config OSF4_COMPAT · 23 unmodified lines | ||
| 168 | 168 | config BINFMT_EM86 |
| 169 | 169 | tristate "Kernel support for Linux/Intel ELF binaries" |
| 170 | 170 | depends on ALPHA |
| 171 | − ---help--- | |
| 171 | + help | |
| 172 | 172 | Say Y here if you want to be able to execute Linux/Intel ELF |
| 173 | 173 | binaries just like native Alpha binaries on your Alpha machine. For |
| 174 | 174 | this to work, you need to have the emulator /usr/bin/em86 in place. |
| @@ -182,7 +182,7 @@ config BINFMT_EM86 · 7 unmodified lines | ||
| 182 | 182 | |
| 183 | 183 | config BINFMT_MISC |
| 184 | 184 | tristate "Kernel support for MISC binaries" |
| 185 | − ---help--- | |
| 185 | + help | |
| 186 | 186 | If you say Y here, it will be possible to plug wrapper-driven binary |
| 187 | 187 | formats into the kernel. You will like this especially when you use |
| 188 | 188 | programs that need an interpreter to run like Java, Python, .NET or |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | |
| 6 | 6 | menuconfig NLS |
| 7 | 7 | tristate "Native language support" |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | The base Native Language Support. A number of filesystems |
| 10 | 10 | depend on it (e.g. FAT, JOLIET, NT, BEOS filesystems), as well |
| 11 | 11 | as the ability of some filesystems to use native languages |
| @@ -21,7 +21,7 @@ if NLS · 9 unmodified lines | ||
| 21 | 21 | config NLS_DEFAULT |
| 22 | 22 | string "Default NLS Option" |
| 23 | 23 | default "iso8859-1" |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | The default NLS used when mounting file system. Note, that this is |
| 26 | 26 | the NLS used by your console, not the NLS used by a specific file |
| 27 | 27 | system (if different) to store data (filenames) on a disk. |
| @@ -76,7 +76,7 @@ config NLS_CODEPAGE_775 · 48 unmodified lines | ||
| 76 | 76 | |
| 77 | 77 | config NLS_CODEPAGE_850 |
| 78 | 78 | tristate "Codepage 850 (Europe)" |
| 79 | − ---help--- | |
| 79 | + help | |
| 80 | 80 | The Microsoft FAT file system family can deal with filenames in |
| 81 | 81 | native language character sets. These character sets are stored in |
| 82 | 82 | so-called DOS codepages. You need to include the appropriate |
| @@ -92,7 +92,7 @@ config NLS_CODEPAGE_850 · 9 unmodified lines | ||
| 92 | 92 | |
| 93 | 93 | config NLS_CODEPAGE_852 |
| 94 | 94 | tristate "Codepage 852 (Central/Eastern Europe)" |
| 95 | − ---help--- | |
| 95 | + help | |
| 96 | 96 | The Microsoft FAT file system family can deal with filenames in |
| 97 | 97 | native language character sets. These character sets are stored in |
| 98 | 98 | so-called DOS codepages. You need to include the appropriate |
| @@ -421,7 +421,7 @@ config NLS_ISO8859_14 · 322 unmodified lines | ||
| 421 | 421 | |
| 422 | 422 | config NLS_ISO8859_15 |
| 423 | 423 | tristate "NLS ISO 8859-15 (Latin 9; Western European Languages with Euro)" |
| 424 | − ---help--- | |
| 424 | + help | |
| 425 | 425 | If you want to display filenames with native language characters |
| 426 | 426 | from the Microsoft FAT file system family or from JOLIET CD-ROMs |
| 427 | 427 | correctly on the screen, you need to include the appropriate |
| @@ -455,7 +455,7 @@ config NLS_KOI8_U · 27 unmodified lines | ||
| 455 | 455 | |
| 456 | 456 | config NLS_MAC_ROMAN |
| 457 | 457 | tristate "Codepage macroman" |
| 458 | − ---help--- | |
| 458 | + help | |
| 459 | 459 | The Apple HFS file system family can deal with filenames in |
| 460 | 460 | native language character sets. These character sets are stored in |
| 461 | 461 | so-called MAC codepages. You need to include the appropriate |
| @@ -470,7 +470,7 @@ config NLS_MAC_ROMAN · 8 unmodified lines | ||
| 470 | 470 | |
| 471 | 471 | config NLS_MAC_CELTIC |
| 472 | 472 | tristate "Codepage macceltic" |
| 473 | − ---help--- | |
| 473 | + help | |
| 474 | 474 | The Apple HFS file system family can deal with filenames in |
| 475 | 475 | native language character sets. These character sets are stored in |
| 476 | 476 | so-called MAC codepages. You need to include the appropriate |
| @@ -484,7 +484,7 @@ config NLS_MAC_CELTIC · 7 unmodified lines | ||
| 484 | 484 | |
| 485 | 485 | config NLS_MAC_CENTEURO |
| 486 | 486 | tristate "Codepage maccenteuro" |
| 487 | − ---help--- | |
| 487 | + help | |
| 488 | 488 | The Apple HFS file system family can deal with filenames in |
| 489 | 489 | native language character sets. These character sets are stored in |
| 490 | 490 | so-called MAC codepages. You need to include the appropriate |
| @@ -498,7 +498,7 @@ config NLS_MAC_CENTEURO · 7 unmodified lines | ||
| 498 | 498 | |
| 499 | 499 | config NLS_MAC_CROATIAN |
| 500 | 500 | tristate "Codepage maccroatian" |
| 501 | − ---help--- | |
| 501 | + help | |
| 502 | 502 | The Apple HFS file system family can deal with filenames in |
| 503 | 503 | native language character sets. These character sets are stored in |
| 504 | 504 | so-called MAC codepages. You need to include the appropriate |
| @@ -512,7 +512,7 @@ config NLS_MAC_CROATIAN · 7 unmodified lines | ||
| 512 | 512 | |
| 513 | 513 | config NLS_MAC_CYRILLIC |
| 514 | 514 | tristate "Codepage maccyrillic" |
| 515 | − ---help--- | |
| 515 | + help | |
| 516 | 516 | The Apple HFS file system family can deal with filenames in |
| 517 | 517 | native language character sets. These character sets are stored in |
| 518 | 518 | so-called MAC codepages. You need to include the appropriate |
| @@ -526,7 +526,7 @@ config NLS_MAC_CYRILLIC · 7 unmodified lines | ||
| 526 | 526 | |
| 527 | 527 | config NLS_MAC_GAELIC |
| 528 | 528 | tristate "Codepage macgaelic" |
| 529 | − ---help--- | |
| 529 | + help | |
| 530 | 530 | The Apple HFS file system family can deal with filenames in |
| 531 | 531 | native language character sets. These character sets are stored in |
| 532 | 532 | so-called MAC codepages. You need to include the appropriate |
| @@ -540,7 +540,7 @@ config NLS_MAC_GAELIC · 7 unmodified lines | ||
| 540 | 540 | |
| 541 | 541 | config NLS_MAC_GREEK |
| 542 | 542 | tristate "Codepage macgreek" |
| 543 | − ---help--- | |
| 543 | + help | |
| 544 | 544 | The Apple HFS file system family can deal with filenames in |
| 545 | 545 | native language character sets. These character sets are stored in |
| 546 | 546 | so-called MAC codepages. You need to include the appropriate |
| @@ -554,7 +554,7 @@ config NLS_MAC_GREEK · 7 unmodified lines | ||
| 554 | 554 | |
| 555 | 555 | config NLS_MAC_ICELAND |
| 556 | 556 | tristate "Codepage maciceland" |
| 557 | − ---help--- | |
| 557 | + help | |
| 558 | 558 | The Apple HFS file system family can deal with filenames in |
| 559 | 559 | native language character sets. These character sets are stored in |
| 560 | 560 | so-called MAC codepages. You need to include the appropriate |
| @@ -568,7 +568,7 @@ config NLS_MAC_ICELAND · 7 unmodified lines | ||
| 568 | 568 | |
| 569 | 569 | config NLS_MAC_INUIT |
| 570 | 570 | tristate "Codepage macinuit" |
| 571 | − ---help--- | |
| 571 | + help | |
| 572 | 572 | The Apple HFS file system family can deal with filenames in |
| 573 | 573 | native language character sets. These character sets are stored in |
| 574 | 574 | so-called MAC codepages. You need to include the appropriate |
| @@ -582,7 +582,7 @@ config NLS_MAC_INUIT · 7 unmodified lines | ||
| 582 | 582 | |
| 583 | 583 | config NLS_MAC_ROMANIAN |
| 584 | 584 | tristate "Codepage macromanian" |
| 585 | − ---help--- | |
| 585 | + help | |
| 586 | 586 | The Apple HFS file system family can deal with filenames in |
| 587 | 587 | native language character sets. These character sets are stored in |
| 588 | 588 | so-called MAC codepages. You need to include the appropriate |
| @@ -596,7 +596,7 @@ config NLS_MAC_ROMANIAN · 7 unmodified lines | ||
| 596 | 596 | |
| 597 | 597 | config NLS_MAC_TURKISH |
| 598 | 598 | tristate "Codepage macturkish" |
| 599 | − ---help--- | |
| 599 | + help | |
| 600 | 600 | The Apple HFS file system family can deal with filenames in |
| 601 | 601 | native language character sets. These character sets are stored in |
| 602 | 602 | so-called MAC codepages. You need to include the appropriate |
| @@ -4,7 +4,7 @@ config FANOTIFY · 3 unmodified lines | ||
| 4 | 4 | select FSNOTIFY |
| 5 | 5 | select EXPORTFS |
| 6 | 6 | default n |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | Say Y here to enable fanotify support. fanotify is a file access |
| 9 | 9 | notification system which differs from inotify in that it sends |
| 10 | 10 | an open file descriptor to the userspace listener along with |
| @@ -17,7 +17,7 @@ config FANOTIFY_ACCESS_PERMISSIONS · 6 unmodified lines | ||
| 17 | 17 | depends on FANOTIFY |
| 18 | 18 | depends on SECURITY |
| 19 | 19 | default n |
| 20 | − ---help--- | |
| 20 | + help | |
| 21 | 21 | Say Y here is you want fanotify listeners to be able to make permissions |
| 22 | 22 | decisions concerning filesystem events. This is used by some fanotify |
| 23 | 23 | listeners which need to scan files before allowing the system access to |
| @@ -3,7 +3,7 @@ config INOTIFY_USER · 2 unmodified lines | ||
| 3 | 3 | bool "Inotify support for userspace" |
| 4 | 4 | select FSNOTIFY |
| 5 | 5 | default y |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | Say Y here to enable inotify support for userspace, including the |
| 8 | 8 | associated system calls. Inotify allows monitoring of both files and |
| 9 | 9 | directories via a single open fd. Events are read from the file |
| @@ -66,7 +66,7 @@ config PROC_SYSCTL · 65 unmodified lines | ||
| 66 | 66 | depends on PROC_FS |
| 67 | 67 | select SYSCTL |
| 68 | 68 | default y |
| 69 | − ---help--- | |
| 69 | + help | |
| 70 | 70 | The sysctl interface provides a means of dynamically changing |
| 71 | 71 | certain kernel parameters and variables on the fly without requiring |
| 72 | 72 | a recompile of the kernel or reboot of the system. The primary |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config ROMFS_FS |
| 3 | 3 | tristate "ROM file system support" |
| 4 | 4 | depends on BLOCK || MTD |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This is a very small read-only file system mainly intended for |
| 7 | 7 | initial ram disks of installation disks, but it could be used for |
| 8 | 8 | other read-only media as well. Read |
| @@ -326,7 +326,7 @@ config SWAP · 325 unmodified lines | ||
| 326 | 326 | |
| 327 | 327 | config SYSVIPC |
| 328 | 328 | bool "System V IPC" |
| 329 | − ---help--- | |
| 329 | + help | |
| 330 | 330 | Inter Process Communication is a suite of library functions and |
| 331 | 331 | system calls which let processes (running programs) synchronize and |
| 332 | 332 | exchange information. It is generally considered to be a good thing, |
| @@ -348,7 +348,7 @@ config SYSVIPC_SYSCTL · 15 unmodified lines | ||
| 348 | 348 | config POSIX_MQUEUE |
| 349 | 349 | bool "POSIX Message Queues" |
| 350 | 350 | depends on NET |
| 351 | − ---help--- | |
| 351 | + help | |
| 352 | 352 | POSIX variant of message queues is a part of IPC. In POSIX message |
| 353 | 353 | queues every message has a priority which decides about succession |
| 354 | 354 | of receiving it by a process. If you want to compile and run |
| @@ -626,7 +626,7 @@ config BUILD_BIN2C · 271 unmodified lines | ||
| 626 | 626 | |
| 627 | 627 | config IKCONFIG |
| 628 | 628 | tristate "Kernel .config support" |
| 629 | − ---help--- | |
| 629 | + help | |
| 630 | 630 | This option enables the complete Linux kernel ".config" file |
| 631 | 631 | contents to be saved in the kernel. It provides documentation |
| 632 | 632 | of which kernel options are used in a running kernel or in an |
| @@ -639,7 +639,7 @@ config IKCONFIG · 6 unmodified lines | ||
| 639 | 639 | config IKCONFIG_PROC |
| 640 | 640 | bool "Enable access to .config through /proc/config.gz" |
| 641 | 641 | depends on IKCONFIG && PROC_FS |
| 642 | − ---help--- | |
| 642 | + help | |
| 643 | 643 | This option enables access to the kernel configuration file |
| 644 | 644 | through /proc/config.gz. |
| 645 | 645 | |
| @@ -885,7 +885,7 @@ config BLK_CGROUP · 239 unmodified lines | ||
| 885 | 885 | bool "IO controller" |
| 886 | 886 | depends on BLOCK |
| 887 | 887 | default n |
| 888 | − ---help--- | |
| 888 | + help | |
| 889 | 889 | Generic block IO controller cgroup interface. This is the common |
| 890 | 890 | cgroup interface which should be used by various IO controlling |
| 891 | 891 | policies. |
| @@ -1386,7 +1386,7 @@ config MULTIUSER · 494 unmodified lines | ||
| 1386 | 1386 | config SGETMASK_SYSCALL |
| 1387 | 1387 | bool "sgetmask/ssetmask syscalls support" if EXPERT |
| 1388 | 1388 | def_bool PARISC || M68K || PPC || MIPS || X86 || SPARC || MICROBLAZE || SUPERH |
| 1389 | − ---help--- | |
| 1389 | + help | |
| 1390 | 1390 | sys_sgetmask and sys_ssetmask are obsolete system calls |
| 1391 | 1391 | no longer supported in libc but still enabled by default in some |
| 1392 | 1392 | architectures. |
| @@ -1396,7 +1396,7 @@ config SGETMASK_SYSCALL · 3 unmodified lines | ||
| 1396 | 1396 | config SYSFS_SYSCALL |
| 1397 | 1397 | bool "Sysfs syscall support" if EXPERT |
| 1398 | 1398 | default y |
| 1399 | − ---help--- | |
| 1399 | + help | |
| 1400 | 1400 | sys_sysfs is an obsolete system call no longer supported in libc. |
| 1401 | 1401 | Note that disabling this option is more secure but might break |
| 1402 | 1402 | compatibility with some systems. |
| @@ -6,7 +6,7 @@ config GCOV_KERNEL · 5 unmodified lines | ||
| 6 | 6 | depends on DEBUG_FS |
| 7 | 7 | select CONSTRUCTORS if !UML |
| 8 | 8 | default n |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This option enables gcov-based code profiling (e.g. for code coverage |
| 11 | 11 | measurements). |
| 12 | 12 | |
| @@ -42,7 +42,7 @@ config GCOV_PROFILE_ALL · 29 unmodified lines | ||
| 42 | 42 | depends on GCOV_KERNEL |
| 43 | 43 | depends on ARCH_HAS_GCOV_PROFILE_ALL |
| 44 | 44 | default n |
| 45 | − ---help--- | |
| 45 | + help | |
| 46 | 46 | This options activates profiling for the entire kernel. |
| 47 | 47 | |
| 48 | 48 | If unsure, say N. |
| @@ -118,7 +118,7 @@ config IRQ_FORCED_THREADING · 117 unmodified lines | ||
| 118 | 118 | |
| 119 | 119 | config SPARSE_IRQ |
| 120 | 120 | bool "Support sparse irq numbering" if MAY_HAVE_SPARSE_IRQ |
| 121 | − ---help--- | |
| 121 | + help | |
| 122 | 122 | |
| 123 | 123 | Sparse irq numbering is useful for distro kernels that want |
| 124 | 124 | to define a high CONFIG_NR_CPUS value but still want to have |
| @@ -134,7 +134,7 @@ config GENERIC_IRQ_DEBUGFS · 9 unmodified lines | ||
| 134 | 134 | depends on DEBUG_FS |
| 135 | 135 | select GENERIC_IRQ_INJECTION |
| 136 | 136 | default n |
| 137 | − ---help--- | |
| 137 | + help | |
| 138 | 138 | |
| 139 | 139 | Exposes internal state information through debugfs. Mostly for |
| 140 | 140 | developers and debugging of hard to diagnose interrupt problems. |
| @@ -3,7 +3,7 @@ config SUSPEND · 2 unmodified lines | ||
| 3 | 3 | bool "Suspend to RAM and standby" |
| 4 | 4 | depends on ARCH_SUSPEND_POSSIBLE |
| 5 | 5 | default y |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | Allow the system to enter sleep states in which main memory is |
| 8 | 8 | powered and thus its contents are preserved, such as the |
| 9 | 9 | suspend-to-RAM state (e.g. the ACPI S3 state). |
| @@ -42,7 +42,7 @@ config HIBERNATION · 32 unmodified lines | ||
| 42 | 42 | select LZO_COMPRESS |
| 43 | 43 | select LZO_DECOMPRESS |
| 44 | 44 | select CRC32 |
| 45 | − ---help--- | |
| 45 | + help | |
| 46 | 46 | Enable the suspend to disk (STD) functionality, which is usually |
| 47 | 47 | called "hibernation" in user interfaces. STD checkpoints the |
| 48 | 48 | system and powers it off; and restores that checkpoint on reboot. |
| @@ -84,7 +84,7 @@ config HIBERNATION_SNAPSHOT_DEV · 35 unmodified lines | ||
| 84 | 84 | bool "Userspace snapshot device" |
| 85 | 85 | depends on HIBERNATION |
| 86 | 86 | default y |
| 87 | − ---help--- | |
| 87 | + help | |
| 88 | 88 | Device used by the uswsusp tools. |
| 89 | 89 | |
| 90 | 90 | Say N if no snapshotting from userspace is needed, this also |
| @@ -96,7 +96,7 @@ config PM_STD_PARTITION · 5 unmodified lines | ||
| 96 | 96 | string "Default resume partition" |
| 97 | 97 | depends on HIBERNATION |
| 98 | 98 | default "" |
| 99 | − ---help--- | |
| 99 | + help | |
| 100 | 100 | The default resume partition is the partition that the suspend- |
| 101 | 101 | to-disk implementation will look for a suspended disk image. |
| 102 | 102 | |
| @@ -131,7 +131,7 @@ config PM_SLEEP_SMP_NONZERO_CPU · 28 unmodified lines | ||
| 131 | 131 | def_bool y |
| 132 | 132 | depends on PM_SLEEP_SMP |
| 133 | 133 | depends on ARCH_SUSPEND_NONZERO_CPU |
| 134 | − ---help--- | |
| 134 | + help | |
| 135 | 135 | If an arch can suspend (for suspend, hibernate, kexec, etc) on a |
| 136 | 136 | non-zero numbered CPU, it may define ARCH_SUSPEND_NONZERO_CPU. This |
| 137 | 137 | will allow nohz_full mask to include CPU0. |
| @@ -140,7 +140,7 @@ config PM_AUTOSLEEP · 2 unmodified lines | ||
| 140 | 140 | bool "Opportunistic sleep" |
| 141 | 141 | depends on PM_SLEEP |
| 142 | 142 | default n |
| 143 | − ---help--- | |
| 143 | + help | |
| 144 | 144 | Allow the kernel to trigger a system transition into a global sleep |
| 145 | 145 | state automatically whenever there are no active wakeup sources. |
| 146 | 146 | |
| @@ -148,7 +148,7 @@ config PM_WAKELOCKS · 1 unmodified line | ||
| 148 | 148 | bool "User space wakeup sources interface" |
| 149 | 149 | depends on PM_SLEEP |
| 150 | 150 | default n |
| 151 | − ---help--- | |
| 151 | + help | |
| 152 | 152 | Allow user space to create, activate and deactivate wakeup source |
| 153 | 153 | objects with the help of a sysfs-based interface. |
| 154 | 154 | |
| @@ -165,7 +165,7 @@ config PM_WAKELOCKS_GC · 10 unmodified lines | ||
| 165 | 165 | |
| 166 | 166 | config PM |
| 167 | 167 | bool "Device power management core functionality" |
| 168 | − ---help--- | |
| 168 | + help | |
| 169 | 169 | Enable functionality allowing I/O devices to be put into energy-saving |
| 170 | 170 | (low power) states, for example after a specified period of inactivity |
| 171 | 171 | (autosuspended), and woken up in response to a hardware-generated |
| @@ -179,7 +179,7 @@ config PM · 7 unmodified lines | ||
| 179 | 179 | config PM_DEBUG |
| 180 | 180 | bool "Power Management Debug Support" |
| 181 | 181 | depends on PM |
| 182 | − ---help--- | |
| 182 | + help | |
| 183 | 183 | This option enables various debugging support in the Power Management |
| 184 | 184 | code. This is helpful when debugging and reporting PM bugs, like |
| 185 | 185 | suspend support. |
| @@ -187,7 +187,7 @@ config PM_DEBUG · 1 unmodified line | ||
| 187 | 187 | config PM_ADVANCED_DEBUG |
| 188 | 188 | bool "Extra PM attributes in sysfs for low-level debugging/testing" |
| 189 | 189 | depends on PM_DEBUG |
| 190 | − ---help--- | |
| 190 | + help | |
| 191 | 191 | Add extra sysfs attributes allowing one to access some Power Management |
| 192 | 192 | fields of device objects from user space. If you are not a kernel |
| 193 | 193 | developer interested in debugging/testing Power Management, say "no". |
| @@ -195,7 +195,7 @@ config PM_ADVANCED_DEBUG · 1 unmodified line | ||
| 195 | 195 | config PM_TEST_SUSPEND |
| 196 | 196 | bool "Test suspend/resume and wakealarm during bootup" |
| 197 | 197 | depends on SUSPEND && PM_DEBUG && RTC_CLASS=y |
| 198 | − ---help--- | |
| 198 | + help | |
| 199 | 199 | This option will let you suspend your machine during bootup, and |
| 200 | 200 | make it wake up a few seconds later using an RTC wakeup alarm. |
| 201 | 201 | Enable this with a kernel parameter like "test_suspend=mem". |
| @@ -210,7 +210,7 @@ config PM_SLEEP_DEBUG · 8 unmodified lines | ||
| 210 | 210 | config DPM_WATCHDOG |
| 211 | 211 | bool "Device suspend/resume watchdog" |
| 212 | 212 | depends on PM_DEBUG && PSTORE && EXPERT |
| 213 | − ---help--- | |
| 213 | + help | |
| 214 | 214 | Sets up a watchdog timer to capture drivers that are |
| 215 | 215 | locked up attempting to suspend/resume a device. |
| 216 | 216 | A detected lockup causes system panic with message |
| @@ -243,7 +243,7 @@ config PM_TRACE_RTC · 26 unmodified lines | ||
| 243 | 243 | depends on PM_SLEEP_DEBUG |
| 244 | 244 | depends on X86 |
| 245 | 245 | select PM_TRACE |
| 246 | − ---help--- | |
| 246 | + help | |
| 247 | 247 | This enables some cheesy code to save the last PM event point in the |
| 248 | 248 | RTC across reboots, so that you can debug a machine that just hangs |
| 249 | 249 | during suspend (or more commonly, during resume). |
| @@ -822,7 +822,7 @@ config HAVE_DEBUG_STACKOVERFLOW · 821 unmodified lines | ||
| 822 | 822 | config DEBUG_STACKOVERFLOW |
| 823 | 823 | bool "Check for stack overflows" |
| 824 | 824 | depends on DEBUG_KERNEL && HAVE_DEBUG_STACKOVERFLOW |
| 825 | − ---help--- | |
| 825 | + help | |
| 826 | 826 | Say Y here if you want to check for overflows of kernel, IRQ |
| 827 | 827 | and exception stacks (if your architecture uses them). This |
| 828 | 828 | option will show detailed messages if free stack space drops |
| @@ -1956,7 +1956,7 @@ config ASYNC_RAID6_TEST · 1127 unmodified lines | ||
| 1956 | 1956 | tristate "Self test for hardware accelerated raid6 recovery" |
| 1957 | 1957 | depends on ASYNC_RAID6_RECOV |
| 1958 | 1958 | select ASYNC_MEMCPY |
| 1959 | − ---help--- | |
| 1959 | + help | |
| 1960 | 1960 | This is a one-shot self test that permutes through the |
| 1961 | 1961 | recovery of all the possible two disk failure scenarios for a |
| 1962 | 1962 | N-disk array. Recovery is performed with the asynchronous |
| @@ -2312,7 +2312,7 @@ endif # RUNTIME_TESTING_MENU · 349 unmodified lines | ||
| 2312 | 2312 | |
| 2313 | 2313 | config MEMTEST |
| 2314 | 2314 | bool "Memtest" |
| 2315 | − ---help--- | |
| 2315 | + help | |
| 2316 | 2316 | This option adds a kernel parameter 'memtest', which allows memtest |
| 2317 | 2317 | to be set. |
| 2318 | 2318 | memtest=0, mean disabled; -- default |
| @@ -1,7 +1,7 @@ | ||
| 1 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | 2 | config PAGE_EXTENSION |
| 3 | 3 | bool "Extend memmap on extra space for more information on page" |
| 4 | − ---help--- | |
| 4 | + help | |
| 5 | 5 | Extend memmap on extra space for more information on page. This |
| 6 | 6 | could be used for debugging features that need to insert extra |
| 7 | 7 | field for every page. This extension enables us to save memory |
| @@ -13,7 +13,7 @@ config DEBUG_PAGEALLOC · 5 unmodified lines | ||
| 13 | 13 | depends on DEBUG_KERNEL |
| 14 | 14 | depends on !HIBERNATION || ARCH_SUPPORTS_DEBUG_PAGEALLOC && !PPC && !SPARC |
| 15 | 15 | select PAGE_POISONING if !ARCH_SUPPORTS_DEBUG_PAGEALLOC |
| 16 | − ---help--- | |
| 16 | + help | |
| 17 | 17 | Unmap pages from the kernel linear mapping after free_pages(). |
| 18 | 18 | Depending on runtime enablement, this results in a small or large |
| 19 | 19 | slowdown, but helps to find certain types of memory corruption. |
| @@ -41,7 +41,7 @@ config DEBUG_PAGEALLOC · 21 unmodified lines | ||
| 41 | 41 | config DEBUG_PAGEALLOC_ENABLE_DEFAULT |
| 42 | 42 | bool "Enable debug page memory allocations by default?" |
| 43 | 43 | depends on DEBUG_PAGEALLOC |
| 44 | − ---help--- | |
| 44 | + help | |
| 45 | 45 | Enable debug page memory allocations by default? This value |
| 46 | 46 | can be overridden by debug_pagealloc=off|on. |
| 47 | 47 | |
| @@ -65,7 +65,7 @@ config PAGE_OWNER · 17 unmodified lines | ||
| 65 | 65 | config PAGE_POISONING |
| 66 | 66 | bool "Poison pages after freeing" |
| 67 | 67 | select PAGE_POISONING_NO_SANITY if HIBERNATION |
| 68 | − ---help--- | |
| 68 | + help | |
| 69 | 69 | Fill the pages with poison patterns after free_pages() and verify |
| 70 | 70 | the patterns before alloc_pages. The filling of the memory helps |
| 71 | 71 | reduce the risk of information leaks from freed data. This does |
| @@ -80,7 +80,7 @@ config PAGE_POISONING · 8 unmodified lines | ||
| 80 | 80 | config PAGE_POISONING_NO_SANITY |
| 81 | 81 | depends on PAGE_POISONING |
| 82 | 82 | bool "Only poison, don't sanity check" |
| 83 | − ---help--- | |
| 83 | + help | |
| 84 | 84 | Skip the sanity checking on alloc, only fill the pages with |
| 85 | 85 | poison on free. This reduces some of the overhead of the |
| 86 | 86 | poisoning feature. |
| @@ -91,7 +91,7 @@ config PAGE_POISONING_NO_SANITY · 4 unmodified lines | ||
| 91 | 91 | config PAGE_POISONING_ZERO |
| 92 | 92 | bool "Use zero for poisoning instead of debugging value" |
| 93 | 93 | depends on PAGE_POISONING |
| 94 | − ---help--- | |
| 94 | + help | |
| 95 | 95 | Instead of using the existing poison value, fill the pages with |
| 96 | 96 | zeros. This makes it harder to detect when errors are occurring |
| 97 | 97 | due to sanitization but the zeroing at free means that it is |
| @@ -104,7 +104,7 @@ config DEBUG_PAGE_REF · 6 unmodified lines | ||
| 104 | 104 | bool "Enable tracepoint to track down page reference manipulation" |
| 105 | 105 | depends on DEBUG_KERNEL |
| 106 | 106 | depends on TRACEPOINTS |
| 107 | − ---help--- | |
| 107 | + help | |
| 108 | 108 | This is a feature to add tracepoint for tracking down page reference |
| 109 | 109 | manipulation. This tracking is useful to diagnose functional failure |
| 110 | 110 | due to migration failures caused by page reference mismatches. Be |
| @@ -115,7 +115,7 @@ config DEBUG_PAGE_REF · 4 unmodified lines | ||
| 115 | 115 | config DEBUG_RODATA_TEST |
| 116 | 116 | bool "Testcase for the marking rodata read-only" |
| 117 | 117 | depends on STRICT_KERNEL_RWX |
| 118 | − ---help--- | |
| 118 | + help | |
| 119 | 119 | This option enables a testcase for the setting rodata read-only. |
| 120 | 120 | |
| 121 | 121 | config ARCH_HAS_DEBUG_WX |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | menuconfig 6LOWPAN |
| 3 | 3 | tristate "6LoWPAN Support" |
| 4 | 4 | depends on IPV6 |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This enables IPv6 over Low power Wireless Personal Area Network - |
| 7 | 7 | "6LoWPAN" which is supported by IEEE 802.15.4 or Bluetooth stacks. |
| 8 | 8 | |
| @@ -10,7 +10,7 @@ config 6LOWPAN_DEBUGFS · 1 unmodified line | ||
| 10 | 10 | bool "6LoWPAN debugfs support" |
| 11 | 11 | depends on 6LOWPAN |
| 12 | 12 | depends on DEBUG_FS |
| 13 | − ---help--- | |
| 13 | + help | |
| 14 | 14 | This enables 6LoWPAN debugfs support. For example to manipulate |
| 15 | 15 | IPHC context information at runtime. |
| 16 | 16 | |
| @@ -18,7 +18,7 @@ menuconfig 6LOWPAN_NHC · 1 unmodified line | ||
| 18 | 18 | tristate "Next Header and Generic Header Compression Support" |
| 19 | 19 | depends on 6LOWPAN |
| 20 | 20 | default y |
| 21 | − ---help--- | |
| 21 | + help | |
| 22 | 22 | Support for next header and generic header compression defined in |
| 23 | 23 | RFC6282 and RFC7400. |
| 24 | 24 | |
| @@ -27,78 +27,78 @@ if 6LOWPAN_NHC · 2 unmodified lines | ||
| 27 | 27 | config 6LOWPAN_NHC_DEST |
| 28 | 28 | tristate "Destination Options Header Support" |
| 29 | 29 | default y |
| 30 | − ---help--- | |
| 30 | + help | |
| 31 | 31 | 6LoWPAN IPv6 Destination Options Header compression according to |
| 32 | 32 | RFC6282. |
| 33 | 33 | |
| 34 | 34 | config 6LOWPAN_NHC_FRAGMENT |
| 35 | 35 | tristate "Fragment Header Support" |
| 36 | 36 | default y |
| 37 | − ---help--- | |
| 37 | + help | |
| 38 | 38 | 6LoWPAN IPv6 Fragment Header compression according to RFC6282. |
| 39 | 39 | |
| 40 | 40 | config 6LOWPAN_NHC_HOP |
| 41 | 41 | tristate "Hop-by-Hop Options Header Support" |
| 42 | 42 | default y |
| 43 | − ---help--- | |
| 43 | + help | |
| 44 | 44 | 6LoWPAN IPv6 Hop-by-Hop Options Header compression according to |
| 45 | 45 | RFC6282. |
| 46 | 46 | |
| 47 | 47 | config 6LOWPAN_NHC_IPV6 |
| 48 | 48 | tristate "IPv6 Header Support" |
| 49 | 49 | default y |
| 50 | − ---help--- | |
| 50 | + help | |
| 51 | 51 | 6LoWPAN IPv6 Header compression according to RFC6282. |
| 52 | 52 | |
| 53 | 53 | config 6LOWPAN_NHC_MOBILITY |
| 54 | 54 | tristate "Mobility Header Support" |
| 55 | 55 | default y |
| 56 | − ---help--- | |
| 56 | + help | |
| 57 | 57 | 6LoWPAN IPv6 Mobility Header compression according to RFC6282. |
| 58 | 58 | |
| 59 | 59 | config 6LOWPAN_NHC_ROUTING |
| 60 | 60 | tristate "Routing Header Support" |
| 61 | 61 | default y |
| 62 | − ---help--- | |
| 62 | + help | |
| 63 | 63 | 6LoWPAN IPv6 Routing Header compression according to RFC6282. |
| 64 | 64 | |
| 65 | 65 | config 6LOWPAN_NHC_UDP |
| 66 | 66 | tristate "UDP Header Support" |
| 67 | 67 | default y |
| 68 | − ---help--- | |
| 68 | + help | |
| 69 | 69 | 6LoWPAN IPv6 UDP Header compression according to RFC6282. |
| 70 | 70 | |
| 71 | 71 | config 6LOWPAN_GHC_EXT_HDR_HOP |
| 72 | 72 | tristate "GHC Hop-by-Hop Options Header Support" |
| 73 | − ---help--- | |
| 73 | + help | |
| 74 | 74 | 6LoWPAN IPv6 Hop-by-Hop option generic header compression according |
| 75 | 75 | to RFC7400. |
| 76 | 76 | |
| 77 | 77 | config 6LOWPAN_GHC_UDP |
| 78 | 78 | tristate "GHC UDP Support" |
| 79 | − ---help--- | |
| 79 | + help | |
| 80 | 80 | 6LoWPAN IPv6 UDP generic header compression according to RFC7400. |
| 81 | 81 | |
| 82 | 82 | config 6LOWPAN_GHC_ICMPV6 |
| 83 | 83 | tristate "GHC ICMPv6 Support" |
| 84 | − ---help--- | |
| 84 | + help | |
| 85 | 85 | 6LoWPAN IPv6 ICMPv6 generic header compression according to RFC7400. |
| 86 | 86 | |
| 87 | 87 | config 6LOWPAN_GHC_EXT_HDR_DEST |
| 88 | 88 | tristate "GHC Destination Options Header Support" |
| 89 | − ---help--- | |
| 89 | + help | |
| 90 | 90 | 6LoWPAN IPv6 destination option generic header compression according |
| 91 | 91 | to RFC7400. |
| 92 | 92 | |
| 93 | 93 | config 6LOWPAN_GHC_EXT_HDR_FRAG |
| 94 | 94 | tristate "GHC Fragmentation Options Header Support" |
| 95 | − ---help--- | |
| 95 | + help | |
| 96 | 96 | 6LoWPAN IPv6 fragmentation option generic header compression |
| 97 | 97 | according to RFC7400. |
| 98 | 98 | |
| 99 | 99 | config 6LOWPAN_GHC_EXT_HDR_ROUTE |
| 100 | 100 | tristate "GHC Routing Options Header Support" |
| 101 | − ---help--- | |
| 101 | + help | |
| 102 | 102 | 6LoWPAN IPv6 routing option generic header compression according |
| 103 | 103 | to RFC7400. |
| 104 | 104 | |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | |
| 6 | 6 | config VLAN_8021Q |
| 7 | 7 | tristate "802.1Q/802.1ad VLAN Support" |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | Select this and you will be able to create 802.1Q VLAN interfaces |
| 10 | 10 | on your Ethernet interfaces. 802.1Q VLAN supports almost |
| 11 | 11 | everything a regular Ethernet interface does, including |
| @@ -8,7 +8,7 @@ menuconfig NET · 7 unmodified lines | ||
| 8 | 8 | select NLATTR |
| 9 | 9 | select GENERIC_NET_UTILS |
| 10 | 10 | select BPF |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | Unless you really know what you are doing, you should say Y here. |
| 13 | 13 | The reason is that some programs need kernel networking support even |
| 14 | 14 | when running on a stand-alone machine that isn't connected to any |
| @@ -70,7 +70,7 @@ source "net/xdp/Kconfig" · 55 unmodified lines | ||
| 70 | 70 | |
| 71 | 71 | config INET |
| 72 | 72 | bool "TCP/IP networking" |
| 73 | − ---help--- | |
| 73 | + help | |
| 74 | 74 | These are the protocols used on the Internet and on most local |
| 75 | 75 | Ethernets. It is highly recommended to say Y here (this will enlarge |
| 76 | 76 | your kernel by about 400 KB), since some programs (e.g. the X window |
| @@ -121,7 +121,7 @@ config NETWORK_PHY_TIMESTAMPING · 44 unmodified lines | ||
| 121 | 121 | |
| 122 | 122 | menuconfig NETFILTER |
| 123 | 123 | bool "Network packet filtering framework (Netfilter)" |
| 124 | − ---help--- | |
| 124 | + help | |
| 125 | 125 | Netfilter is a framework for filtering and mangling network packets |
| 126 | 126 | that pass through your Linux box. |
| 127 | 127 | |
| @@ -192,7 +192,7 @@ config BRIDGE_NETFILTER · 64 unmodified lines | ||
| 192 | 192 | depends on NETFILTER_ADVANCED |
| 193 | 193 | select NETFILTER_FAMILY_BRIDGE |
| 194 | 194 | select SKB_EXTENSIONS |
| 195 | − ---help--- | |
| 195 | + help | |
| 196 | 196 | Enabling this option will let arptables resp. iptables see bridged |
| 197 | 197 | ARP resp. IP traffic. If you want a bridging firewall, you probably |
| 198 | 198 | want this option enabled. |
| @@ -268,7 +268,7 @@ config CGROUP_NET_PRIO · 69 unmodified lines | ||
| 268 | 268 | bool "Network priority cgroup" |
| 269 | 269 | depends on CGROUPS |
| 270 | 270 | select SOCK_CGROUP_DATA |
| 271 | − ---help--- | |
| 271 | + help | |
| 272 | 272 | Cgroup subsystem for use in assigning processes to network priorities on |
| 273 | 273 | a per-interface basis. |
| 274 | 274 | |
| @@ -276,7 +276,7 @@ config CGROUP_NET_CLASSID · 1 unmodified line | ||
| 276 | 276 | bool "Network classid cgroup" |
| 277 | 277 | depends on CGROUPS |
| 278 | 278 | select SOCK_CGROUP_DATA |
| 279 | − ---help--- | |
| 279 | + help | |
| 280 | 280 | Cgroup subsystem for use as general purpose socket classid marker that is |
| 281 | 281 | being used in cls_cgroup and for netfilter matching. |
| 282 | 282 | |
| @@ -294,7 +294,7 @@ config BPF_JIT · 11 unmodified lines | ||
| 294 | 294 | bool "enable BPF Just In Time compiler" |
| 295 | 295 | depends on HAVE_CBPF_JIT || HAVE_EBPF_JIT |
| 296 | 296 | depends on MODULES |
| 297 | − ---help--- | |
| 297 | + help | |
| 298 | 298 | Berkeley Packet Filter filtering capabilities are normally handled |
| 299 | 299 | by an interpreter. This option allows kernel to generate a native |
| 300 | 300 | code when filter is loaded in memory. This should speedup |
| @@ -312,7 +312,7 @@ config BPF_STREAM_PARSER · 11 unmodified lines | ||
| 312 | 312 | depends on CGROUP_BPF |
| 313 | 313 | select STREAM_PARSER |
| 314 | 314 | select NET_SOCK_MSG |
| 315 | − ---help--- | |
| 315 | + help | |
| 316 | 316 | Enabling this allows a stream parser to be used with |
| 317 | 317 | BPF_MAP_TYPE_SOCKMAP. |
| 318 | 318 | |
| @@ -324,7 +324,7 @@ config NET_FLOW_LIMIT · 5 unmodified lines | ||
| 324 | 324 | bool |
| 325 | 325 | depends on RPS |
| 326 | 326 | default y |
| 327 | − ---help--- | |
| 327 | + help | |
| 328 | 328 | The network stack has to drop packets when a receive processing CPU's |
| 329 | 329 | backlog reaches netdev_max_backlog. If a few out of many active flows |
| 330 | 330 | generate the vast majority of load, drop their traffic earlier to |
| @@ -337,7 +337,7 @@ menu "Network testing" · 6 unmodified lines | ||
| 337 | 337 | config NET_PKTGEN |
| 338 | 338 | tristate "Packet Generator (USE WITH CAUTION)" |
| 339 | 339 | depends on INET && PROC_FS |
| 340 | − ---help--- | |
| 340 | + help | |
| 341 | 341 | This module will inject preconfigured packets, at a configurable |
| 342 | 342 | rate, out of a given interface. It is used for network interface |
| 343 | 343 | stress testing and performance analysis. If you don't understand |
| @@ -352,7 +352,7 @@ config NET_PKTGEN · 8 unmodified lines | ||
| 352 | 352 | config NET_DROP_MONITOR |
| 353 | 353 | tristate "Network packet drop alerting service" |
| 354 | 354 | depends on INET && TRACEPOINTS |
| 355 | − ---help--- | |
| 355 | + help | |
| 356 | 356 | This feature provides an alerting service to userspace in the |
| 357 | 357 | event that packets are discarded in the network stack. Alerts |
| 358 | 358 | are broadcast via netlink socket to any listening user space |
| @@ -398,7 +398,7 @@ source "net/ife/Kconfig" · 39 unmodified lines | ||
| 398 | 398 | |
| 399 | 399 | config LWTUNNEL |
| 400 | 400 | bool "Network light weight tunnels" |
| 401 | − ---help--- | |
| 401 | + help | |
| 402 | 402 | This feature provides an infrastructure to support light weight |
| 403 | 403 | tunnels like mpls. There is no netdevice associated with a light |
| 404 | 404 | weight tunnel endpoint. Tunnel encapsulation parameters are stored |
| @@ -408,7 +408,7 @@ config LWTUNNEL_BPF · 3 unmodified lines | ||
| 408 | 408 | bool "Execute BPF program as route nexthop action" |
| 409 | 409 | depends on LWTUNNEL && INET |
| 410 | 410 | default y if LWTUNNEL=y |
| 411 | − ---help--- | |
| 411 | + help | |
| 412 | 412 | Allows to run BPF programs as a nexthop action following a route |
| 413 | 413 | lookup for incoming and outgoing packets. |
| 414 | 414 | |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | |
| 6 | 6 | config ATM |
| 7 | 7 | tristate "Asynchronous Transfer Mode (ATM)" |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | ATM is a high-speed networking technology for Local Area Networks |
| 10 | 10 | and Wide Area Networks. It uses a fixed packet size and is |
| 11 | 11 | connection oriented, allowing for the negotiation of minimum |
| @@ -8,7 +8,7 @@ config BRIDGE · 7 unmodified lines | ||
| 8 | 8 | select LLC |
| 9 | 9 | select STP |
| 10 | 10 | depends on IPV6 || IPV6=n |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | If you say Y here, then your Linux box will be able to act as an |
| 13 | 13 | Ethernet bridge, which means that the different Ethernet segments it |
| 14 | 14 | is connected to will appear as one Ethernet to the participants. |
| @@ -39,7 +39,7 @@ config BRIDGE_IGMP_SNOOPING · 24 unmodified lines | ||
| 39 | 39 | depends on BRIDGE |
| 40 | 40 | depends on INET |
| 41 | 41 | default y |
| 42 | − ---help--- | |
| 42 | + help | |
| 43 | 43 | If you say Y here, then the Ethernet bridge will be able selectively |
| 44 | 44 | forward multicast traffic based on IGMP/MLD traffic received from |
| 45 | 45 | each port. |
| @@ -53,7 +53,7 @@ config BRIDGE_VLAN_FILTERING · 7 unmodified lines | ||
| 53 | 53 | depends on BRIDGE |
| 54 | 54 | depends on VLAN_8021Q |
| 55 | 55 | default n |
| 56 | − ---help--- | |
| 56 | + help | |
| 57 | 57 | If you say Y here, then the Ethernet bridge will be able selectively |
| 58 | 58 | receive and forward traffic based on VLAN information in the packet |
| 59 | 59 | any VLAN information configured on the bridge port or bridge device. |
| @@ -7,7 +7,7 @@ menuconfig CAIF · 6 unmodified lines | ||
| 7 | 7 | tristate "CAIF support" |
| 8 | 8 | select CRC_CCITT |
| 9 | 9 | default n |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | The "Communication CPU to Application CPU Interface" (CAIF) is a packet |
| 12 | 12 | based connection-oriented MUX protocol developed by ST-Ericsson for use |
| 13 | 13 | with its modems. It is accessed from user space as sockets (PF_CAIF). |
| @@ -26,7 +26,7 @@ config CAIF_DEBUG · 12 unmodified lines | ||
| 26 | 26 | bool "Enable Debug" |
| 27 | 27 | depends on CAIF |
| 28 | 28 | default n |
| 29 | − ---help--- | |
| 29 | + help | |
| 30 | 30 | Enable the inclusion of debug code in the CAIF stack. |
| 31 | 31 | Be aware that doing this will impact performance. |
| 32 | 32 | If unsure say N. |
| @@ -35,7 +35,7 @@ config CAIF_NETDEV · 2 unmodified lines | ||
| 35 | 35 | tristate "CAIF GPRS Network device" |
| 36 | 36 | depends on CAIF |
| 37 | 37 | default CAIF |
| 38 | − ---help--- | |
| 38 | + help | |
| 39 | 39 | Say Y if you will be using a CAIF based GPRS network device. |
| 40 | 40 | This can be either built-in or a loadable module. |
| 41 | 41 | If you select to build it as a built-in then the main CAIF device must |
| @@ -46,7 +46,7 @@ config CAIF_USB · 4 unmodified lines | ||
| 46 | 46 | tristate "CAIF USB support" |
| 47 | 47 | depends on CAIF |
| 48 | 48 | default n |
| 49 | − ---help--- | |
| 49 | + help | |
| 50 | 50 | Say Y if you are using CAIF over USB CDC NCM. |
| 51 | 51 | This can be either built-in or a loadable module. |
| 52 | 52 | If you select to build it as a built-in then the main CAIF device must |
| @@ -6,7 +6,7 @@ · 5 unmodified lines | ||
| 6 | 6 | menuconfig CAN |
| 7 | 7 | depends on NET |
| 8 | 8 | tristate "CAN bus subsystem support" |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial |
| 11 | 11 | communications protocol. Development of the CAN bus started in |
| 12 | 12 | 1983 at Robert Bosch GmbH, and the protocol was officially |
| @@ -23,7 +23,7 @@ if CAN · 10 unmodified lines | ||
| 23 | 23 | config CAN_RAW |
| 24 | 24 | tristate "Raw CAN Protocol (raw access with CAN-ID filtering)" |
| 25 | 25 | default y |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | The raw CAN protocol option offers access to the CAN bus via |
| 28 | 28 | the BSD socket API. You probably want to use the raw socket in |
| 29 | 29 | most cases where no higher level protocol is being used. The raw |
| @@ -33,7 +33,7 @@ config CAN_RAW · 3 unmodified lines | ||
| 33 | 33 | config CAN_BCM |
| 34 | 34 | tristate "Broadcast Manager CAN Protocol (with content filtering)" |
| 35 | 35 | default y |
| 36 | − ---help--- | |
| 36 | + help | |
| 37 | 37 | The Broadcast Manager offers content filtering, timeout monitoring, |
| 38 | 38 | sending of RTR frames, and cyclic CAN messages without permanent user |
| 39 | 39 | interaction. The BCM can be 'programmed' via the BSD socket API and |
| @@ -45,7 +45,7 @@ config CAN_BCM · 5 unmodified lines | ||
| 45 | 45 | config CAN_GW |
| 46 | 46 | tristate "CAN Gateway/Router (with netlink configuration)" |
| 47 | 47 | default y |
| 48 | − ---help--- | |
| 48 | + help | |
| 49 | 49 | The CAN Gateway/Router is used to route (and modify) CAN frames. |
| 50 | 50 | It is based on the PF_CAN core infrastructure for msg filtering and |
| 51 | 51 | msg sending and can optionally modify routed CAN frames on the fly. |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | config DCB |
| 3 | 3 | bool "Data Center Bridging support" |
| 4 | 4 | default n |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | This enables support for configuring Data Center Bridging (DCB) |
| 7 | 7 | features on DCB capable Ethernet adapters via rtnetlink. Say 'Y' |
| 8 | 8 | if you have a DCB capable Ethernet adapter which supports this |
| @@ -2,7 +2,7 @@ · 1 unmodified line | ||
| 2 | 2 | menuconfig IP_DCCP |
| 3 | 3 | tristate "The DCCP Protocol" |
| 4 | 4 | depends on INET |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | Datagram Congestion Control Protocol (RFC 4340) |
| 7 | 7 | |
| 8 | 8 | From http://www.ietf.org/rfc/rfc4340.txt: |
| @@ -32,7 +32,7 @@ menu "DCCP Kernel Hacking" · 23 unmodified lines | ||
| 32 | 32 | |
| 33 | 33 | config IP_DCCP_DEBUG |
| 34 | 34 | bool "DCCP debug messages" |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | Only use this if you're hacking DCCP. |
| 37 | 37 | |
| 38 | 38 | When compiling DCCP as a module, this debugging output can be toggled |
| @@ -3,7 +3,7 @@ menu "DCCP CCIDs Configuration" · 2 unmodified lines | ||
| 3 | 3 | |
| 4 | 4 | config IP_DCCP_CCID2_DEBUG |
| 5 | 5 | bool "CCID-2 debugging messages" |
| 6 | − ---help--- | |
| 6 | + help | |
| 7 | 7 | Enable CCID-2 specific debugging messages. |
| 8 | 8 | |
| 9 | 9 | The debugging output can additionally be toggled by setting the |
| @@ -14,7 +14,7 @@ config IP_DCCP_CCID2_DEBUG · 4 unmodified lines | ||
| 14 | 14 | config IP_DCCP_CCID3 |
| 15 | 15 | bool "CCID-3 (TCP-Friendly)" |
| 16 | 16 | def_bool y if (IP_DCCP = y || IP_DCCP = m) |
| 17 | − ---help--- | |
| 17 | + help | |
| 18 | 18 | CCID-3 denotes TCP-Friendly Rate Control (TFRC), an equation-based |
| 19 | 19 | rate-controlled congestion control mechanism. TFRC is designed to |
| 20 | 20 | be reasonably fair when competing for bandwidth with TCP-like flows, |
| @@ -39,7 +39,7 @@ config IP_DCCP_CCID3 · 18 unmodified lines | ||
| 39 | 39 | config IP_DCCP_CCID3_DEBUG |
| 40 | 40 | bool "CCID-3 debugging messages" |
| 41 | 41 | depends on IP_DCCP_CCID3 |
| 42 | − ---help--- | |
| 42 | + help | |
| 43 | 43 | Enable CCID-3 specific debugging messages. |
| 44 | 44 | |
| 45 | 45 | The debugging output can additionally be toggled by setting the |
| @@ -4,7 +4,7 @@ · 3 unmodified lines | ||
| 4 | 4 | # |
| 5 | 5 | config DECNET |
| 6 | 6 | tristate "DECnet Support" |
| 7 | − ---help--- | |
| 7 | + help | |
| 8 | 8 | The DECnet networking protocol was used in many products made by |
| 9 | 9 | Digital (now Compaq). It provides reliable stream and sequenced |
| 10 | 10 | packet communications over which run a variety of services similar |
| @@ -29,7 +29,7 @@ config DECNET_ROUTER · 18 unmodified lines | ||
| 29 | 29 | bool "DECnet: router support" |
| 30 | 30 | depends on DECNET |
| 31 | 31 | select FIB_RULES |
| 32 | − ---help--- | |
| 32 | + help | |
| 33 | 33 | Add support for turning your DECnet Endnode into a level 1 or 2 |
| 34 | 34 | router. This is an experimental, but functional option. If you |
| 35 | 35 | do say Y here, then make sure that you also say Y to "Kernel/User |
| @@ -13,7 +13,7 @@ menuconfig NET_DSA · 12 unmodified lines | ||
| 13 | 13 | select NET_SWITCHDEV |
| 14 | 14 | select PHYLINK |
| 15 | 15 | select NET_DEVLINK |
| 16 | − ---help--- | |
| 16 | + help | |
| 17 | 17 | Say Y if you want to enable support for the hardware switches supported |
| 18 | 18 | by the Distributed Switch Architecture. |
| 19 | 19 | |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | |
| 6 | 6 | config HSR |
| 7 | 7 | tristate "High-availability Seamless Redundancy (HSR)" |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | If you say Y here, then your Linux box will be able to act as a |
| 10 | 10 | DANH ("Doubly attached node implementing HSR"). For this to work, |
| 11 | 11 | your Linux box needs (at least) two physical Ethernet interfaces, |
| @@ -2,5 +2,5 @@ · 1 unmodified line | ||
| 2 | 2 | config IEEE802154_6LOWPAN |
| 3 | 3 | tristate "6lowpan support over IEEE 802.15.4" |
| 4 | 4 | depends on 6LOWPAN |
| 5 | − ---help--- | |
| 5 | + help | |
| 6 | 6 | IPv6 compression over IEEE 802.15.4. |
| @@ -1,7 +1,7 @@ | ||
| 1 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | 2 | menuconfig IEEE802154 |
| 3 | 3 | tristate "IEEE Std 802.15.4 Low-Rate Wireless Personal Area Networks support" |
| 4 | − ---help--- | |
| 4 | + help | |
| 5 | 5 | IEEE Std 802.15.4 defines a low data rate, low power and low |
| 6 | 6 | complexity short range wireless personal area networks. It was |
| 7 | 7 | designed to organise networks of sensors, switches, etc automation |
| @@ -15,13 +15,13 @@ if IEEE802154 · 7 unmodified lines | ||
| 15 | 15 | |
| 16 | 16 | config IEEE802154_NL802154_EXPERIMENTAL |
| 17 | 17 | bool "IEEE 802.15.4 experimental netlink support" |
| 18 | − ---help--- | |
| 18 | + help | |
| 19 | 19 | Adds experimental netlink support for nl802154. |
| 20 | 20 | |
| 21 | 21 | config IEEE802154_SOCKET |
| 22 | 22 | tristate "IEEE 802.15.4 socket interface" |
| 23 | 23 | default y |
| 24 | − ---help--- | |
| 24 | + help | |
| 25 | 25 | Socket interface for IEEE 802.15.4. Contains DGRAM sockets interface |
| 26 | 26 | for 802.15.4 dataframes. Also RAW socket interface to build MAC |
| 27 | 27 | header from userspace. |
| @@ -14,7 +14,7 @@ config IP_MULTICAST · 13 unmodified lines | ||
| 14 | 14 | |
| 15 | 15 | config IP_ADVANCED_ROUTER |
| 16 | 16 | bool "IP: advanced router" |
| 17 | − ---help--- | |
| 17 | + help | |
| 18 | 18 | If you intend to run your Linux box mostly as a router, i.e. as a |
| 19 | 19 | computer that forwards and redistributes network packets, say Y; you |
| 20 | 20 | will then be presented with several options that allow more precise |
| @@ -56,7 +56,7 @@ config IP_ADVANCED_ROUTER · 35 unmodified lines | ||
| 56 | 56 | config IP_FIB_TRIE_STATS |
| 57 | 57 | bool "FIB TRIE statistics" |
| 58 | 58 | depends on IP_ADVANCED_ROUTER |
| 59 | − ---help--- | |
| 59 | + help | |
| 60 | 60 | Keep track of statistics on structure of FIB TRIE table. |
| 61 | 61 | Useful for testing and measuring TRIE performance. |
| 62 | 62 | |
| @@ -64,7 +64,7 @@ config IP_MULTIPLE_TABLES · 1 unmodified line | ||
| 64 | 64 | bool "IP: policy routing" |
| 65 | 65 | depends on IP_ADVANCED_ROUTER |
| 66 | 66 | select FIB_RULES |
| 67 | − ---help--- | |
| 67 | + help | |
| 68 | 68 | Normally, a router decides what to do with a received packet based |
| 69 | 69 | solely on the packet's final destination address. If you say Y here, |
| 70 | 70 | the Linux router will also be able to take the packet's source |
| @@ -117,7 +117,7 @@ config IP_PNP · 46 unmodified lines | ||
| 117 | 117 | config IP_PNP_DHCP |
| 118 | 118 | bool "IP: DHCP support" |
| 119 | 119 | depends on IP_PNP |
| 120 | − ---help--- | |
| 120 | + help | |
| 121 | 121 | If you want your Linux box to mount its whole root file system (the |
| 122 | 122 | one containing the directory /) from some other computer over the |
| 123 | 123 | net via NFS and you want the IP address of your computer to be |
| @@ -134,7 +134,7 @@ config IP_PNP_DHCP · 10 unmodified lines | ||
| 134 | 134 | config IP_PNP_BOOTP |
| 135 | 135 | bool "IP: BOOTP support" |
| 136 | 136 | depends on IP_PNP |
| 137 | − ---help--- | |
| 137 | + help | |
| 138 | 138 | If you want your Linux box to mount its whole root file system (the |
| 139 | 139 | one containing the directory /) from some other computer over the |
| 140 | 140 | net via NFS and you want the IP address of your computer to be |
| @@ -163,7 +163,7 @@ config NET_IPIP · 22 unmodified lines | ||
| 163 | 163 | tristate "IP: tunneling" |
| 164 | 164 | select INET_TUNNEL |
| 165 | 165 | select NET_IP_TUNNEL |
| 166 | − ---help--- | |
| 166 | + help | |
| 167 | 167 | Tunneling means encapsulating data of one protocol type within |
| 168 | 168 | another protocol and sending it over a channel that understands the |
| 169 | 169 | encapsulating protocol. This particular tunneling driver implements |
| @@ -267,7 +267,7 @@ config IP_PIMSM_V2 · 97 unmodified lines | ||
| 267 | 267 | |
| 268 | 268 | config SYN_COOKIES |
| 269 | 269 | bool "IP: TCP syncookie support" |
| 270 | − ---help--- | |
| 270 | + help | |
| 271 | 271 | Normal TCP/IP networking is open to an attack known as "SYN |
| 272 | 272 | flooding". This denial-of-service attack prevents legitimate remote |
| 273 | 273 | users from being able to connect to your computer during an ongoing |
| @@ -307,7 +307,7 @@ config NET_IPVTI · 33 unmodified lines | ||
| 307 | 307 | select INET_TUNNEL |
| 308 | 308 | select NET_IP_TUNNEL |
| 309 | 309 | select XFRM |
| 310 | − ---help--- | |
| 310 | + help | |
| 311 | 311 | Tunneling means encapsulating data of one protocol type within |
| 312 | 312 | another protocol and sending it over a channel that understands the |
| 313 | 313 | encapsulating protocol. This can be used with xfrm mode tunnel to give |
| @@ -323,7 +323,7 @@ config NET_FOU · 9 unmodified lines | ||
| 323 | 323 | tristate "IP: Foo (IP protocols) over UDP" |
| 324 | 324 | select XFRM |
| 325 | 325 | select NET_UDP_TUNNEL |
| 326 | − ---help--- | |
| 326 | + help | |
| 327 | 327 | Foo over UDP allows any IP protocol to be directly encapsulated |
| 328 | 328 | over UDP include tunnels (IPIP, GRE, SIT). By encapsulating in UDP |
| 329 | 329 | network mechanisms and optimizations for UDP (such as ECMP |
| @@ -333,7 +333,7 @@ config NET_FOU_IP_TUNNELS · 3 unmodified lines | ||
| 333 | 333 | bool "IP: FOU encapsulation of IP tunnels" |
| 334 | 334 | depends on NET_IPIP || NET_IPGRE || IPV6_SIT |
| 335 | 335 | select NET_FOU |
| 336 | − ---help--- | |
| 336 | + help | |
| 337 | 337 | Allow configuration of FOU or GUE encapsulation for IP tunnels. |
| 338 | 338 | When this option is enabled IP tunnels can be configured to use |
| 339 | 339 | FOU or GUE encapsulation. |
| @@ -345,7 +345,7 @@ config INET_AH · 5 unmodified lines | ||
| 345 | 345 | select CRYPTO_HMAC |
| 346 | 346 | select CRYPTO_MD5 |
| 347 | 347 | select CRYPTO_SHA1 |
| 348 | − ---help--- | |
| 348 | + help | |
| 349 | 349 | Support for IPsec AH. |
| 350 | 350 | |
| 351 | 351 | If unsure, say Y. |
| @@ -361,7 +361,7 @@ config INET_ESP · 9 unmodified lines | ||
| 361 | 361 | select CRYPTO_SHA1 |
| 362 | 362 | select CRYPTO_DES |
| 363 | 363 | select CRYPTO_ECHAINIV |
| 364 | − ---help--- | |
| 364 | + help | |
| 365 | 365 | Support for IPsec ESP. |
| 366 | 366 | |
| 367 | 367 | If unsure, say Y. |
| @@ -371,7 +371,7 @@ config INET_ESP_OFFLOAD · 3 unmodified lines | ||
| 371 | 371 | depends on INET_ESP |
| 372 | 372 | select XFRM_OFFLOAD |
| 373 | 373 | default n |
| 374 | − ---help--- | |
| 374 | + help | |
| 375 | 375 | Support for ESP transformation offload. This makes sense |
| 376 | 376 | only if this system really does IPsec and want to do it |
| 377 | 377 | with high throughput. A typical desktop system does not |
| @@ -395,7 +395,7 @@ config INET_IPCOMP · 17 unmodified lines | ||
| 395 | 395 | tristate "IP: IPComp transformation" |
| 396 | 396 | select INET_XFRM_TUNNEL |
| 397 | 397 | select XFRM_IPCOMP |
| 398 | − ---help--- | |
| 398 | + help | |
| 399 | 399 | Support for IP Payload Compression Protocol (IPComp) (RFC3173), |
| 400 | 400 | typically needed for IPsec. |
| 401 | 401 | |
| @@ -413,7 +413,7 @@ config INET_TUNNEL · 11 unmodified lines | ||
| 413 | 413 | config INET_DIAG |
| 414 | 414 | tristate "INET: socket monitoring interface" |
| 415 | 415 | default y |
| 416 | − ---help--- | |
| 416 | + help | |
| 417 | 417 | Support for INET (TCP, DCCP, etc) socket monitoring interface used by |
| 418 | 418 | native Linux tools such as ss. ss is included in iproute2, currently |
| 419 | 419 | downloadable at: |
| @@ -430,7 +430,7 @@ config INET_UDP_DIAG · 10 unmodified lines | ||
| 430 | 430 | tristate "UDP: socket monitoring interface" |
| 431 | 431 | depends on INET_DIAG && (IPV6 || IPV6=n) |
| 432 | 432 | default n |
| 433 | − ---help--- | |
| 433 | + help | |
| 434 | 434 | Support for UDP socket monitoring interface used by the ss tool. |
| 435 | 435 | If unsure, say Y. |
| 436 | 436 | |
| @@ -438,7 +438,7 @@ config INET_RAW_DIAG · 1 unmodified line | ||
| 438 | 438 | tristate "RAW: socket monitoring interface" |
| 439 | 439 | depends on INET_DIAG && (IPV6 || IPV6=n) |
| 440 | 440 | default n |
| 441 | − ---help--- | |
| 441 | + help | |
| 442 | 442 | Support for RAW socket monitoring interface used by the ss tool. |
| 443 | 443 | If unsure, say Y. |
| 444 | 444 | |
| @@ -446,7 +446,7 @@ config INET_DIAG_DESTROY · 1 unmodified line | ||
| 446 | 446 | bool "INET: allow privileged process to administratively close sockets" |
| 447 | 447 | depends on INET_DIAG |
| 448 | 448 | default n |
| 449 | − ---help--- | |
| 449 | + help | |
| 450 | 450 | Provides a SOCK_DESTROY operation that allows privileged processes |
| 451 | 451 | (e.g., a connection manager or a network administration tool such as |
| 452 | 452 | ss) to close sockets opened by other processes. Closing a socket in |
| @@ -457,7 +457,7 @@ config INET_DIAG_DESTROY · 4 unmodified lines | ||
| 457 | 457 | |
| 458 | 458 | menuconfig TCP_CONG_ADVANCED |
| 459 | 459 | bool "TCP: advanced congestion control" |
| 460 | − ---help--- | |
| 460 | + help | |
| 461 | 461 | Support for selection of various TCP congestion control |
| 462 | 462 | modules. |
| 463 | 463 | |
| @@ -471,7 +471,7 @@ if TCP_CONG_ADVANCED · 7 unmodified lines | ||
| 471 | 471 | config TCP_CONG_BIC |
| 472 | 472 | tristate "Binary Increase Congestion (BIC) control" |
| 473 | 473 | default m |
| 474 | − ---help--- | |
| 474 | + help | |
| 475 | 475 | BIC-TCP is a sender-side only change that ensures a linear RTT |
| 476 | 476 | fairness under large windows while offering both scalability and |
| 477 | 477 | bounded TCP-friendliness. The protocol combines two schemes |
| @@ -485,7 +485,7 @@ config TCP_CONG_BIC · 7 unmodified lines | ||
| 485 | 485 | config TCP_CONG_CUBIC |
| 486 | 486 | tristate "CUBIC TCP" |
| 487 | 487 | default y |
| 488 | − ---help--- | |
| 488 | + help | |
| 489 | 489 | This is version 2.0 of BIC-TCP which uses a cubic growth function |
| 490 | 490 | among other techniques. |
| 491 | 491 | See http://www.csc.ncsu.edu/faculty/rhee/export/bitcp/cubic-paper.pdf |
| @@ -493,7 +493,7 @@ config TCP_CONG_CUBIC · 1 unmodified line | ||
| 493 | 493 | config TCP_CONG_WESTWOOD |
| 494 | 494 | tristate "TCP Westwood+" |
| 495 | 495 | default m |
| 496 | − ---help--- | |
| 496 | + help | |
| 497 | 497 | TCP Westwood+ is a sender-side only modification of the TCP Reno |
| 498 | 498 | protocol stack that optimizes the performance of TCP congestion |
| 499 | 499 | control. It is based on end-to-end bandwidth estimation to set |
| @@ -507,7 +507,7 @@ config TCP_CONG_WESTWOOD · 7 unmodified lines | ||
| 507 | 507 | config TCP_CONG_HTCP |
| 508 | 508 | tristate "H-TCP" |
| 509 | 509 | default m |
| 510 | − ---help--- | |
| 510 | + help | |
| 511 | 511 | H-TCP is a send-side only modifications of the TCP Reno |
| 512 | 512 | protocol stack that optimizes the performance of TCP |
| 513 | 513 | congestion control for high speed network links. It uses a |
| @@ -518,7 +518,7 @@ config TCP_CONG_HTCP · 4 unmodified lines | ||
| 518 | 518 | config TCP_CONG_HSTCP |
| 519 | 519 | tristate "High Speed TCP" |
| 520 | 520 | default n |
| 521 | − ---help--- | |
| 521 | + help | |
| 522 | 522 | Sally Floyd's High Speed TCP (RFC 3649) congestion control. |
| 523 | 523 | A modification to TCP's congestion control mechanism for use |
| 524 | 524 | with large congestion windows. A table indicates how much to |
| @@ -528,7 +528,7 @@ config TCP_CONG_HSTCP · 3 unmodified lines | ||
| 528 | 528 | config TCP_CONG_HYBLA |
| 529 | 529 | tristate "TCP-Hybla congestion control algorithm" |
| 530 | 530 | default n |
| 531 | − ---help--- | |
| 531 | + help | |
| 532 | 532 | TCP-Hybla is a sender-side only change that eliminates penalization of |
| 533 | 533 | long-RTT, large-bandwidth connections, like when satellite legs are |
| 534 | 534 | involved, especially when sharing a common bottleneck with normal |
| @@ -537,7 +537,7 @@ config TCP_CONG_HYBLA · 2 unmodified lines | ||
| 537 | 537 | config TCP_CONG_VEGAS |
| 538 | 538 | tristate "TCP Vegas" |
| 539 | 539 | default n |
| 540 | − ---help--- | |
| 540 | + help | |
| 541 | 541 | TCP Vegas is a sender-side only change to TCP that anticipates |
| 542 | 542 | the onset of congestion by estimating the bandwidth. TCP Vegas |
| 543 | 543 | adjusts the sending rate by modifying the congestion |
| @@ -547,7 +547,7 @@ config TCP_CONG_VEGAS · 3 unmodified lines | ||
| 547 | 547 | config TCP_CONG_NV |
| 548 | 548 | tristate "TCP NV" |
| 549 | 549 | default n |
| 550 | − ---help--- | |
| 550 | + help | |
| 551 | 551 | TCP NV is a follow up to TCP Vegas. It has been modified to deal with |
| 552 | 552 | 10G networks, measurement noise introduced by LRO, GRO and interrupt |
| 553 | 553 | coalescence. In addition, it will decrease its cwnd multiplicatively |
| @@ -563,7 +563,7 @@ config TCP_CONG_NV · 9 unmodified lines | ||
| 563 | 563 | config TCP_CONG_SCALABLE |
| 564 | 564 | tristate "Scalable TCP" |
| 565 | 565 | default n |
| 566 | − ---help--- | |
| 566 | + help | |
| 567 | 567 | Scalable TCP is a sender-side only change to TCP which uses a |
| 568 | 568 | MIMD congestion control algorithm which has some nice scaling |
| 569 | 569 | properties, though is known to have fairness issues. |
| @@ -572,7 +572,7 @@ config TCP_CONG_SCALABLE · 2 unmodified lines | ||
| 572 | 572 | config TCP_CONG_LP |
| 573 | 573 | tristate "TCP Low Priority" |
| 574 | 574 | default n |
| 575 | − ---help--- | |
| 575 | + help | |
| 576 | 576 | TCP Low Priority (TCP-LP), a distributed algorithm whose goal is |
| 577 | 577 | to utilize only the excess network bandwidth as compared to the |
| 578 | 578 | ``fair share`` of bandwidth as targeted by TCP. |
| @@ -581,7 +581,7 @@ config TCP_CONG_LP · 2 unmodified lines | ||
| 581 | 581 | config TCP_CONG_VENO |
| 582 | 582 | tristate "TCP Veno" |
| 583 | 583 | default n |
| 584 | − ---help--- | |
| 584 | + help | |
| 585 | 585 | TCP Veno is a sender-side only enhancement of TCP to obtain better |
| 586 | 586 | throughput over wireless networks. TCP Veno makes use of state |
| 587 | 587 | distinguishing to circumvent the difficult judgment of the packet loss |
| @@ -593,7 +593,7 @@ config TCP_CONG_YEAH · 5 unmodified lines | ||
| 593 | 593 | tristate "YeAH TCP" |
| 594 | 594 | select TCP_CONG_VEGAS |
| 595 | 595 | default n |
| 596 | − ---help--- | |
| 596 | + help | |
| 597 | 597 | YeAH-TCP is a sender-side high-speed enabled TCP congestion control |
| 598 | 598 | algorithm, which uses a mixed loss/delay approach to compute the |
| 599 | 599 | congestion window. It's design goals target high efficiency, |
| @@ -606,7 +606,7 @@ config TCP_CONG_YEAH · 6 unmodified lines | ||
| 606 | 606 | config TCP_CONG_ILLINOIS |
| 607 | 607 | tristate "TCP Illinois" |
| 608 | 608 | default n |
| 609 | − ---help--- | |
| 609 | + help | |
| 610 | 610 | TCP-Illinois is a sender-side modification of TCP Reno for |
| 611 | 611 | high speed long delay links. It uses round-trip-time to |
| 612 | 612 | adjust the alpha and beta parameters to achieve a higher average |
| @@ -618,7 +618,7 @@ config TCP_CONG_ILLINOIS · 5 unmodified lines | ||
| 618 | 618 | config TCP_CONG_DCTCP |
| 619 | 619 | tristate "DataCenter TCP (DCTCP)" |
| 620 | 620 | default n |
| 621 | − ---help--- | |
| 621 | + help | |
| 622 | 622 | DCTCP leverages Explicit Congestion Notification (ECN) in the network to |
| 623 | 623 | provide multi-bit feedback to the end hosts. It is designed to provide: |
| 624 | 624 | |
| @@ -639,7 +639,7 @@ config TCP_CONG_DCTCP · 14 unmodified lines | ||
| 639 | 639 | config TCP_CONG_CDG |
| 640 | 640 | tristate "CAIA Delay-Gradient (CDG)" |
| 641 | 641 | default n |
| 642 | − ---help--- | |
| 642 | + help | |
| 643 | 643 | CAIA Delay-Gradient (CDG) is a TCP congestion control that modifies |
| 644 | 644 | the TCP sender in order to: |
| 645 | 645 | |
| @@ -655,7 +655,7 @@ config TCP_CONG_CDG · 9 unmodified lines | ||
| 655 | 655 | config TCP_CONG_BBR |
| 656 | 656 | tristate "BBR TCP" |
| 657 | 657 | default n |
| 658 | − ---help--- | |
| 658 | + help | |
| 659 | 659 | |
| 660 | 660 | BBR (Bottleneck Bandwidth and RTT) TCP congestion control aims to |
| 661 | 661 | maximize network utilization and minimize queues. It builds an explicit |
| @@ -734,7 +734,7 @@ config TCP_MD5SIG · 72 unmodified lines | ||
| 734 | 734 | bool "TCP: MD5 Signature Option support (RFC2385)" |
| 735 | 735 | select CRYPTO |
| 736 | 736 | select CRYPTO_MD5 |
| 737 | − ---help--- | |
| 737 | + help | |
| 738 | 738 | RFC2385 specifies a method of giving MD5 protection to TCP sessions. |
| 739 | 739 | Its main (only?) use is to protect BGP sessions between core routers |
| 740 | 740 | on the Internet. |
| @@ -94,7 +94,7 @@ config NF_NAT_SNMP_BASIC · 93 unmodified lines | ||
| 94 | 94 | depends on NETFILTER_ADVANCED |
| 95 | 95 | default NF_NAT && NF_CONNTRACK_SNMP |
| 96 | 96 | select ASN1 |
| 97 | − ---help--- | |
| 97 | + help | |
| 98 | 98 | |
| 99 | 99 | This module implements an Application Layer Gateway (ALG) for |
| 100 | 100 | SNMP payloads. In conjunction with NAT, it allows a network |
| @@ -146,7 +146,7 @@ config IP_NF_MATCH_ECN · 45 unmodified lines | ||
| 146 | 146 | tristate '"ecn" match support' |
| 147 | 147 | depends on NETFILTER_ADVANCED |
| 148 | 148 | select NETFILTER_XT_MATCH_ECN |
| 149 | − ---help--- | |
| 149 | + help | |
| 150 | 150 | This is a backwards-compat option for the user's convenience |
| 151 | 151 | (e.g. when running oldconfig). It selects |
| 152 | 152 | CONFIG_NETFILTER_XT_MATCH_ECN. |
| @@ -155,7 +155,7 @@ config IP_NF_MATCH_RPFILTER · 2 unmodified lines | ||
| 155 | 155 | tristate '"rpfilter" reverse path filter match support' |
| 156 | 156 | depends on NETFILTER_ADVANCED |
| 157 | 157 | depends on IP_NF_MANGLE || IP_NF_RAW |
| 158 | − ---help--- | |
| 158 | + help | |
| 159 | 159 | This option allows you to match packets whose replies would |
| 160 | 160 | go out via the interface the packet came in. |
| 161 | 161 | |
| @@ -166,7 +166,7 @@ config IP_NF_MATCH_TTL · 4 unmodified lines | ||
| 166 | 166 | tristate '"ttl" match support' |
| 167 | 167 | depends on NETFILTER_ADVANCED |
| 168 | 168 | select NETFILTER_XT_MATCH_HL |
| 169 | − ---help--- | |
| 169 | + help | |
| 170 | 170 | This is a backwards-compat option for the user's convenience |
| 171 | 171 | (e.g. when running oldconfig). It selects |
| 172 | 172 | CONFIG_NETFILTER_XT_MATCH_HL. |
| @@ -234,7 +234,7 @@ config IP_NF_TARGET_NETMAP · 61 unmodified lines | ||
| 234 | 234 | tristate "NETMAP target support" |
| 235 | 235 | depends on NETFILTER_ADVANCED |
| 236 | 236 | select NETFILTER_XT_TARGET_NETMAP |
| 237 | − ---help--- | |
| 237 | + help | |
| 238 | 238 | This is a backwards-compat option for the user's convenience |
| 239 | 239 | (e.g. when running oldconfig). It selects |
| 240 | 240 | CONFIG_NETFILTER_XT_TARGET_NETMAP. |
| @@ -243,7 +243,7 @@ config IP_NF_TARGET_REDIRECT · 2 unmodified lines | ||
| 243 | 243 | tristate "REDIRECT target support" |
| 244 | 244 | depends on NETFILTER_ADVANCED |
| 245 | 245 | select NETFILTER_XT_TARGET_REDIRECT |
| 246 | − ---help--- | |
| 246 | + help | |
| 247 | 247 | This is a backwards-compat option for the user's convenience |
| 248 | 248 | (e.g. when running oldconfig). It selects |
| 249 | 249 | CONFIG_NETFILTER_XT_TARGET_REDIRECT. |
| @@ -279,7 +279,7 @@ config IP_NF_TARGET_ECN · 29 unmodified lines | ||
| 279 | 279 | tristate "ECN target support" |
| 280 | 280 | depends on IP_NF_MANGLE |
| 281 | 281 | depends on NETFILTER_ADVANCED |
| 282 | − ---help--- | |
| 282 | + help | |
| 283 | 283 | This option adds a `ECN' target, which can be used in the iptables mangle |
| 284 | 284 | table. |
| 285 | 285 | |
| @@ -294,7 +294,7 @@ config IP_NF_TARGET_TTL · 8 unmodified lines | ||
| 294 | 294 | tristate '"TTL" target support' |
| 295 | 295 | depends on NETFILTER_ADVANCED && IP_NF_MANGLE |
| 296 | 296 | select NETFILTER_XT_TARGET_HL |
| 297 | − ---help--- | |
| 297 | + help | |
| 298 | 298 | This is a backwards-compatible option for the user's convenience |
| 299 | 299 | (e.g. when running oldconfig). It selects |
| 300 | 300 | CONFIG_NETFILTER_XT_TARGET_HL. |
| @@ -7,7 +7,7 @@ · 6 unmodified lines | ||
| 7 | 7 | menuconfig IPV6 |
| 8 | 8 | tristate "The IPv6 protocol" |
| 9 | 9 | default y |
| 10 | − ---help--- | |
| 10 | + help | |
| 11 | 11 | Support for IP version 6 (IPv6). |
| 12 | 12 | |
| 13 | 13 | For general information about IPv6, see |
| @@ -23,7 +23,7 @@ if IPV6 · 9 unmodified lines | ||
| 23 | 23 | |
| 24 | 24 | config IPV6_ROUTER_PREF |
| 25 | 25 | bool "IPv6: Router Preference (RFC 4191) support" |
| 26 | − ---help--- | |
| 26 | + help | |
| 27 | 27 | Router Preference is an optional extension to the Router |
| 28 | 28 | Advertisement message which improves the ability of hosts |
| 29 | 29 | to pick an appropriate router, especially when the hosts |
| @@ -34,14 +34,14 @@ config IPV6_ROUTER_PREF · 4 unmodified lines | ||
| 34 | 34 | config IPV6_ROUTE_INFO |
| 35 | 35 | bool "IPv6: Route Information (RFC 4191) support" |
| 36 | 36 | depends on IPV6_ROUTER_PREF |
| 37 | − ---help--- | |
| 37 | + help | |
| 38 | 38 | Support of Route Information. |
| 39 | 39 | |
| 40 | 40 | If unsure, say N. |
| 41 | 41 | |
| 42 | 42 | config IPV6_OPTIMISTIC_DAD |
| 43 | 43 | bool "IPv6: Enable RFC 4429 Optimistic DAD" |
| 44 | − ---help--- | |
| 44 | + help | |
| 45 | 45 | Support for optimistic Duplicate Address Detection. It allows for |
| 46 | 46 | autoconfigured addresses to be used more quickly. |
| 47 | 47 | |
| @@ -54,7 +54,7 @@ config INET6_AH · 6 unmodified lines | ||
| 54 | 54 | select CRYPTO_HMAC |
| 55 | 55 | select CRYPTO_MD5 |
| 56 | 56 | select CRYPTO_SHA1 |
| 57 | − ---help--- | |
| 57 | + help | |
| 58 | 58 | Support for IPsec AH. |
| 59 | 59 | |
| 60 | 60 | If unsure, say Y. |
| @@ -70,7 +70,7 @@ config INET6_ESP · 9 unmodified lines | ||
| 70 | 70 | select CRYPTO_SHA1 |
| 71 | 71 | select CRYPTO_DES |
| 72 | 72 | select CRYPTO_ECHAINIV |
| 73 | − ---help--- | |
| 73 | + help | |
| 74 | 74 | Support for IPsec ESP. |
| 75 | 75 | |
| 76 | 76 | If unsure, say Y. |
| @@ -80,7 +80,7 @@ config INET6_ESP_OFFLOAD · 3 unmodified lines | ||
| 80 | 80 | depends on INET6_ESP |
| 81 | 81 | select XFRM_OFFLOAD |
| 82 | 82 | default n |
| 83 | − ---help--- | |
| 83 | + help | |
| 84 | 84 | Support for ESP transformation offload. This makes sense |
| 85 | 85 | only if this system really does IPsec and want to do it |
| 86 | 86 | with high throughput. A typical desktop system does not |
| @@ -104,7 +104,7 @@ config INET6_IPCOMP · 17 unmodified lines | ||
| 104 | 104 | tristate "IPv6: IPComp transformation" |
| 105 | 105 | select INET6_XFRM_TUNNEL |
| 106 | 106 | select XFRM_IPCOMP |
| 107 | − ---help--- | |
| 107 | + help | |
| 108 | 108 | Support for IP Payload Compression Protocol (IPComp) (RFC3173), |
| 109 | 109 | typically needed for IPsec. |
| 110 | 110 | |
| @@ -113,7 +113,7 @@ config INET6_IPCOMP · 2 unmodified lines | ||
| 113 | 113 | config IPV6_MIP6 |
| 114 | 114 | tristate "IPv6: Mobility" |
| 115 | 115 | select XFRM |
| 116 | − ---help--- | |
| 116 | + help | |
| 117 | 117 | Support for IPv6 Mobility described in RFC 3775. |
| 118 | 118 | |
| 119 | 119 | If unsure, say N. |
| @@ -123,7 +123,7 @@ config IPV6_ILA · 3 unmodified lines | ||
| 123 | 123 | depends on NETFILTER |
| 124 | 124 | select DST_CACHE |
| 125 | 125 | select LWTUNNEL |
| 126 | − ---help--- | |
| 126 | + help | |
| 127 | 127 | Support for IPv6 Identifier Locator Addressing (ILA). |
| 128 | 128 | |
| 129 | 129 | ILA is a mechanism to do network virtualization without |
| @@ -153,7 +153,7 @@ tristate "Virtual (secure) IPv6: tunneling" · 23 unmodified lines | ||
| 153 | 153 | select IPV6_TUNNEL |
| 154 | 154 | select NET_IP_TUNNEL |
| 155 | 155 | select XFRM |
| 156 | − ---help--- | |
| 156 | + help | |
| 157 | 157 | Tunneling means encapsulating data of one protocol type within |
| 158 | 158 | another protocol and sending it over a channel that understands the |
| 159 | 159 | encapsulating protocol. This can be used with xfrm mode tunnel to give |
| @@ -166,7 +166,7 @@ config IPV6_SIT · 6 unmodified lines | ||
| 166 | 166 | select NET_IP_TUNNEL |
| 167 | 167 | select IPV6_NDISC_NODETYPE |
| 168 | 168 | default y |
| 169 | − ---help--- | |
| 169 | + help | |
| 170 | 170 | Tunneling means encapsulating data of one protocol type within |
| 171 | 171 | another protocol and sending it over a channel that understands the |
| 172 | 172 | encapsulating protocol. This driver implements encapsulation of IPv6 |
| @@ -179,7 +179,7 @@ config IPV6_SIT_6RD · 6 unmodified lines | ||
| 179 | 179 | bool "IPv6: IPv6 Rapid Deployment (6RD)" |
| 180 | 180 | depends on IPV6_SIT |
| 181 | 181 | default n |
| 182 | − ---help--- | |
| 182 | + help | |
| 183 | 183 | IPv6 Rapid Deployment (6rd; draft-ietf-softwire-ipv6-6rd) builds upon |
| 184 | 184 | mechanisms of 6to4 (RFC3056) to enable a service provider to rapidly |
| 185 | 185 | deploy IPv6 unicast service to IPv4 sites to which it provides |
| @@ -202,7 +202,7 @@ config IPV6_TUNNEL · 16 unmodified lines | ||
| 202 | 202 | select INET6_TUNNEL |
| 203 | 203 | select DST_CACHE |
| 204 | 204 | select GRO_CELLS |
| 205 | − ---help--- | |
| 205 | + help | |
| 206 | 206 | Support for IPv6-in-IPv6 and IPv4-in-IPv6 tunnels described in |
| 207 | 207 | RFC 2473. |
| 208 | 208 | |
| @@ -213,7 +213,7 @@ config IPV6_GRE · 4 unmodified lines | ||
| 213 | 213 | select IPV6_TUNNEL |
| 214 | 214 | select NET_IP_TUNNEL |
| 215 | 215 | depends on NET_IPGRE_DEMUX |
| 216 | − ---help--- | |
| 216 | + help | |
| 217 | 217 | Tunneling means encapsulating data of one protocol type within |
| 218 | 218 | another protocol and sending it over a channel that understands the |
| 219 | 219 | encapsulating protocol. This particular tunneling driver implements |
| @@ -238,13 +238,13 @@ config IPV6_FOU_TUNNEL · 18 unmodified lines | ||
| 238 | 238 | config IPV6_MULTIPLE_TABLES |
| 239 | 239 | bool "IPv6: Multiple Routing Tables" |
| 240 | 240 | select FIB_RULES |
| 241 | − ---help--- | |
| 241 | + help | |
| 242 | 242 | Support multiple routing tables. |
| 243 | 243 | |
| 244 | 244 | config IPV6_SUBTREES |
| 245 | 245 | bool "IPv6: source address based routing" |
| 246 | 246 | depends on IPV6_MULTIPLE_TABLES |
| 247 | − ---help--- | |
| 247 | + help | |
| 248 | 248 | Enable routing by source address or prefix. |
| 249 | 249 | |
| 250 | 250 | The destination address is still the primary routing key, so mixing |
| @@ -259,7 +259,7 @@ config IPV6_MROUTE · 8 unmodified lines | ||
| 259 | 259 | bool "IPv6: multicast routing" |
| 260 | 260 | depends on IPV6 |
| 261 | 261 | select IP_MROUTE_COMMON |
| 262 | − ---help--- | |
| 262 | + help | |
| 263 | 263 | Support for IPv6 multicast forwarding. |
| 264 | 264 | If unsure, say N. |
| 265 | 265 | |
| @@ -280,7 +280,7 @@ config IPV6_MROUTE_MULTIPLE_TABLES · 14 unmodified lines | ||
| 280 | 280 | config IPV6_PIMSM_V2 |
| 281 | 281 | bool "IPv6: PIM-SM version 2 support" |
| 282 | 282 | depends on IPV6_MROUTE |
| 283 | − ---help--- | |
| 283 | + help | |
| 284 | 284 | Support for IPv6 PIM multicast routing protocol PIM-SMv2. |
| 285 | 285 | If unsure, say N. |
| 286 | 286 | |
| @@ -290,7 +290,7 @@ config IPV6_SEG6_LWTUNNEL · 3 unmodified lines | ||
| 290 | 290 | select LWTUNNEL |
| 291 | 291 | select DST_CACHE |
| 292 | 292 | select IPV6_MULTIPLE_TABLES |
| 293 | − ---help--- | |
| 293 | + help | |
| 294 | 294 | Support for encapsulation of packets within an outer IPv6 |
| 295 | 295 | header and a Segment Routing Header using the lightweight |
| 296 | 296 | tunnels mechanism. Also enable support for advanced local |
| @@ -304,7 +304,7 @@ config IPV6_SEG6_HMAC · 7 unmodified lines | ||
| 304 | 304 | select CRYPTO_HMAC |
| 305 | 305 | select CRYPTO_SHA1 |
| 306 | 306 | select CRYPTO_SHA256 |
| 307 | − ---help--- | |
| 307 | + help | |
| 308 | 308 | Support for HMAC signature generation and verification |
| 309 | 309 | of SR-enabled packets. |
| 310 | 310 | |
| @@ -319,7 +319,7 @@ config IPV6_RPL_LWTUNNEL · 8 unmodified lines | ||
| 319 | 319 | bool "IPv6: RPL Source Routing Header support" |
| 320 | 320 | depends on IPV6 |
| 321 | 321 | select LWTUNNEL |
| 322 | − ---help--- | |
| 322 | + help | |
| 323 | 323 | Support for RFC6554 RPL Source Routing Header using the lightweight |
| 324 | 324 | tunnels mechanism. |
| 325 | 325 | |
| @@ -127,7 +127,7 @@ config IP6_NF_MATCH_HL · 126 unmodified lines | ||
| 127 | 127 | tristate '"hl" hoplimit match support' |
| 128 | 128 | depends on NETFILTER_ADVANCED |
| 129 | 129 | select NETFILTER_XT_MATCH_HL |
| 130 | − ---help--- | |
| 130 | + help | |
| 131 | 131 | This is a backwards-compat option for the user's convenience |
| 132 | 132 | (e.g. when running oldconfig). It selects |
| 133 | 133 | CONFIG_NETFILTER_XT_MATCH_HL. |
| @@ -153,7 +153,7 @@ config IP6_NF_MATCH_RPFILTER · 19 unmodified lines | ||
| 153 | 153 | tristate '"rpfilter" reverse path filter match support' |
| 154 | 154 | depends on NETFILTER_ADVANCED |
| 155 | 155 | depends on IP6_NF_MANGLE || IP6_NF_RAW |
| 156 | − ---help--- | |
| 156 | + help | |
| 157 | 157 | This option allows you to match packets whose replies would |
| 158 | 158 | go out via the interface the packet came in. |
| 159 | 159 | |
| @@ -183,7 +183,7 @@ config IP6_NF_TARGET_HL · 23 unmodified lines | ||
| 183 | 183 | tristate '"HL" hoplimit target support' |
| 184 | 184 | depends on NETFILTER_ADVANCED && IP6_NF_MANGLE |
| 185 | 185 | select NETFILTER_XT_TARGET_HL |
| 186 | − ---help--- | |
| 186 | + help | |
| 187 | 187 | This is a backwards-compatible option for the user's convenience |
| 188 | 188 | (e.g. when running oldconfig). It selects |
| 189 | 189 | CONFIG_NETFILTER_XT_TARGET_HL. |
| @@ -5,7 +5,7 @@ config AF_KCM · 4 unmodified lines | ||
| 5 | 5 | depends on INET |
| 6 | 6 | select BPF_SYSCALL |
| 7 | 7 | select STREAM_PARSER |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | KCM (Kernel Connection Multiplexor) sockets provide a method |
| 10 | 10 | for multiplexing messages of a message based application |
| 11 | 11 | protocol over kernel connectons (e.g. TCP connections). |
| @@ -8,7 +8,7 @@ menuconfig L2TP · 7 unmodified lines | ||
| 8 | 8 | depends on (IPV6 || IPV6=n) |
| 9 | 9 | depends on INET |
| 10 | 10 | select NET_UDP_TUNNEL |
| 11 | − ---help--- | |
| 11 | + help | |
| 12 | 12 | Layer Two Tunneling Protocol |
| 13 | 13 | |
| 14 | 14 | From RFC 2661 <http://www.ietf.org/rfc/rfc2661.txt>. |
| @@ -6,6 +6,6 @@ · 5 unmodified lines | ||
| 6 | 6 | config NET_L3_MASTER_DEV |
| 7 | 7 | bool "L3 Master device support" |
| 8 | 8 | depends on INET || IPV6 |
| 9 | − ---help--- | |
| 9 | + help | |
| 10 | 10 | This module provides glue between core networking code and device |
| 11 | 11 | drivers to support L3 master devices like VRF. |
| @@ -5,7 +5,7 @@ · 4 unmodified lines | ||
| 5 | 5 | |
| 6 | 6 | config LAPB |
| 7 | 7 | tristate "LAPB Data Link Driver" |
| 8 | − ---help--- | |
| 8 | + help | |
| 9 | 9 | Link Access Procedure, Balanced (LAPB) is the data link layer (i.e. |
| 10 | 10 | the lower) part of the X.25 protocol. It offers a reliable |
| 11 | 11 | connection service to exchange data frames with one other host, and |
| @@ -9,7 +9,7 @@ config MAC80211 · 8 unmodified lines | ||
| 9 | 9 | select CRYPTO_GCM |
| 10 | 10 | select CRYPTO_CMAC |
| 11 | 11 | select CRC32 |
| 12 | − ---help--- | |
| 12 | + help | |
| 13 | 13 | This option enables the hardware independent IEEE 802.11 |
| 14 | 14 | networking stack. |
| 15 | 15 | |
| @@ -25,14 +25,14 @@ config MAC80211_RC_MINSTREL · 9 unmodified lines | ||
| 25 | 25 | bool "Minstrel" if EXPERT |
| 26 | 26 | select MAC80211_HAS_RC |
| 27 | 27 | default y |
| 28 | − ---help--- | |
| 28 | + help | |
| 29 | 29 | This option enables the 'minstrel' TX rate control algorithm |
| 30 | 30 | |
| 31 | 31 | choice |
| 32 | 32 | prompt "Default rate control algorithm" |
| 33 | 33 | depends on MAC80211_HAS_RC |
| 34 | 34 | default MAC80211_RC_DEFAULT_MINSTREL |
| 35 | − ---help--- | |
| 35 | + help | |
| 36 | 36 | This option selects the default rate control algorithm |
| 37 | 37 | mac80211 will use. Note that this default can still be |
| 38 | 38 | overridden through the ieee80211_default_rc_algo module |
| @@ -41,7 +41,7 @@ choice · 2 unmodified lines | ||
| 41 | 41 | config MAC80211_RC_DEFAULT_MINSTREL |
| 42 | 42 | bool "Minstrel" |
| 43 | 43 | depends on MAC80211_RC_MINSTREL |
| 44 | − ---help--- | |
| 44 | + help | |
| 45 | 45 | Select Minstrel as the default rate control algorithm. |
| 46 | 46 | |
| 47 | 47 | |
| @@ -60,7 +60,7 @@ comment "Some wireless drivers require a rate control algorithm" · 12 unmodified lines | ||
| 60 | 60 | config MAC80211_MESH |
| 61 | 61 | bool "Enable mac80211 mesh networking support" |
| 62 | 62 | depends on MAC80211 |
| 63 | − ---help--- | |
| 63 | + help | |
| 64 | 64 | Select this option to enable 802.11 mesh operation in mac80211 |
| 65 | 65 | drivers that support it. 802.11 mesh connects multiple stations |
| 66 | 66 | over (possibly multi-hop) wireless links to form a single logical |
| @@ -71,14 +71,14 @@ config MAC80211_LEDS · 4 unmodified lines | ||
| 71 | 71 | depends on MAC80211 |
| 72 | 72 | depends on LEDS_CLASS |
| 73 | 73 | select LEDS_TRIGGERS |
| 74 | − ---help--- | |
| 74 | + help | |
| 75 | 75 | This option enables a few LED triggers for different |
| 76 | 76 | packet receive/transmit events. |
| 77 | 77 | |
| 78 | 78 | config MAC80211_DEBUGFS |
| 79 | 79 | bool "Export mac80211 internals in DebugFS" |
| 80 | 80 | depends on MAC80211 && DEBUG_FS |
| 81 | − ---help--- | |
| 81 | + help | |
| 82 | 82 | Select this to see extensive information about |
| 83 | 83 | the internal state of mac80211 in debugfs. |
| 84 | 84 | |
| @@ -87,7 +87,7 @@ config MAC80211_DEBUGFS · 2 unmodified lines | ||
| 87 | 87 | config MAC80211_MESSAGE_TRACING |
| 88 | 88 | bool "Trace all mac80211 debug messages" |
| 89 | 89 | depends on MAC80211 |
| 90 | − ---help--- | |
| 90 | + help | |
| 91 | 91 | Select this option to have mac80211 register the |
| 92 | 92 | mac80211_msg trace subsystem with tracepoints to |
| 93 | 93 | collect all debugging messages, independent of |
| @@ -100,13 +100,13 @@ config MAC80211_MESSAGE_TRACING · 6 unmodified lines | ||
| 100 | 100 | menuconfig MAC80211_DEBUG_MENU |
| 101 | 101 | bool "Select mac80211 debugging features" |
| 102 | 102 | depends on MAC80211 |
| 103 | − ---help--- | |
| 103 | + help | |
| 104 | 104 | This option collects various mac80211 debug settings. |
| 105 | 105 | |
| 106 | 106 | config MAC80211_NOINLINE |
| 107 | 107 | bool "Do not inline TX/RX handlers" |
| 108 | 108 | depends on MAC80211_DEBUG_MENU |
| 109 | − ---help--- | |
| 109 | + help | |
| 110 | 110 | This option affects code generation in mac80211, when |
| 111 | 111 | selected some functions are marked "noinline" to allow |
| 112 | 112 | easier debugging of problems in the transmit and receive |
| @@ -122,7 +122,7 @@ config MAC80211_NOINLINE · 9 unmodified lines | ||
| 122 | 122 | config MAC80211_VERBOSE_DEBUG |
| 123 | 123 | bool "Verbose debugging output" |
| 124 | 124 | depends on MAC80211_DEBUG_MENU |
| 125 | − ---help--- | |
| 125 | + help | |
| 126 | 126 | Selecting this option causes mac80211 to print out |
| 127 | 127 | many debugging messages. It should not be selected |
| 128 | 128 | on production systems as some of the messages are |
| @@ -133,7 +133,7 @@ config MAC80211_VERBOSE_DEBUG · 4 unmodified lines | ||
| 133 | 133 | config MAC80211_MLME_DEBUG |
| 134 | 134 | bool "Verbose managed MLME output" |
| 135 | 135 | depends on MAC80211_DEBUG_MENU |
| 136 | − ---help--- | |
| 136 | + help | |
| 137 | 137 | Selecting this option causes mac80211 to print out |
| 138 | 138 | debugging messages for the managed-mode MLME. It |
| 139 | 139 | should not be selected on production systems as some |
| @@ -144,7 +144,7 @@ config MAC80211_MLME_DEBUG · 4 unmodified lines | ||
| 144 | 144 | config MAC80211_STA_DEBUG |
| 145 | 145 | bool "Verbose station debugging" |
| 146 | 146 | depends on MAC80211_DEBUG_MENU |
| 147 | − ---help--- | |
| 147 | + help | |
| 148 | 148 | Selecting this option causes mac80211 to print out |
| 149 | 149 | debugging messages for station addition/removal. |
| 150 | 150 | |
| @@ -153,7 +153,7 @@ config MAC80211_STA_DEBUG · 2 unmodified lines | ||
| 153 | 153 | config MAC80211_HT_DEBUG |
| 154 | 154 | bool "Verbose HT debugging" |
| 155 | 155 | depends on MAC80211_DEBUG_MENU |
| 156 | − ---help--- | |
| 156 | + help | |
111 more lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.
This diff is large: its 25 lines aren’t shown here.
This diff is large: its 17 lines aren’t shown here.
This diff is large: its 261 lines aren’t shown here.
This diff is large: its 237 lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.
This diff is large: its 8 lines aren’t shown here.
This diff is large: its 8 lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.
This diff is large: its 36 lines aren’t shown here.
This diff is large: its 17 lines aren’t shown here.
This diff is large: its 25 lines aren’t shown here.
This diff is large: its 26 lines aren’t shown here.
This diff is large: its 544 lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.
This diff is large: its 18 lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.
This diff is large: its 17 lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.
This diff is large: its 17 lines aren’t shown here.
This diff is large: its 54 lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.
This diff is large: its 63 lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.
This diff is large: its 11 lines aren’t shown here.
This diff is large: its 8 lines aren’t shown here.
This diff is large: its 27 lines aren’t shown here.
This diff is large: its 20 lines aren’t shown here.
This diff is large: its 14 lines aren’t shown here.
This diff is large: its 27 lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.
This diff is large: its 26 lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.
This diff is large: its 16 lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.
This diff is large: its 9 lines aren’t shown here.