# Linux kernel 2.6.12 Kconfig .pot file # Licensed under GNU GPL v2 # # The Linux Kernel Translation Project # http://tlktp.sourceforge.net # # Translators: # msgid "" msgstr "" "Project-Id-Version: Linux 2.6.12\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2005-06-26 01:06+0100\n" "PO-Revision-Date: 2002-08-29 23:36+0100\n" "Last-Translator: Karl Eichwalder\n" "Language-Team: German\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: drivers/mtd/Kconfig:3 msgid "Memory Technology Devices (MTD)" msgstr "" #: drivers/mtd/Kconfig:6 #, fuzzy msgid "Memory Technology Device (MTD) support" msgstr "MTRR control and configuration" # arch/cris/arch-v10/drivers/Kconfig:636 drivers/mtd/Kconfig:7 #: drivers/mtd/Kconfig:7 msgid "" "Memory Technology Devices are flash, RAM and similar chips, often\n" "used for solid state file systems on embedded devices. This option\n" "will provide the generic support for MTD drivers to register\n" "themselves with the kernel and for potential users of MTD devices\n" "to enumerate the devices which are present and obtain a handle on\n" "them. It will also allow you to select individual drivers for\n" "particular hardware and users of MTD devices. If unsure, say N.\n" msgstr "" #: drivers/mtd/Kconfig:17 msgid "Debugging" msgstr "" #: drivers/mtd/Kconfig:19 msgid "" "This turns on low-level debugging for the entire MTD sub-system.\n" "Normally, you should say 'N'.\n" msgstr "" #: drivers/mtd/Kconfig:24 msgid "Debugging verbosity (0 = quiet, 3 = noisy)" msgstr "" #: drivers/mtd/Kconfig:27 msgid "Determines the verbosity level of the MTD debugging messages.\n" msgstr "" #: drivers/mtd/Kconfig:31 #, fuzzy msgid "MTD concatenating support" msgstr "Optimierung für CMD640 Chipsatz" #: drivers/mtd/Kconfig:33 msgid "" "Support for concatenating several MTD devices into a single\n" "(virtual) one. This allows you to have -for example- a JFFS(2)\n" "file system spanning multiple physical flash chips. If unsure,\n" "say 'Y'.\n" msgstr "" #: drivers/mtd/Kconfig:40 #, fuzzy msgid "MTD partitioning support" msgstr "Unterstuetzung fuer Macintosh Partitionen" # arch/cris/arch-v10/drivers/Kconfig:728 drivers/mtd/Kconfig:42 #: drivers/mtd/Kconfig:42 msgid "" "If you have a device which needs to divide its flash chip(s) up\n" "into multiple 'partitions', each of which appears to the user as\n" "a separate MTD device, you require this option to be enabled. If\n" "unsure, say 'Y'.\n" "\n" "Note, however, that you don't need this option for the DiskOnChip\n" "devices. Partitioning on NFTL 'devices' is a different - that's the\n" "'normal' form of partitioning used on a block device.\n" msgstr "" #: drivers/mtd/Kconfig:53 msgid "RedBoot partition table parsing" msgstr "" #: drivers/mtd/Kconfig:55 msgid "" "RedBoot is a ROM monitor and bootloader which deals with multiple\n" "'images' in flash devices by putting a table one of the erase\n" "blocks on the device, similar to a partition table, which gives\n" "the offsets, lengths and names of all the images stored in the\n" "flash.\n" "\n" "If you need code which can detect and parse this table, and register\n" "MTD 'partitions' corresponding to each image in the table, enable\n" "this option.\n" "\n" "You will still need the parsing functions to be called by the driver\n" "for your particular device. It won't happen automatically. The\n" "SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for\n" "example.\n" msgstr "" #: drivers/mtd/Kconfig:72 msgid "Location of RedBoot partition table" msgstr "" #: drivers/mtd/Kconfig:75 msgid "" "This option is the Linux counterpart to the\n" "CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time\n" "option.\n" "\n" "The option specifies which Flash sectors holds the RedBoot\n" "partition table. A zero or positive value gives an absolete\n" "erase block number. A negative value specifies a number of\n" "sectors before the end of the device.\n" "\n" "For example \"2\" means block number 2, \"-1\" means the last\n" "block and \"-2\" means the penultimate block.\n" msgstr "" #: drivers/mtd/Kconfig:89 msgid " Include unallocated flash regions" msgstr "" #: drivers/mtd/Kconfig:91 msgid "" "If you need to register each unallocated flash region as a MTD\n" "'partition', enable this option.\n" msgstr "" #: drivers/mtd/Kconfig:96 msgid " Force read-only for RedBoot system images" msgstr "" #: drivers/mtd/Kconfig:98 msgid "" "If you need to force read-only for 'RedBoot', 'RedBoot Config' and\n" "'FIS directory' images, enable this option.\n" msgstr "" #: drivers/mtd/Kconfig:103 #, fuzzy msgid "Command line partition table parsing" msgstr "Unterstuetzung fuer Solaris (x86) Partitionstabellen" #: drivers/mtd/Kconfig:105 msgid "" "Allow generic configuration of the MTD paritition tables via the kernel\n" "command line. Multiple flash resources are supported for hardware where\n" "different kinds of flash memory are available.\n" "\n" "You will still need the parsing functions to be called by the driver\n" "for your particular device. It won't happen automatically. The\n" "SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for\n" "example.\n" "\n" "The format for the command line is as follows:\n" "\n" "mtdparts=[; := :[,]\n" " := [@offset][][ro]\n" " := unique id used in mapping driver/device\n" " := standard linux memsize OR \"-\" to denote all\n" "remaining space\n" " := (NAME)\n" "\n" "Due to the way Linux handles the command line, no spaces are\n" "allowed in the partition definition, including mtd id's and partition\n" "names.\n" "\n" "Examples:\n" "\n" "1 flash resource (mtd-id \"sa1100\"), with 1 single writable partition:\n" "mtdparts=sa1100:-\n" "\n" "Same flash, but 2 named partitions, the first one being read-only:\n" "mtdparts=sa1100:256k(ARMboot)ro,-(root)\n" "\n" "If unsure, say 'N'.\n" msgstr "" #: drivers/mtd/Kconfig:140 msgid "ARM Firmware Suite partition parsing" msgstr "" #: drivers/mtd/Kconfig:142 msgid "" "The ARM Firmware Suite allows the user to divide flash devices into\n" "multiple 'images'. Each such image has a header containing its name\n" "and offset/size etc.\n" "\n" "If you need code which can detect and parse these tables, and\n" "register MTD 'partitions' corresponding to each image detected,\n" "enable this option.\n" "\n" "You will still need the parsing functions to be called by the driver\n" "for your particular device. It won't happen automatically. The\n" "'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example.\n" msgstr "" #: drivers/mtd/Kconfig:155 msgid "User Modules And Translation Layers" msgstr "" #: drivers/mtd/Kconfig:159 msgid "Direct char device access to MTD devices" msgstr "" # arch/cris/arch-v10/drivers/Kconfig:695 drivers/mtd/Kconfig:161 #: drivers/mtd/Kconfig:161 msgid "" "This provides a character device for each MTD device present in\n" "the system, allowing the user to read and write directly to the\n" "memory chips, and also use ioctl() to obtain information about\n" "the device, or to erase parts of it.\n" msgstr "" #: drivers/mtd/Kconfig:168 msgid "Caching block device access to MTD devices" msgstr "" # arch/cris/arch-v10/drivers/Kconfig:705 drivers/mtd/Kconfig:170 #: drivers/mtd/Kconfig:170 msgid "" "Although most flash chips have an erase size too large to be useful\n" "as block devices, it is possible to use MTD devices which are based\n" "on RAM chips in this manner. This block device is a user of MTD\n" "devices performing that function.\n" "\n" "At the moment, it is also required for the Journalling Flash File\n" "System(s) to obtain a handle on the MTD device when it's mounted\n" "(although JFFS and JFFS2 don't actually use any of the functionality\n" "of the mtdblock device).\n" "\n" "Later, it may be extended to perform read/erase/modify/write cycles\n" "on flash chips to emulate a smaller block size. Needless to say,\n" "this is very unsafe, but could be useful for file systems which are\n" "almost never written to.\n" "\n" "You do not need this option for use with the DiskOnChip devices. For\n" "those, enable NFTL support (CONFIG_NFTL) instead.\n" msgstr "" #: drivers/mtd/Kconfig:190 msgid "Readonly block device access to MTD devices" msgstr "" #: drivers/mtd/Kconfig:192 msgid "" "This allows you to mount read-only file systems (such as cramfs)\n" "from an MTD device, without the overhead (and danger) of the caching\n" "driver.\n" "\n" "You do not need this option for use with the DiskOnChip devices. For\n" "those, enable NFTL support (CONFIG_NFTL) instead.\n" msgstr "" #: drivers/mtd/Kconfig:201 #, fuzzy msgid "FTL (Flash Translation Layer) support" msgstr "SLIP (serial line) Unterstützung" #: drivers/mtd/Kconfig:203 msgid "" "This provides support for the original Flash Translation Layer which\n" "is part of the PCMCIA specification. It uses a kind of pseudo-\n" "file system on a flash device to emulate a block device with\n" "512-byte sectors, on top of which you put a 'normal' file system.\n" "\n" "You may find that the algorithms used in this code are patented\n" "unless you live in the Free World where software patents aren't\n" "legal - in the USA you are only permitted to use this on PCMCIA\n" "hardware, although under the terms of the GPL you're obviously\n" "permitted to copy, modify and distribute the code as you wish. Just\n" "not use it.\n" msgstr "" #: drivers/mtd/Kconfig:217 msgid "NFTL (NAND Flash Translation Layer) support" msgstr "" #: drivers/mtd/Kconfig:219 msgid "" "This provides support for the NAND Flash Translation Layer which is\n" "used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-\n" "file system on a flash device to emulate a block device with\n" "512-byte sectors, on top of which you put a 'normal' file system.\n" "\n" "You may find that the algorithms used in this code are patented\n" "unless you live in the Free World where software patents aren't\n" "legal - in the USA you are only permitted to use this on DiskOnChip\n" "hardware, although under the terms of the GPL you're obviously\n" "permitted to copy, modify and distribute the code as you wish. Just\n" "not use it.\n" msgstr "" #: drivers/mtd/Kconfig:233 #, fuzzy msgid "Write support for NFTL" msgstr "Unterstützung des ELF Binärformat" #: drivers/mtd/Kconfig:235 msgid "" "Support for writing to the NAND Flash Translation Layer, as used\n" "on the DiskOnChip.\n" msgstr "" #: drivers/mtd/Kconfig:240 msgid "INFTL (Inverse NAND Flash Translation Layer) support" msgstr "" #: drivers/mtd/Kconfig:242 msgid "" "This provides support for the Inverse NAND Flash Translation\n" "Layer which is used on M-Systems' newer DiskOnChip devices. It\n" "uses a kind of pseudo-file system on a flash device to emulate\n" "a block device with 512-byte sectors, on top of which you put\n" "a 'normal' file system.\n" "\n" "You may find that the algorithms used in this code are patented\n" "unless you live in the Free World where software patents aren't\n" "legal - in the USA you are only permitted to use this on DiskOnChip\n" "hardware, although under the terms of the GPL you're obviously\n" "permitted to copy, modify and distribute the code as you wish. Just\n" "not use it.\n" msgstr ""