diff options
Diffstat (limited to 'target/linux/config/Config.in.block')
| -rw-r--r-- | target/linux/config/Config.in.block | 1034 |
1 files changed, 751 insertions, 283 deletions
diff --git a/target/linux/config/Config.in.block b/target/linux/config/Config.in.block index 87fce5e8e..8ccb10e72 100644 --- a/target/linux/config/Config.in.block +++ b/target/linux/config/Config.in.block @@ -1,256 +1,674 @@ -config ADK_KERNEL_BLOCK - boolean +# This file is part of the OpenADK project. OpenADK is copyrighted +# material, please see the LICENCE file in the top-level directory. -config ADK_KERNEL_MD - boolean +config ADK_LINUX_KERNEL_BLOCK + bool + select ADK_LINUX_KERNEL_AIO + select ADK_LINUX_KERNEL_INOTIFY_USER +config ADK_LINUX_KERNEL_AIO + bool -config ADK_KERNEL_LBD - boolean +menu "Block devices support" +depends on ADK_TARGET_WITH_BLOCK \ + || ADK_TARGET_QEMU \ + || ADK_TARGET_GENERIC -config ADK_KERNEL_BLK_DEV_IO_TRACE - boolean +config ADK_LINUX_KERNEL_IOSCHED_DEADLINE + bool -config ADK_KERNEL_LSF - boolean +config ADK_LINUX_KERNEL_IOSCHED_CFQ + bool -config ADK_KERNEL_IOSCHED_AS - boolean +config ADK_LINUX_KERNEL_IOSCHED_NOOP + bool -config ADK_KERNEL_IOSCHED_DEADLINE - boolean +choice +prompt "I/O scheduler" -config ADK_KERNEL_IOSCHED_CFQ - boolean +config ADK_LINUX_KERNEL_DEFAULT_DEADLINE + bool "deadline" + select ADK_LINUX_KERNEL_IOSCHED_DEADLINE -config ADK_KERNEL_SCSI - boolean +config ADK_LINUX_KERNEL_DEFAULT_CFQ + bool "cfq" + select ADK_LINUX_KERNEL_IOSCHED_CFQ -config ADK_KERNEL_BLK_DEV_SD - boolean +config ADK_LINUX_KERNEL_DEFAULT_NOOP + bool "noop" + select ADK_LINUX_KERNEL_IOSCHED_NOOP -config ADK_KERNEL_ISCSI_TCP - boolean +endchoice -config ADK_KERNEL_DM_CRYPT - boolean +config ADK_LINUX_KERNEL_IDE + bool -config ADK_KERNEL_BLK_DEV - boolean +config ADK_LINUX_KERNEL_IDE_GD + bool -config ADK_KERNEL_BLK_DEV_DM - boolean - select ADK_KERNEL_MD +config ADK_LINUX_KERNEL_IDE_GD_ATA + bool -config ADK_KERNEL_ATA - boolean +config ADK_LINUX_KERNEL_LBDAF + bool -config ADK_KERNEL_ATA_SFF - boolean +config ADK_LINUX_KERNEL_BLK_DEV_BSG + bool -config ADK_KERNEL_ATA_BMDMA - boolean +config ADK_LINUX_KERNEL_BLK_DEV_BSGLIB + bool -config ADK_KERNEL_CONNECTOR - boolean +config ADK_LINUX_KERNEL_BLK_DEV_THROTTLING + bool -config ADK_KERNEL_MMC - boolean +config ADK_LINUX_KERNEL_MD + bool -config ADK_KERNEL_MMC_BLOCK - boolean +config ADK_LINUX_KERNEL_RAID6_PQ + tristate -config ADK_KERNEL_SCSI_SYM53C8XX_2 - boolean +config ADK_LINUX_KERNEL_BLK_DEV_IO_TRACE + bool -config ADK_KERNEL_PATA_PCMCIA - boolean +config ADK_LINUX_KERNEL_IOSCHED_AS + bool -config ADK_KERNEL_PATA_PXA - boolean - select ADK_KERNEL_BLOCK - select ADK_KERNEL_SCSI - select ADK_KERNEL_ATA - select ADK_KERNEL_ATA_SFF - select ADK_KERNEL_ATA_BMDMA - select ADK_KERNEL_BLK_DEV - select ADK_KERNEL_BLK_DEV_SD - select ADK_KERNEL_PATA_PCMCIA - default y if ADK_TARGET_SYSTEM_SHARP_ZAURUS - default n +config ADK_LINUX_KERNEL_IOSCHED_DEADLINE + bool -config ADK_KERNEL_MMC_AT91 - boolean - select ADK_KERNEL_BLOCK - select ADK_KERNEL_SCSI - select ADK_KERNEL_MMC - select ADK_KERNEL_MMC_BLOCK - select ADK_KERNEL_BLK_DEV - select ADK_KERNEL_BLK_DEV_SD - default y if ADK_TARGET_SYSTEM_ACMESYSTEMS_FOXG20 - default n +config ADK_LINUX_KERNEL_IOSCHED_CFQ + bool + +config ADK_LINUX_KERNEL_SCSI_LOWLEVEL + bool + +config ADK_LINUX_KERNEL_SCSI_DMA + bool + +config ADK_LINUX_KERNEL_SCSI_MULTI_LUN + bool + +config ADK_LINUX_KERNEL_SCSI_CONSTANTS + bool + +config ADK_LINUX_KERNEL_SCSI_LOGGING + bool + +config ADK_LINUX_KERNEL_SCSI_SCAN_ASYNC + bool + +config ADK_LINUX_KERNEL_ISCSI_TCP + bool + +config ADK_LINUX_KERNEL_BLK_DEV + bool + +config ADK_LINUX_KERNEL_ATA + bool + +config ADK_LINUX_KERNEL_ATA_SFF + bool + +config ADK_LINUX_KERNEL_ATA_BMDMA + bool + +config ADK_LINUX_KERNEL_SATA_AHCI_PLATFORM + bool + +config ADK_LINUX_KERNEL_SATA_PMP + bool + +config ADK_LINUX_KERNEL_AHCI_IMX + bool + +config ADK_LINUX_KERNEL_CONNECTOR + bool + +config ADK_LINUX_KERNEL_MMC + bool + +config ADK_LINUX_KERNEL_MMC_SPI + bool + +config ADK_LINUX_KERNEL_MMC_BLOCK + bool + +config ADK_LINUX_KERNEL_MMC_BLOCK_BOUNCE + bool + +config ADK_LINUX_KERNEL_MMC_UNSAFE_RESUME + bool + +config ADK_LINUX_KERNEL_MMC_SDHCI + bool + +config ADK_LINUX_KERNEL_MMC_SDHCI_IO_ACCESSORS + bool -config ADK_KERNEL_PATA_RB532 - boolean - select ADK_KERNEL_BLOCK - select ADK_KERNEL_SCSI - select ADK_KERNEL_ATA - select ADK_KERNEL_ATA_SFF - select ADK_KERNEL_ATA_BMDMA - select ADK_KERNEL_BLK_DEV - select ADK_KERNEL_BLK_DEV_SD +config ADK_LINUX_KERNEL_MMC_SDHCI_PLTFM + bool + +config ADK_LINUX_KERNEL_MMC_SDHCI_IPROC + bool + +config ADK_LINUX_KERNEL_MMC_SDHCI_BRCMSTB + bool + +config ADK_LINUX_KERNEL_MMC_SDHCI_DOVE + bool + +config ADK_LINUX_KERNEL_MMC_SDHCI_PXAV3 + bool + +config ADK_LINUX_KERNEL_MMC_BCM2835_MMC + bool + +config ADK_LINUX_KERNEL_MMC_BCM2835_DMA + bool + +config ADK_LINUX_KERNEL_MMC_BCM2835_SDHOST + bool + +config ADK_LINUX_KERNEL_MMC_DW + bool + +config ADK_LINUX_KERNEL_MMC_DW_PLTFM + bool + +config ADK_LINUX_KERNEL_PWRSEQ_EMMC + bool + +config ADK_LINUX_KERNEL_PWRSEQ_SIMPLE + bool + +config ADK_LINUX_KERNEL_BOARD_GRASSHOPPER_MMC + bool + +config ADK_LINUX_KERNEL_BOARD_GRASSHOPPER_MMCLED + bool + +menu "SATA/PATA devices support" +depends on ADK_TARGET_WITH_PATA \ + || ADK_TARGET_WITH_SATA \ + || ADK_TARGET_QEMU \ + || ADK_TARGET_GENERIC + +config ADK_LINUX_KERNEL_PATA_RB532 + tristate "CF disk driver for Mikrotik RB532" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_ATA + select ADK_LINUX_KERNEL_ATA_SFF + select ADK_LINUX_KERNEL_ATA_BMDMA + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on ADK_TARGET_SYSTEM_MIKROTIK_RB532 default y if ADK_TARGET_SYSTEM_MIKROTIK_RB532 default n -config ADK_KERNEL_PATA_AMD - boolean - select ADK_KERNEL_BLOCK - select ADK_KERNEL_SCSI - select ADK_KERNEL_ATA - select ADK_KERNEL_ATA_SFF - select ADK_KERNEL_ATA_BMDMA - select ADK_KERNEL_BLK_DEV - select ADK_KERNEL_BLK_DEV_SD - default y if ADK_TARGET_SYSTEM_PCENGINES_ALIX2D2 - default y if ADK_TARGET_SYSTEM_PCENGINES_ALIX2D13 - default y if ADK_TARGET_SYSTEM_PCENGINES_ALIX1C +config ADK_LINUX_KERNEL_PATA_AMD + tristate "AMD PATA driver" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_ATA + select ADK_LINUX_KERNEL_ATA_SFF + select ADK_LINUX_KERNEL_ATA_BMDMA + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on ADK_TARGET_SYSTEM_PCENGINES_ALIX \ + || ADK_TARGET_SYSTEM_LEMOTE_YEELONG \ + || ADK_TARGET_GENERIC + default y if ADK_TARGET_SYSTEM_PCENGINES_ALIX default y if ADK_TARGET_SYSTEM_LEMOTE_YEELONG default n -config ADK_KERNEL_PATA_SC1200 - boolean - select ADK_KERNEL_BLOCK - select ADK_KERNEL_SCSI - select ADK_KERNEL_ATA - select ADK_KERNEL_ATA_SFF - select ADK_KERNEL_ATA_BMDMA - select ADK_KERNEL_BLK_DEV - select ADK_KERNEL_BLK_DEV_SD +config ADK_LINUX_KERNEL_PATA_SC1200 + tristate + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_ATA + select ADK_LINUX_KERNEL_ATA_SFF + select ADK_LINUX_KERNEL_ATA_BMDMA + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on ADK_TARGET_SYSTEM_PCENGINES_WRAP default y if ADK_TARGET_SYSTEM_PCENGINES_WRAP default n -config ADK_KERNEL_ATA_PIIX - boolean - select ADK_KERNEL_BLOCK - select ADK_KERNEL_SCSI - select ADK_KERNEL_ATA - select ADK_KERNEL_ATA_SFF - select ADK_KERNEL_ATA_BMDMA - select ADK_KERNEL_BLK_DEV - select ADK_KERNEL_BLK_DEV_SD - default y if ADK_TARGET_SYSTEM_QEMU_I686 - default y if ADK_TARGET_SYSTEM_QEMU_MIPS - default y if ADK_TARGET_SYSTEM_QEMU_MIPSEL - default y if ADK_TARGET_SYSTEM_QEMU_PPC - default y if ADK_TARGET_SYSTEM_QEMU_SPARC - default y if ADK_TARGET_SYSTEM_QEMU_X86_64 - default y if ADK_TARGET_SYSTEM_IBM_X40 - default y if ADK_NATIVE_SYSTEM_IBM_X40 - default y if ADK_TARGET_SYSTEM_INTEL_ATOM - default y if ADK_NATIVE_SYSTEM_INTEL_ATOM +config ADK_LINUX_KERNEL_SATA_AHCI + tristate "AHCI SATA driver" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_ATA + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on \ + ADK_TARGET_SYSTEM_PCENGINES_APU || \ + ADK_TARGET_GENERIC + default y if ADK_TARGET_SYSTEM_PCENGINES_APU default n + help + Enables support for AHCI Serial ATA. -config ADK_KERNEL_SATA_AHCI - tristate - select ADK_KERNEL_BLOCK - select ADK_KERNEL_SCSI - select ADK_KERNEL_ATA - select ADK_KERNEL_BLK_DEV - select ADK_KERNEL_BLK_DEV_SD - depends on ADK_TARGET_WITH_SATA - default y if ADK_TARGET_SYSTEM_SHUTTLE_SA76 - default n - -menu "Block devices support" - -config ADK_KPACKAGE_KMOD_SATA_AHCI - prompt "kmod-sata-ahci.................... AHCI SATA driver" - tristate - select ADK_KERNEL_BLOCK - select ADK_KERNEL_ATA - select ADK_KERNEL_BLK_DEV_SD - depends on !ADK_KERNEL_SATA_AHCI - depends on ADK_TARGET_WITH_SATA - default y if ADK_TARGET_SYSTEM_INTEL_ATOM - default y if ADK_NATIVE_SYSTEM_INTEL_ATOM +config ADK_LINUX_KERNEL_ATA_PIIX + tristate "ATA PIIX support" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_SCSI_DMA + select ADK_LINUX_KERNEL_ATA + select ADK_LINUX_KERNEL_ATA_SFF + select ADK_LINUX_KERNEL_ATA_BMDMA + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on \ + ADK_TARGET_GENERIC || \ + ADK_TARGET_SYSTEM_QEMU_MIPS || \ + ADK_TARGET_SYSTEM_QEMU_MIPS64 || \ + ADK_TARGET_SYSTEM_QEMU_X86 || \ + ADK_TARGET_SYSTEM_QEMU_X86_64 default n help - Enables support for AHCI Serial ATA. + ATA PIIX driver. + +config ADK_LINUX_KERNEL_PATA_MACIO + tristate "MAC IO support" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_ATA + select ADK_LINUX_KERNEL_ATA_SFF + select ADK_LINUX_KERNEL_ATA_BMDMA + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on ADK_TARGET_SYSTEM_QEMU_PPC_MACPPC + +config ADK_LINUX_KERNEL_PATA_PLATFORM + tristate "PATA platform driver" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_ATA + select ADK_LINUX_KERNEL_ATA_SFF + select ADK_LINUX_KERNEL_ATA_BMDMA + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on ADK_TARGET_SYSTEM_QEMU_SH + default n -config ADK_KPACKAGE_KMOD_BLK_DEV_LOOP - prompt "kmod-blk-dev-loop................. Loop mount support" +config ADK_LINUX_KERNEL_PATA_PCMCIA tristate - select ADK_KERNEL_BLOCK - select ADK_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_PCCARD + select ADK_LINUX_KERNEL_PCMCIA + +config ADK_LINUX_KERNEL_PATA_IMX + tristate "eSATA driver for IMX6 boards" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_ATA + select ADK_LINUX_KERNEL_ATA_SFF + select ADK_LINUX_KERNEL_ATA_BMDMA + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + select ADK_LINUX_KERNEL_ATA + select ADK_LINUX_KERNEL_AHCI_IMX + select ADK_LINUX_KERNEL_SATA_PMP + select ADK_LINUX_KERNEL_SATA_AHCI_PLATFORM + depends on ADK_TARGET_SYSTEM_SOLIDRUN_IMX6 || \ + ADK_TARGET_SYSTEM_PHYTEC_IMX6 + default y if ADK_TARGET_SYSTEM_SOLIDRUN_IMX6 || \ + ADK_TARGET_SYSTEM_PHYTEC_IMX6 default n help - Saying Y here will allow you to use a regular file as a block - device; you can then create a file system on that block device and - mount it just as you would mount other block devices such as hard - drive partitions, CD-ROM drives or floppy drives. The loop devices - are block special device files with major number 7 and typically - called /dev/loop0, /dev/loop1 etc. + eSATA driver for IMX6 boards. + +config ADK_LINUX_KERNEL_PATA_CMD64X + tristate "CMD64x PATA driver" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_ATA + select ADK_LINUX_KERNEL_ATA_SFF + select ADK_LINUX_KERNEL_ATA_BMDMA + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on ADK_TARGET_SYSTEM_QEMU_SPARC64 + help + Driver for CMD64x chipsets. + +config ADK_LINUX_KERNEL_PATA_PXA + tristate "PATA driver for Sharp Zaurus" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_ATA + select ADK_LINUX_KERNEL_ATA_SFF + select ADK_LINUX_KERNEL_ATA_BMDMA + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + select ADK_LINUX_KERNEL_PATA_PCMCIA + select ADK_LINUX_KERNEL_PCMCIA_PXA2XX + depends on ADK_TARGET_SYSTEM_SHARP_ZAURUS \ + || ADK_TARGET_SYSTEM_QEMU_ARM_TERRIER \ + || ADK_TARGET_SYSTEM_QEMU_ARM_SPITZ + default y if ADK_TARGET_SYSTEM_SHARP_ZAURUS + default n + help + Driver for PATA on Sharp Zaurus - This is useful if you want to check an ISO 9660 file system before - burning the CD, or if you want to use floppy images without first - writing them to floppy. Furthermore, some Linux distributions avoid - the need for a dedicated Linux partition by keeping their complete - root file system inside a DOS FAT file using this loop device - driver. +endmenu - To use the loop device, you need the losetup utility, found in the - util-linux package, see - <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>. +menu "IDE driver support" +depends on ADK_TARGET_SYSTEM_QEMU_ALPHA - The loop device driver can also be used to "hide" a file system in - a disk partition, floppy, or regular file, either using encryption - (scrambling the data) or steganography (hiding the data in the low - bits of, say, a sound file). This is also safe if the file resides - on a remote file server. +config ADK_LINUX_KERNEL_BLK_DEV_CMD64X + tristate "CMD64x support" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_IDE + select ADK_LINUX_KERNEL_IDE_GD + select ADK_LINUX_KERNEL_IDE_GD_ATA + depends on ADK_TARGET_SYSTEM_QEMU_ALPHA + help + CMD64x IDE driver. - There are several ways of encrypting disks. Some of these require - kernel patches. The vanilla kernel offers the cryptoloop option - and a Device Mapper target (which is superior, as it supports all - file systems). If you want to use the cryptoloop, say Y to both - LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12 - or later) version of util-linux. Additionally, be aware that - the cryptoloop is not safe for storing journaled filesystems. +endmenu - Note that this loop device has nothing to do with the loopback - device used for network connections from the machine to itself. +menu "SCSI driver support" +depends on ADK_TARGET_WITH_SCSI || \ + ADK_TARGET_SYSTEM_QEMU_ARM_VERSATILEPB || \ + ADK_TARGET_SYSTEM_QEMU_M68K_Q800 || \ + ADK_TARGET_SYSTEM_QEMU_PPC64 || \ + ADK_TARGET_SYSTEM_QEMU_SPARC + +config ADK_LINUX_KERNEL_SCSI_AIC7XXX + tristate "Adaptec AIC-7XXX support" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_SCSI_LOWLEVEL + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + +config ADK_LINUX_KERNEL_SCSI_SYM53C8XX_2 + tristate "Symbios Logic 53C8XX2 support" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_SCSI_LOWLEVEL + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on ADK_TARGET_SYSTEM_QEMU_ARM_VERSATILEPB + +config ADK_LINUX_KERNEL_SCSI_IBMVSCSI + tristate "IBM VSCSI support" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_SCSI_LOWLEVEL + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on ADK_TARGET_SYSTEM_QEMU_PPC64 + +config ADK_LINUX_KERNEL_SCSI_MAC_ESP + tristate "MAC ESP support" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_SCSI_LOWLEVEL + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on ADK_TARGET_SYSTEM_QEMU_M68K_Q800 + +config ADK_LINUX_KERNEL_SCSI_SUNESP + tristate "SUN ESP support" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_SCSI_LOWLEVEL + select ADK_LINUX_KERNEL_SBUS + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on ADK_TARGET_SYSTEM_QEMU_SPARC + +endmenu + +menu "SD/MMC driver support" +depends on ADK_TARGET_WITH_SD || ADK_TARGET_QEMU + +config ADK_LINUX_KERNEL_MMC_ARMMMCI + bool "SD card support for Qemu ARM Vexpress A9" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_MMC + select ADK_LINUX_KERNEL_MMC_BLOCK + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on ADK_TARGET_SYSTEM_QEMU_ARM_VEXPRESS_A9 + default n -config ADK_KPACKAGE_KMOD_BLK_DEV_NBD - prompt "kmod-blk-dev-nbd.................. Network Block Device" +config ADK_LINUX_KERNEL_MMC_AT91 tristate + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_MMC + select ADK_LINUX_KERNEL_MMC_BLOCK + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + depends on ADK_TARGET_SYSTEM_ACMESYSTEMS_FOXG20 + default y if ADK_TARGET_SYSTEM_ACMESYSTEMS_FOXG20 default n - help - Saying Y here will allow your computer to be a client for network - block devices, i.e. it will be able to use block devices exported by - servers (mount file systems on them etc.). Communication between - client and server works over TCP/IP networking, but to the client - program this is hidden: it looks like a regular local file access to - a block device special file such as /dev/nd0. - Network block devices also allows you to run a block-device in - userland (making server and client physically the same computer, - communicating using the loopback network device). +config ADK_LINUX_KERNEL_MMC_BCM2835_MMC + bool "SD card support for BCM28XX boards" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_MMC + select ADK_LINUX_KERNEL_MMC_SPI + select ADK_LINUX_KERNEL_MMC_BLOCK + select ADK_LINUX_KERNEL_MMC_BLOCK_BOUNCE + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + select ADK_LINUX_KERNEL_BLK_DEV_BSG + select ADK_LINUX_KERNEL_BLK_DEV_BSGLIB + select ADK_LINUX_KERNEL_BLK_DEV_THROTTLING + select ADK_LINUX_KERNEL_MMC_SDHCI + select ADK_LINUX_KERNEL_MMC_SDHCI_PLTFM + select ADK_LINUX_KERNEL_MMC_SDHCI_IPROC + select ADK_LINUX_KERNEL_MMC_SDHCI_BRCMSTB if ADK_TARGET_SYSTEM_RASPBERRY_PI5 + select ADK_LINUX_KERNEL_MMC_BCM2835_DMA + select ADK_LINUX_KERNEL_MMC_BCM2835_SDHOST + depends on ADK_TARGET_BOARD_BCM28XX + default y if ADK_TARGET_BOARD_BCM28XX + default n - Read <file:Documentation/nbd.txt> for more information, especially - about where to find the server code, which runs in user space and - does not need special kernel support. +config ADK_LINUX_KERNEL_MMC_DW + bool "SD card support for Synopsys HSDK board" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_MMC + select ADK_LINUX_KERNEL_MMC_SPI + select ADK_LINUX_KERNEL_MMC_BLOCK + select ADK_LINUX_KERNEL_MMC_DW_PLTFM + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + select ADK_LINUX_KERNEL_MMC_SDHCI + select ADK_LINUX_KERNEL_MMC_SDHCI_PLTFM + select ADK_LINUX_KERNEL_PWRSEQ_EMMC + select ADK_LINUX_KERNEL_PWRSEQ_SIMPLE + depends on ADK_TARGET_SYSTEM_SYNOPSYS_HSDK + default y if ADK_TARGET_SYSTEM_SYNOPSYS_HSDK + default n - Note that this has nothing to do with the network file systems NFS - or Coda; you can say N here even if you intend to use NFS or Coda. +config ADK_LINUX_KERNEL_MMC_MVSDIO + bool "SD card support for Solidrun Clearfog" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_SCSI_DMA + select ADK_LINUX_KERNEL_SCSI_MULTI_LUN + select ADK_LINUX_KERNEL_SCSI_CONSTANTS + select ADK_LINUX_KERNEL_SCSI_LOGGING + select ADK_LINUX_KERNEL_SCSI_SCAN_ASYNC + select ADK_LINUX_KERNEL_MMC + select ADK_LINUX_KERNEL_MMC_BLOCK + select ADK_LINUX_KERNEL_MMC_BLOCK_BOUNCE + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + select ADK_LINUX_KERNEL_BLK_DEV_BSG + select ADK_LINUX_KERNEL_BLK_DEV_BSGLIB + select ADK_LINUX_KERNEL_MMC_SDHCI + select ADK_LINUX_KERNEL_MMC_SDHCI_IO_ACCESSORS + select ADK_LINUX_KERNEL_MMC_SDHCI_PLTFM + select ADK_LINUX_KERNEL_MMC_SDHCI_DOVE + select ADK_LINUX_KERNEL_MMC_SDHCI_PXAV3 + select ADK_LINUX_KERNEL_MMC_UNSAFE_RESUME + depends on ADK_TARGET_SYSTEM_SOLIDRUN_CLEARFOG + default y if ADK_TARGET_SYSTEM_SOLIDRUN_CLEARFOG + default n -config ADK_KPACKAGE_KMOD_SCSI - prompt "kmod-scsi......................... SCSI support" - select ADK_KERNEL_LBD - select ADK_KERNEL_LSF - select ADK_KERNEL_IOSCHED_AS - depends on !ADK_KERNEL_SCSI - depends on !ADK_KERNEL_SATA_AHCI - depends on !ADK_KERNEL_ATA_PIIX - tristate +config ADK_LINUX_KERNEL_MMC_SDHCI_ESDHC_IMX + bool "SD card support for IMX6 boards" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_SCSI_DMA + select ADK_LINUX_KERNEL_SCSI_MULTI_LUN + select ADK_LINUX_KERNEL_SCSI_CONSTANTS + select ADK_LINUX_KERNEL_SCSI_LOGGING + select ADK_LINUX_KERNEL_SCSI_SCAN_ASYNC + select ADK_LINUX_KERNEL_MMC + select ADK_LINUX_KERNEL_MMC_BLOCK + select ADK_LINUX_KERNEL_MMC_BLOCK_BOUNCE + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + select ADK_LINUX_KERNEL_BLK_DEV_BSG + select ADK_LINUX_KERNEL_BLK_DEV_BSGLIB + select ADK_LINUX_KERNEL_MMC_SDHCI + select ADK_LINUX_KERNEL_MMC_SDHCI_IO_ACCESSORS + select ADK_LINUX_KERNEL_MMC_SDHCI_PLTFM + select ADK_LINUX_KERNEL_MMC_UNSAFE_RESUME + select ADK_LINUX_KERNEL_PWRSEQ_EMMC + select ADK_LINUX_KERNEL_PWRSEQ_SIMPLE + depends on ADK_TARGET_SYSTEM_SOLIDRUN_IMX6 || \ + ADK_TARGET_SYSTEM_PHYTEC_IMX6 + default y if ADK_TARGET_SYSTEM_SOLIDRUN_IMX6 || \ + ADK_TARGET_SYSTEM_PHYTEC_IMX6 + default n + +config ADK_LINUX_KERNEL_MMC_SUNXI + bool "SD card support for SUNXI boards" + select ADK_LINUX_KERNEL_REGULATOR_FIXED_VOLTAGE + select ADK_LINUX_KERNEL_REGULATOR_GPIO + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_SCSI_DMA + select ADK_LINUX_KERNEL_SCSI_MULTI_LUN + select ADK_LINUX_KERNEL_SCSI_CONSTANTS + select ADK_LINUX_KERNEL_SCSI_LOGGING + select ADK_LINUX_KERNEL_SCSI_SCAN_ASYNC + select ADK_LINUX_KERNEL_MMC + select ADK_LINUX_KERNEL_MMC_BLOCK + select ADK_LINUX_KERNEL_MMC_BLOCK_BOUNCE + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_BLK_DEV_SD + select ADK_LINUX_KERNEL_BLK_DEV_BSG + select ADK_LINUX_KERNEL_BLK_DEV_BSGLIB + select ADK_LINUX_KERNEL_MMC_SDHCI + select ADK_LINUX_KERNEL_MMC_SDHCI_IO_ACCESSORS + select ADK_LINUX_KERNEL_MMC_SDHCI_PLTFM + select ADK_LINUX_KERNEL_MMC_UNSAFE_RESUME + select ADK_LINUX_KERNEL_LBDAF + depends on ADK_TARGET_SYSTEM_BANANA_PRO || \ + ADK_TARGET_SYSTEM_ORANGE_PI0 + default y if ADK_TARGET_SYSTEM_BANANA_PRO + default y if ADK_TARGET_SYSTEM_ORANGE_PI0 + default n + +config ADK_LINUX_KERNEL_MMC_ATMELMCI + bool "Atmel SD/MMC Driver (Multimedia Card Interface)" + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_MMC + select ADK_LINUX_KERNEL_MMC_BLOCK + select ADK_LINUX_KERNEL_MMC_BLOCK_BOUNCE + select ADK_LINUX_KERNEL_MMC_SDHCI + select ADK_LINUX_KERNEL_MMC_SDHCI_IO_ACCESSORS + select ADK_LINUX_KERNEL_MMC_SDHCI_PLTFM + select ADK_LINUX_KERNEL_BOARD_GRASSHOPPER_MMC if ADK_TARGET_SYSTEM_GRASSHOPPER + select ADK_LINUX_KERNEL_BOARD_GRASSHOPPER_MMCLED if ADK_TARGET_SYSTEM_GRASSHOPPER + depends on ADK_TARGET_SYSTEM_GRASSHOPPER \ + || ADK_TARGET_SYSTEM_ATMEL_NGW100 + default y if ADK_TARGET_SYSTEM_GRASSHOPPER + default y if ADK_TARGET_SYSTEM_ATMEL_NGW100 + default n + help + Atmel Multimedia Card Interface driver for AT32 + and AT91 plattforms. + +config ADK_LINUX_KERNEL_MMC_DW_ROCKCHIP + bool "SD/MMC Driver (Rockchip)" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_SCSI_DMA + select ADK_LINUX_KERNEL_SCSI_MULTI_LUN + select ADK_LINUX_KERNEL_SCSI_CONSTANTS + select ADK_LINUX_KERNEL_SCSI_LOGGING + select ADK_LINUX_KERNEL_SCSI_SCAN_ASYNC + select ADK_LINUX_KERNEL_MMC + select ADK_LINUX_KERNEL_MMC_BLOCK + select ADK_LINUX_KERNEL_MMC_BLOCK_BOUNCE + select ADK_LINUX_KERNEL_MMC_SDHCI + select ADK_LINUX_KERNEL_MMC_SDHCI_IO_ACCESSORS + select ADK_LINUX_KERNEL_MMC_SDHCI_PLTFM + select ADK_LINUX_KERNEL_MMC_DW + select ADK_LINUX_KERNEL_MMC_DW_PLTFM + depends on ADK_TARGET_SYSTEM_ROCKPI4_PLUS + default y if ADK_TARGET_SYSTEM_ROCKPI4_PLUS + default n + help + RockPI 4 Plus driver for MMC + +config ADK_LINUX_KERNEL_MMC_DW_STARFIVE + bool "SD/MMC Driver (Starfive)" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_LBDAF + select ADK_LINUX_KERNEL_SCSI + select ADK_LINUX_KERNEL_SCSI_DMA + select ADK_LINUX_KERNEL_SCSI_MULTI_LUN + select ADK_LINUX_KERNEL_SCSI_CONSTANTS + select ADK_LINUX_KERNEL_SCSI_LOGGING + select ADK_LINUX_KERNEL_SCSI_SCAN_ASYNC + select ADK_LINUX_KERNEL_MMC + select ADK_LINUX_KERNEL_MMC_BLOCK + select ADK_LINUX_KERNEL_MMC_BLOCK_BOUNCE + select ADK_LINUX_KERNEL_MMC_SDHCI + select ADK_LINUX_KERNEL_MMC_SDHCI_IO_ACCESSORS + select ADK_LINUX_KERNEL_MMC_SDHCI_PLTFM + select ADK_LINUX_KERNEL_MMC_DW + select ADK_LINUX_KERNEL_MMC_DW_PLTFM + depends on ADK_TARGET_SYSTEM_STARFIVE_VISIONFIVE2 + default y if ADK_TARGET_SYSTEM_STARFIVE_VISIONFIVE2 + default n + help + Starfive Visionfive2 driver for MMC + +endmenu + +menu "Block driver support" + +config ADK_LINUX_KERNEL_SCSI + tristate "SCSI support" + select ADK_LINUX_KERNEL_IOSCHED_AS help If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or any other SCSI device under Linux, say Y and make sure that you know @@ -263,11 +681,9 @@ config ADK_KPACKAGE_KMOD_SCSI version of the IOMEGA ZIP drive, USB storage devices, Fibre Channel, FireWire storage and the IDE-SCSI emulation driver. -config ADK_KPACKAGE_KMOD_BLK_DEV_SD - prompt "kmod-scsi-disk.................... SCSI disk support" - select ADK_KPACKAGE_KMOD_SCSI - depends on !ADK_KERNEL_BLK_DEV_SD - tristate +config ADK_LINUX_KERNEL_BLK_DEV_SD + tristate "SCSI disk support" + select ADK_LINUX_KERNEL_SCSI help If you want to use SCSI hard disks, Fibre Channel disks, USB storage or the SCSI or parallel port version of @@ -276,68 +692,34 @@ config ADK_KPACKAGE_KMOD_BLK_DEV_SD <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI CD-ROMs. -config ADK_KPACKAGE_KMOD_BLK_DEV_SR - prompt "kmod-scsi-cdrom................... SCSI CDROM support" - depends on !ADK_KERNEL_SCSI - depends on ADK_KPACKAGE_KMOD_SCSI - tristate +config ADK_LINUX_KERNEL_BLK_DEV_SR + tristate "SCSI CDROM support" + select ADK_LINUX_KERNEL_SCSI help If you want to use a SCSI or FireWire CD-ROM under Linux, say Y and read the SCSI-HOWTO and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>. Also make sure to say Y or M to "ISO 9660 CD-ROM file system support" later. -config ADK_KERNEL_BLK_DEV_MD - prompt "md support........................ RAID support (kernel)" - tristate - select ADK_KERNEL_MD - default n - -config ADK_KPACKAGE_KMOD_BLK_DEV_MD - prompt "kmod-blk-dev-md................... RAID support (module)" - tristate - depends on !ADK_KERNEL_BLK_DEV_MD - select ADK_KERNEL_MD - depends on !ADK_TARGET_SYSTEM_FOXBOARD_LX - help +config ADK_LINUX_KERNEL_BLK_DEV_MD + tristate "RAID support" + select ADK_LINUX_KERNEL_MD -config ADK_KERNEL_MD_RAID0 - prompt "raid0 support.................... RAID0 support (kernel)" - tristate - depends on ADK_KERNEL_BLK_DEV_MD - help +config ADK_LINUX_KERNEL_MD_RAID0 + tristate "RAID0 support" + depends on ADK_LINUX_KERNEL_BLK_DEV_MD -config ADK_KPACKAGE_KMOD_MD_RAID0 - prompt "kmod-md-raid0..................... RAID0 support (module)" - tristate - depends on ADK_KPACKAGE_KMOD_BLK_DEV_MD - depends on !ADK_KERNEL_MD_RAID0 - help +config ADK_LINUX_KERNEL_MD_RAID1 + tristate "RAID1 support" + depends on ADK_LINUX_KERNEL_BLK_DEV_MD -config ADK_KERNEL_MD_RAID1 - prompt "raid1 support.................... RAID1 support (kernel)" - tristate - depends on ADK_KERNEL_BLK_DEV_MD - help - -config ADK_KPACKAGE_KMOD_MD_RAID1 - prompt "kmod-md-raid1..................... RAID1 support (module)" - tristate - depends on ADK_KPACKAGE_KMOD_BLK_DEV_MD - help - -config ADK_KPACKAGE_KMOD_MD_RAID456 - prompt "kmod-md-raid456................... RAID456 support" - tristate - depends on ADK_KPACKAGE_KMOD_BLK_DEV_MD - help +config ADK_LINUX_KERNEL_MD_RAID456 + tristate "RAID456 support" + depends on ADK_LINUX_KERNEL_BLK_DEV_MD -config ADK_KPACKAGE_KMOD_BLK_DEV_DM - prompt "kmod-blk-dev-dm................... Device Mapper support" - select ADK_KERNEL_MD - depends on !ADK_KERNEL_BLK_DEV_DM - depends on !ADK_TARGET_SYSTEM_FOXBOARD_LX - tristate +config ADK_LINUX_KERNEL_BLK_DEV_DM + tristate "Device Mapper support" + select ADK_LINUX_KERNEL_MD help Device-mapper is a low level volume manager. It works by allowing people to specify mappings for ranges of logical sectors. Various @@ -346,15 +728,14 @@ config ADK_KPACKAGE_KMOD_BLK_DEV_DM Higher level volume managers such as LVM2 use this driver. -config ADK_KPACKAGE_KMOD_DM_CRYPT - prompt "kmod-dm-crypt..................... Crypt target support" - depends on !ADK_KERNEL_DM_CRYPT - depends on ADK_KPACKAGE_KMOD_BLK_DEV_DM - select ADK_KERNEL_MD - select ADK_KERNEL_CRYPTO - select ADK_KPACKAGE_KMOD_CRYPTO_CBC - select ADK_KPACKAGE_KMOD_CRYPTO_BLKCIPHER - tristate +config ADK_LINUX_KERNEL_DM_CRYPT + tristate "Crypt target support" + select ADK_LINUX_KERNEL_MD + select ADK_LINUX_KERNEL_CRYPTO + select ADK_LINUX_KERNEL_CRYPTO_CBC + select ADK_LINUX_KERNEL_CRYPTO_BLKCIPHER + depends on ADK_LINUX_KERNEL_BLK_DEV_DM + default n help This device-mapper target allows you to create a device that transparently encrypts the data on it. You'll need to activate @@ -364,34 +745,121 @@ config ADK_KPACKAGE_KMOD_DM_CRYPT <http://www.saout.de/misc/dm-crypt/> -config ADK_KPACKAGE_KMOD_DM_SNAPSHOT - prompt "kmod-dm-snapshot.................. Snapshot target" - depends on ADK_KPACKAGE_KMOD_BLK_DEV_DM - tristate +config ADK_LINUX_KERNEL_DM_SNAPSHOT + tristate "Devicemapper Snapshot target" + depends on ADK_LINUX_KERNEL_BLK_DEV_DM help Allow volume managers to take writable snapshots of a device. -config ADK_KPACKAGE_KMOD_DM_MIRROR - prompt "kmod-dm-mirror.................... Mirror target" - depends on ADK_KPACKAGE_KMOD_BLK_DEV_DM - tristate +config ADK_LINUX_KERNEL_DM_MIRROR + tristate "Devicemapper Mirror target" + depends on ADK_LINUX_KERNEL_BLK_DEV_DM help Allow volume managers to mirror logical volumes, also needed for live data migration tools such as 'pvmove'. -config ADK_KPACKAGE_KMOD_BLK_DEV_DRBD - prompt "kmod-blk-dev-drbd................. DRBD support (Network RAID 1)" - tristate - select ADK_KERNEL_BLK_DEV - select ADK_KERNEL_CONNECTOR - depends on !ADK_TARGET_SYSTEM_FOXBOARD_LX +config ADK_LINUX_KERNEL_DM_RAID + tristate "RAID 1/4/5/6/10 target" + depends on ADK_LINUX_KERNEL_BLK_DEV_DM + select ADK_LINUX_KERNEL_MD_RAID0 + select ADK_LINUX_KERNEL_MD_RAID1 + select ADK_LINUX_KERNEL_MD_RAID10 + select ADK_LINUX_KERNEL_MD_RAID456 + select ADK_LINUX_KERNEL_BLK_DEV_MD + ---help--- + A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings + + A RAID-5 set of N drives with a capacity of C MB per drive provides + the capacity of C * (N - 1) MB, and protects against a failure + of a single drive. For a given sector (row) number, (N - 1) drives + contain data sectors, and one drive contains the parity protection. + For a RAID-4 set, the parity blocks are present on a single drive, + while a RAID-5 set distributes the parity across the drives in one + of the available parity distribution methods. + + A RAID-6 set of N drives with a capacity of C MB per drive + provides the capacity of C * (N - 2) MB, and protects + against a failure of any two drives. For a given sector + (row) number, (N - 2) drives contain data sectors, and two + drives contains two independent redundancy syndromes. Like + RAID-5, RAID-6 distributes the syndromes across the drives + in one of the available parity distribution methods. + +config ADK_LINUX_KERNEL_BLK_DEV_DRBD + tristate "DRBD support (Network RAID 1)" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_BLK_DEV + select ADK_LINUX_KERNEL_CONNECTOR + default n help DRBD - http://www.drbd.org + +config ADK_LINUX_KERNEL_BLK_DEV_LOOP + tristate "Loop mount support" + select ADK_LINUX_KERNEL_BLOCK + select ADK_LINUX_KERNEL_BLK_DEV + default n + help + Saying Y here will allow you to use a regular file as a block + device; you can then create a file system on that block device and + mount it just as you would mount other block devices such as hard + drive partitions, CD-ROM drives or floppy drives. The loop devices + are block special device files with major number 7 and typically + called /dev/loop0, /dev/loop1 etc. + + This is useful if you want to check an ISO 9660 file system before + burning the CD, or if you want to use floppy images without first + writing them to floppy. Furthermore, some Linux distributions avoid + the need for a dedicated Linux partition by keeping their complete + root file system inside a DOS FAT file using this loop device + driver. + + To use the loop device, you need the losetup utility, found in the + util-linux package, see + <ftp://ftp.kernel.org/pub/linux/utils/util-linux/>. + + The loop device driver can also be used to "hide" a file system in + a disk partition, floppy, or regular file, either using encryption + (scrambling the data) or steganography (hiding the data in the low + bits of, say, a sound file). This is also safe if the file resides + on a remote file server. + + There are several ways of encrypting disks. Some of these require + kernel patches. The vanilla kernel offers the cryptoloop option + and a Device Mapper target (which is superior, as it supports all + file systems). If you want to use the cryptoloop, say Y to both + LOOP and CRYPTOLOOP, and make sure you have a recent (version 2.12 + or later) version of util-linux. Additionally, be aware that + the cryptoloop is not safe for storing journaled filesystems. + + Note that this loop device has nothing to do with the loopback + device used for network connections from the machine to itself. + +config ADK_LINUX_KERNEL_BLK_DEV_NBD + tristate "Network Block Device support" + help + Saying Y here will allow your computer to be a client for network + block devices, i.e. it will be able to use block devices exported by + servers (mount file systems on them etc.). Communication between + client and server works over TCP/IP networking, but to the client + program this is hidden: it looks like a regular local file access to + a block device special file such as /dev/nd0. + + Network block devices also allows you to run a block-device in + userland (making server and client physically the same computer, + communicating using the loopback network device). + + Read <file:Documentation/nbd.txt> for more information, especially + about where to find the server code, which runs in user space and + does not need special kernel support. + + Note that this has nothing to do with the network file systems NFS + or Coda; you can say N here even if you intend to use NFS or Coda. -config ADK_KERNEL_SWAP - prompt "swap.............................. SWAP support" - boolean +config ADK_LINUX_KERNEL_SWAP + bool "SWAP support" help - Kernel swap support. + Kernel swap support endmenu +endmenu |