Searched refs:issue (Results 1 – 25 of 29) sorted by relevance
12
/u-boot/board/esd/vme8349/ |
A D | caddy.h | 33 uint32_t issue; member 40 uint32_t issue; member
|
A D | caddy.c | 31 answer->issue = cmd->issue; in generate_answer()
|
/u-boot/arch/arm/dts/ |
A D | rk3328-roc-cc-u-boot.dtsi | 58 * around an issue where either XHCI only works with USB 2.0 or OTG doesn't
|
A D | rk3328-rock64-u-boot.dtsi | 58 * around an issue where either XHCI only works with USB 2.0 or OTG doesn't
|
A D | exynos5420-peach-pit.dts | 169 * fix the 30Hz no display issue
|
A D | imx6dl-b1x5v2.dts | 51 * documented dependencies for it's speaker supply pin. The issue
|
A D | exynos5250-spring.dts | 646 * display issue
|
/u-boot/doc/usage/ |
A D | button.rst | 18 status of a button with name 'button1' you would issue the command
|
A D | mbr.rst | 53 text description one has to issue following command (assuming that
|
/u-boot/doc/arch/ |
A D | mips.rst | 18 * Cache incoherency issue caused by do_bootelf_exec() at cmd_elf.c
|
A D | sandbox.rst | 76 You can issue commands as your would normally. If the command you want is 359 With this setup you can issue SPI flash commands as normal::
|
/u-boot/doc/ |
A D | README.cfi | 7 * We do not yet know what kind of commandset to use, so we issue
|
A D | README.generic-board | 124 the board config, which I have sent patches for. The main issue is
|
A D | README.usb | 205 Another way of doing this is to issue a tftp command, which will cause the
|
A D | README.unaligned-memory-access.txt | 162 capability, there is no issue with this code. But when the hardware isn't
|
/u-boot/doc/device-tree-bindings/clock/ |
A D | nvidia,tegra20-car.txt | 21 this issue. Implementations that interpret these clock IDs as bit values
|
/u-boot/doc/device-tree-bindings/net/ |
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.
|
/u-boot/doc/imx/misc/ |
A D | sdp.txt | 116 issue the command:
|
/u-boot/doc/device-tree-bindings/ram/ |
A D | fsl,mpc83xx-mem-controller.txt | 102 - last_write_data_to_read: Last write data pair to read command issue
|
/u-boot/drivers/net/phy/ |
A D | Kconfig | 249 issue in U-Boot on reboot if the PHY retains the register value.
|
/u-boot/board/sbc8548/ |
A D | README | 100 issue and allow SPD autodetection of RAM to work.
|
/u-boot/board/ti/am335x/ |
A D | README | 118 boards with multiple boot methods, recovery should not be an issue in this
|
/u-boot/doc/board/google/ |
A D | chromebook_coral.rst | 87 known issue with Intel SoCs with modern DRAM and apparently cannot be improved.
|
/u-boot/drivers/mmc/ |
A D | Kconfig | 775 bool "enable eSDHC workaround for 3.3v IO reliability issue" 781 runs, the more damage accumulates. This issue now is found on LX2160A
|
/u-boot/drivers/i2c/ |
A D | Kconfig | 90 is no documented way to issue repeated START conditions for more than
|
Completed in 48 milliseconds
12