Lines Matching refs:to

7 defconfig contains all of the Linux kconfig settings required to properly
12 It may be desirable to modify the kernel configuration beyond what the hardware
13 platform requires in order to support a particular hardware or software
17 needed to support the hardware or software feature/behavior in question.
18 Maintainers of hardware extensions or software features can use fragments to
27 Kernel configuration settings that must be present for Android to function are
29 that enhance Android’s functionality in some way but are not required for it to
36 config fragment. In releases up to and including Android P, kernel config
37 requirements that are specific to a particular architecture are contained in
42 specific to that architecture. Note that the architecture-agnostic kernel
59 way to enable these options would be to use the aforementioned
66 This will generate a `.config` that can then be used to save a new defconfig or
80 version combination, it is necessary to review it and manually edit your
81 defconfig to satisfy any applicable requirements.
95 Devices launched with prior releases of Android must be able to upgrade to
97 device kernels that adhere to the Android kernel configs of the current
98 release, but also with those device kernels that adhere to the configs of past
104 If you are adding a new feature to AOSP which depends on a particular kernel
107 supported upgrade path, or the feature must be designed in a way to degrade
109 essential to AOSP’s overall functionality). All configs on the supported
127 copied into a new directory for the release (this change is propagated to
128 master) and the top-level configs are removed (this change is not propagated to
131 ## I want to add/modify/remove a kernel config requirement. What do I do?
133 Modify the top level kernel configs in AOSP. Make sure to modify the configs
137 Because there is no tool to consistently generate these config fragments,
154 Build rules from the aforementioned files to a
160 ## I want to freeze/release the current kernel requirements. What do I do?
162 Prior to a [FCM Version release](https://source.android.com/devices/architecture/vintf/fcm#new-fcm-…
166 * Copy the top-level `android-*` directories to a release directory, preferably
168   * Remove top-level `android-*` directories. This change is not propagated to
172   to `kernel_config_q_4.9`
175   to use the new modules.
176   * `framework_compatibility_matrix.current.xml` will be renamed to
180 ## I want to edit a released kernel requirement. What do I do?
182 Don't edit a released kernel requirement unless necessary. If you have to make
192     * Lower minimum LTS requirement from `x.y.u` to `x.y.v` (where `v < u`)
203     * Raise minimum LTS requirement from `x.y.u` to `x.y.v` (where `v < u`)