| /linux/arch/m68k/math-emu/ |
| H A D | fp_decode.h | 112 | extract the addressing mode 128 | extract the register for the addressing mode 214 | addressing mode: data register direct 220 | addressing mode: address register indirect 244 | addressing mode: address register indirect with postincrement 263 | addressing mode: address register indirect with predecrement 289 | addressing mode: address register/programm counter indirect 331 | all other indirect addressing modes will finally end up here 345 | addressing mode: address register/programm counter indirect 355 3: | addressing mode: address register/programm counter memory indirect
|
| H A D | fp_scan.S | 133 | decode addressing mode for source 141 | addressing mode: data register direct 171 | addressing mode: address register indirect 176 | addressing mode: address register indirect with postincrement 181 | addressing mode: address register indirect with predecrement 186 | addressing mode: address register/programm counter indirect 192 | all other indirect addressing modes will finally end up here 197 | all pc relative addressing modes and immediate/absolute modes end up here 211 | addressing mode: absolute short 216 | addressing mode: absolute long [all …]
|
| H A D | fp_move.S | 64 | encode addressing mode for dest 72 | addressing mode: data register direct 135 | addressing mode: address register indirect 140 | addressing mode: address register indirect with postincrement 145 | addressing mode: address register indirect with predecrement 150 | addressing mode: address register indirect with 16bit displacement
|
| H A D | fp_movem.S | 88 | addressing mode: address register indirect 93 | addressing mode: address register indirect with postincrement 102 | addressing mode: address register/programm counter indirect
|
| H A D | fp_cond.S | 105 | decode addressing mode 113 | addressing mode: data register direct
|
| /linux/Documentation/filesystems/ |
| H A D | qnx6.rst | 56 data and the addressing levels in that specific tree. 60 Level 1 adds an additional indirect addressing level where each indirect 61 addressing block holds up to blocksize / 4 bytes pointers to data blocks. 62 Level 2 adds an additional indirect addressing block level (so, already up 66 indirect addressing blocks or inodes. 97 For more than 16 blocks an indirect addressing in form of another tree is 143 Long filenames are stored in a separate addressing tree. The staring point 165 smaller than addressing space in the bitmap. 183 Bitmap blocks, Inode blocks and indirect addressing blocks for those two
|
| /linux/Documentation/networking/ |
| H A D | iso15765-2.rst | 29 In its simplest form, ISO-TP is based on two kinds of addressing modes for the 32 * physical addressing is implemented by two node-specific addresses and is used 35 * functional addressing is implemented by one node-specific address and is used 38 Three different addressing formats can be employed: 55 is generating and the optional extended addressing. In the first case, the data 163 additional address component. This enables the "mixed" addressing format if 164 used alone, or the "extended" addressing format if used in conjunction with 191 as extended addressing byte on the reception path. If used in conjunction 193 addressing format. 198 * ``CAN_ISOTP_SF_BROADCAST``: use 1-to-N functional addressing (cannot be [all …]
|
| /linux/Documentation/scsi/ |
| H A D | aha152x.rst | 126 The BIOS uses a cylinder/head/sector addressing scheme (C/H/S) 128 C/H/S addressing. 131 as base for requests in C/H/S addressing. SCSI only knows about the 135 geometry just to be able to support that addressing scheme. The geometry 141 instead of C/H/S addressing. Unfortunately C/H/S addressing is also used 145 Moreover there are certain limitations to the C/H/S addressing scheme,
|
| H A D | ChangeLog.sym53c8xx_2 | 105 - Add infrastructure for the forthcoming 64 bit DMA addressing support. 111 - Add support for 64 bit DMA addressing using segment registers.
|
| /linux/Documentation/arch/x86/x86_64/ |
| H A D | fsgs.rst | 7 memory can use segment register based addressing mode. The following 38 applications. GCC and Clang support GS based addressing via address space 85 more flexible usage of the FS/GS addressing modes in user space 141 Compiler support for FS/GS based addressing 144 GCC version 6 and newer provide support for FS/GS based addressing via 189 FS/GS based addressing with inline assembly 193 be used for FS/GS based addressing mode::
|
| /linux/arch/arm/boot/dts/ti/omap/ |
| H A D | omap4-cpu-thermal.dtsi | 16 * See 44xx files for single sensor addressing, omap5 and dra7 need 17 * also sensor ID for addressing.
|
| /linux/Documentation/driver-api/serial/ |
| H A D | serial-rs485.rst | 110 The Linux kernel provides addressing mode for multipoint RS-485 serial 111 communications line. The addressing mode is enabled with 117 - ``SER_RS485_ADDRB``: Enabled addressing mode (sets also ADDRB in termios). 130 Note: not all devices supporting RS485 support multipoint addressing.
|
| /linux/drivers/memory/ |
| H A D | emif.c | 298 static u32 get_zq_config_reg(const struct lpddr2_addressing *addressing, in get_zq_config_reg() argument 303 val = EMIF_ZQCS_INTERVAL_US * 1000 / addressing->tREFI_ns; in get_zq_config_reg() 327 static u32 get_temp_alert_config(const struct lpddr2_addressing *addressing, in get_temp_alert_config() argument 340 interval /= addressing->tREFI_ns; /* Convert to refresh cycles */ in get_temp_alert_config() 708 const struct lpddr2_addressing *addressing; in emif_onetime_settings() local 712 addressing = get_addressing_table(device_info); in emif_onetime_settings() 725 zq = get_zq_config_reg(addressing, device_info->cs1_used, in emif_onetime_settings() 735 temp_alert_cfg = get_temp_alert_config(addressing, in emif_onetime_settings()
|
| /linux/arch/sh/mm/ |
| H A D | Kconfig | 78 # Physical addressing modes 89 bool "Support 32-bit physical addressing through PMB" 94 If you say Y here, physical addressing will be extended to 96 29-bit physical addressing will be used.
|
| /linux/drivers/media/dvb-frontends/drx39xyj/ |
| H A D | drx_dap_fasi.h | 98 #error At least one of short- or long-addressing format must be allowed.
|
| /linux/arch/alpha/lib/ |
| H A D | ev6-memset.S | 84 subq $3,8,$3 # E : Invert (for addressing uses) 262 subq $3,8,$3 # E : Invert (for addressing uses) 450 subq $3,8,$3 # E : Invert (for addressing uses)
|
| /linux/arch/mips/sgi-ip27/ |
| H A D | Kconfig | 3 prompt "Node addressing mode"
|
| /linux/arch/s390/boot/ |
| H A D | head_kdump.S | 25 sam64 # Switch to 64 bit addressing
|
| /linux/Documentation/networking/device_drivers/ethernet/google/ |
| H A D | gve.rst | 57 GVE supports two addressing modes: QPL and RDA. 61 For RDA ("raw DMA addressing") mode, the set of pages is dynamic.
|
| /linux/arch/powerpc/platforms/ |
| H A D | Kconfig.cputype | 467 instructions that include large immediate, pc relative addressing, 471 allows a pc relative addressing option to be selected. 482 bool "Build Kernel with PC-Relative addressing model" 484 POWER10 and later CPUs support pc relative addressing. Recent
|
| /linux/arch/m68k/ |
| H A D | Kconfig | 87 Select if you want MMU-based virtualised addressing space
|
| /linux/tools/testing/selftests/arm64/signal/ |
| H A D | README | 40 be really sure that the tests are really addressing what they are meant
|
| /linux/Documentation/tee/ |
| H A D | ts-tee.rst | 24 an "interface ID". This is just a short ID to simplify message addressing.
|
| /linux/Documentation/arch/arm/ |
| H A D | memory.rst | 13 The ARM CPU is capable of addressing a maximum of 4GB virtual memory
|
| /linux/Documentation/security/ |
| H A D | SCTP.rst | 334 6) CIPSO is only supported for IPv4 addressing: ``socket(AF_INET, ...)`` 335 CALIPSO is only supported for IPv6 addressing: ``socket(AF_INET6, ...)``
|