docs: fix syntax highlighting on shell commands
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27010>
This commit is contained in:
committed by
Marge Bot
parent
eb505979ba
commit
eb96a4bffe
+9
-9
@@ -41,7 +41,7 @@ Then, create your Meson cross file to use it, something like this
|
||||
Now, use that cross file for your Android build directory (as in this
|
||||
one cross-compiling the turnip driver for a stock Pixel phone)
|
||||
|
||||
.. code-block:: console
|
||||
.. code-block:: sh
|
||||
|
||||
meson setup build-android-aarch64 \
|
||||
--cross-file android-aarch64 \
|
||||
@@ -61,7 +61,7 @@ read-only disk image on ``/vendor``. To be able to replace them for
|
||||
driver development, we need to unlock the device and remount
|
||||
``/vendor`` read/write.
|
||||
|
||||
.. code-block:: console
|
||||
.. code-block:: sh
|
||||
|
||||
adb disable-verity
|
||||
adb reboot
|
||||
@@ -69,7 +69,7 @@ driver development, we need to unlock the device and remount
|
||||
|
||||
Now you can replace drivers as in:
|
||||
|
||||
.. code-block:: console
|
||||
.. code-block:: sh
|
||||
|
||||
adb push build-android-aarch64/src/freedreno/vulkan/libvulkan_freedreno.so /vendor/lib64/hw/vulkan.sdm710.so
|
||||
|
||||
@@ -91,7 +91,7 @@ using scp from outside the container.
|
||||
On your device, you'll want to make ``/`` read-write. ssh in as root
|
||||
and run:
|
||||
|
||||
.. code-block:: console
|
||||
.. code-block:: sh
|
||||
|
||||
crossystem dev_boot_signed_only=0
|
||||
/usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions 4
|
||||
@@ -100,7 +100,7 @@ and run:
|
||||
Then, we'll switch Android from using an image for ``/vendor`` to using a
|
||||
bind-mount from a directory we control.
|
||||
|
||||
.. code-block:: console
|
||||
.. code-block:: sh
|
||||
|
||||
cd /opt/google/containers/android/
|
||||
mkdir vendor-ro
|
||||
@@ -123,7 +123,7 @@ change it to::
|
||||
|
||||
Now, restart the UI to do a full reload:
|
||||
|
||||
.. code-block:: console
|
||||
.. code-block:: sh
|
||||
|
||||
restart ui
|
||||
|
||||
@@ -136,7 +136,7 @@ then the ``mount`` command should show::
|
||||
Now, replacing your DRI driver with a new one built for Android should
|
||||
be a matter of:
|
||||
|
||||
.. code-block:: console
|
||||
.. code-block:: sh
|
||||
|
||||
scp msm_dri.so $HOST:/opt/google/containers/android/vendor-rw/lib64/dri/
|
||||
|
||||
@@ -149,7 +149,7 @@ available to the NDK, assuming you're building anything but the
|
||||
Freedreno Vulkan driver for KGSL. You can mostly put things in place
|
||||
with:
|
||||
|
||||
.. code-block:: console
|
||||
.. code-block:: sh
|
||||
|
||||
scp $HOST:/opt/google/containers/android/vendor-rw/lib64/libdrm.so \
|
||||
NDKDIR/sysroot/usr/lib/aarch64-linux-android/lib/
|
||||
@@ -166,6 +166,6 @@ find you need to reload the whole Android container. To do so without
|
||||
having to log in to Chrome again every time, you can just kill the
|
||||
container and let it restart:
|
||||
|
||||
.. code-block:: console
|
||||
.. code-block:: sh
|
||||
|
||||
kill $(cat /run/containers/android-run_oci/container.pid )
|
||||
|
||||
Reference in New Issue
Block a user