source: branches/contrib/Config.in @ 346

Last change on this file since 346 was 346, checked in by ehem, 10 years ago

Straighten out $(OPENWRT_REVISION), now $(OPENWRT_REVISION) is *strictly*
the revision (for svn's -r option). Whereas $(OPENWRT_BRANCH) specifies
which branch of OpenWRT's tree to use.

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