Changeset 517 for trunk/Config.in


Ignore:
Timestamp:
Jun 26, 2013, 11:25:44 PM (6 years ago)
Author:
amain
Message:

Merge contrib branch 340:516. Main features added:

  • updated plugin architecture
  • improved patch system
  • bitten continous integration support
  • sever build fixed over time to remain in sync with OpenWrt
Location:
trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk

  • trunk/Config.in

    r328 r517  
    11# DebWrt - Debian on Embedded devices
    22#
    3 # Copyright (C) 2010 Johan van Zoomeren <amain@debwrt.net>
     3# Copyright (C) 2012 Johan van Zoomeren <amain@debwrt.net>
    44#
    55# This program is free software: you can redistribute it and/or modify
     
    2525        bool
    2626
     27config DO_CONF_TARGETS
     28        bool
     29        default y
     30
     31config DO_CONF_OPENWRT_REVISON
     32        bool
     33        default y
     34
     35config ALT_TARGET
     36        bool
     37        default n
     38
     39#config DO_CONF_FLASH_IP
     40#       bool
     41#       default y
     42
     43#config DO_CONF_TARGET_IMAGE_NAME_TRX
     44#       bool
     45#       default y
     46
    2747mainmenu "DebWrt Configuration"
    2848
    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
     49source "config/plugin.in"
    8150
    8251source "config/archs.in"
    83 source "config/config-target.in"
     52source "config/target.in"
    8453
    85 #source "config/board.in"
    86 #source "config/sub_board.in"
    8754source "config/image_name.in"
    8855source "config/flash_ip.in"
    8956
    90 choice
    91         prompt "OpenWrt Revision"
    92         default OPENWRT_REVISION_TRUNK
    93 
    94 config OPENWRT_REVISION_TRUNK
    95         bool "trunk"
    96 
    97 config OPENWRT_REVISION_BACKFIRE
    98         bool "backfire ( not tested recently )"
    99 
    100 endchoice
    101 
    102 source "config/openwrt_revision.in"
    103 
    104 choice
    105         prompt "Kernel Version"
    106         default DEBWRT_KERNEL_DEFAULT
    107         help
    108           Select the linux kernel version you want to use with DebWrt
    109 
    110 config 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 
    130 endchoice
     57source "config/openwrt_version.in"
     58source "config/openwrt_extra.in"
    13159
    13260source "config/kernel_version.in"
     61source "config/kernel_config.in"
    13362
     63source "config/debian_cross.in"
     64source "config/debian_rootfs.in"
    13465
    135 menu "Kernel Configuration"
    136 
    137 # note: DMA Engine support
    138 # note: SDIO support
    139 #
    140 
    141 menu "General configuration"
    142 
    143 #CONFIG_MIPS_FPU_EMU=y
    144 config 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 
    154 config 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 
    171 config 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
    186 config 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 
    193 endmenu
    194 
    195 menu "IDE Configuration"
    196 
    197 #CONFIG_IDEPCI_PCIBUS_ORDER=y
    198 config IDEPCI_PCIBUS_ORDER
    199     bool
    200     default y
    201 
    202 #CONFIG_IDE_XFER_MODE=y
    203 config IDE_XFER_MODE
    204     bool
    205     default y
    206 
    207 #CONFIG_BLK_DEV_IDEDMA_SFF=y
    208 config BLK_DEV_IDEDMA_SFF
    209     bool
    210     default y
    211 
    212 #CONFIG_BLK_DEV_IDEPCI=y
    213 config BLK_DEV_IDEPCI
    214     bool
    215     default y
    216 
    217 #CONFIG_BLK_DEV_IDEDMA_PCI=y
    218 config BLK_DEV_IDEDMA_PCI
    219     bool
    220     default y
    221 
    222 #CONFIG_BLK_DEV_IDEDMA=y
    223 config BLK_DEV_IDEDMA
    224     bool
    225     default y
    226 
    227 # make kernel compile not stop:
    228 config IDE_GD_ATAPI
    229         bool
    230         default n
    231 
    232 #CONFIG_IDE=y
    233 config 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
    254 config 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
    266 config 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
    276 config 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
    288 config 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 
    310 endmenu
    311 
    312 menu "SCSI configuration"
    313 
    314 #CONFIG_SCSI=y
    315 config SCSI
    316         tristate "SCSI device support"
    317         default y
    318         help
    319           SCSI device support
    320 
    321 #CONFIG_SCSI_DMA=y
    322 config SCSI_DMA
    323         bool
    324         prompt "Enable DMA for SCSI" if SCSI
    325         default y
    326  
    327 #CONFIG_SCSI_PROC_FS=y
    328 config 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
    338 config 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
    351 config 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 
    373 endmenu
    374 
    375 menu "USB configuration"
    376 
    377 #CONFIG_USB=y
    378 config 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 
    385 config 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
    395 config 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
    411 config 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
    438 config 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
    462 config 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
    475 config 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
    499 config 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
    518 config 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
    536 config 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
    544 config 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  
    551 config 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
    565 config 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 
    584 endmenu
    585 
    586 menu "Filesystem support"
    587 
    588 config 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 
    619 config 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 
    638 config 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 
    651 config 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 
    664 config 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 
    676 config FS_POSIX_ACL
    677         bool
    678         default y
    679 
    680 #CONFIG_JBD=y
    681 config 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
    697 config 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 
    705 endmenu 
    706  
    707 menu "OpenWrt Kernel Module Packages"
    708 
    709 menu "Wireless Kernel Modules"
    710 
    711 config 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 
    719 config 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 
    727 config 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 
    734 config 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 config PACKAGE_kmod-b43legacy
    742         bool "kmod-b43legacy..................... Broadcom 43xx-legacy wireless support"
    743         default y
    744     help
    745       Kernel module for Broadcom 43xx-legacy wireless support (mac80211 stack) new
    746       http://linuxwireless.org/en/users/Drivers/b43
    747 
    748 config PACKAGE_kmod-rt2500-pci
    749         bool "kmod-rt2500-pci............. Ralink Drivers for RT2x00 cards (RT2500 PCI)"
    750         default y
    751         help
    752       Ralink Drivers for RT2x00 cards (RT2500 PCI)
    753       http://linuxwireless.org/
    754 
    755 config PACKAGE_kmod-rt2500-usb
    756         bool "kmod-rt2500-usb............. Ralink Drivers for RT2x00 cards (RT2500 USB)"
    757         default y
    758         help
    759         Ralink Drivers for RT2x00 cards (RT2500 USB)
    760         http://linuxwireless.org/
    761 
    762 endmenu
    763  
    764 endmenu
    765 
    766 config NETCONSOLE
    767         bool "Network console logging support (EXPERIMENTAL)"
    768         default y
    769         ---help---
    770         If you want to log kernel messages over the network, enable this.
    771         See <file:Documentation/networking/netconsole.txt> for details.
    772 
    773 config NETCONSOLE_DYNAMIC
    774         bool
    775         default n
    776 
    777 config NETPOLL_TRAP
    778         bool
    779         default n
    780 
    781 endmenu
    782 
    783 menu "Debian Cross-Compile Environment Configuration"
    784        
    785 config DEBIAN_BUILDENV_REPOSITORY
    786         string "Debian Repository"
    787         default "http://ftp.debian.org/debian"
    788         help
    789           Specify the Debian Repository used to set up de Debian Cross-Compile chroot
    790           environment and used to install Debian chroot for the target architecture.
    791 
    792 config EMDEBIAN_BUILDENV_REPOSITORY
    793         string "Emdebian Repository"
    794         default "http://www.emdebian.org/debian"
    795         help
    796           Specify the Debian Repository used to set up de Debian Cross-Compile chroot
    797           environment and used to install Debian chroot for the target architecture.
    798 
    799 config DEBIAN_BUILDENV_INCLUDE_PACKAGES
    800         string "Additional packages"
    801         default "file,less,strace,sudo"
    802         help
    803           Specify a comma seperated list of additional packages to install in the
    804           Debian cross-compile environment. The cross compile environment is a
    805           debootstrapped chrooted Debian sid installation.
    806 
    807 config DEBIAN_BUILDENV_QEMU_VERSION
    808         string "Qemu version"
    809         default "0.15.0-rc0"
    810         help
    811           At least 0.12.2 is needed for mips targets.
    812 
    813 endmenu
    814 
    815 menu "Debian Root Filesystem Configuration"
    816 
    817 choice
    818     prompt "DebWrt Debian Release"
    819         default DEBWRT_DEBIAN_RELEASE_SQUEEZE
    820         help
    821           Select the the Debian release for the root filesystem. Also sets the build environment release.
    822 
    823 config DEBWRT_DEBIAN_RELEASE_SID
    824     bool
    825     prompt "Sid"
    826 
    827 config DEBWRT_DEBIAN_RELEASE_WHEEZY
    828     bool
    829     prompt "Wheezy"
    830 
    831 config DEBWRT_DEBIAN_RELEASE_SQUEEZE
    832     bool
    833     prompt "Squeeze"
    834 
    835 config DEBWRT_DEBIAN_RELEASE_LENNY
    836     bool
    837     prompt "Lenny"
    838 
    839 endchoice
    840 
    841 config DEBIAN_ROOTFS_INCLUDE_PACKAGES
    842         string "Additional packages"
    843         default "debian/rootfs/include_packages.list"
    844         help
    845           Specify the file name of the list of additional packages
    846           to install in the Debian rootfs.
    847           .
    848           The default file is fine.
    849           You may use as a start for your own list
    850           of additional packages.
    851 
    852 config DEBIAN_ROOTFS_QEMU_2ND_STAGE
    853         bool "Use qemu to perform Debian second stage install on the host"
    854         default y
    855         help
    856       Use qemu to perform Debian root fs second stage install on the host. This
    857       eliminates the need to do the second stage install on the target device. Using
    858       qemu is much faster and easier then doing 2nd stage on the target device.
    859 
    860 endmenu
    861 
    862 
    863 menu "DebWrt boot options"
    864 
    865 choice
    866     prompt "Boot method"
    867         default BOOT_METHOD_SCRIPT
    868         help
    869           Select how DebWrt should boot
    870 
    871 config BOOT_METHOD_SCRIPT
    872         bool "Use DebWrt boot script"
    873         help
    874           Auto discover root device, optionally kexec to a alternate kernel and boot from this device.
    875           .
    876           Normally DebWrt boots directly from the root= device. With this option enabled, DebWrt boots initially
    877           from /dev/mtdblock2 and runs an alternate boot script (/etc/preinit). This scripts discovers block
    878           devices and will look for a device with a label of DEBWRT_ROOT or fall back to /dev/sda1. And mounts it.
    879           .
    880           Next it will kexec to /boot/vmlinux.elf if it exits on the DEBWRT_ROOT device.
    881           .
    882           After mounting ( or kexec ), a pivot_root to the DEBWRT_ROOT device is done and /sbin/init is executed.
    883 
    884 config BOOT_METHOD_DEVICE
    885         bool "Directly boot from device /dev/sda1"
    886 
    887 endchoice
    888 
    889 config CMDLINE_BOOL
    890         bool
    891         default y
    892         depends BOOT_METHOD_DEVICE
    893 
    894 #CONFIG_CMDLINE="root=/dev/sda1 init=/sbin/init rootdelay=10 noinitrd console=ttyS0,115200"
    895 # default "root=/dev/sda1 init=/sbin/init rootdelay=15 noinitrd console=ttyS0,115200"
    896 # 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"
    897 # TODO: use patch-kernel script to append only netconsole=6665@192.168.1.1/eth0,6666@192.168.1.2/ to OpenWrt default cmdline"
    898 #       for now netconsole can't be set when BOOT_METHOD_SCRIPT
    899 config CMDLINE
    900         string "Default kernel command line"
    901         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/"
    902         depends BOOT_METHOD_DEVICE
    903         help
    904           Override OpenWrt default kernel command line. Tell the kernel to boot from /dev/sda1,
    905           an USB storage device. Rootdelay is specified, to give the USB storage/SCSI driver
    906           to become ready, before the kernel tries to boot from it.
    907 
    908 source "config/kexec.in"
    909 
    910 endmenu
    911 
    912 
    913 
    914 
    915 source "config/debian_release.in"
    916 
    917 config OPENWRT_DOWNLOAD_DIR
    918         string "Alternate OpenWrt download directory"
    919         help
    920           When checking out and building multiple revisions of OpenWrt it
    921           comes in handy to not download all required external sources over
    922           and over again, but save them in one directory. If this directory
    923           exists, during checkout, a symlink will be created to it from
    924           the build directory of the checked out revision.  Be aware that
    925           if you use a relative directory here, it must be relative to
    926           "build/openwrt-<board>-<revision>-<kernel>" and not to "."
    927 
    928 config OPENWRT_MAKE_OPTIONS
    929         string "OpenWrt make command line options"
    930     default ""
    931     help
    932       Add make command line options to OpenWrt. For example -j 3. Note -j does
    933       not seem to work for OpenWrt.
     66source "config/debwrt_general.in"
     67source "config/debwrt_boot.in"
    93468
    93569# End of file
Note: See TracChangeset for help on using the changeset viewer.