security/hakurei.app
security/hakurei.app
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

start adding Pixel 4 to build documentation

Browse Source
This commit is contained in:
Daniel Micay 2020-06-04 23:34:17 -04:00
parent ce375cf685
commit af01d7f6d7
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
static/build.html
View File

@ -122,6 +122,8 @@
<li>aosp_blueline (Pixel 3)</li>
<li>aosp_bonito (Pixel 3a XL)</li>
<li>aosp_sargo (Pixel 3a)</li>
<li>aosp_coral (Pixel 4 XL) - incomplete / experimental, do not report issues</li>
<li>aosp_flame (Pixel 4) - incomplete / experimental, do not report issues</li>
</ul>
<p>These are all fully supported production-ready targets supporting all the baseline
@ -361,6 +363,7 @@ cd ../..</pre>
<ul>
<li>Pixel 2, Pixel 2 XL: wahoo - separate taimen and walleye builds due to hardening</li>
<li>Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL: crosshatch - separate crosshatch, blueline and bonito builds due to hardening</li>
<li>Pixel 4, Pixel 4 XL: coral</li>
</ul>
<p>As part of the hardening in GrapheneOS, it uses fully monolithic kernel builds with
@ -370,11 +373,12 @@ cd ../..</pre>
marked as using a separate build above need to have the device variant passed to the
GrapheneOS kernel build script to select the device.</p>
<p>For the Pixel 3, Pixel 3 XL, Pixel 3a and Pixel 3a XL, the kernel repository uses
submodules for building in out-of-tree modules. You need to make sure the submodule
sources are updated before building. In the future, this should end up being handled
automatically by <code>repo</code>. There's no harm in running the submodule commands
for other devices as they will simply not do anything.</p>
<p>For the Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL, Pixel 4 and Pixel 4 XL the
kernel repository uses submodules for building in out-of-tree modules. You need to
make sure the submodule sources are updated before building. In the future, this
should end up being handled automatically by <code>repo</code>. There's no harm in
running the submodule commands for other devices as they will simply not do
anything.</p>
<p>For example, to build the kernel for blueline:</p>