Searched full:can (Results 1 – 25 of 8745) sorted by relevance
12345678910>>...350
| /openbmc/qemu/docs/system/devices/ |
| H A D | can.rst | 1 CAN Bus Emulation Support
3 The CAN bus emulation provides mechanism to connect multiple
4 emulated CAN controller chips together by one or multiple CAN buses
6 can be connected to host system CAN API (at this time only Linux
9 The concept of buses is generic and different CAN controllers
10 can be implemented.
16 The PCI addon card hardware has been selected as the first CAN
17 interface to implement because such device can be easily connected
20 In 2020, CTU CAN FD controller model has been added as part
28 CAN subsystem for RTEMS. But lack of common environment for code and RTEMS
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/net/can/ |
| D | renesas,rcar-can.yaml | |
| D | allwinner,sun4i-a10-can.yaml | |
| D | st,stm32-bxcan.yaml | |
| /openbmc/linux/net/can/ |
| D | proc.c | |
| D | Makefile | |
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 083.out | 4 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
8 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
12 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
16 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
20 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
24 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
28 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
32 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
36 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
40 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
[all …]
|
| H A D | 092.out | 5 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
6 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
7 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
8 qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
12 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
13 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
14 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
15 qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
19 qemu-io: can't open device TEST_DIR/t.qcow: Image too large
20 qemu-io: can't open device TEST_DIR/t.qcow: Image too large
[all …]
|
| /openbmc/linux/include/uapi/linux/can/ |
| D | gw.h | |
| D | netlink.h | |
| /openbmc/openbmc/poky/meta/lib/oeqa/runtime/cases/ |
| H A D | parselogs-ignores-qemuall.txt | 9 # pci 0000:00:00.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
10 # pci 0000:00:00.0: [Firmware Bug]: reg 0x14: invalid BAR (can't size)
11 # pci 0000:00:00.0: [Firmware Bug]: reg 0x18: invalid BAR (can't size)
12 # pci 0000:00:00.0: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)
13 # pci 0000:00:00.0: [Firmware Bug]: reg 0x20: invalid BAR (can't size)
14 # pci 0000:00:00.0: [Firmware Bug]: reg 0x24: invalid BAR (can't size)
15 invalid BAR (can't size)
17 # pci 0000:00:00.0: [Firmware Bug]: BAR 0: invalid; can't size
18 # pci 0000:00:00.0: [Firmware Bug]: BAR 1: invalid; can't size
19 # pci 0000:00:00.0: [Firmware Bug]: BAR 2: invalid; can't size
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/rc/ |
| D | lirc-get-features.rst | |
| /openbmc/linux/include/uapi/linux/ |
| D | mii.h | |
| /openbmc/u-boot/drivers/spi/ |
| H A D | Kconfig | 31 Enable the Altera SPI driver. This driver can be used to
40 Enable the Aspeed AST2500 FMC/SPI driver. This driver can be
54 Enable the Andestech ATCSPI200 SPI driver. This driver can be
72 many AT91 (ARM) chips. This driver can be used to access
79 Enable the BCM6328 HSSPI driver. This driver can be used to
87 Enable the BCM6348/BCM6358 SPI driver. This driver can be used to
94 Enable the Broadcom set-top box SPI driver. This driver can
101 Enable the Cadence Quad-SPI (QSPI) driver. This driver can be
108 Enable the Designware SPI driver. This driver can be used to
115 Enable the Samsung Exynos SPI driver. This driver can be used to
[all …]
|
| /openbmc/linux/drivers/accessibility/speakup/ |
| D | Kconfig | |
| /openbmc/linux/fs/nls/ |
| D | Kconfig | |
| /openbmc/linux/net/netfilter/ipset/ |
| D | Kconfig | |
| /openbmc/linux/drivers/net/can/peak_canfd/ |
| D | Kconfig | |
| /openbmc/openbmc/meta-facebook/meta-bletchley/conf/templates/default/ |
| H A D | local.conf.sample | 4 # to the system might want to change but pretty much any configuration option can
5 # be set in this file. More adventurous users can look at local.conf.extended
6 # which contains other examples of configuration which can be placed in this file
23 # from various upstream projects. This can take a while, particularly if your network
25 # can preserve this directory to speed up this part of subsequent builds. This directory
36 # This is done using "shared state" files which can be thought of as cache objects
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
54 # which can use Gigabytes of hard disk space.
79 # can be enabled at once and the first item listed in the variable will be used
93 # you can build the SDK packages for architectures other than the machine you are
[all …]
|
| /openbmc/openbmc/meta-ibm/meta-romulus/conf/templates/default/ |
| H A D | local.conf.sample | 4 # to the system might want to change but pretty much any configuration option can
5 # be set in this file. More adventurous users can look at local.conf.extended
6 # which contains other examples of configuration which can be placed in this file
23 # from various upstream projects. This can take a while, particularly if your network
25 # can preserve this directory to speed up this part of subsequent builds. This directory
36 # This is done using "shared state" files which can be thought of as cache objects
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
54 # which can use Gigabytes of hard disk space.
79 # can be enabled at once and the first item listed in the variable will be used
93 # you can build the SDK packages for architectures other than the machine you are
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-catalina/conf/templates/default/ |
| H A D | local.conf.sample | 4 # to the system might want to change but pretty much any configuration option can
5 # be set in this file. More adventurous users can look at local.conf.extended
6 # which contains other examples of configuration which can be placed in this file
23 # from various upstream projects. This can take a while, particularly if your network
25 # can preserve this directory to speed up this part of subsequent builds. This directory
36 # This is done using "shared state" files which can be thought of as cache objects
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
54 # which can use Gigabytes of hard disk space.
79 # can be enabled at once and the first item listed in the variable will be used
93 # you can build the SDK packages for architectures other than the machine you are
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-tiogapass/conf/templates/default/ |
| H A D | local.conf.sample | 4 # to the system might want to change but pretty much any configuration option can
5 # be set in this file. More adventurous users can look at local.conf.extended
6 # which contains other examples of configuration which can be placed in this file
23 # from various upstream projects. This can take a while, particularly if your network
25 # can preserve this directory to speed up this part of subsequent builds. This directory
36 # This is done using "shared state" files which can be thought of as cache objects
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
54 # which can use Gigabytes of hard disk space.
79 # can be enabled at once and the first item listed in the variable will be used
93 # you can build the SDK packages for architectures other than the machine you are
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/meta-yosemite4n/conf/templates/default/ |
| H A D | local.conf.sample | 4 # to the system might want to change but pretty much any configuration option can
5 # be set in this file. More adventurous users can look at local.conf.extended
6 # which contains other examples of configuration which can be placed in this file
23 # from various upstream projects. This can take a while, particularly if your network
25 # can preserve this directory to speed up this part of subsequent builds. This directory
36 # This is done using "shared state" files which can be thought of as cache objects
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
54 # which can use Gigabytes of hard disk space.
79 # can be enabled at once and the first item listed in the variable will be used
93 # you can build the SDK packages for architectures other than the machine you are
[all …]
|
| /openbmc/openbmc/meta-ibm/meta-sbp1/conf/templates/default/ |
| H A D | local.conf.sample | 4 # to the system might want to change but pretty much any configuration option can
5 # be set in this file. More adventurous users can look at local.conf.extended
6 # which contains other examples of configuration which can be placed in this file
23 # from various upstream projects. This can take a while, particularly if your network
25 # can preserve this directory to speed up this part of subsequent builds. This directory
36 # This is done using "shared state" files which can be thought of as cache objects
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
54 # which can use Gigabytes of hard disk space.
79 # can be enabled at once and the first item listed in the variable will be used
93 # you can build the SDK packages for architectures other than the machine you are
[all …]
|
| /openbmc/openbmc/meta-hpe/meta-dl360poc/conf/templates/default/ |
| H A D | local.conf.sample | 4 # to the system might want to change but pretty much any configuration option can
5 # be set in this file. More adventurous users can look at local.conf.extended
6 # which contains other examples of configuration which can be placed in this file
23 # from various upstream projects. This can take a while, particularly if your network
25 # can preserve this directory to speed up this part of subsequent builds. This directory
36 # This is done using "shared state" files which can be thought of as cache objects
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
54 # which can use Gigabytes of hard disk space.
79 # can be enabled at once and the first item listed in the variable will be used
93 # you can build the SDK packages for architectures other than the machine you are
[all …]
|
12345678910>>...350