Home
last modified time | relevance | path

Searched refs:ROM (Results 1 – 25 of 306) sorted by relevance

12345678910>>...13

/openbmc/u-boot/board/synopsys/iot_devkit/
H A Du-boot.lds10 ROM : ORIGIN = ROM_BASE, LENGTH = ROM_SIZE
26 } > ROM
34 } > ROM
39 } > ROM
48 } > ROM
56 * copied from ROM to RAM in board_early_init_f().
63 } > RAM AT > ROM
/openbmc/linux/Documentation/cdrom/
H A Dcdrom-standard.rst2 A Linux CD-ROM standard
44 When the CD-ROM was developed, the interface between the CD-ROM drive
99 help CD-ROM driver developers adapt their code to use the Uniform CD-ROM
128 low-level CD-ROM device drivers. The Uniform CD-ROM Driver now provides another
190 Registering a particular CD-ROM drive with the Uniform CD-ROM Driver
236 CD-ROM hardware and/or low-level CD-ROM driver when a CD-ROM drive
527 CD-ROM capabilities
641 *O_SYNC* have no meaning to a CD-ROM.
749 Uniform CD-ROM Driver::
926 entirely in Uniform CD-ROM Driver.
[all …]
/openbmc/u-boot/doc/
H A DREADME.sh7752evb12 - SPI ROM 8MB
35 You can write MAC address to SPI ROM.
57 Update SPI ROM:
64 3. Erase SPI ROM.
66 4. Write u-boot image to SPI ROM.
H A DREADME.sh7753evb12 - SPI ROM 8MB
35 You can write MAC address to SPI ROM.
57 Update SPI ROM:
64 3. Erase SPI ROM.
66 4. Write u-boot image to SPI ROM.
H A DREADME.ag101p22 If you want to boot this system from SPI ROM and bypass e-bios (the
23 other boot loader on ROM). You should undefine CONFIG_SKIP_LOWLEVEL_INIT
33 Burn u-boot to SPI ROM:
/openbmc/u-boot/arch/xtensa/cpu/
H A Du-boot.lds17 * U-Boot resets from SYSROM and unpacks itself from a ROM store to RAM.
19 * above it for the ROM store into which the rest of U-Boot is packed.
20 * The ROM store also needs to be above any other vectors that are in ROM.
21 * If a core has its vectors near the top of ROM, this must be edited.
23 * Note that to run C code out of ROM, the processor would have to support
28 * other means (serial ROM, for example) or are initialized early (requiring
91 * On many Xtensa boards a region of RAM may be mapped to the ROM address
105 "U-Boot ROM image is too large. Check optimization level.")
/openbmc/u-boot/board/renesas/sh7757lcr/
H A DREADME.sh7757lcr12 - SPI ROM 8MB
43 You can write MAC address to SPI ROM.
67 Update SPI ROM:
74 3. Erase SPI ROM.
76 4. Write u-boot image to SPI ROM.
/openbmc/linux/fs/isofs/
H A DKconfig10 driver. If you have a CD-ROM drive and want to do more with it than
12 <file:Documentation/filesystems/isofs.rst> and the CD-ROM-HOWTO,
24 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
37 data in compressed form on a CD-ROM and have it transparently
38 decompressed when the CD-ROM is accessed. See
/openbmc/linux/Documentation/devicetree/bindings/rng/
H A Dti,omap-rom-rng.yaml7 title: OMAP ROM Random Number Generator
14 Secure SoCs may provide RNG via secure ROM calls like Nokia N900 does.
15 The implementation can depend on the SoC secure ROM used.
/openbmc/u-boot/arch/arm/mach-k3/
H A DKconfig20 specify the total size of SPL as ROM can use some part
21 of this RAM. Once ROM gives control to SPL then this
28 Describes the maximum size of the image that ROM can download
47 Address at which ROM stores the value which determines if SPL
/openbmc/u-boot/board/synopsys/emsdp/
H A DREADME44 * 256 KiB of "ROM"
45 - This so-called "ROM" is a part of FPGA image and even though it
65 3. To build binary image to be put in "ROM":
73 1. The EMSDP board is supposed to auto-start U-Boot image stored in ROM on
77 in "ROM" and start it from the debugger. One important note here we first
78 need to enable writes into "ROM" by writing 1 to 0xf0001000.
/openbmc/u-boot/arch/arm/mach-omap2/
H A Dlowlevel_init.S53 push {r4-r12, lr} @ save registers - ROM code may pollute
61 @ call ROM Code API for the service requested
66 push {r4-r12, lr} @ save registers - ROM code may pollute
/openbmc/qemu/scripts/coccinelle/
H A Dmemory-region-housekeeping.cocci51 // Do not call memory_region_set_readonly() on ROM alias
53 expression ROM, E1, E2, E3, E4;
57 memory_region_init_rom(ROM, E1, E2, E3, E4);
59 memory_region_init_rom_nomigrate(ROM, E1, E2, E3, E4);
62 memory_region_init_alias(ALIAS, E5, E6, ROM, E7, E8);
/openbmc/linux/Documentation/networking/devlink/
H A Dsfc.rst52 - Expansion ROM version. For boards where the expansion ROM is split between
54 ROM version.
/openbmc/qemu/docs/system/arm/
H A Dsx1.rst9 - ROM and RAM memories (ROM firmware image can be loaded with
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/OperatingSystem/
H A DStatus.interface.yaml27 CD-ROM Boot completed.
30 ROM Boot Completed
/openbmc/linux/arch/m68k/
H A DKconfig.machine433 comment "ROM configuration"
435 config ROM config
436 bool "Specify ROM linker regions"
443 hex "Address of the base of the ROM vectors"
445 depends on ROM
452 hex "Address of the base of system image in ROM"
454 depends on ROM
457 is strait after the ROM vectors.
470 bool "ROM"
471 depends on ROM
[all …]
/openbmc/linux/Documentation/admin-guide/
H A Ddevices.txt391 11 block SCSI CD-ROM devices
463 16 block GoldStar CD-ROM
464 0 = /dev/gscd GoldStar CD-ROM
470 17 block Optics Storage CD-ROM
477 18 block Sanyo CD-ROM
478 0 = /dev/sjcd Sanyo CD-ROM
492 0 = /dev/hitcd Hitachi CD-ROM
528 0 = /dev/mcd Mitsumi CD-ROM
543 24 block Sony CDU-535 CD-ROM
639 0 = /dev/aztcd Aztech CD-ROM
[all …]
/openbmc/linux/fs/romfs/
H A DKconfig3 tristate "ROM file system support"
30 bool "Block device-backed ROM file system support"
40 bool "MTD-backed ROM file system support"
/openbmc/linux/arch/powerpc/platforms/ps3/
H A DKconfig126 tristate "PS3 BD/DVD/CD-ROM Storage Driver"
130 Include support for the PS3 ROM Storage.
132 This support is required to access the PS3 BD/DVD/CD-ROM drive.
137 tristate "PS3 FLASH ROM Storage Driver"
141 Include support for the PS3 FLASH ROM Storage.
143 This support is required to access the PS3 FLASH ROM, which
/openbmc/qemu/docs/system/ppc/
H A Damigang.rst32 The ROM image is in the last 512kB which can be extracted with the
85 The Pegasos II board has an Open Firmware compliant ROM based on
87 the ROM binary cannot be included in QEMU. An updater was available
90 The ROM image can be extracted from it with the following command:
112 firmware ROM using the QEMU built-in minimal Virtual Open Firmware
134 modifications to support booting AmigaOS 4. The firmware ROM is
/openbmc/linux/fs/cramfs/
H A DKconfig3 tristate "Compressed ROM file system support (cramfs)"
6 Saying Y here includes support for CramFs (Compressed ROM File
8 file system for ROM based embedded systems. CramFs is read-only,
/openbmc/u-boot/doc/SPL/
H A DREADME.am335x-network4 have support for booting via network in ROM. The following describes
49 Identifier (VCI) set by BOOTP client (RBL sets VCI to "DM814x ROM v1.0"
60 if substring (option vendor-class-identifier, 0, 10) = "DM814x ROM" {
69 May the ROM bootloader sends another "vendor-class-identifier"
71 "AM335x ROM"
/openbmc/u-boot/board/ti/am65x/
H A DREADME20 On AM65x family devices, ROM supports boot only via MCU(R5). This means that
40 | | *ROM* |----------|-->| Reset rls | | |
43 | | ROM | | : | |
46 | | | | | *R5 ROM* | | |
/openbmc/linux/Documentation/ABI/stable/
H A Dfirewire-cdev21 - Get the Configuration ROM
46 nodes' Configuration ROM
54 nodes' Configuration ROM
104 nodes' Configuration ROM. Deallocate isochronous channels and

12345678910>>...13