Searched full:future (Results 1 – 25 of 411) sorted by relevance
12345678910>>...17
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.
25 capability flags are reserved for future extensions.37 reserved for future extensions.
47 ``reserved`` array (which in the future may contain writable properties)86 - Reserved for future extensions. Drivers and applications must set
47 - Reserved for future extensions. Should be zeroed by drivers and118 - Reserved for future extensions. Should be zeroed by drivers and
80 - Reserved for future extensions. Drivers and applications must set106 - Reserved for future extensions. Drivers and applications must set133 - Reserved for future extensions. Drivers and applications must set
156 - Reserved for future extensions. Drivers and applications must set184 - Reserved for future extensions. Drivers and applications must set241 - Reserved for future extensions. Drivers and applications must set277 - Reserved for future extensions. Drivers and applications must set
91 u32 padding[7]; /* room for future expansion */114 u64 padding64[8]; /* room for future expansion */154 natural_width paddingl[8]; /* room for future expansion */201 u32 padding32[8]; /* room for future expansion */
162 - x1 = 0 (reserved for future use)163 - x2 = 0 (reserved for future use)164 - x3 = 0 (reserved for future use)316 - x0 = 0 (reserved for future use)317 - x1 = 0 (reserved for future use)318 - x2 = 0 (reserved for future use)319 - x3 = 0 (reserved for future use)
33 user space to solve the problem. In future, we may48 In the future there may be additional types.
54 What is future plan?62 We hope that LSM becomes stackable in future. Meanwhile, you can use non-LSM
26 in future.
48 mind the filesystem becoming unreadable to future kernels.100 >12 ulelong x future 0x%x110 >524 ulelong x future 0x%x
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
9 Server CPUs. It will be available in future non-server Intel parts10 and future AMD processors.
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
24 Future plan is to migrate hwmod data base contents into device tree
14 - For newer hardware (rk3328 and future socs): specified by name
25 * Further registers may be appended to the region in case of future interface
15 3. Future plans143 For now, this can be simplified to just the following (but see Future plans):148 3. Future plans