| /rk3399_rockchip-uboot/board/esd/vme8349/ |
| H A D | caddy.h | 34 uint32_t issue; member
41 uint32_t issue; member
|
| H A D | caddy.c | 31 answer->issue = cmd->issue; in generate_answer()
|
| /rk3399_rockchip-uboot/arch/arm/dts/ |
| H A D | zynqmp-zc1751-xm019-dc5.dts | 47 xlnx,src-issue = <31>;
53 xlnx,src-issue = <4>; /* for testing purpose */
|
| H A D | zynqmp-zc1751-xm018-dc4.dts | 64 xlnx,src-issue = <31>;
70 xlnx,src-issue = <4>; /* for testing purpose */
|
| H A D | zynqmp-zc1751-xm016-dc2.dts | 59 xlnx,src-issue = <31>;
65 xlnx,src-issue = <4>; /* for testing purpose */
|
| H A D | zynqmp-zc1751-xm015-dc1.dts | 49 xlnx,src-issue = <31>;
55 xlnx,src-issue = <4>; /* for testing purpose */
|
| H A D | zynqmp-zcu102-revA.dts | 83 xlnx,src-issue = <31>;
89 xlnx,src-issue = <4>; /* for testing purpose */
|
| H A D | exynos5420-peach-pit.dts | 154 * fix the 30Hz no display issue
|
| H A D | exynos5250-spring.dts | 595 * display issue
|
| /rk3399_rockchip-uboot/doc/ |
| H A D | README.mips | 19 * Cache incoherency issue caused by do_bootelf_exec() at cmd_elf.c
|
| H A D | README.cfi | 7 * We do not yet know what kind of commandset to use, so we issue
|
| H A D | README.imx6 | 109 issue the command:
|
| H A D | README.generic-board | 126 the board config, which I have sent patches for. The main issue is
|
| H A D | README.usb | 206 Another way of doing this is to issue a tftp command, which will cause the
|
| H A D | README.unaligned-memory-access.txt | 162 capability, there is no issue with this code. But when the hardware isn't
|
| H A D | README.armada-secureboot | 348 chosen circuit, the issue needs to be addressed accordingly!
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/clock/ |
| H A D | nvidia,tegra20-car.txt | 21 this issue. Implementations that interpret these clock IDs as bit values
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/net/ |
| H A D | snps,dwc-qos-ethernet.txt | 110 - snps,write-requests: Number of write requests that the AXI port can issue.
112 - snps,read-requests: Number of read requests that the AXI port can issue.
|
| /rk3399_rockchip-uboot/board/sandbox/ |
| H A D | README.sandbox | 65 You can issue commands as your would normally. If the command you want is
288 With this setup you can issue SPI flash commands as normal:
|
| /rk3399_rockchip-uboot/drivers/i2c/ |
| H A D | Kconfig | 80 is no documented way to issue repeated START conditions for more than
|
| /rk3399_rockchip-uboot/board/sbc8548/ |
| H A D | README | 100 issue and allow SPD autodetection of RAM to work.
|
| /rk3399_rockchip-uboot/board/ti/am335x/ |
| H A D | README | 118 boards with multiple boot methods, recovery should not be an issue in this
|
| /rk3399_rockchip-uboot/lib/libxbc/ |
| H A D | COPYING | 58 and issue tracking systems that are managed by, or on behalf of, the
|
| /rk3399_rockchip-uboot/ |
| H A D | README | 1108 Once firmware is rebuilt from a serial console issue the
|