Searched full:magic (Results 1 – 25 of 129) sorted by relevance
123456
| /Documentation/staging/ |
| D | magic-number.rst | 3 Linux magic numbers
6 This file is a registry of magic numbers which are in use. When you
7 add a magic number to a structure, you should also add it to this
8 file, since it is best if the magic numbers used by various structures
11 It is a **very** good idea to protect kernel data structures with magic
19 The way to use magic numbers is to declare them at the beginning of
23 int magic;
38 The magic table is current to Linux 2.1.55.
53 Updated the magic table to Linux 2.5.45. Right over the feature freeze,
54 but it is possible that some new magic numbers will sneak into the
[all …]
|
| D | index.rst | 11 magic-number
|
| /Documentation/translations/zh_CN/arch/riscv/ |
| D | boot-image-header.rst | 33 u64 magic = 0x5643534952; /* Magic number, little endian, "RISCV" */
34 u32 magic2 = 0x05435352; /* Magic number 2, little endian, "RSC\x05" */
58 - 从版本0.2开始，结构体成员“magic”就已经被弃用，在之后的版本中，可能会移除掉它。
59 最初，该成员应该与ARM64头的“magic”成员匹配，但遗憾的是并没有。
60 “magic2”成员代替“magic”成员与ARM64头相匹配。
|
| /Documentation/devicetree/bindings/misc/ |
| D | xlnx,tmr-inject.yaml | 26 xlnx,magic:
30 Magic number, When configured it allows the controller to perform
37 - xlnx,magic
46 xlnx,magic = <0x46>;
|
| /Documentation/arch/riscv/ |
| D | boot-image-header.rst | 20 u64 magic = 0x5643534952; /* Magic number, little endian, "RISCV" */
21 u32 magic2 = 0x05435352; /* Magic number 2, little endian, "RSC\x05" */
34 with "MZ" magic string and res3(at offset 0x3c) points to the rest of the
47 - The "magic" field is deprecated as of version 0.2. In a future
49 with the ARM64 header "magic" field, but unfortunately does not.
|
| /Documentation/virt/kvm/ |
| D | ppc-pv.rst | 70 The magic page
77 With this hypercall issued the guest always gets the magic page mapped at the
82 instruction reads the first field of the magic page::
87 additional registers to the magic page. If you add fields to the magic page,
91 The magic page layout is described by struct kvm_vcpu_arch_shared
94 Magic page features
97 When mapping the magic page using the KVM hypercall KVM_HC_PPC_MAP_MAGIC_PAGE,
99 a bitmap of available features inside the magic page.
101 The following enhancements to the magic page are currently available:
104 KVM_MAGIC_FEAT_SR Maps SR registers r/w in the magic page
[all …]
|
| /Documentation/admin-guide/ |
| D | binfmt-misc.rst | 10 at the beginning of the file with a magic byte sequence (masking out specified
19 ``:name:type:offset:magic:mask:interpreter:flags`` (where you can choose the
29 is the type of recognition. Give ``M`` for magic and ``E`` for extension.
31 is the offset of the magic/mask in the file, counted in bytes. This
32 defaults to 0 if you omit it (i.e. you write ``:name:type::magic...``).
34 - ``magic``
35 is the byte sequence binfmt_misc is matching for. The magic string
45 bits from matching by supplying a string like magic and as long as magic.
96 - the magic must reside in the first 128 bytes of the file, i.e.
97 offset+size(magic) has to be less than 128
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-ubifs | 6 Exposes magic errors: every node starts with a magic number.
9 with a corrupted magic number.
|
| D | sysfs-bus-event_source-devices-format | 6 Attribute group to describe the magic bits that go into
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,trx.txt | 33 - brcm,trx-magic: TRX magic, if it is different from the default magic
|
| D | brcm,bcm947xx-cfe-partitions.yaml | 16 header and/or magic signature at the beginning of each of them. They are also
19 Most of partitions use ASCII text based magic for determining a type. More
20 complex partitions (like TRX with its HDR0 magic) may include extra header
|
| /Documentation/filesystems/xfs/ |
| D | xfs-self-describing-metadata.rst | 44 magic number in the metadata block, we have no other way of identifying what it
70 Luckily, almost all XFS metadata has magic numbers embedded already - only the
72 magic numbers. Hence we can change the on-disk format of all these objects to
73 add more identifying information and detect this simply by changing the magic
74 numbers in the metadata objects. That is, if it has the current magic number,
75 the metadata isn't self identifying. If it contains a new magic number, it is
175 The first step in read verification is checking the magic number and determining
195 __be32 magic; /* magic number */
216 - directory/attribute node blocks have a 16 bit magic number, and the
217 header that contains the magic number has other information in it as
[all …]
|
| /Documentation/arch/arm/samsung/ |
| D | bootloader-interface.rst | 27 0x0c 0x00000bad (Magic cookie) System suspend
30 0x20 0xfcba0d10 (Magic cookie) AFTR
32 0x28 + 4*cpu 0x8 (Magic cookie, Exynos3250) AFTR
48 0x24 0xfcba0d10 (Magic cookie, Exynos4210 r1.0) AFTR
58 0x0804 0xfcba0d10 (Magic cookie) AFTR
59 0x0804 0x00000bad (Magic cookie) System suspend
61 0x0818 0xfcba0d10 (Magic cookie, Exynos4210 r1.1) AFTR
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | reboot-mode.yaml | 14 interface to store the magic value in special register
20 as mode-xxx = <magic> (xxx is mode name, magic should be a non-zero value).
|
| D | nvmem-reboot-mode.yaml | 13 This driver gets the reboot mode magic value from the reboot-mode driver
24 magic value representing the reboot mode is stored.
|
| D | syscon-reboot-mode.yaml | 13 This driver gets reboot mode magic value from reboot-mode driver
15 can read it and take different action according to the magic
|
| /Documentation/power/ |
| D | s2ram.rst | 45 Magic number: 4:156:725
69 pm_trace uses the system's Real Time Clock (RTC) to save the magic number.
79 clock will have a value corresponding to the magic number instead of the
87 corrupt the magic value.
|
| /Documentation/devicetree/bindings/firmware/ |
| D | coreboot.txt | 13 parameters. It is identified by the magic string "LBIO" in its first
20 is identified by a root node descriptor with the magic number
|
| /Documentation/userspace-api/media/drivers/ |
| D | cx2341x-uapi.rst | 149 for a bitmask determining which lines are captured and 4 bytes for a magic cookie,
152 two different magic numbers were introduced:
154 'itv0': After this magic number two unsigned longs follow. Bits 0-17 of the first
159 'ITV0': This magic number assumes all VBI lines are captured, i.e. it implicitly
162 After these magic cookies (and the 8 byte bitmask in case of cookie 'itv0') the
|
| /Documentation/input/devices/ |
| D | walkera0701.rst | 114 four channels. In nibbles 22 and 23 is a special magic number. Nibble 24 is
118 binary value can be sampled. This bit and magic number is not used in
119 software driver. Some details about this magic numbers can be found in
|
| /Documentation/translations/sp_SP/process/ |
| D | magic-number.rst | 3 :Original: :ref:`Documentation/staging/magic-number.rst <magicnumbers>`
29 int magic;
74 Magic Name Number Structure File
|
| D | index.rst | 19 magic-number
|
| /Documentation/device-mapper/ |
| D | dm-bow.txt | 79 | Magic | Count | Sequence | Log entry | Log entry | …
82 Magic is a magic number. Count is the number of log entries. Sequence is 0
|
| /Documentation/devicetree/bindings/net/ |
| D | fsl-tsec-phy.txt | 62 - fsl,magic-packet : If present, indicates that the hardware supports
63 waking up via magic packet.
|
| /Documentation/translations/zh_CN/process/ |
| D | magic-number.rst | 3 :Original: Documentation/staging/magic-number.rst
27 int magic;
|
123456