source: trunk/Config.in @ 288

Last change on this file since 288 was 288, checked in by amain, 8 years ago

Add menuconfig option to pass commandline parameters to openwrt make ( by default -j 3 is passed )

File size: 30.5 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# Kconfig documentation: http://lxr.linux.no/#linux+v2.6.34.1/Documentation/kbuild/kconfig-language.txt
19
20config HAVE_DOT_CONFIG
21        bool
22        default y
23
24config HAS_SUBTARGETS
25        bool
26
27mainmenu "DebWrt Configuration"
28
29#choice
30#        prompt "Target System"
31#        default TARGET_ar71xx
32#
33#config TARGET_ar71xx
34#               bool "Atheros AR71xx/AR7240/AR913x"
35#               default y
36#               select HAS_SUBTARGETS
37#               select DEBWRT_TARGET_ARCH_MIPS
38#               help
39#                       Build firmware images for Atheros AR71xx/AR913x based boards.
40#
41#config TARGET_brcm47xx
42#       bool "Broadcom BCM947xx/953xx"
43#       default y
44#       select HAS_SUBTARGETS
45#               select DEBWRT_TARGET_ARCH_MIPSEL
46#    help
47#      Build firmware images for Broadcom based routers
48#      (e.g. Netgear WGT634U, Asus WL-500gd)
49#
50#endchoice
51#
52#choice
53#        prompt "Target Subsytem" if HAS_SUBTARGETS
54#       default TARGET_ar71xx_UBNTRSPRO
55#
56#config TARGET_ar71xx_UBNTRS
57#        bool "Ubiquiti RouterStation"
58#        depends TARGET_ar71xx
59#        help
60#          Package set optimized for the Ubiquiti RouterStation.
61#
62#config TARGET_ar71xx_UBNTRSPRO
63#        bool "Ubiquiti RouterStation Pro"
64#        depends TARGET_ar71xx
65#        help
66#          Package set optimized for the Ubiquiti RouterStation Pro.
67#
68#config TARGET_brcm47xx_Broadcom-b43
69#        bool "Broadcom BCM43xx WiFi (default)"
70#        depends TARGET_brcm47xx
71#        help
72#             Package set compatible with hardware using Broadcom BCM43xx cards
73#
74#config TARGET_brcm47xx_WGT634U
75#    bool "Netgear WGT634U"
76#    depends TARGET_brcm47xx
77#       help
78#         Package set compatible with the Netgear WGT634U.
79#
80#endchoice
81
82source "config/archs.in"
83source "config/config-target.in"
84
85#source "config/board.in"
86#source "config/sub_board.in"
87source "config/image_name.in"
88source "config/flash_ip.in"
89
90choice
91        prompt "OpenWrt Revision"
92        default OPENWRT_REVISION_TRUNK
93
94config OPENWRT_REVISION_TRUNK
95        bool "trunk"
96
97config OPENWRT_REVISION_BACKFIRE
98        bool "backfire ( not tested recently )"
99
100endchoice
101
102source "config/openwrt_revision.in"
103
104choice
105        prompt "Kernel Version"
106        default DEBWRT_KERNEL_DEFAULT
107        help
108          Select the linux kernel version you want to use with DebWrt
109
110config DEBWRT_KERNEL_DEFAULT
111        bool
112        prompt "Default"
113
114#config DEBWRT_KERNEL_2_6_32
115#        bool
116#       prompt "2.6.32" if OPENWRT_REVISION_TRUNK || OPENWRT_REVISION_R18829
117#
118#config DEBWRT_KERNEL_2_6_31
119#        bool
120#       prompt "2.6.31" if OPENWRT_REVISION_TRUNK || OPENWRT_REVISION_R18829
121#
122#config DEBWRT_KERNEL_2_6_30
123#        bool
124#       prompt "2.6.30" if OPENWRT_REVISION_TRUNK || OPENWRT_REVISION_R18829
125#
126#config DEBWRT_KERNEL_2_6_28
127#        bool
128#       prompt "2.6.28" if OPENWRT_REVISION_8_09
129
130endchoice
131
132source "config/kernel_version.in"
133
134
135menu "Kernel Configuration"
136
137# note: DMA Engine support
138# note: SDIO support
139#
140
141menu "General configuration"
142
143#CONFIG_MIPS_FPU_EMU=y
144config MIPS_FPU_EMU
145        bool "Enable kernel Floating Point emulation for MIPS"
146        default y
147        help
148          Build MIPS Floating Point emultaion into the kernel. Actually OpenWrt created a patch
149          to remove FPU code for MIPS from the kernel, to save a few bytes. However, Debian needs
150          the FPU to be enabled since glibc? does not have FPU code compiled in. When FPU is not
151          available no Debian compiled program will run. Init(which is the first process which is
152          started by the kernel will just freeze.
153
154config INOTIFY
155        bool "Inotify file change notification support"
156        default y
157        ---help---
158          udev in Debian SID won't boot if Inotify file change notification is not enabled in the
159          kernel.
160
161          Say Y here to enable inotify support.  Inotify is a file change
162          notification system and a replacement for dnotify.  Inotify fixes
163          numerous shortcomings in dnotify and introduces several new features
164          including multiple file events, one-shot support, and unmount
165          notification.
166
167          For more information, see <file:Documentation/filesystems/inotify.txt>
168
169          If unsure, say Y.
170
171config INOTIFY_USER
172        bool "Inotify support for userspace"
173        depends on INOTIFY
174        default y
175        ---help---
176          Say Y here to enable inotify support for userspace, including the
177          associated system calls.  Inotify allows monitoring of both files and
178          directories via a single open fd.  Events are read from the file
179          descriptor, which is also select()- and poll()-able.
180
181          For more information, see <file:Documentation/filesystems/inotify.txt>
182
183          If unsure, say Y.
184
185#CONFIG_BLK_DEV_LOOP=y
186config BLK_DEV_LOOP
187        bool "Loopback device support"
188        default y
189        help
190          Saying Y here will allow you to use a regular file as a block device. I can't live without
191          this feature ;-)
192
193endmenu
194
195menu "IDE Configuration"
196
197#CONFIG_IDEPCI_PCIBUS_ORDER=y
198config IDEPCI_PCIBUS_ORDER
199    bool
200    default y
201
202#CONFIG_IDE_XFER_MODE=y
203config IDE_XFER_MODE
204    bool
205    default y
206
207#CONFIG_BLK_DEV_IDEDMA_SFF=y
208config BLK_DEV_IDEDMA_SFF
209    bool
210    default y
211
212#CONFIG_BLK_DEV_IDEPCI=y
213config BLK_DEV_IDEPCI
214    bool
215    default y
216
217#CONFIG_BLK_DEV_IDEDMA_PCI=y
218config BLK_DEV_IDEDMA_PCI
219    bool
220    default y
221
222#CONFIG_BLK_DEV_IDEDMA=y
223config BLK_DEV_IDEDMA
224    bool
225    default y
226
227# make kernel compile not stop:
228config IDE_GD_ATAPI
229        bool
230        default n
231
232#CONFIG_IDE=y
233config IDE
234    bool "ATA/ATAPI/MFM/RLL support (DEPRECATED)"
235    default y
236    ---help---
237      If you say Y here, your kernel will be able to manage ATA/(E)IDE and
238      ATAPI units. The most common cases are IDE hard drives and ATAPI
239      CD-ROM drives.
240
241      This subsystem is currently in maintenance mode with only bug fix
242      changes applied. Users of ATA hardware are encouraged to migrate to
243      the newer ATA subsystem ("Serial ATA (prod) and Parallel ATA
244      (experimental) drivers") which is more actively maintained.
245
246      To compile this driver as a module, choose M here: the
247      module will be called ide-core.
248
249      For further information, please read <file:Documentation/ide/ide.txt>.
250
251      If unsure, say N.
252
253#CONFIG_IDE_GD=y
254config IDE_GD
255    tristate "generic ATA/ATAPI disk support"
256    default y
257    help
258      Support for ATA/ATAPI disks (including ATAPI floppy drives).
259
260      To compile this driver as a module, choose M here.
261      The module will be called ide-gd_mod.
262
263      If unsure, say Y.
264
265#CONFIG_IDE_GD_ATA=y
266config IDE_GD_ATA
267    bool "ATA disk support"
268    depends on IDE_GD
269    default y
270    help
271      This will include support for ATA hard disks.
272
273      If unsure, say Y.
274
275#CONFIG_IDE_PROC_FS=y
276config IDE_PROC_FS
277    bool "legacy /proc/ide/ support"
278    depends on IDE
279    default y
280    help
281      This option enables support for the various files in
282      /proc/ide.  In Linux 2.6 this has been superseded by
283      files in sysfs but many legacy applications rely on this.
284
285      If unsure say Y.
286
287#CONFIG_BLK_DEV_PDC202XX_OLD=y
288config BLK_DEV_PDC202XX_OLD
289    tristate "PROMISE PDC202{46|62|65|67} support"
290    select BLK_DEV_IDEDMA_PCI
291    default y
292    help
293      Promise Ultra33 or PDC20246
294      Promise Ultra66 or PDC20262
295      Promise Ultra100 or PDC20265/PDC20267/PDC20268
296
297      This driver adds up to 4 more EIDE devices sharing a single
298      interrupt. This add-on card is a bootable PCI UDMA controller. Since
299      multiple cards can be installed and there are BIOS ROM problems that
300      happen if the BIOS revisions of all installed cards (three-max) do
301      not match, the driver attempts to do dynamic tuning of the chipset
302      at boot-time for max-speed.  Ultra33 BIOS 1.25 or newer is required
303      for more than one card.
304
305      Please read the comments at the top of
306      <file:drivers/ide/pci/pdc202xx_old.c>.
307
308      If unsure, say N.
309
310endmenu
311
312menu "SCSI configuration"
313
314#CONFIG_SCSI=y
315config SCSI
316        tristate "SCSI device support"
317        default y
318        help
319          SCSI device support
320
321#CONFIG_SCSI_DMA=y
322config SCSI_DMA
323        bool
324        prompt "Enable DMA for SCSI" if SCSI
325        default y
326 
327#CONFIG_SCSI_PROC_FS=y
328config SCSI_PROC_FS
329        bool "legacy /proc/scsi/ support"
330        depends on SCSI
331        default y
332        help
333          This option enables support for the various files in
334          /proc/scsi. In Linux 2.6 this has been superseded by
335          files in sysfs but many legacy applications rely on this.
336
337#CONFIG_SCSI_WAIT_SCAN=m
338config SCSI_WAIT_SCAN
339        tristate "Wait for SCSI scan completion"
340        depends on SCSI
341        default n
342        help
343          The SCSI subsystem can probe for devices while the rest of the
344          system continues booting, and even probe devices on different
345          busses in parallel, leading to a significant speed-up.
346       
347          You can load the scsi_wait_scan module to ensure that all scans
348          have completed.
349 
350#CONFIG_BLK_DEV_SD=y
351config BLK_DEV_SD
352        tristate "SCSI disk support"
353        depends on SCSI
354        default y
355        help
356          If you want to use SCSI hard disks, Fibre Channel disks,
357          Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
358          USB storage or the SCSI or parallel port version of
359          the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
360          the Disk-HOWTO and the Multi-Disk-HOWTO, available from
361          <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
362          CD-ROMs.
363
364          To compile this driver as a module, choose M here and read
365          <file:Documentation/scsi/scsi.txt>.
366          The module will be called sd_mod.
367
368          Do not compile this driver as a module if your root file system
369          (the one containing the directory /) is located on a SCSI disk.
370          In this case, do not compile the driver for your SCSI host adapter
371          (below) as a module either.
372
373endmenu
374
375menu "USB configuration"
376
377#CONFIG_USB=y
378config USB
379        tristate "USB support"
380        default y
381        help
382          This option adds core support for Universal Serial Bus (USB).
383          You will also need drivers from the following menu to make use of it.
384
385config USB_DEBUG
386        bool "USB verbose debug messages"
387        default n
388        depends on USB
389        help
390          Say Y here if you want the USB core & hub drivers to produce a bunch
391          of debug messages to the system log. Select this if you are having a
392          problem with USB support and want to see more of what is going on.
393
394#CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
395config USB_ANNOUNCE_NEW_DEVICES
396        bool "USB announce new devices"
397        depends on USB
398        default y
399        help
400          Say Y here if you want the USB core to always announce the
401          idVendor, idProduct, Manufacturer, Product, and SerialNumber
402          strings for every new USB device to the syslog.  This option is
403          usually used by distro vendors to help with debugging and to
404          let users know what specific device was added to the machine
405          in what location.
406
407          If you do not want this kind of information sent to the system
408          log, or have any doubts about this, say N here.
409
410#CONFIG_USB_DEVICEFS=y
411config USB_DEVICEFS
412        bool "USB device filesystem"
413        depends on USB
414        default y
415        help
416          If you say Y here (and to "/proc file system support" in the "File
417          systems" section, above), you will get a file /proc/bus/usb/devices
418          which lists the devices currently connected to your USB bus or
419          busses, and for every connected device a file named
420          "/proc/bus/usb/xxx/yyy", where xxx is the bus number and yyy the
421          device number; the latter files can be used by user space programs
422          to talk directly to the device. These files are "virtual", meaning
423          they are generated on the fly and not stored on the hard drive.
424
425          You may need to mount the usbfs file system to see the files, use
426          mount -t usbfs none /proc/bus/usb
427
428          For the format of the various /proc/bus/usb/ files, please read
429          <file:Documentation/usb/proc_usb_info.txt>.
430
431          Usbfs files can't handle Access Control Lists (ACL), which are the
432          default way to grant access to USB devices for untrusted users of a
433          desktop system. The usbfs functionality is replaced by real
434          device-nodes managed by udev. These nodes live in /dev/bus/usb and
435          are used by libusb.
436 
437#CONFIG_USB_DEVICE_CLASS=y
438config USB_DEVICE_CLASS
439        bool "USB device class-devices (DEPRECATED)"
440        depends on USB
441        default y
442        ---help---
443          Userspace access to USB devices is granted by device-nodes exported
444          directly from the usbdev in sysfs. Old versions of the driver
445          core and udev needed additional class devices to export device nodes.
446
447          These additional devices are difficult to handle in userspace, if
448          information about USB interfaces must be available. One device
449          contains the device node, the other device contains the interface
450          data. Both devices are at the same level in sysfs (siblings) and one
451          can't access the other. The device node created directly by the
452          usb device is the parent device of the interface and therefore
453          easily accessible from the interface event.
454
455          This option provides backward compatibility for libusb device
456          nodes (lsusb) when usbfs is not used, and the following udev rule
457          doesn't exist:
458            SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", \
459            NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0644"
460
461#CONFIG_USB_MON=y
462config USB_MON
463        tristate "USB Monitor"
464        depends on USB
465        default y if USB=y
466        default m if USB=m
467        help
468          If you select this option, a component which captures the USB traffic
469          between peripheral-specific drivers and HC drivers will be built.
470          For more information, see <file:Documentation/usb/usbmon.txt>.
471
472          If unsure, say Y (if allowed), otherwise M.
473 
474#CONFIG_USB_EHCI_HCD=y
475config USB_EHCI_HCD
476    bool "EHCI HCD (USB 2.0) support"
477        depends on USB
478        default y
479        ---help---
480          The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0
481          "high speed" (480 Mbit/sec, 60 Mbyte/sec) host controller hardware.
482          If your USB host controller supports USB 2.0, you will likely want to
483          configure this Host Controller Driver.
484
485          EHCI controllers are packaged with "companion" host controllers (OHCI
486          or UHCI) to handle USB 1.1 devices connected to root hub ports.  Ports
487          will connect to EHCI if the device is high speed, otherwise they
488          connect to a companion controller.  If you configure EHCI, you should
489          probably configure the OHCI (for NEC and some other vendors) USB Host
490          Controller Driver or UHCI (for Via motherboards) Host Controller
491          Driver too.
492
493          You may want to read <file:Documentation/usb/ehci.txt>.
494
495          To compile this driver as a module, choose M here: the
496          module will be called ehci-hcd.
497
498# +CONFIG_USB_OHCI_HCD=y
499config USB_OHCI_HCD
500    tristate "OHCI HCD support"
501    depends on USB
502        default m if TARGET_brcm47xx=y
503        default y if TARGET_brcm47xx!=y
504    ---help---
505      The Open Host Controller Interface (OHCI) is a standard for accessing
506      USB 1.1 host controller hardware.  It does more in hardware than Intel's
507      UHCI specification.  If your USB host controller follows the OHCI spec,
508      say Y.  On most non-x86 systems, and on x86 hardware that's not using a
509      USB controller from Intel or VIA, this is appropriate.  If your host
510      controller doesn't use PCI, this is probably appropriate.  For a PCI
511      based system where you're not sure, the "lspci -v" entry will list the
512      right "prog-if" for your USB controller(s):  EHCI, OHCI, or UHCI.
513
514      To compile this driver as a module, choose M here: the
515      module will be called ohci-hcd.
516
517# +CONFIG_USB_UHCI_HCD=y
518config USB_UHCI_HCD
519    tristate "UHCI HCD (most Intel and VIA) support"
520    depends on USB
521        default y
522    ---help---
523      The Universal Host Controller Interface is a standard by Intel for
524      accessing the USB hardware in the PC (which is also called the USB
525      host controller). If your USB host controller conforms to this
526      standard, you may want to say Y, but see below. All recent boards
527      with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
528      i810, i820) conform to this standard. Also all VIA PCI chipsets
529      (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
530      133). If unsure, say Y.
531
532      To compile this driver as a module, choose M here: the
533      module will be called uhci-hcd.
534
535#CONFIG_USB_EHCI_AR71XX=y
536config USB_EHCI_AR71XX
537        bool "USB EHCI support for AR71xx"
538        depends on USB_EHCI_HCD
539        default y
540        help
541          Support for Atheros AR71xx built-in EHCI controller
542
543#CONFIG_USB_OHCI_AR71XX=y
544config USB_OHCI_AR71XX
545        bool "USB OHCI support for Atheros AR71xx"
546        depends on USB_OHCI_HCD
547        default y
548        help
549          Support for Atheros AR71xx built-in OHCI controller
550 
551config USB_EHCI_ROOT_HUB_TT
552        bool "Root Hub Transaction Translators"
553        depends on USB_EHCI_HCD
554        default n
555        ---help---
556          Some EHCI chips have vendor-specific extensions to integrate
557          transaction translators, so that no OHCI or UHCI companion
558          controller is needed.  It's safe to say "y" even if your
559          controller doesn't support this feature.
560
561          This supports the EHCI implementation that's originally
562          from ARC, and has since changed hands a few times.
563 
564#CONFIG_USB_STORAGE=y
565config USB_STORAGE
566        tristate "USB Mass Storage support"
567        depends on USB && SCSI
568        default y
569        ---help---
570          Say Y here if you want to connect USB mass storage devices to your
571          computer's USB port. This is the driver you need for USB
572          floppy drives, USB hard disks, USB tape drives, USB CD-ROMs,
573          USB flash devices, and memory sticks, along with
574          similar devices. This driver may also be used for some cameras
575          and card readers.
576
577          This option depends on 'SCSI' support being enabled, but you
578          probably also need 'SCSI device support: SCSI disk support'
579          (BLK_DEV_SD) for most USB storage devices.
580
581          To compile this driver as a module, choose M here: the
582          module will be called usb-storage.
583
584endmenu
585
586menu "Filesystem support"
587
588config EXT3_FS
589        tristate "Ext3 journalling file system support"
590        default y
591        select JBD
592        help
593          This is the journalling version of the Second extended file system
594          (often called ext3), the de facto standard Linux file system
595          (method to organize files on a storage device) for hard disks.
596
597          The journalling code included in this driver means you do not have
598          to run e2fsck (file system checker) on your file systems after a
599          crash.  The journal keeps track of any changes that were being made
600          at the time the system crashed, and can ensure that your file system
601          is consistent without the need for a lengthy check.
602
603          Other than adding the journal to the file system, the on-disk format
604          of ext3 is identical to ext2.  It is possible to freely switch
605          between using the ext3 driver and the ext2 driver, as long as the
606          file system has been cleanly unmounted, or e2fsck is run on the file
607          system.
608
609          To add a journal on an existing ext2 file system or change the
610          behavior of ext3 file systems, you can use the tune2fs utility ("man
611          tune2fs").  To modify attributes of files and directories on ext3
612          file systems, use chattr ("man chattr").  You need to be using
613          e2fsprogs version 1.20 or later in order to create ext3 journals
614          (available at <http://sourceforge.net/projects/e2fsprogs/>).
615
616          To compile this file system support as a module, choose M here: the
617          module will be called ext3.
618
619config EXT3_DEFAULTS_TO_ORDERED
620        bool "Default to 'data=ordered' in ext3 (legacy option)"
621        depends on EXT3_FS
622        help
623          If a filesystem does not explicitly specify a data ordering
624          mode, and the journal capability allowed it, ext3 used to
625          historically default to 'data=ordered'.
626
627          That was a rather unfortunate choice, because it leads to all
628          kinds of latency problems, and the 'data=writeback' mode is more
629          appropriate these days.
630
631          You should probably always answer 'n' here, and if you really
632          want to use 'data=ordered' mode, set it in the filesystem itself
633          with 'tune2fs -o journal_data_ordered'.
634
635          But if you really want to enable the legacy default, you can do
636          so by answering 'y' to this question.
637
638config EXT3_FS_XATTR
639        bool "Ext3 extended attributes"
640        depends on EXT3_FS
641        default y
642        help
643          Extended attributes are name:value pairs associated with inodes by
644          the kernel or by users (see the attr(5) manual page, or visit
645          <http://acl.bestbits.at/> for details).
646
647          If unsure, say N.
648
649          You need this for POSIX ACL support on ext3.
650
651config EXT3_FS_POSIX_ACL
652        bool "Ext3 POSIX Access Control Lists"
653        depends on EXT3_FS_XATTR
654        select FS_POSIX_ACL
655        help
656          Posix Access Control Lists (ACLs) support permissions for users and
657          groups beyond the owner/group/world scheme.
658
659          To learn more about Access Control Lists, visit the Posix ACLs for
660          Linux website <http://acl.bestbits.at/>.
661
662          If you don't know what Access Control Lists are, say N
663
664config EXT3_FS_SECURITY
665        bool "Ext3 Security Labels"
666        depends on EXT3_FS_XATTR
667        help
668          Security labels support alternative access control models
669          implemented by security modules like SELinux.  This option
670          enables an extended attribute handler for file security
671          labels in the ext3 filesystem.
672
673          If you are not using a security module that requires using
674          extended attributes for file security labels, say N.
675
676config FS_POSIX_ACL
677        bool
678        default y
679
680#CONFIG_JBD=y
681config JBD
682        tristate "JBD generic journalling layer"
683        help
684          This is a generic journalling layer for block devices.  It is
685          currently used by the ext3 file system, but it could also be
686          used to add journal support to other file systems or block
687          devices such as RAID or LVM.
688
689          If you are using the ext3 file system, you need to say Y here.
690          If you are not using ext3 then you will probably want to say N.
691
692          To compile this device as a module, choose M here: the module will be
693          called jbd.  If you are compiling ext3 into the kernel, you
694          cannot compile this code as a module.
695
696#CONFIG_FS_MBCACHE=y
697config FS_MBCACHE
698# Meta block cache for Extended Attributes (ext2/ext3/ext4)
699        tristate "Meta block cache for Extended Attributes (ext2/ext3/ext4)"
700        default y if EXT2_FS=y && EXT2_FS_XATTR
701        default y if EXT3_FS=y && EXT3_FS_XATTR
702        default y if EXT4_FS=y && EXT4_FS_XATTR
703        default m if EXT2_FS_XATTR || EXT3_FS_XATTR || EXT4_FS_XATTR
704
705endmenu 
706 
707menu "OpenWrt Kernel Module Packages"
708
709menu "Wireless Kernel Modules"
710
711config PACKAGE_kmod-ath5k
712        bool "kmod-ath5k........................... Atheros 5xxx wireless cards support"
713        default y
714        help
715          This module adds support for wireless adapters based on
716          Atheros 5xxx chipset.
717          http://linuxwireless.org/en/users/Drivers/ath5k
718
719config PACKAGE_kmod-ath9k
720        bool "kmod-ath9k........................ Atheros 802.11n wireless cards support"
721        default y
722        help
723          This module adds support for wireless adapters based on
724          Atheros IEEE 802.11n AR5008 and AR9001 family of chipsets.
725          http://linuxwireless.org/en/users/Drivers/ath9k
726
727config PACKAGE_kmod-madwifi
728        bool "kmod-madwifi........................ Driver for Atheros wireless chipsets"
729        default y
730    help
731     This package contains a driver for Atheros 802.11a/b/g chipsets.
732     http://madwifi-project.org/
733
734menuconfig PACKAGE_kmod-b43
735        bool "kmod-b43.................................. Broadcom 43xx wireless support"
736        default y
737        help
738          Kernel module for Broadcom 43xx wireless support (mac80211 stack) new
739          http://linuxwireless.org/en/users/Drivers/b43
740
741        menu "Configuration"
742                depends on PACKAGE_kmod-b43
743
744        choice
745                prompt "b43 firmware version"
746                default B43_EXPERIMENTAL
747                help
748                  This option allows you to select the version of the b43 firmware. DebWrt note:
749                  Over the years this experimental version showed better results then the stable
750                  version
751
752        config B43_STABLE
753                bool "4.150.10.5 (stable)"
754                help
755                  Stable firmware for BCM43xx devices.
756
757                  If unsure, select this.
758
759        config B43_EXPERIMENTAL
760                bool "4.178.10.4 (experimental)"
761                help
762                  Experimental firmware for BCM43xx devices.
763
764                  This firmware is not tested as much as the "stable" firmware.
765
766                  If unsure, select the "stable" firmware.
767
768        config B43_OPENFIRMWARE
769                bool "Open FirmWare for WiFi networks"
770                help
771                  Opensource firmware for BCM43xx devices.
772
773                  Do _not_ select this, unless you know what you are doing.
774                  The Opensource firmware is not suitable for embedded devices, yet.
775                  It does not support QoS, which is bad for AccessPoints.
776                  It does not support hardware crypto acceleration, which is a showstopper
777                  for embedded devices with low CPU resources.
778
779                  If unsure, select the "stable" firmware.
780
781        endchoice
782
783        config B43_FW_SQUASH
784                bool "Remove unnecessary firmware files"
785                depends on !B43_OPENFIRMWARE
786                default n
787                help
788                  This options allows you to remove unnecessary b43 firmware files
789                  from the final rootfs image. This can reduce the rootfs size by
790                  up to 200k.
791
792                  If unsure, say Y.
793
794        config B43_FW_SQUASH_COREREVS
795                string "Core revisions to include"
796                depends on B43_FW_SQUASH
797                default "5,6,7,8,9,10,13,14,15"
798                help
799                  This is a comma seperated list of core revision numbers.
800
801                  Example (keep files for rev5 only):
802                    5
803
804                  Example (keep files for rev5 and rev11):
805                    5,11
806
807        config B43_FW_SQUASH_PHYTYPES
808                string "PHY types to include"
809                depends on B43_FW_SQUASH
810                default "G,LP"
811                help
812                  This is a comma seperated list of PHY types:
813                    A  => A-PHY
814                    AG => Dual A-PHY G-PHY
815                    G  => G-PHY
816                    LP => LP-PHY
817                    N  => N-PHY
818
819                  Example (keep files for G-PHY only):
820                    G
821
822                  Example (keep files for G-PHY and N-PHY):
823                    G,N
824
825        endmenu
826
827config PACKAGE_kmod-b43legacy
828        bool "kmod-b43legacy..................... Broadcom 43xx-legacy wireless support"
829        default y
830    help
831      Kernel module for Broadcom 43xx-legacy wireless support (mac80211 stack) new
832      http://linuxwireless.org/en/users/Drivers/b43
833
834config PACKAGE_kmod-rt2500-pci
835        bool "kmod-rt2500-pci............. Ralink Drivers for RT2x00 cards (RT2500 PCI)"
836        default y
837        help
838      Ralink Drivers for RT2x00 cards (RT2500 PCI)
839      http://linuxwireless.org/
840
841config PACKAGE_kmod-rt2500-usb
842        bool "kmod-rt2500-usb............. Ralink Drivers for RT2x00 cards (RT2500 USB)"
843        default y
844        help
845        Ralink Drivers for RT2x00 cards (RT2500 USB)
846        http://linuxwireless.org/
847
848endmenu
849 
850endmenu
851
852config NETCONSOLE
853        bool "Network console logging support (EXPERIMENTAL)"
854        default y
855        ---help---
856        If you want to log kernel messages over the network, enable this.
857        See <file:Documentation/networking/netconsole.txt> for details.
858
859config NETCONSOLE_DYNAMIC
860        bool
861        default n
862
863config NETPOLL_TRAP
864        bool
865        default n
866
867config CMDLINE_BOOL
868        bool
869        default y
870
871#CONFIG_CMDLINE="root=/dev/sda1 init=/sbin/init rootdelay=10 noinitrd console=ttyS0,115200"
872# default "root=/dev/sda1 init=/sbin/init rootdelay=15 noinitrd console=ttyS0,115200"
873# default "root=/dev/sda1 init=/sbin/init rootdelay=15 noinitrd console=ttyS0,115200 netconsole=6665@10.0.2.1/eth0,6666@10.0.2.2"
874config CMDLINE
875        string "Default kernel command line"
876        default "root=/dev/sda1 init=/sbin/init rootdelay=15 noinitrd console=ttyS0,115200 netconsole=6665@192.168.1.1/eth0,6666@192.168.1.2/"
877        help
878          Override OpenWrt default kernel command line. Tell the kernel to boot from /dev/sda1,
879          an USB storage device. Rootdelay is specified, to give the USB storage/SCSI driver
880          to become ready, before the kernel tries to boot from it.
881
882endmenu
883
884menu "Debian Cross-Compile Environment Configuration"
885       
886config DEBIAN_BUILDENV_REPOSITORY
887        string "Debian Repository"
888        default "http://ftp.debian.org/debian"
889        help
890          Specify the Debian Repository used to set up de Debian Cross-Compile chroot
891          environment and used to install Debian chroot for the target architecture.
892
893config EMDEBIAN_BUILDENV_REPOSITORY
894        string "Emdebian Repository"
895        default "http://www.emdebian.org/debian"
896        help
897          Specify the Debian Repository used to set up de Debian Cross-Compile chroot
898          environment and used to install Debian chroot for the target architecture.
899
900config DEBIAN_BUILDENV_INCLUDE_PACKAGES
901        string "Additional packages"
902        default "file,less,strace,sudo"
903        help
904          Specify a comma seperated list of additional packages to install in the
905          Debian cross-compile environment. The cross compile environment is a
906          debootstrapped chrooted Debian sid installation.
907
908config DEBIAN_BUILDENV_QEMU_VERSION
909        string "Qemu version"
910        default "0.12.4"
911        help
912          At least 0.12.2 is needed for mips targets.
913
914endmenu
915
916menu "Debian Root Filesystem Configuration"
917
918choice
919    prompt "DebWrt Debian Release"
920        default DEBWRT_DEBIAN_RELEASE_SQUEEZE
921        help
922          Select the the Debian release for the root filesystem
923
924config DEBWRT_DEBIAN_RELEASE_SID
925    bool
926    prompt "Sid"
927
928config DEBWRT_DEBIAN_RELEASE_SQUEEZE
929    bool
930    prompt "Squeeze"
931
932config DEBWRT_DEBIAN_RELEASE_LENNY
933    bool
934    prompt "Lenny"
935
936endchoice
937
938config DEBIAN_ROOTFS_INCLUDE_PACKAGES
939        string "Additional packages"
940        default "debian/rootfs/include_packages.list"
941        help
942          Specify the file name of the list of additional packages
943          to install in the Debian rootfs.
944          .
945          The default file is fine.
946          You may use as a start for your own list
947          of additional packages.
948
949endmenu
950
951source "config/debian_release.in"
952
953config OPENWRT_DOWNLOAD_DIR
954        string "Alternate OpenWrt download directory"
955        help
956          When checking out and building multiple revisions of OpenWrt it
957          comes in handy to not download all required external sources over
958          and over again, but save them in one directory. If this directory
959          exists, during checkout, a symlink will be created to it from
960          the build directory of the checked out revision.  Be aware that
961          if you use a relative directory here, it must be relative to
962          "build/openwrt-<board>-<revision>-<kernel>" and not to "."
963
964config OPENWRT_MAKE_OPTIONS
965        string "OpenWrt make command line options"
966    default "-j 3"
967    help
968      Add make command line options to OpenWrt
969
970# End of file
Note: See TracBrowser for help on using the repository browser.