Home
last modified time | relevance | path

Searched refs:an (Results 1 – 25 of 316) sorted by relevance

12345678910>>...13

/rk3399_rockchip-uboot/drivers/video/bridge/
H A DKconfig7 requires LVDS, an eDP->LVDS bridge chip can be used to provide the
15 differential signalling) converters. They enable an LVDS LCD panel
16 to be connected to an eDP output device such as an SoC that lacks
25 signalling) converter. It enables an LVDS LCD panel to be connected
26 to an eDP output device such as an SoC that lacks LVDS capability,
34 The Analogix ANX6345 is RGB-to-DP converter. It enables an eDP LCD
35 panel to be connected to an parallel LCD interface.
/rk3399_rockchip-uboot/doc/device-tree-bindings/gpu/
H A Dnvidia,tegra20-host1x.txt9 - #size-cells: The number of cells used to represent the size of an address
14 - resets: Must contain an entry for each entry in reset-names.
30 - resets: Must contain an entry for each entry in reset-names.
43 - resets: Must contain an entry for each entry in reset-names.
56 - resets: Must contain an entry for each entry in reset-names.
69 - resets: Must contain an entry for each entry in reset-names.
82 - resets: Must contain an entry for each entry in reset-names.
92 - clocks: Must contain an entry for each entry in clock-names.
99 - resets: Must contain an entry for each entry in reset-names.
111 - clocks: Must contain an entry for each entry in clock-names.
[all …]
/rk3399_rockchip-uboot/drivers/sound/
H A DKconfig6 Support making sounds through an audio codec. This is normally a
28 Samsung Exynos SoCs support an I2S interface for sending audio
29 data to an audio codec. This option enables support for this,
31 option provides an implementation for sound_init() and
38 Rockchip SoCs support an I2S interface for sending audio
39 data to an audio codec. This option enables support for this,
41 option provides an implementation for sound_init() and
/rk3399_rockchip-uboot/doc/
H A DREADME.xtensa16 There are an effectively infinite number of CPUs in the Xtensa
21 In the same manner as the Linux port to Xtensa, U-Boot adapts to an
29 Adding support for an additional processor configuration
62 an 'entry' at the beginning of a function, which rotates the register
63 file and reserves a stack frame. This is an integral part of the
64 windowed ABI implemented in hardware. It makes using a jump table to an
82 addresses: an area of physical address space may not be mapped to RAM
83 or peripherals, or in the presence of MMU an area of virtual address
87 reading of meaningless data, written data being ignored or an exception,
89 invalid addresses always ends with an exception.
H A DREADME.imx513 condition in an analog flip-flop when used at high frequencies.
14 This workaround implements an undocumented feature in the PLL (dither
30 This is an example how to program an example MAC address 01:23:45:67:89:ab
H A DREADME.displaying-bmps4 Some architectures cannot handle unaligned memory accesses, and an attempt to
8 always the case when dealing with data that has an internal layout such as a
23 When placed in an aligned address such as 0x80a00000, char signature offsets
H A DREADME.sata48 1.3 How to load an image from an ext2 file system in U-Boot?
50 U-Boot doesn't support writing to an ext2 file system, so the
H A DREADME.nvme24 to a SCSI LUN. Each namespace is operated as an independent "device".
28 There is an NVMe uclass driver (driver name "nvme"), an NVMe host controller
29 driver (driver name "nvme") and an NVMe namespace block driver (driver name
47 To use an NVMe hard disk from U-Boot shell, a 'nvme scan' command needs to
H A DREADME.unaligned-memory-access.txt13 The definition of an unaligned access
17 from an address that is not evenly divisible by N (i.e. addr % N != 0).
19 reading 4 bytes of data from address 0x10005 would be an unaligned memory
49 The effects of performing an unaligned memory access vary from architecture
87 Let us assume that an instance of the above structure resides in memory
89 not be unreasonable to expect that accessing field2 would cause an unaligned
105 will never cause an unaligned access, because all memory addresses are evenly
143 that can cause an unaligned memory access. The following function taken
144 from the Linux Kernel's include/linux/etherdevice.h is an optimized routine
166 Think about what would happen if addr1 was an odd address such as 0x10003.
[all …]
H A DREADME.efi32 as an application or just as a means of getting U-Boot onto a new platform.
43 - You need to use an EFI implementation (e.g. UEFI) because your vendor
59 U-Boot supports running as an EFI application for 32-bit EFI only. This is
71 First choose a board that has EFI support and obtain an EFI implementation
75 To build U-Boot as an EFI application (32-bit EFI required), enable CONFIG_EFI
82 To build U-Boot as an EFI payload (32-bit or 64-bit EFI can be used), adjust an
98 QEMU is an emulator and it can emulate an x86 machine. Please make sure your
120 EFI (or vice versa). Also it will often fail to print an error message if
187 present this feature is used to pass the EFI memory map, an inordinately
203 it is possible that an interrupt will fire that U-Boot cannot handle. This
[all …]
H A DREADME.rockchip94 Booting from an SD card
97 To write an image that boots from an SD card (assumed to be /dev/sdc):
128 The rockchip bootrom can load and boot an initial spl, then continue to
142 If you have an HDMI cable attached you should see a video console.
153 Booting from an SD card on RK3288 with TPL
164 To write an image that boots from an SD card (assumed to be /dev/mmcblk0):
171 Booting from an SD card on RK3188
224 To write an image that boots from SPI flash (e.g. for the Haier Chromebook):
286 rkimage.c produces an SPL image suitable for sending directly to the boot ROM
296 rksd.c produces an image consisting of 32KB of empty space, a header and
[all …]
H A DREADME.ti-secure34 Within the SECDEV package exists an image creation script:
55 SPI_X-LOADER - Generates an image for SPI flash (byte swapped)
56 X-LOADER - Generates an image for non-XIP flash
57 MLO - Generates an image for SD/MMC/eMMC media
58 2ND - Generates an image for USB, UART and Ethernet
87 SPI_X-LOADER - Generates an image for SPI flash (byte
91 ISSW - Generates an image for all other boot modes
116 X-LOADER - Generates an image for NOR or QSPI boot modes
117 MLO - Generates an image for SD/MMC/eMMC boot modes
118 ULO - Generates an image for USB/UART peripheral boot modes
[all …]
H A DREADME.usb31 started after the U-Boot is up and running. To boot an OS with a an
44 an USB keyboard is assigned as stdin. The stdin
72 to obtain an IP address and load a kernel from a network server.
75 client. In that case your board is pretending to be an Ethernet adapter
76 and will appear as a network interface to an attached computer. In that
81 the outside world is your adapter's Ethernet cable. Your board becomes an
182 You can see that it found an ethernet device and we can print out the
185 Then 'bootp' or 'dhcp' should use it to obtain an IP address from DHCP,
219 have an assigned MAC address. In this case it is up to you to assign
224 an ethaddr environment variable for each interface (ethaddr, eth1addr,
/rk3399_rockchip-uboot/lib/efi/
H A DKconfig7 final system boot. Another option is to run U-Boot as an EFI
15 bool "Support running as an EFI application"
17 Build U-Boot as an application which can be started from EFI. This
24 bool "Support running as an EFI payload"
/rk3399_rockchip-uboot/board/logicpd/imx6/
H A DREADME6 Logic PD has an i.MX6 System On Module (SOM) and a correspondong development
8 an SMSC Ethernet PHY, serial debug port and a variety of peripherals.
10 On the intial release, the SOM came with either an i.MX6D or i.MX6Q.
/rk3399_rockchip-uboot/board/freescale/mpc8323erdb/
H A DREADME27 N.b, have an alternate means of programming
35 an erase goes ahead and wipes out your current firmware.
61 want an NFS root or a ramdisk root:
/rk3399_rockchip-uboot/tools/binman/
H A DREADME10 For example, we may have SPL, U-Boot, a device tree and an environment area
15 general way. Each SoC does what it needs to build an image, often packing or
28 to read an image and extract its constituent parts.
92 - image - an output file containing a firmware image
93 - binary - an input binary that goes into the image
103 FIT was originally designed to support booting a Linux kernel (with an
112 execution (since FIT itself does not have an executable header) and dealing
124 needed an image description file: a device tree, like binman, but in a
134 which it can place in an image. Binman does not replace the mkimage tool or
150 1. It uses a custom mksunxiboot tool to build an SPL image called
[all …]
/rk3399_rockchip-uboot/doc/device-tree-bindings/
H A Dchosen.txt48 In a system using an SPL stage and having multiple boot sources
50 device may be probed by reading the image and verifying an image
57 path or an alias is expected for each entry.
64 Note that if "same-as-spl" expands to an actual node for a given
/rk3399_rockchip-uboot/board/sunxi/
H A DREADME.sunxi6416 - Transfer to an uSD card (see "microSD card" below)
22 The Allwinner A64/H5 firmware consists of three parts: U-Boot's SPL, an
68 controller, typically an on-board eMMC chip. If there is no eMMC or it does
91 Transfer the SPL and the U-Boot FIT image directly to an uSD card:
112 Now connect either an "A to A" USB cable to the upper USB port on the Pine64
113 or get an adaptor and use a regular A-microB cable connected to it. Other
119 This should give you an output starting with: AWUSBFEX soc=00001689(A64) ...
123 Now boot the board without an SD card inserted and you should see the
129 of SPL replacement to get U-Boot up and running from an microSD card.
134 A64 based boards, the H5 uses an incompatible layout which is not supported
[all …]
/rk3399_rockchip-uboot/fs/fat/
H A DKconfig13 This provides support for creating and writing new files to an
23 file. Unless you have an extremely tight memory memory constraints,
/rk3399_rockchip-uboot/board/bachmann/ot1200/
H A DREADME8 FEC is connected directly to an ethernet switch (KSZ8895). The ethernet
20 are making use of EDID data stored in an i2c EEPROM.
/rk3399_rockchip-uboot/doc/device-tree-bindings/pinctrl/
H A Dpinctrl-bindings.txt20 The common pinctrl bindings defined in this file provide an infrastructure
35 For each client device individually, every pin state is assigned an integer
59 used in an SoC either without a pin controller, or where the
90 * For an IP block whose binding supports pin configuration,
91 * but in use on an SoC that doesn't have any pin control hardware
168 settings represented as a single integer or an array of integers.
170 The pinmux property accepts an array of pinmux groups, each of them describing
216 enabling an input buffer)
218 disabling an input buffer)
225 output-disable - disable output on a pin (such as disable an output
[all …]
/rk3399_rockchip-uboot/scripts/dtc/pylibfdt/
H A Dlibfdt.i_shipped41 # altogether. All # functions passed this value will return an error instead
42 # of raising an exception.
45 # instead of raising an exception.
50 """An exception caused by an error such as one of the codes above"""
58 """Get the string for an error number
69 """Raise an error if the return value is -ve
89 """Raise an error if the return value is NULL
102 FdtException if val indicates an error was reported and the error
106 # If we get just an integer error code, it means the function failed.
123 All methods raise an FdtException if an error occurs. To avoid this
[all …]
/rk3399_rockchip-uboot/drivers/timer/
H A DKconfig18 function. This enables the drivers in drivers/timer as part of an
27 function. This enables the drivers in drivers/timer as part of an
37 use an early timer. These functions must be supported by your timer
59 Select this to enable an emulated timer for sandbox. It gets
72 Select this to enable an timer for Omap devices.
/rk3399_rockchip-uboot/common/spl/
H A DKconfig303 drivers in drivers/cpu as part of an SPL build.
310 this option to build the drivers in drivers/crypto as part of an
318 this option to build the drivers in drivers/keylad as part of an
329 as part of an SPL build.
337 in drivers/dma as part of an SPL build.
344 option to build the drivers in drivers/misc as part of an SPL
348 bool "Support an environment"
378 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
379 link rather than from an on-board peripheral. Environment support
387 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
[all …]

12345678910>>...13