| /f-stack/freebsd/contrib/device-tree/Bindings/net/can/ |
| H A D | rcar_can.txt | 6 "renesas,can-r8a7744" if CAN controller is a part of R8A7744 SoC. 7 "renesas,can-r8a7745" if CAN controller is a part of R8A7745 SoC. 8 "renesas,can-r8a77470" if CAN controller is a part of R8A77470 SoC. 9 "renesas,can-r8a774a1" if CAN controller is a part of R8A774A1 SoC. 12 "renesas,can-r8a7778" if CAN controller is a part of R8A7778 SoC. 13 "renesas,can-r8a7779" if CAN controller is a part of R8A7779 SoC. 25 "renesas,rcar-gen2-can" for a generic R-Car Gen2 or RZ/G1 27 "renesas,rcar-gen3-can" for a generic R-Car Gen3 or RZ/G2 42 For the denoted SoCs, "clkp2" can be CANFD clock. This is a div6 clock and can 61 can0: can@e6e80000 { [all …]
|
| H A D | allwinner,sun4i-a10-can.yaml | 4 $id: http://devicetree.org/schemas/net/can/allwinner,sun4i-a10-can.yaml# 17 - const: allwinner,sun7i-a20-can 18 - const: allwinner,sun4i-a10-can 19 - const: allwinner,sun4i-a10-can 43 can0: can@1c2bc00 { 44 compatible = "allwinner,sun7i-a20-can", 45 "allwinner,sun4i-a10-can";
|
| H A D | atmel-can.txt | 4 - compatible: Should be "atmel,at91sam9263-can", "atmel,at91sam9x5-can" or 5 "microchip,sam9x60-can" 11 can0: can@f000c000 { 12 compatible = "atmel,at91sam9x5-can";
|
| H A D | xilinx_can.txt | 6 - "xlnx,zynq-can-1.0" for Zynq CAN controllers 7 - "xlnx,axi-can-1.00.a" for Axi CAN controllers 30 zynq_can_0: can@e0008000 { 31 compatible = "xlnx,zynq-can-1.0"; 41 axi_can_0: axi-can@40000000 { 42 compatible = "xlnx,axi-can-1.00.a";
|
| H A D | mpc5xxx-mscan.txt | 9 In addition to the required compatible-, reg- and interrupt-properties, you can 20 In addition to the required compatible-, reg- and interrupt-properties, you can 33 clock divider can be specified. By default, a 39 can@1300 { 46 can@1380 {
|
| H A D | can-transceiver.yaml | 4 $id: http://devicetree.org/schemas/net/can/can-transceiver.yaml# 17 description: a positive non 0 value that determines the max speed that CAN/CAN-FD can run.
|
| /f-stack/dpdk/doc/guides/vdpadevs/ |
| H A D | features_overview.rst | 19 Device can handle packets with any GSO type. 22 Guest can receive TSOv4. 25 Guest can receive TSOv6. 28 Device can receive TSO with ECN. 31 Device can receive UFO. 34 Device can receive TSOv4. 37 Device can receive TSOv6. 40 Guest can merge receive buffers. 49 Device can handle any descriptor layout. 52 Guest can send gratuitous packets. [all …]
|
| /f-stack/tools/libxo/doc/ |
| H A D | xolint.rst | 4 The message "A percent sign appearing in text is a literal" can be caused by code like: 16 This can be a bit surprising and could be a field that was not 23 The message "Unknown long name for role/modifier" can be caused by code like: 76 'Only one field role can be used' 79 The message "Only one field role can be used" can be caused by code like: 133 Fields with the C, D, L, or N roles can't have both 258 flag can be used to generate underscores in JSON, if desired. 380 the set of anchored fields. The value can be positive 382 right padding/left justification) and can appear in 389 The message "Anchor format should be "%d"" can be caused by code like: [all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/display/exynos/ |
| H A D | exynos_dp.txt | 47 -video interfaces: Device node can contain video interface port 60 -interlaced: deprecated prop that can parsed from drm_display_mode. 61 -vsync-active-high: deprecated prop that can parsed from drm_display_mode. 62 -hsync-active-high: deprecated prop that can parsed from drm_display_mode. 63 -samsung,ycbcr-coeff: deprecated prop that can parsed from drm_display_mode. 64 -samsung,dynamic-range: deprecated prop that can parsed from drm_display_mode. 65 -samsung,color-space: deprecated prop that can parsed from drm_display_info. 66 -samsung,color-depth: deprecated prop that can parsed from drm_display_info. 67 -samsung,link-rate: deprecated prop that can reading from monitor by dpcd method. 68 -samsung,lane-count: deprecated prop that can reading from monitor by dpcd method.
|
| /f-stack/dpdk/doc/guides/platform/ |
| H A D | octeontx.rst | 12 More information about SoC can be found at `Cavium, Inc Official Website 50 For example, the *aarch64* Linaro Toolchain, which can be obtained from 55 Any *aarch64* supporting filesystem can be used. For example, 56 Ubuntu 15.10 (Wily) or 16.04 LTS (Xenial) userland which can be obtained 70 The OCTEON TX platform drivers can be compiled either natively on 93 drivers can be compiled with the following steps, 100 The example applications can be compiled using the following: 110 The DPDK applications can be cross-compiled on any x86 based platform. The 116 The following steps can be used to perform cross-compilation with OCTEON TX 133 The example applications can be compiled using the following: [all …]
|
| H A D | dpaa2.rst | 19 More information about SoC can be found at `NXP Official Website 60 …It can be obtained from `NXP's Github hosting <https://source.codeaurora.org/external/qoriq/qoriq-… 64 Any *aarch64* supporting filesystem can be used. For example, 65 Ubuntu 16.04 LTS (Xenial) or 18.04 (Bionic) userland which can be obtained 71 DPAA2 based resources can be configured easily with the help of ready scripts 78 As an alternative method, DPAA2 PMD can also be executed using images provided 94 …SDK and related information can be obtained from: `NXP QorIQ SDK <http://www.nxp.com/products/so… 101 DPAA2 based resources can be configured easily with the help of ready scripts
|
| /f-stack/dpdk/doc/guides/linux_gsg/ |
| H A D | build_dpdk.rst | 34 DPDK can be configured, built and installed on your system using the tools 47 where "build" is the desired output build directory, and "<options>" can be 51 each item disabled, a reason why that is the case. This information can be 81 Many of these options come from the "meson" tool itself and can be seen documented on the 85 to a regular "debug" build, you can either: 91 Other options are specific to the DPDK project but can be adjusted similarly. 92 To set the "max_lcores" value to 256, for example, you can either: 98 Some of the DPDK sample applications in the `examples` directory can be 118 This can be done either by setting ``CFLAGS`` and ``LDFLAGS`` in the environment, 137 DPDK can be compiled using ``ninja`` as described above. [all …]
|
| /f-stack/app/redis-5.0.5/tests/unit/ |
| H A D | introspection.tcl | 6 test {MONITOR can log executed commands} { 15 test {MONITOR can log commands issued by the scripting engine} { 37 test {CLIENT SETNAME can assign a name to this connection} { 42 test {CLIENT SETNAME can change the name of an existing connection} { 47 test {After CLIENT SETNAME, connection can still be closed} {
|
| /f-stack/freebsd/contrib/device-tree/Bindings/hwmon/ |
| H A D | aspeed-pwm-tacho.txt | 3 The ASPEED PWM controller can support upto 8 PWM outputs. The ASPEED Fan Tacho 4 controller can support upto 16 Fan tachometer inputs. 6 There can be upto 8 fans supported. Each fan can have one PWM output and 31 Under fan subnode there can upto 8 child nodes, with each child node 32 representing a fan. If there are 8 fans each fan can have one PWM port and 34 For PWM port can be configured cooling-levels to create cooling device.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/power/reset/ |
| H A D | keystone-reset.txt | 6 The Keystone SoCs can contain up to 4 watchdog timers to reset 8 block. The Reset Mux block can be configured to cause reset or not. 10 Additionally soft or hard reset can be configured. 29 - ti,wdt-list: WDT list that can cause SoC reset. It's not related 32 in format: <0>, <2>; It can be in random order and 33 begins from 0 to 3, as keystone can contain up to 4 SoC 34 reset watchdogs and can be in random order.
|
| /f-stack/dpdk/doc/guides/howto/ |
| H A D | avx512.rst | 8 AVX-512 is not used by default in DPDK, but it can be selected at runtime by apps through the use o… 10 which can be modified and will then limit the vector path taken by the code. 16 Apps can request DPDK uses AVX-512 at runtime, if it provides improved application performance. 17 This can be done by modifying the EAL setting for max SIMD bitwidth to 512, as by default it is 256, 31 The user can select to use AVX-512 at runtime, using the following argument to set the max bitwidth…
|
| H A D | flow_bifurcation.rst | 9 hardware assisted feature this approach can provide line rate processing 12 movement during the traffic split. This can yield better performance with 17 the Linux kernel stack). It can direct some traffic, for example data plane 31 network adapters. Filters can be configured to direct specific flows to a 35 In this way the Linux networking stack can receive specific traffic through 36 the kernel driver while a DPDK application can receive specific traffic 55 The DPDK application can setup some flow steering rules, 58 the :ref:`flow_isolated_mode` can be configured.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/regulator/ |
| H A D | max77686.txt | 4 More information can be found in ../mfd/max77686.txt file. 7 regulators that can be controlled over I2C. 24 -LDOn : for LDOs, where n can lie in range 1 to 26. 26 -BUCKn : for BUCKs, where n can lie in range 1 to 9. 29 Regulators which can be turned off during system suspend: 34 LDO20, LDO21, LDO22, BUCK8 and BUCK9 can be configured to GPIO enable
|
| /f-stack/dpdk/doc/guides/freebsd_gsg/ |
| H A D | build_dpdk.rst | 18 These can be installed using (as root):: 24 need to be installed. If not already present on the system, these can be 31 be installed, and can be installed via:: 41 The following commands can be used to build and install DPDK on a system. 62 that queries for DPDK information may fail. This can be fixed by 77 system, the module can be found in the `/boot/modules` directory. 80 contiguous blocks to be reserved by the module can be set at runtime prior to 94 The variables can be inspected using the following command:: 102 The module can then be loaded using kldload:: 125 kldload: can't load <build_dir>/kernel/freebsd/contigmem.ko: [all …]
|
| /f-stack/freebsd/contrib/device-tree/src/arm/ |
| H A D | at91sam9x5_can.dtsi | 15 can0: can@f8000000 { 16 compatible = "atmel,at91sam9x5-can"; 26 can1: can@f8004000 { 27 compatible = "atmel,at91sam9x5-can";
|
| H A D | sama5d3_can.dtsi | 34 can0: can@f000c000 { 35 compatible = "atmel,at91sam9x5-can"; 45 can1: can@f8010000 { 46 compatible = "atmel,at91sam9x5-can";
|
| /f-stack/doc/ |
| H A D | F-Stack_Development_Guide.md | 3 …ss can avoid performance bottlenecks caused by kernel packet copying, thread scheduling, system ca… 7 1. Ultra high network performance which the network card can achieve under full load: 10 million co… 9 3. Support Nginx, Redis, and other mature applications. Services can easily use F-Stack. 11 5. Provides micro thread interface. Various applications with stateful applications can easily use … 31 …ation of the standard DPDK. By setting the NIC port and CPU core mask, you can set binding relatio… 41 …ted into F-Stack. The FreeBSD network stack provides complete features and can follow up the impro… 83 HTTP web application can use F-Stack with Nginx. 87 key-value db application can use F-Stack with redis, and can start multi Redis instance. 91 …can directly use the F-Stack micro threading framework. Applications only need to focus on with th… 101 For example, if `lcore_mask=f` in config.ini, you can start your app like this: [all …]
|
| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | metrics_lib.rst | 9 The Metrics library implements a mechanism by which *producers* can 31 Before the library can be used, it has to be initialized by calling 48 be done individually, or a set of metrics can be registered as a group. 58 or alternatively, a set of metrics can be registered together using 72 can be obtained using ``rte_metrics_get_names()``. 89 if metrics were registered as a single set, they can either be updated 187 statistics can be obtained by querying the metrics library. 192 Before the library can be used, it has to be initialised by calling 251 statistics can be obtained by querying the metrics library. 256 Before the library can be used, it has to be initialised by calling [all …]
|
| /f-stack/freebsd/contrib/device-tree/src/mips/ingenic/ |
| H A D | gcw0.dts | 142 linux,can-disable; 149 linux,can-disable; 156 linux,can-disable; 163 linux,can-disable; 170 linux,can-disable; 177 linux,can-disable; 184 linux,can-disable; 191 linux,can-disable; 198 linux,can-disable; 205 linux,can-disable; [all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/fpga/ |
| H A D | xilinx-pr-decoupler.txt | 5 The controller can decouple/disable the bridges which prevents signal 6 changes from passing through the bridge. The controller can also 10 The Driver supports only MMIO handling. A PR region can have multiple 11 PR Decouplers which can be handled independently or chained via decouple/
|