Searched full:future (Results 1 – 25 of 390) sorted by relevance
12345678910>>...16
29 header in future.34 - This header can also be reused to support EFI stub for RISC-V in future. EFI50 - The "magic" field is deprecated as of version 0.2. In a future
16 For CPU hotplug Linux/x86-64 expects now that any possible future hotpluggable19 of disabled LAPICs to compute the maximum number of future CPUs.
33 user space to solve the problem. In future, we may47 In the future there may be additional types.
13 by design and may be removed in the future.
162 - x1 = 0 (reserved for future use)163 - x2 = 0 (reserved for future use)164 - x3 = 0 (reserved for future use)290 x0 = 0 (reserved for future use)291 x1 = 0 (reserved for future use)292 x2 = 0 (reserved for future use)293 x3 = 0 (reserved for future use)
32 capability flags are reserved for future extensions.44 reserved for future extensions.
54 ``reserved`` array (which in the future may contain writable properties)94 - Reserved for future extensions. Drivers and applications must set
86 u32 padding[7]; /* room for future expansion */109 u64 padding64[8]; /* room for future expansion */152 natural_width paddingl[8]; /* room for future expansion */199 u32 padding32[8]; /* room for future expansion */
89 - Reserved for future extensions. Drivers and applications must set116 - Reserved for future extensions. Drivers and applications must set144 - Reserved for future extensions. Drivers and applications must set
165 - Reserved for future extensions. Drivers and applications must set194 - Reserved for future extensions. Drivers and applications must set252 - Reserved for future extensions. Drivers and applications must set289 - Reserved for future extensions. Drivers and applications must set
54 What is future plan?62 We hope that LSM becomes stackable in future. Meanwhile, you can use non-LSM
45 mind the filesystem becoming unreadable to future kernels.96 >12 ulelong x future 0x%x106 >524 ulelong x future 0x%x
26 in future.
3 Binding status: Unstable - ABI compatibility may be broken in the future
19 Further clocks may be added in the future according to requirements of
8 and future SoCs from Samsung16 future controllers.
1 Status: Unstable - ABI compatibility may be broken in the future
16 services to current and future WiMAX devices from any vendor.21 accommodate future requirements.
9 future, the HDMI pins support can also be added.
23 9) Future Work115 allowed incremental context unsharing in future without an ABI change.117 unshare() interface should accommodate possible future addition of322 9) Future Work328 process is even more complex. If in the future there is a specific
25 * Further registers may be appended to the region in case of future interface
14 - For newer hardware (rk3328 and future socs): specified by name
24 Future plan is to migrate hwmod data base contents into device tree
18 Future plan is to migrate hwmod data base contents into device tree