Fix formatting in text files
@@ -6,7 +6,7 @@ include::_support/common.inc[]
=== Hardware Revisions
This device has been through several hardware revisions: the kernel
-describes P0A, P1A, P1B,P2A, P2A2, P2B, and P3A but that's not an
+describes `P0A`, `P1A`, `P1B`, `P2A`, `P2A2`, `P2B`, and `P3A` but that's not an
exhaustive list. Each of these revisions corresponds to a separate
hardware configuration description (device tree) in the vendor kernel,
but on examination it turns out that several are identical to each
@@ -38,19 +38,19 @@ Thus,we can accommodate all revisions with three DTs:
- msm8953-potter-p2a2-plus.dtb (contains no fix)
-==== What about P3B?
+==== What about `P3B`?
The vendor kernel does not include a device tree source with
-appropriate board-id for hwrev P3B, but empirically (by consulting
+appropriate board-id for hwrev `P3B`, but empirically (by consulting
`/proc/device-tree/board-id` on a device running Android) it looks like
-the bootloader chooses the P3A DTB instead. As far as I understand it
+the bootloader chooses the `P3A` DTB instead. As far as I understand it
this goes against the https://github.com/xiaolu/mkbootimg_tools/blob/master/dtbtool.txt[documented rules]
for choosing a device tree - https://android.googlesource.com/kernel/msm.git/+/android-msm-bullhead-3.10-n-preview-1/Documentation/devicetree/bindings/arm/msm/board-id.txt?autodive=0%2F%2F%2F%2F[according to
sources]
the platform subtype is the lowest 8 bits of the second element of the
-board-id, and clearly 0xa0 != 0xb0, but it seems to do it anyway.
+`board-id`, and clearly `0xa0 != 0xb0`, but it seems to do it anyway.
-If you have a device with a hwrev *after* P3B, I'd love to hear from
+If you have a device with a hwrev *after* `P3B`, I'd love to hear from
you about how it behaves in this regard.
