/freebsd/share/man/man4/ |
H A D | uplcom.4 | 6 .\" This code is derived from software contributed to The NetBSD Foundation 20 .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 23 .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 35 .Nd USB support for Prolific PL-2303/2303X/2303HX serial adapters driver 40 .Bd -ragged -offset indent 41 .Cd "device usb" 46 Alternatively, to load the driver as a 49 .Bd -literal -offset indent 55 driver provides support for various serial adapters based on the Prolific 56 PL-2303, PL-2303X and PL-2303HX USB-to-RS232 Bridge chips. [all …]
|
H A D | uftdi.4 | 6 .\" This code is derived from software contributed to The NetBSD Foundation 20 .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 23 .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 35 .Nd USB support for serial adapters based on the FTDI family of USB 36 serial adapter chips. 41 .Bd -ragged -offset indent 42 .Cd "device usb" 47 Alternatively, to load the driver as a 50 .Bd -literal -offset indent 56 driver provides support for various serial adapters based on the [all …]
|
H A D | usb_template.4 | 14 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 18 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 34 .Nd "USB device side templates" 40 .Bd -ragged -offset indent 46 .Bd -literal -offset indent 53 module implements various USB templates that are needed when 54 programming an USB device side driver. 56 A USB template consists of an USB device descriptor, one or more USB 57 configuration descriptors, one or more USB interface descriptors, one 58 or more USB endpoint descriptors, USB strings and additional USB [all …]
|
H A D | uslcom.4 | 5 .\" Permission to use, copy, modify, and distribute this software for any 10 .\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF 22 .Nd Silicon Laboratories CP2101/CP2102/CP2103/CP2104/CP2105 based USB serial adapter 27 .Bd -ragged -offset indent 28 .Cd "device usb" 33 Alternatively, to load the driver as a 36 .Bd -literal -offset indent 43 based USB serial adapters. 54 .Bl -bullet -compact 56 AC-Services CAN, CIS-IBUS, IBUS and OBD interfaces [all …]
|
H A D | umcs.4 | 5 .\" This code is derived from software contributed to The NetBSD Foundation 19 .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 22 .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 34 .Nd USB support for serial adapters based on the MCS7820 and MCS7840 chips 39 .Bd -ragged -offset indent 40 .Cd "device usb" 45 Alternatively, to load the driver as a 48 .Bd -literal -offset indent 54 driver provides support for various multiport serial adapters based on the MosCom 56 They are 2- or 4-port adapters with full-featured [all …]
|
H A D | umodem.4 | 6 .\" This code is derived from software contributed to The NetBSD Foundation 20 .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 23 .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 35 .Nd USB Communication Device Class serial (CDC ACM) driver 40 .Bd -ragged -offset indent 41 .Cd "device usb" 46 Alternatively, to load the driver as a 49 .Bd -literal -offset indent 55 driver provides support for USB modems and serial devices that 57 It also provides device-side CDC ACM support. [all …]
|
H A D | ubsa.4 | 5 .\" This code is derived from software contributed to The NetBSD Foundation 19 .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 22 .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 34 .Nd USB support for Belkin serial adapters 39 .Bd -ragged -offset indent 40 .Cd "device usb" 45 Alternatively, to load the driver as a 48 .Bd -literal -offset indent 54 driver provides support for the USB-to-RS232 Bridge chip used by a variety of 55 serial adapters from Belkin and other vendors. [all …]
|
H A D | uark.4 | 5 .\" Permission to use, copy, modify, and distribute this software for any 10 .\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF 22 .Nd Arkmicro Technologies ARK3116 based USB serial adapter 27 .Bd -ragged -offset indent 28 .Cd "device usb" 33 Alternatively, to load the driver as a 36 .Bd -literal -offset indent 42 driver supports Arkmicro Technologies ARK3116 based serial adapters. 48 .Bl -bullet -compact 50 HL USB-RS232 [all …]
|
H A D | cdce.4 | 8 .\" - Redistributions of source code must retain the above copyright 10 .\" - Redistributions in binary form must reproduce the above 17 .\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS 21 .\" BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 35 .Nd "USB Communication Device Class Ethernet (CDC ECM/NCM) driver" 40 .Bd -ragged -offset indent 43 .Cd "device usb" 51 .Bd -ragged -offset indent 56 Alternatively, to load the driver as a 59 .Bd -literal -offset indent [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/leds/ |
H A D | leds-bcm6328.txt | 1 LEDs connected to Broadcom BCM6328 controller 4 In these SoCs it's possible to control LEDs both as GPIOs or by hardware. 5 However, on some devices there are Serial LEDs (LEDs connected to a 74x164 7 as spi-gpio. See Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml), 9 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and 10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware 11 controlled, so the only chance to keep them working is by using this driver. 16 is usually 1:1 for hardware to LED signals, but through the activity/link 18 explained later in brcm,link-signal-sources). Even if a LED is hardware 19 controlled you are still able to make it blink or light it up if it isn't, [all …]
|
H A D | leds-bcm6328.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-bcm6328.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: LEDs connected to Broadcom BCM6328 controller 10 - Álvaro Fernández Rojas <noltari@gmail.com> 14 In these SoCs it's possible to control LEDs both as GPIOs or by hardware. 15 However, on some devices there are Serial LEDs (LEDs connected to a 74x164 17 as spi-gpio. See 20 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and [all …]
|
/freebsd/sys/dev/usb/ |
H A D | usbdevs | 3 /*- 4 * Copyright (c) 1998-2004 The NetBSD Foundation, Inc. 7 * This code is derived from software contributed to The NetBSD Foundation 22 * TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 25 * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 34 * List of known USB vendors 36 * USB.org publishes a VID list of USB-IF member companies at 37 * http://www.usb.org/developers/tools 43 * available to the source code and does not change any functionality, nor 44 * does it make your device available to a specific driver. [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/usb/ |
H A D | usb.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/usb/usb.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Generic USB Controller 10 - Greg Kroah-Hartman <gregkh@linuxfoundation.org> 16 pattern: "^usb(@.*)?" 20 List of all the USB PHYs on this HCD 22 phy-names: 24 Name specifier for the USB PHY [all …]
|
H A D | usb251xb.txt | 1 Microchip USB 2.0 Hi-Speed Hub Controller 3 The device node for the configuration of a Microchip USB251x/xBi USB 2.0 4 Hi-Speed Controller. 7 - compatible : Should be "microchip,usb251xb" or one of the specific types: 11 - reg : I2C address on the selected bus (default is <0x2C>) 14 - reset-gpios : Should specify the gpio for hub reset 15 - vdd-supply : Should specify the phandle to the regulator supplying vdd 16 - skip-config : Skip Hub configuration, but only send the USB-Attach command 17 - vendor-id : Set USB Vendor ID of the hub (16 bit, default is 0x0424) 18 - product-id : Set USB Product ID of the hub (16 bit, default depends on type) [all …]
|
H A D | fsl-usb.txt | 1 Freescale SOC USB controllers 3 The device node for a USB controller that is part of a Freescale 5 Practice : Universal Serial Bus" with the following modifications 9 - compatible : Should be "fsl-usb2-mph" for multi port host USB 10 controllers, or "fsl-usb2-dr" for dual role USB controllers 11 or "fsl,mpc5121-usb2-dr" for dual role USB controllers of MPC5121. 12 Wherever applicable, the IP version of the USB controller should 13 also be mentioned (for eg. fsl-usb2-dr-v2.2 for bsc9132). 14 - phy_type : For multi port host USB controllers, should be one of 15 "ulpi", or "serial". For dual role USB controllers, should be [all …]
|
H A D | usb251xb.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/usb/usb251xb.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Microchip USB 2.0 Hi-Speed Hub Controller 10 - Richard Leitner <richard.leitner@skidata.com> 15 - microchip,usb2422 16 - microchip,usb2512b 17 - microchip,usb2512bi 18 - microchip,usb2513b [all …]
|
H A D | aspeed,usb-vhub.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 5 $id: http://devicetree.org/schemas/usb/aspeed,usb-vhub.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 title: ASPEED USB 2.0 Virtual Hub Controller 11 - Benjamin Herrenschmidt <benh@kernel.crashing.org> 14 The ASPEED USB 2.0 Virtual Hub Controller implements 1 set of USB Hub 15 register and several sets of Device and Endpoint registers to support 16 the Virtual Hub's downstream USB devices. 26 - aspeed,ast2400-usb-vhub [all …]
|
/freebsd/usr.sbin/moused/ |
H A D | moused.8 | 1 .\"- 2 .\" SPDX-License-Identifier: BSD-4-Clause 19 .\" may be used to endorse or promote products derived from this software 23 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 27 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 39 .Nd pass mouse data to the system video console driver 67 utility and the console driver work together to suppor [all...] |
/freebsd/sys/dev/usb/serial/ |
H A D | uplcom.c | 3 /*- 4 * SPDX-License-Identifier: BSD-2-Clause 6 * Copyright (c) 2001-2003, 2005 Shunsuke Akiyama <akiyama@jp.FreeBSD.org>. 19 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 23 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 31 /*- 35 * This code is derived from software contributed to The NetBSD Foundation 49 * TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 52 * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 61 * This driver supports several USB-to-RS232 serial adapters driven by [all …]
|
/freebsd/share/misc/ |
H A D | usb_vendors | 2 # List of USB ID's 4 # Maintained by Stephen J. Gowdy <linux.usb.ids@gmail.com> 6 # http://www.linux-usb.org/usb-ids.html 7 # or send entries as patches (diff -u old new) in the 8 # body of your email (a bot will attempt to deal with it). 10 # http://www.linux-usb.org/usb.ids 13 # Date: 2024-12-04 20:34:02 20 # device device_name <-- single tab 21 # interface interface_name <-- two tabs 38 5301 GW-US54ZGL 802.11bg [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/gnss/ |
H A D | u-blox,neo-6m.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/gnss/u-blox,neo-6m.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: U-blox GNSS Receiver 10 - $ref: gnss-common.yaml# 11 - $ref: /schemas/serial/serial-peripheral-props.yaml# 14 - Johan Hovold <johan@kernel.org> 17 The U-blox GNSS receivers can use UART, DDC (I2C), SPI and USB interfaces. 22 - u-blox,neo-6m [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/ |
H A D | xilinx.txt | 5 of standard device types (network, serial, etc.) and miscellaneous 10 Each IP-core has a set of parameters which the FPGA designer can use to 12 extract the device parameters relevant to device drivers and copy them 15 to be recompiled every time the FPGA bitstream is resynthesized. 17 The new approach is to export the parameters into the device tree and 19 parameters which used to be exported as #defines will now become 20 properties of the device node. In general, device nodes for IP-cores 23 (name): (generic-name)@(base-address) { 24 compatible = "xlnx,(ip-core-name)-(HW_VER)" 27 interrupt-parent = <&interrupt-controller-phandle>; [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/dma/ |
H A D | ste-dma40.txt | 4 - compatible: "stericsson,dma40" 5 - reg: Address range of the DMAC registers 6 - reg-names: Names of the above areas to use during resource look-up 7 - interrupt: Should contain the DMAC interrupt number 8 - #dma-cells: must be <3> 9 - memcpy-channels: Channels to be used for memcpy 12 - dma-channels: Number of channels supported by hardware - if not present 13 the driver will attempt to obtain the information from H/W 14 - disabled-channels: Channels which can not be used 18 dma: dma-controller@801c0000 { [all …]
|
H A D | stericsson,dma40.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: ST-Ericsso [all...] |
/freebsd/sys/contrib/device-tree/src/arm/renesas/ |
H A D | r7s9210-rza2mevb.dts | 1 // SPDX-License-Identifier: GPL-2.0 8 * Hence the 64 MiB of SDRAM on the sub-board needs to be enabled, which has 10 * - SCIF4 connected to the on-board USB-seria [all...] |