# Linux kernel Kconfig .pot file # Licensed under GNU GPL v2 # # The Linux Kernel Translation Project # http://tlktp.sourceforge.net # # Translators: # msgid "" msgstr "" "POT-Creation-Date: 2005-06-26 01:06+0100\n" "PO-Revision-Date: 2005-06-20 13:06+0100\n" "Last-Translator: FULL NAME \n" "Language-Team: TLKTP \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8-bit\n" "Project-Id-Version kernel 2.6.12\n" #: drivers/usb/gadget/Kconfig:15 msgid "USB Gadget Support" msgstr "" #: drivers/usb/gadget/Kconfig:18 msgid "Support for USB Gadgets" msgstr "" #: drivers/usb/gadget/Kconfig:19 msgid "" "USB is a master/slave protocol, organized with one master\n" "host (such as a PC) controlling up to 127 peripheral devices.\n" "The USB hardware is asymmetric, which makes it easier to set up:\n" "you can't connect a \"to-the-host\" connector to a peripheral.\n" "\n" "Linux can run in the host, or in the peripheral. In both cases\n" "you need a low level bus controller driver, and some software\n" "talking to it. Peripheral controllers are often discrete silicon,\n" "or are integrated with the CPU in a microcontroller. The more\n" "familiar host side controllers have names like like \"EHCI\", \"OHCI\",\n" "or \"UHCI\", and are usually integrated into southbridges on PC\n" "motherboards.\n" "\n" "Enable this configuration option if you want to run Linux inside\n" "a USB peripheral device. Configure one hardware driver for your\n" "peripheral/device side bus controller, and a \"gadget driver\" for\n" "your peripheral protocol. (If you use modular gadget drivers,\n" "you may configure more than one.)\n" "\n" "If in doubt, say \"N\" and don't enable these drivers; most people\n" "don't have this kind of hardware (except maybe inside Linux PDAs).\n" "\n" "For more information, see and\n" "the kernel DocBook documentation for this API.\n" msgstr "" #: drivers/usb/gadget/Kconfig:46 msgid "Debugging information files" msgstr "" #: drivers/usb/gadget/Kconfig:48 msgid "" "Some of the drivers in the \"gadget\" framework can expose\n" "debugging information in files such as /proc/driver/udc\n" "(for a peripheral controller). The information in these\n" "files may help when you're troubleshooting or bringing up a\n" "driver on a new board. Enable these files by choosing \"Y\"\n" "here. If in doubt, or to conserve kernel memory, say \"N\".\n" msgstr "" #: drivers/usb/gadget/Kconfig:60 msgid "USB Peripheral Controller" msgstr "" #: drivers/usb/gadget/Kconfig:62 msgid "" "A USB device uses a controller to talk to its host.\n" "Systems should have only one such upstream link.\n" "Many controller drivers are platform-specific; these\n" "often need board-specific hooks.\n" msgstr "" #: drivers/usb/gadget/Kconfig:69 msgid "NetChip 2280" msgstr "" #: drivers/usb/gadget/Kconfig:72 msgid "" "NetChip 2280 is a PCI based USB peripheral controller which\n" "supports both full and high speed USB 2.0 data transfers.\n" "\n" "It has six configurable endpoints, as well as endpoint zero\n" "(for control transfers) and several endpoints with dedicated\n" "functions.\n" "\n" "Say \"y\" to link the driver statically, or \"m\" to build a\n" "dynamically linked module called \"net2280\" and force all\n" "gadget drivers to also be dynamically linked.\n" msgstr "" #: drivers/usb/gadget/Kconfig:90 msgid "PXA 25x or IXP 4xx" msgstr "" #: drivers/usb/gadget/Kconfig:92 msgid "" "Intel's PXA 25x series XScale ARM-5TE processors include\n" "an integrated full speed USB 1.1 device controller. The\n" "controller in the IXP 4xx series is register-compatible.\n" "\n" "It has fifteen fixed-function endpoints, as well as endpoint\n" "zero (for control transfers).\n" "\n" "Say \"y\" to link the driver statically, or \"m\" to build a\n" "dynamically linked module called \"pxa2xx_udc\" and force all\n" "gadget drivers to also be dynamically linked.\n" msgstr "" #: drivers/usb/gadget/Kconfig:120 msgid "Toshiba TC86C001 'Goku-S'" msgstr "" #: drivers/usb/gadget/Kconfig:122 msgid "" "The Toshiba TC86C001 is a PCI device which includes controllers\n" "for full speed USB devices, IDE, I2C, SIO, plus a USB host (OHCI).\n" "\n" "The device controller has three configurable (bulk or interrupt)\n" "endpoints, plus endpoint zero (for control transfers).\n" "\n" "Say \"y\" to link the driver statically, or \"m\" to build a\n" "dynamically linked module called \"goku_udc\" and to force all\n" "gadget drivers to also be dynamically linked.\n" msgstr "" #: drivers/usb/gadget/Kconfig:140 msgid "LH7A40X" msgstr "" #: drivers/usb/gadget/Kconfig:142 msgid "This driver provides USB Device Controller driver for LH7A40x\n" msgstr "" #: drivers/usb/gadget/Kconfig:152 msgid "OMAP USB Device Controller" msgstr "" #: drivers/usb/gadget/Kconfig:155 msgid "" "Many Texas Instruments OMAP processors have flexible full\n" "speed USB device controllers, with support for up to 30\n" "endpoints (plus endpoint zero). This driver supports the\n" "controller in the OMAP 1611, and should work with controllers\n" "in other OMAP processors too, given minor tweaks.\n" "\n" "Say \"y\" to link the driver statically, or \"m\" to build a\n" "dynamically linked module called \"omap_udc\" and force all\n" "gadget drivers to also be dynamically linked.\n" msgstr "" #: drivers/usb/gadget/Kconfig:172 msgid "OTG Support" msgstr "" #: drivers/usb/gadget/Kconfig:174 msgid "" "The most notable feature of USB OTG is support for a\n" "\"Dual-Role\" device, which can act as either a device\n" "or a host. The initial role choice can be changed\n" "later, when two dual-role devices talk to each other.\n" "\n" "Select this only if your OMAP board has a Mini-AB connector.\n" "\n" msgstr "" #: drivers/usb/gadget/Kconfig:184 msgid "Dummy HCD (DEVELOPMENT)" msgstr "" #: drivers/usb/gadget/Kconfig:187 msgid "" "This host controller driver emulates USB, looping all data transfer\n" "requests back to a USB \"gadget driver\" in the same host. The host\n" "side is the master; the gadget side is the slave. Gadget drivers\n" "can be high, full, or low speed; and they have access to endpoints\n" "like those from NET2280, PXA2xx, or SA1100 hardware.\n" "\n" "This may help in some stages of creating a driver to embed in a\n" "Linux device, since it lets you debug several parts of the gadget\n" "driver without its hardware or drivers being involved.\n" "\n" "Since such a gadget side driver needs to interoperate with a host\n" "side Linux-USB device driver, this may help to debug both sides\n" "of a USB protocol stack.\n" "\n" "Say \"y\" to link the driver statically, or \"m\" to build a\n" "dynamically linked module called \"dummy_hcd\" and force all\n" "gadget drivers to also be dynamically linked.\n" msgstr "" #: drivers/usb/gadget/Kconfig:220 msgid "" "Means that gadget drivers should include extra descriptors\n" "and code to handle dual-speed controllers.\n" msgstr "" #: drivers/usb/gadget/Kconfig:228 msgid "USB Gadget Drivers" msgstr "" #: drivers/usb/gadget/Kconfig:231 msgid "" "A Linux \"Gadget Driver\" talks to the USB Peripheral Controller\n" "driver through the abstract \"gadget\" API. Some other operating\n" "systems call these \"client\" drivers, of which \"class drivers\"\n" "are a subset (implementing a USB device class specification).\n" "A gadget driver implements one or more USB functions using\n" "the peripheral hardware.\n" "\n" "Gadget drivers are hardware-neutral, or \"platform independent\",\n" "except that they sometimes must understand quirks or limitations\n" "of the particular controllers they work with. For example, when\n" "a controller doesn't support alternate configurations or provide\n" "enough of the right types of endpoints, the gadget driver might\n" "not be able work with that controller, or might need to implement\n" "a less common variant of a device class protocol.\n" msgstr "" #: drivers/usb/gadget/Kconfig:250 msgid "Gadget Zero (DEVELOPMENT)" msgstr "" #: drivers/usb/gadget/Kconfig:252 msgid "" "Gadget Zero is a two-configuration device. It either sinks and\n" "sources bulk data; or it loops back a configurable number of\n" "transfers. It also implements control requests, for \"chapter 9\"\n" "conformance. The driver needs only two bulk-capable endpoints, so\n" "it can work on top of most device-side usb controllers. It's\n" "useful for testing, and is also a working example showing how\n" "USB \"gadget drivers\" can be written.\n" "\n" "Make this be the first driver you try using on top of any new\n" "USB peripheral controller driver. Then you can use host-side\n" "test software, like the \"usbtest\" driver, to put your hardware\n" "and its driver through a basic set of functional tests.\n" "\n" "Gadget Zero also works with the host-side \"usb-skeleton\" driver,\n" "and with many kinds of host-side test software. You may need\n" "to tweak product and vendor IDs before host software knows about\n" "this device, and arrange to select an appropriate configuration.\n" "\n" "Say \"y\" to link the driver statically, or \"m\" to build a\n" "dynamically linked module called \"g_zero\".\n" msgstr "" #: drivers/usb/gadget/Kconfig:275 msgid "HNP Test Device" msgstr "" #: drivers/usb/gadget/Kconfig:277 msgid "" "You can configure this device to enumerate using the device\n" "identifiers of the USB-OTG test device. That means that when\n" "this gadget connects to another OTG device, with this one using\n" "the \"B-Peripheral\" role, that device will use HNP to let this\n" "one serve as the USB host instead (in the \"B-Host\" role).\n" msgstr "" #: drivers/usb/gadget/Kconfig:285 msgid "Ethernet Gadget (with CDC Ethernet support)" msgstr "" #: drivers/usb/gadget/Kconfig:287 msgid "" "This driver implements Ethernet style communication, in either\n" "of two ways:\n" "\n" " - The \"Communication Device Class\" (CDC) Ethernet Control Model.\n" " That protocol is often avoided with pure Ethernet adapters, in\n" " favor of simpler vendor-specific hardware, but is widely\n" " supported by firmware for smart network devices.\n" "\n" " - On hardware can't implement that protocol, a simple CDC subset\n" " is used, placing fewer demands on USB.\n" "\n" "RNDIS support is a third option, more demanding than that subset.\n" "\n" "Within the USB device, this gadget driver exposes a network device\n" "\"usbX\", where X depends on what other networking devices you have.\n" "Treat it like a two-node Ethernet link: host, and gadget.\n" "\n" "The Linux-USB host-side \"usbnet\" driver interoperates with this\n" "driver, so that deep I/O queues can be supported. On 2.4 kernels,\n" "use \"CDCEther\" instead, if you're using the CDC option. That CDC\n" "mode should also interoperate with standard CDC Ethernet class\n" "drivers on other host operating systems.\n" "\n" "Say \"y\" to link the driver statically, or \"m\" to build a\n" "dynamically linked module called \"g_ether\".\n" msgstr "" #: drivers/usb/gadget/Kconfig:315 msgid "RNDIS support (EXPERIMENTAL)" msgstr "" #: drivers/usb/gadget/Kconfig:318 msgid "" "Microsoft Windows XP bundles the \"Remote NDIS\" (RNDIS) protocol,\n" "and Microsoft provides redistributable binary RNDIS drivers for\n" "older versions of Windows.\n" "\n" "If you say \"y\" here, the Ethernet gadget driver will try to provide\n" "a second device configuration, supporting RNDIS to talk to such\n" "Microsoft USB hosts.\n" "\n" "To make MS-Windows work with this, use Documentation/usb/linux.inf\n" "as the \"driver info file\". For versions of MS-Windows older than\n" "XP, you'll need to download drivers from Microsoft's website; a URL\n" "is given in comments found in that info file.\n" msgstr "" #: drivers/usb/gadget/Kconfig:333 msgid "Gadget Filesystem (EXPERIMENTAL)" msgstr "" #: drivers/usb/gadget/Kconfig:335 msgid "" "This driver provides a filesystem based API that lets user mode\n" "programs implement a single-configuration USB device, including\n" "endpoint I/O and control requests that don't relate to enumeration.\n" "All endpoints, transfer speeds, and transfer types supported by\n" "the hardware are available, through read() and write() calls.\n" "\n" "Say \"y\" to link the driver statically, or \"m\" to build a\n" "dynamically linked module called \"gadgetfs\".\n" msgstr "" #: drivers/usb/gadget/Kconfig:346 msgid "File-backed Storage Gadget" msgstr "" #: drivers/usb/gadget/Kconfig:347 msgid "" "The File-backed Storage Gadget acts as a USB Mass Storage\n" "disk drive. As its storage repository it can use a regular\n" "file or a block device (in much the same way as the \"loop\"\n" "device driver), specified as a module parameter.\n" "\n" "Say \"y\" to link the driver statically, or \"m\" to build a\n" "dynamically linked module called \"g_file_storage\".\n" msgstr "" #: drivers/usb/gadget/Kconfig:357 msgid "File-backed Storage Gadget testing version" msgstr "" #: drivers/usb/gadget/Kconfig:360 msgid "" "Say \"y\" to generate the larger testing version of the\n" "File-backed Storage Gadget, useful for probing the\n" "behavior of USB Mass Storage hosts. Not needed for\n" "normal operation.\n" msgstr "" #: drivers/usb/gadget/Kconfig:367 msgid "Serial Gadget (with CDC ACM support)" msgstr "" #: drivers/usb/gadget/Kconfig:368 msgid "" "The Serial Gadget talks to the Linux-USB generic serial driver.\n" "This driver supports a CDC-ACM module option, which can be used\n" "to interoperate with MS-Windows hosts or with the Linux-USB\n" "\"cdc-acm\" driver.\n" "\n" "Say \"y\" to link the driver statically, or \"m\" to build a\n" "dynamically linked module called \"g_serial\".\n" "\n" "For more information, see Documentation/usb/gadget_serial.txt\n" "which includes instructions and a \"driver info file\" needed to\n" "make MS-Windows work with this driver.\n" "\n" msgstr ""