source: debwrt/trunk/Config.in @ 54

Last change on this file since 54 was 54, checked in by amain, 9 years ago

Make debwrt-kernel-headers auto use compiled openwrt kernel-headers or if not the default in the svn repo

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