avoid misinterpretation of update requirements
The update requirements exist because we need to include device support code for each supported device including firmware, drivers and HALs. It was easiest to define the requirement as having proper overall updates, but we can clarify that we only need it for the device support code even though it's not going to be updated by itself without the OS also being updated. This adds a bit of additional text, but it avoids the current situation where several people are misrepresenting this requirement.
This commit is contained in:
parent
e372cb0522
commit
04d793f8d4
@ -300,12 +300,13 @@
|
||||
<li>Support for using alternate operating systems including full hardware
|
||||
security functionality</li>
|
||||
<li>Complete monthly Android Security Bulletin patches without any regular
|
||||
delays longer than a week</li>
|
||||
<li>At least 5 years of updates from launch for phones (Pixels now have 7)
|
||||
and 7 years for tablets</li>
|
||||
<li>Vendor code updated to new monthly, quarterly and yearly releases of
|
||||
AOSP within several months to provide new security improvements (Pixels
|
||||
receive these in the month they're released)</li>
|
||||
delays longer than a week for device support code (firmware, drivers and
|
||||
HALs)</li>
|
||||
<li>At least 5 years of updates from launch for device support code with
|
||||
phones (Pixels now have 7) and 7 years with tablets</li>
|
||||
<li>Device support code updated to new monthly, quarterly and yearly
|
||||
releases of AOSP within several months to provide new security improvements
|
||||
(Pixels receive these in the month they're released)</li>
|
||||
<li>Linux 5.15, 6.1 or 6.6 Generic Kernel Image (GKI) support</li>
|
||||
<li>Hardware accelerated virtualization usable by GrapheneOS (ideally pKVM
|
||||
to match Pixels but another usable implementation may be acceptable)</li>
|
||||
|
Loading…
x
Reference in New Issue
Block a user