source: trunk/config/kernel/config/options.in @ 724

Last change on this file since 724 was 724, checked in by amain, 5 years ago

Simplyfy patch / release management. Restructure make menuconfig. Add auto upload for buildbot builds. Latest OpenWrt trunk fixes.

File size: 28.8 KB
Line 
1# DebWrt - Debian on Embedded devices
2#
3# Copyright (C) 2010 Johan van Zoomeren <amain@debwrt.net>
4#
5# This program is free software: you can redistribute it and/or modify
6# it under the terms of the GNU General Public License as published by
7# the Free Software Foundation, either version 3 of the License, or
8# (at your option) any later version.
9#
10# This program is distributed in the hope that it will be useful,
11# but WITHOUT ANY WARRANTY; without even the implied warranty of
12# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
13# GNU General Public License for more details.
14#
15# You should have received a copy of the GNU General Public License
16# along with this program.  If not, see <http://www.gnu.org/licenses/>.
17
18
19menu "DebWrt kernel options/overrides"
20
21menu "Overrides"
22
23config SYSFS_DEPRECATED
24        bool "Enable deprecated sysfs features to support old userspace tools"
25        default n
26        help
27          For DebWrt/Debian: say N hre.
28          .
29          This option adds code that switches the layout of the "block" class
30          devices, to not show up in /sys/class/block/, but only in
31          /sys/block/.
32          .
33          This switch is only active when the sysfs.deprecated=1 boot option is
34          passed or the SYSFS_DEPRECATED_V2 option is set.
35          .
36          This option allows new kernels to run on old distributions and tools,
37          which might get confused by /sys/class/block/. Since 2007/2008 all
38          major distributions and tools handle this just fine.
39          .
40          Recent distributions and userspace tools after 2009/2010 depend on
41          the existence of /sys/class/block/, and will not work with this
42          option enabled.
43          .
44          Only if you are using a new kernel on an old distribution, you might
45          need to say Y here.
46
47config SYSFS_DEPRECATED_V2
48        bool "Enable deprecated sysfs features by default"
49        default n
50        depends on SYSFS_DEPRECATED
51        help
52          For DebWrt/Debian: say N hre.
53          .
54          Enable deprecated sysfs by default.
55          .
56          See the CONFIG_SYSFS_DEPRECATED option for more details about this
57          option.
58          .
59          Only if you are using a new kernel on an old distribution, you might
60          need to say Y here. Even then, odds are you would not need it
61          enabled, you can always pass the boot option if absolutely necessary.
62
63endmenu
64
65source "config/kernel/config/systemd.in"
66
67menu "General configuration"
68
69# systemd kernel requirements/recommendations: http://cgit.freedesktop.org/systemd/systemd/tree/README
70
71config NET_NS
72        bool "Network namespace support"
73        default y
74        help
75          Allow user space to create what appear to be multiple instances of the
76          network stack.
77          .
78          Systemd requirement, starting with Jessie.
79
80config BLK_DEV_BSG
81        bool "Block layer SG support v4"
82        default y
83        help
84          Saying Y here will enable generic SG (SCSI generic) v4 support for any
85          block device. Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG
86          v4 can handle complicated SCSI commands: tagged variable length cdbs with
87          bidirectional data transfers and generic request/response protocols (e.g.
88          Task Management Functions and SMP in Serial Attached SCSI).
89          .
90          This option is required by recent UDEV versions to properly access device
91          serial numbers, etc.
92          .
93          If unsure, say Y.
94          .
95          Recommended by systemd, starting with Jessie.
96
97
98config DMIID
99        bool "Export DMI identification via sysfs to userspace"
100        default y
101        help
102          Say Y here if you want to query SMBIOS/DMI system identification information
103          from userspace through /sys/class/dmi/id/ or if you want DMI-based module
104          auto-loading.
105          loading firmware files as a fallback after the direct file loading in kernel
106          fails. The user-mode helper is no longer required unless you have a special
107          .
108          Recommended for systemd, starting with Jessie.
109
110config FW_LOADER_USER_HELPER
111        bool "Fallback user-helper invocation for firmware loading"
112        default n
113        help
114          This option enables / disables the invocation of user-helper (e.g. udev) for
115          loading firmware files as a fallback after the direct file loading in kernel
116          fails. The user-mode helper is no longer required unless you have a special
117          firmware file that resides in a non-standard path.
118          .
119          Required disabled for systemd, starting with Jessie.
120
121config UEVENT_HELPER_PATH
122        string "Path to uevent helper"
123        default ""
124        help
125          To disable user space helper program execution at by default specify an empty
126          string here. This setting can still be altered via /proc/sys/kernel/hotplug
127          or via /sys/kernel/uevent_helper later at runtime.
128          .
129          Recommended disabled for performance tuning for systemd, starting with Jessie.
130
131config FHANDLE
132        bool "Open by fhandle syscalls"
133        default y
134        help
135          If you say Y here, a user level program will be able to map file names
136          to handle and then later use the handle for different file system operations.
137          This is useful in implementing userspace file servers, which now track files
138          using handles instead of names. The handle would remain the same even if file
139          names get renamed. Enables open_by_handle_at(2) and name_to_handle_at(2)
140          syscalls.
141          .
142          Required for systemd, starting with Jessie.
143
144# remove: can't be a module:
145# .config:137:warning: symbol value 'm' invalid for IPV6
146#config IPV6
147#        boolean "The IPv6 protocol"
148#       default m
149#        help
150#          This is complemental support for the IP version 6.
151#          You will still be able to do traditional IPv4 networking as well.
152#          .
153#          Recommended for systemd, starting with Jessie.
154
155config AUTOFS4_FS
156        tristate "Kernel automounter version 4 support (also supports v3)"
157        default m
158        help
159          The automounter is a tool to automatically mount remote file systems
160          on demand. This implementation is partially kernel-based to reduce
161          overhead in the already-mounted case; this is unlike the BSD
162          automounter (amd), which is a pure user space daemon.
163          .
164          Recommended for systemd, starting with Jessie.
165
166config CGROUPS
167        bool "Control Group Support"
168        default y
169        help
170          This option adds support for grouping sets of processes together, for
171          use with process control subsystems such as Cpusets, CFS, memory
172          controls or device isolation.
173          .
174          Required by systemd, starting with Jessie.
175
176config DEVTMPFS
177        bool "Maintain devtmpfs to mount at /dev"
178        default y
179        help
180          This creates a tmpfs/ramfs filesystem instance early at bootup. In this filesystem,
181          the kernel driver core maintains device nodes with their default names and
182          permissions for all registered devices with an assigned major/minor number.
183          .
184          Debian Jessie requires this.
185
186#CONFIG_MIPS_FPU_EMU=y
187config MIPS_FPU_EMU
188        bool "Enable kernel Floating Point emulation for MIPS"
189        default y
190        help
191          Build MIPS Floating Point emultaion into the kernel. Actually OpenWrt created a patch
192          to remove FPU code for MIPS from the kernel, to save a few bytes. However, Debian needs
193          the FPU to be enabled since glibc? does not have FPU code compiled in. When FPU is not
194          available no Debian compiled program will run. Init(which is the first process which is
195          started by the kernel will just freeze.
196
197config MIPS_FPU_EMULATOR
198        bool "MIPS FPU Emulator"
199        default y
200        help
201          MIPS_FPU_EMU now renamed to MIPS_FPU_EMULATOR. See help text of MIPS_FPU_EMU for more
202          information.
203
204config INOTIFY
205        bool "Inotify file change notification support"
206        default y
207        ---help---
208          udev in Debian SID won't boot if Inotify file change notification is not enabled in the
209          kernel.
210
211          Say Y here to enable inotify support.  Inotify is a file change
212          notification system and a replacement for dnotify.  Inotify fixes
213          numerous shortcomings in dnotify and introduces several new features
214          including multiple file events, one-shot support, and unmount
215          notification.
216
217          For more information, see <file:Documentation/filesystems/inotify.txt>
218
219          If unsure, say Y.
220
221config INOTIFY_USER
222        bool "Inotify support for userspace"
223        depends on INOTIFY
224        default y
225        ---help---
226          Say Y here to enable inotify support for userspace, including the
227          associated system calls.  Inotify allows monitoring of both files and
228          directories via a single open fd.  Events are read from the file
229          descriptor, which is also select()- and poll()-able.
230
231          For more information, see <file:Documentation/filesystems/inotify.txt>
232
233          If unsure, say Y.
234
235#CONFIG_BLK_DEV_LOOP=y
236config BLK_DEV_LOOP
237        bool "Loopback device support"
238        default y
239        help
240          Saying Y here will allow you to use a regular file as a block device. I can't live without
241          this feature ;-)
242
243endmenu
244
245menu "IDE Configuration"
246
247#CONFIG_IDEPCI_PCIBUS_ORDER=y
248config IDEPCI_PCIBUS_ORDER
249    bool
250    default y
251
252#CONFIG_IDE_XFER_MODE=y
253config IDE_XFER_MODE
254    bool
255    default y
256
257#CONFIG_BLK_DEV_IDEDMA_SFF=y
258config BLK_DEV_IDEDMA_SFF
259    bool
260    default y
261
262#CONFIG_BLK_DEV_IDEPCI=y
263config BLK_DEV_IDEPCI
264    bool
265    default y
266
267#CONFIG_BLK_DEV_IDEDMA_PCI=y
268config BLK_DEV_IDEDMA_PCI
269    bool
270    default y
271
272#CONFIG_BLK_DEV_IDEDMA=y
273config BLK_DEV_IDEDMA
274    bool
275    default y
276
277# make kernel compile not stop:
278config IDE_GD_ATAPI
279        bool
280        default n
281
282#CONFIG_IDE=y
283config IDE
284    bool "ATA/ATAPI/MFM/RLL support (DEPRECATED)"
285    default n
286    ---help---
287      If you say Y here, your kernel will be able to manage ATA/(E)IDE and
288      ATAPI units. The most common cases are IDE hard drives and ATAPI
289      CD-ROM drives.
290
291      This subsystem is currently in maintenance mode with only bug fix
292      changes applied. Users of ATA hardware are encouraged to migrate to
293      the newer ATA subsystem ("Serial ATA (prod) and Parallel ATA
294      (experimental) drivers") which is more actively maintained.
295
296      To compile this driver as a module, choose M here: the
297      module will be called ide-core.
298
299      For further information, please read <file:Documentation/ide/ide.txt>.
300
301      If unsure, say N.
302
303#CONFIG_IDE_GD=y
304config IDE_GD
305    tristate "generic ATA/ATAPI disk support"
306    default y
307    help
308      Support for ATA/ATAPI disks (including ATAPI floppy drives).
309
310      To compile this driver as a module, choose M here.
311      The module will be called ide-gd_mod.
312
313      If unsure, say Y.
314
315#CONFIG_IDE_GD_ATA=y
316config IDE_GD_ATA
317    bool "ATA disk support"
318    depends on IDE_GD
319    default y
320    help
321      This will include support for ATA hard disks.
322
323      If unsure, say Y.
324
325#CONFIG_IDE_PROC_FS=y
326config IDE_PROC_FS
327    bool "legacy /proc/ide/ support"
328    depends on IDE
329    default y
330    help
331      This option enables support for the various files in
332      /proc/ide.  In Linux 2.6 this has been superseded by
333      files in sysfs but many legacy applications rely on this.
334
335      If unsure say Y.
336
337#CONFIG_BLK_DEV_PDC202XX_OLD=y
338config BLK_DEV_PDC202XX_OLD
339    tristate "PROMISE PDC202{46|62|65|67} support"
340    select BLK_DEV_IDEDMA_PCI
341    default y
342    help
343      Promise Ultra33 or PDC20246
344      Promise Ultra66 or PDC20262
345      Promise Ultra100 or PDC20265/PDC20267/PDC20268
346
347      This driver adds up to 4 more EIDE devices sharing a single
348      interrupt. This add-on card is a bootable PCI UDMA controller. Since
349      multiple cards can be installed and there are BIOS ROM problems that
350      happen if the BIOS revisions of all installed cards (three-max) do
351      not match, the driver attempts to do dynamic tuning of the chipset
352      at boot-time for max-speed.  Ultra33 BIOS 1.25 or newer is required
353      for more than one card.
354
355      Please read the comments at the top of
356      <file:drivers/ide/pci/pdc202xx_old.c>.
357
358      If unsure, say N.
359
360endmenu
361
362menu "SCSI configuration"
363
364#CONFIG_SCSI=y
365config SCSI
366        tristate "SCSI device support"
367        default y
368        help
369          SCSI device support
370
371#CONFIG_SCSI_DMA=y
372config SCSI_DMA
373        bool
374        prompt "Enable DMA for SCSI" if SCSI
375        default y
376 
377#CONFIG_SCSI_PROC_FS=y
378config SCSI_PROC_FS
379        bool "legacy /proc/scsi/ support"
380        depends on SCSI
381        default y
382        help
383          This option enables support for the various files in
384          /proc/scsi. In Linux 2.6 this has been superseded by
385          files in sysfs but many legacy applications rely on this.
386
387#CONFIG_SCSI_WAIT_SCAN=m
388config SCSI_WAIT_SCAN
389        tristate "Wait for SCSI scan completion"
390        depends on SCSI
391        default n
392        help
393          The SCSI subsystem can probe for devices while the rest of the
394          system continues booting, and even probe devices on different
395          busses in parallel, leading to a significant speed-up.
396       
397          You can load the scsi_wait_scan module to ensure that all scans
398          have completed.
399 
400#CONFIG_BLK_DEV_SD=y
401config BLK_DEV_SD
402        tristate "SCSI disk support"
403        depends on SCSI
404        default y
405        help
406          If you want to use SCSI hard disks, Fibre Channel disks,
407          Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
408          USB storage or the SCSI or parallel port version of
409          the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
410          the Disk-HOWTO and the Multi-Disk-HOWTO, available from
411          <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
412          CD-ROMs.
413
414          To compile this driver as a module, choose M here and read
415          <file:Documentation/scsi/scsi.txt>.
416          The module will be called sd_mod.
417
418          Do not compile this driver as a module if your root file system
419          (the one containing the directory /) is located on a SCSI disk.
420          In this case, do not compile the driver for your SCSI host adapter
421          (below) as a module either.
422
423endmenu
424
425menu "USB configuration"
426
427#CONFIG_USB=y
428config USB
429        tristate "USB support"
430        default y
431        help
432          This option adds core support for Universal Serial Bus (USB).
433          You will also need drivers from the following menu to make use of it.
434
435config USB_DEBUG
436        bool "USB verbose debug messages"
437        default n
438        depends on USB
439        help
440          Say Y here if you want the USB core & hub drivers to produce a bunch
441          of debug messages to the system log. Select this if you are having a
442          problem with USB support and want to see more of what is going on.
443
444#CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
445config USB_ANNOUNCE_NEW_DEVICES
446        bool "USB announce new devices"
447        depends on USB
448        default y
449        help
450          Say Y here if you want the USB core to always announce the
451          idVendor, idProduct, Manufacturer, Product, and SerialNumber
452          strings for every new USB device to the syslog.  This option is
453          usually used by distro vendors to help with debugging and to
454          let users know what specific device was added to the machine
455          in what location.
456
457          If you do not want this kind of information sent to the system
458          log, or have any doubts about this, say N here.
459
460#CONFIG_USB_DEVICEFS=y
461config USB_DEVICEFS
462        bool "USB device filesystem"
463        depends on USB
464        default y
465        help
466          If you say Y here (and to "/proc file system support" in the "File
467          systems" section, above), you will get a file /proc/bus/usb/devices
468          which lists the devices currently connected to your USB bus or
469          busses, and for every connected device a file named
470          "/proc/bus/usb/xxx/yyy", where xxx is the bus number and yyy the
471          device number; the latter files can be used by user space programs
472          to talk directly to the device. These files are "virtual", meaning
473          they are generated on the fly and not stored on the hard drive.
474
475          You may need to mount the usbfs file system to see the files, use
476          mount -t usbfs none /proc/bus/usb
477
478          For the format of the various /proc/bus/usb/ files, please read
479          <file:Documentation/usb/proc_usb_info.txt>.
480
481          Usbfs files can't handle Access Control Lists (ACL), which are the
482          default way to grant access to USB devices for untrusted users of a
483          desktop system. The usbfs functionality is replaced by real
484          device-nodes managed by udev. These nodes live in /dev/bus/usb and
485          are used by libusb.
486 
487#CONFIG_USB_DEVICE_CLASS=y
488config USB_DEVICE_CLASS
489        bool "USB device class-devices (DEPRECATED)"
490        depends on USB
491        default y
492        ---help---
493          Userspace access to USB devices is granted by device-nodes exported
494          directly from the usbdev in sysfs. Old versions of the driver
495          core and udev needed additional class devices to export device nodes.
496
497          These additional devices are difficult to handle in userspace, if
498          information about USB interfaces must be available. One device
499          contains the device node, the other device contains the interface
500          data. Both devices are at the same level in sysfs (siblings) and one
501          can't access the other. The device node created directly by the
502          usb device is the parent device of the interface and therefore
503          easily accessible from the interface event.
504
505          This option provides backward compatibility for libusb device
506          nodes (lsusb) when usbfs is not used, and the following udev rule
507          doesn't exist:
508            SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", \
509            NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0644"
510
511#CONFIG_USB_MON=y
512config USB_MON
513        tristate "USB Monitor"
514        depends on USB
515        default y if USB=y
516        default m if USB=m
517        help
518          If you select this option, a component which captures the USB traffic
519          between peripheral-specific drivers and HC drivers will be built.
520          For more information, see <file:Documentation/usb/usbmon.txt>.
521
522          If unsure, say Y (if allowed), otherwise M.
523 
524#CONFIG_USB_EHCI_HCD=y
525config USB_EHCI_HCD
526    bool "EHCI HCD (USB 2.0) support"
527        depends on USB
528        default y
529        ---help---
530          The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0
531          "high speed" (480 Mbit/sec, 60 Mbyte/sec) host controller hardware.
532          If your USB host controller supports USB 2.0, you will likely want to
533          configure this Host Controller Driver.
534
535          EHCI controllers are packaged with "companion" host controllers (OHCI
536          or UHCI) to handle USB 1.1 devices connected to root hub ports.  Ports
537          will connect to EHCI if the device is high speed, otherwise they
538          connect to a companion controller.  If you configure EHCI, you should
539          probably configure the OHCI (for NEC and some other vendors) USB Host
540          Controller Driver or UHCI (for Via motherboards) Host Controller
541          Driver too.
542
543          You may want to read <file:Documentation/usb/ehci.txt>.
544
545          To compile this driver as a module, choose M here: the
546          module will be called ehci-hcd.
547
548# +CONFIG_USB_OHCI_HCD=y
549config USB_OHCI_HCD
550    tristate "OHCI HCD support"
551    depends on USB
552        default m if TARGET_brcm47xx=y
553        default y if TARGET_brcm47xx!=y
554    ---help---
555      The Open Host Controller Interface (OHCI) is a standard for accessing
556      USB 1.1 host controller hardware.  It does more in hardware than Intel's
557      UHCI specification.  If your USB host controller follows the OHCI spec,
558      say Y.  On most non-x86 systems, and on x86 hardware that's not using a
559      USB controller from Intel or VIA, this is appropriate.  If your host
560      controller doesn't use PCI, this is probably appropriate.  For a PCI
561      based system where you're not sure, the "lspci -v" entry will list the
562      right "prog-if" for your USB controller(s):  EHCI, OHCI, or UHCI.
563
564      To compile this driver as a module, choose M here: the
565      module will be called ohci-hcd.
566
567# +CONFIG_USB_UHCI_HCD=y
568config USB_UHCI_HCD
569    tristate "UHCI HCD (most Intel and VIA) support"
570    depends on USB
571        default y
572    ---help---
573      The Universal Host Controller Interface is a standard by Intel for
574      accessing the USB hardware in the PC (which is also called the USB
575      host controller). If your USB host controller conforms to this
576      standard, you may want to say Y, but see below. All recent boards
577      with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
578      i810, i820) conform to this standard. Also all VIA PCI chipsets
579      (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
580      133). If unsure, say Y.
581
582      To compile this driver as a module, choose M here: the
583      module will be called uhci-hcd.
584
585#CONFIG_USB_EHCI_AR71XX=y
586config USB_EHCI_AR71XX
587        bool "USB EHCI support for AR71xx"
588        depends on USB_EHCI_HCD && TARGET_ar71xx
589        default y
590        help
591          Support for Atheros AR71xx built-in EHCI controller
592
593#CONFIG_USB_OHCI_AR71XX=y
594config USB_OHCI_AR71XX
595        bool "USB OHCI support for Atheros AR71xx"
596        depends on USB_OHCI_HCD && TARGET_ar71xx
597        default y
598        help
599          Support for Atheros AR71xx built-in OHCI controller
600 
601config USB_EHCI_ROOT_HUB_TT
602        bool "Root Hub Transaction Translators"
603        depends on USB_EHCI_HCD
604        default n
605        ---help---
606          Some EHCI chips have vendor-specific extensions to integrate
607          transaction translators, so that no OHCI or UHCI companion
608          controller is needed.  It's safe to say "y" even if your
609          controller doesn't support this feature.
610
611          This supports the EHCI implementation that's originally
612          from ARC, and has since changed hands a few times.
613 
614#CONFIG_USB_STORAGE=y
615config USB_STORAGE
616        tristate "USB Mass Storage support"
617        depends on USB && SCSI
618        default y
619        ---help---
620          Say Y here if you want to connect USB mass storage devices to your
621          computer's USB port. This is the driver you need for USB
622          floppy drives, USB hard disks, USB tape drives, USB CD-ROMs,
623          USB flash devices, and memory sticks, along with
624          similar devices. This driver may also be used for some cameras
625          and card readers.
626
627          This option depends on 'SCSI' support being enabled, but you
628          probably also need 'SCSI device support: SCSI disk support'
629          (BLK_DEV_SD) for most USB storage devices.
630
631          To compile this driver as a module, choose M here: the
632          module will be called usb-storage.
633
634endmenu
635
636menu "Filesystem support"
637
638config EXT3_FS
639        tristate "Ext3 journalling file system support"
640        default y
641        select JBD
642        help
643          This is the journalling version of the Second extended file system
644          (often called ext3), the de facto standard Linux file system
645          (method to organize files on a storage device) for hard disks.
646
647          The journalling code included in this driver means you do not have
648          to run e2fsck (file system checker) on your file systems after a
649          crash.  The journal keeps track of any changes that were being made
650          at the time the system crashed, and can ensure that your file system
651          is consistent without the need for a lengthy check.
652
653          Other than adding the journal to the file system, the on-disk format
654          of ext3 is identical to ext2.  It is possible to freely switch
655          between using the ext3 driver and the ext2 driver, as long as the
656          file system has been cleanly unmounted, or e2fsck is run on the file
657          system.
658
659          To add a journal on an existing ext2 file system or change the
660          behavior of ext3 file systems, you can use the tune2fs utility ("man
661          tune2fs").  To modify attributes of files and directories on ext3
662          file systems, use chattr ("man chattr").  You need to be using
663          e2fsprogs version 1.20 or later in order to create ext3 journals
664          (available at <http://sourceforge.net/projects/e2fsprogs/>).
665
666          To compile this file system support as a module, choose M here: the
667          module will be called ext3.
668
669config EXT3_DEFAULTS_TO_ORDERED
670        bool "Default to 'data=ordered' in ext3 (legacy option)"
671        depends on EXT3_FS
672        help
673          If a filesystem does not explicitly specify a data ordering
674          mode, and the journal capability allowed it, ext3 used to
675          historically default to 'data=ordered'.
676
677          That was a rather unfortunate choice, because it leads to all
678          kinds of latency problems, and the 'data=writeback' mode is more
679          appropriate these days.
680
681          You should probably always answer 'n' here, and if you really
682          want to use 'data=ordered' mode, set it in the filesystem itself
683          with 'tune2fs -o journal_data_ordered'.
684
685          But if you really want to enable the legacy default, you can do
686          so by answering 'y' to this question.
687
688config EXT3_FS_XATTR
689        bool "Ext3 extended attributes"
690        depends on EXT3_FS
691        default y
692        help
693          Extended attributes are name:value pairs associated with inodes by
694          the kernel or by users (see the attr(5) manual page, or visit
695          <http://acl.bestbits.at/> for details).
696
697          If unsure, say N.
698
699          You need this for POSIX ACL support on ext3.
700
701config EXT3_FS_POSIX_ACL
702        bool "Ext3 POSIX Access Control Lists"
703        depends on EXT3_FS_XATTR
704        select FS_POSIX_ACL
705        default y
706        help
707          Posix Access Control Lists (ACLs) support permissions for users and
708          groups beyond the owner/group/world scheme.
709
710          To learn more about Access Control Lists, visit the Posix ACLs for
711          Linux website <http://acl.bestbits.at/>.
712
713          If you don't know what Access Control Lists are, say N
714
715config EXT3_FS_SECURITY
716        bool "Ext3 Security Labels"
717        depends on EXT3_FS_XATTR
718        default y
719        help
720          Security labels support alternative access control models
721          implemented by security modules like SELinux.  This option
722          enables an extended attribute handler for file security
723          labels in the ext3 filesystem.
724
725          If you are not using a security module that requires using
726          extended attributes for file security labels, say N.
727
728config FS_POSIX_ACL
729        bool
730        default y
731
732#CONFIG_JBD=y
733config JBD
734        tristate "JBD generic journalling layer"
735        help
736          This is a generic journalling layer for block devices.  It is
737          currently used by the ext3 file system, but it could also be
738          used to add journal support to other file systems or block
739          devices such as RAID or LVM.
740
741          If you are using the ext3 file system, you need to say Y here.
742          If you are not using ext3 then you will probably want to say N.
743
744          To compile this device as a module, choose M here: the module will be
745          called jbd.  If you are compiling ext3 into the kernel, you
746          cannot compile this code as a module.
747
748#CONFIG_FS_MBCACHE=y
749config FS_MBCACHE
750# Meta block cache for Extended Attributes (ext2/ext3/ext4)
751        tristate "Meta block cache for Extended Attributes (ext2/ext3/ext4)"
752        default y if EXT2_FS=y && EXT2_FS_XATTR
753        default y if EXT3_FS=y && EXT3_FS_XATTR
754        default y if EXT4_FS=y && EXT4_FS_XATTR
755        default m if EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4_FS_XATTR
756
757endmenu 
758 
759menu "OpenWrt Kernel Module Packages"
760
761menu "Wireless Kernel Modules"
762
763config PACKAGE_kmod-ath5k
764        bool "kmod-ath5k........................... Atheros 5xxx wireless cards support"
765        default y
766        help
767          This module adds support for wireless adapters based on
768          Atheros 5xxx chipset.
769          http://linuxwireless.org/en/users/Drivers/ath5k
770
771config PACKAGE_kmod-ath9k
772        bool "kmod-ath9k........................ Atheros 802.11n wireless cards support"
773        default y
774        help
775          This module adds support for wireless adapters based on
776          Atheros IEEE 802.11n AR5008 and AR9001 family of chipsets.
777          http://linuxwireless.org/en/users/Drivers/ath9k
778
779config PACKAGE_kmod-madwifi
780        bool "kmod-madwifi........................ Driver for Atheros wireless chipsets"
781        default y
782    help
783     This package contains a driver for Atheros 802.11a/b/g chipsets.
784     http://madwifi-project.org/
785
786config PACKAGE_kmod-b43
787        bool "kmod-b43.................................. Broadcom 43xx wireless support"
788        default y
789        help
790          Kernel module for Broadcom 43xx wireless support (mac80211 stack) new
791          http://linuxwireless.org/en/users/Drivers/b43
792
793config PACKAGE_kmod-b43legacy
794        bool "kmod-b43legacy..................... Broadcom 43xx-legacy wireless support"
795        default y
796    help
797      Kernel module for Broadcom 43xx-legacy wireless support (mac80211 stack) new
798      http://linuxwireless.org/en/users/Drivers/b43
799
800config PACKAGE_kmod-rt2500-pci
801        bool "kmod-rt2500-pci............. Ralink Drivers for RT2x00 cards (RT2500 PCI)"
802        default y
803        help
804      Ralink Drivers for RT2x00 cards (RT2500 PCI)
805      http://linuxwireless.org/
806
807config PACKAGE_kmod-rt2500-usb
808        bool "kmod-rt2500-usb............. Ralink Drivers for RT2x00 cards (RT2500 USB)"
809        default y
810        help
811        Ralink Drivers for RT2x00 cards (RT2500 USB)
812        http://linuxwireless.org/
813
814endmenu
815 
816endmenu
817
818config NETCONSOLE
819        bool "Network console logging support (EXPERIMENTAL)"
820        default y
821        ---help---
822        If you want to log kernel messages over the network, enable this.
823        See <file:Documentation/networking/netconsole.txt> for details.
824
825config NETCONSOLE_DYNAMIC
826        bool
827        default n
828
829config NETPOLL_TRAP
830        bool
831        default n
832
833
834endmenu
Note: See TracBrowser for help on using the repository browser.