aboutsummaryrefslogtreecommitdiff
path: root/en/devices/architecture/kernel
diff options
context:
space:
mode:
Diffstat (limited to 'en/devices/architecture/kernel')
-rw-r--r--en/devices/architecture/kernel/modular-kernels.html10
-rw-r--r--en/devices/architecture/kernel/network_tests.html6
2 files changed, 8 insertions, 8 deletions
diff --git a/en/devices/architecture/kernel/modular-kernels.html b/en/devices/architecture/kernel/modular-kernels.html
index 5c4b54c3..70debebe 100644
--- a/en/devices/architecture/kernel/modular-kernels.html
+++ b/en/devices/architecture/kernel/modular-kernels.html
@@ -181,8 +181,8 @@ mounted in Recovery mode.</li>
partitions are <strong>not</strong> mounted early. In Android 8.0, to make
module loading from these partitions possible, provisions have been made to
mount partitions early for both
-<a href="https://source.android.com/devices/tech/ota/ab_updates">non-A/B and A/B
-devices</a>. This also ensures the partitions are mounted in both Android and
+<a href="/devices/tech/ota/ab_updates">non-A/B and A/B devices</a>. This also
+ensures the partitions are mounted in both Android and
Charger modes.</p>
<h3 id="android-build-system-support">Android build system support</h3>
@@ -604,9 +604,9 @@ see <a href="/devices/architecture/dto/partitions.html">DTB/DTBO Partitions</a>.
The assumption is that bootloader already knows where and how to load the
SoC–specific DTB.</li>
<li>Overlay DT partition should be
-<a href="https://source.android.com/devices/tech/ota/ab_updates.html">A/B-ed</a>
-for A/B devices. For these devices, the recovery kernel is the same as Android
-kernel, but the partition must be A/B-ed as it can be updated via OTA.</li>
+<a href="/devices/tech/ota/ab_updates.html">A/B-ed</a> for A/B devices. For these
+devices, the recovery kernel is the same as Android kernel, but the partition
+must be A/B-ed as it can be updated via OTA.</li>
<li>Partition size is board–specific.
<ul>
<li>The DT overlay partition size depends on the device and the amount of
diff --git a/en/devices/architecture/kernel/network_tests.html b/en/devices/architecture/kernel/network_tests.html
index bc437ad2..39329d2b 100644
--- a/en/devices/architecture/kernel/network_tests.html
+++ b/en/devices/architecture/kernel/network_tests.html
@@ -45,9 +45,9 @@ Suite (CTS) tests.</p>
<h2 id=using>Using the tests</h2> <p>The tests use <a
href="http://user-mode-linux.sourceforge.net/">User-Mode Linux</a> to boot the
-kernel as a process on a Linux host machine. See <a
-href="https://source.android.com/source/initializing.html">Establishing a Build
-Environment</a> for suitable operating system versions. The unit test framework
+kernel as a process on a Linux host machine. See
+<a href="/setup/initializing.html">Establishing a Build Environment</a> for
+suitable operating system versions. The unit test framework
boots the kernel with an appropriate disk image and runs the tests from the
host file system. The tests are written in Python 2.x and use TAP interfaces to
exercise kernel behaviour and the socket API.</p>