mirror of
https://github.com/cirosantilli/linux-kernel-module-cheat.git
synced 2026-01-23 02:05:57 +01:00
readme: add explicit title ids to all titles that contain apostrophes
To work around divergence between 1.5.7+ and GitHub's header id generation: https://github.com/asciidoctor/asciidoctor/issues/3093
This commit is contained in:
@@ -1893,6 +1893,7 @@ For when it breaks again, or you want to add a new feature!
|
||||
|
||||
See also: https://stackoverflow.com/questions/13496389/gdb-remote-protocol-how-to-analyse-packets
|
||||
|
||||
[[remote-g-packet]]
|
||||
==== Remote 'g' packet reply is too long
|
||||
|
||||
This error means that the GDB server, e.g. in QEMU, sent more registers than the GDB client expected.
|
||||
@@ -4442,7 +4443,7 @@ although this can be useful when someone gives you a random image.
|
||||
|
||||
By default, link:build-linux[] generates a `.config` that is a mixture of:
|
||||
|
||||
* a base config extracted from Buildroot's minimal per machine `.config`, which has the minimal options needed to boot: <<about-buildroot-s-kernel-configs>>
|
||||
* a base config extracted from Buildroot's minimal per machine `.config`, which has the minimal options needed to boot: <<buildroot-kernel-config>>.
|
||||
* small overlays put top of that
|
||||
|
||||
To find out which kernel configs are being used exactly, simply run:
|
||||
@@ -4472,6 +4473,7 @@ On top of those, we add the following by default:
|
||||
+
|
||||
We have since observed that the kernel size itself is very bloated compared to `defconfig`: <<linux-kernel-defconfig>>.
|
||||
|
||||
[[buildroot-kernel-config]]
|
||||
===== About Buildroot's kernel configs
|
||||
|
||||
To see Buildroot's base configs, start from link:https://github.com/buildroot/buildroot/blob/2018.05/configs/qemu_x86_64_defconfig[`buildroot/configs/qemu_x86_64_defconfig`].
|
||||
@@ -11420,7 +11422,7 @@ So we see in both cases that the `svc` is done, then an exception happens, and t
|
||||
|
||||
The vector table format is described on <<armarm8>> Table D1-7 "Vector offsets from vector table base address".
|
||||
|
||||
A good representation of the format of the vector table can also be found at <<programmer-s-guide-for-armv8-a>> Table 10-2 "Vector table offsets from vector table base address".
|
||||
A good representation of the format of the vector table can also be found at <<armv8-programmers-guide>> Table 10-2 "Vector table offsets from vector table base address".
|
||||
|
||||
The first part of the table contains:
|
||||
|
||||
@@ -11637,6 +11639,7 @@ Latest version: https://developer.arm.com/docs/ddi0487/latest/arm-architecture-r
|
||||
|
||||
We use: DDI 0487C.a: https://static.docs.arm.com/ddi0487/ca/DDI0487C_a_armv8_arm.pdf
|
||||
|
||||
[[armv8-programmers-guide]]
|
||||
===== Programmer's Guide for ARMv8-A
|
||||
|
||||
A more terse human readable introduction to the ARM architecture than the reference manuals.
|
||||
@@ -12370,6 +12373,7 @@ Native Windows is unlikely feasible because Buildroot is a huge set of GNU Make
|
||||
|
||||
=== Common build issues
|
||||
|
||||
[[put-source-uris-in-sources]]
|
||||
==== You must put some 'source' URIs in your sources.list
|
||||
|
||||
If `./build --download-dependencies` fails with:
|
||||
|
||||
Reference in New Issue
Block a user