3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-28 04:24:26 +01:00
Code Issues Releases Wiki Activity

readme: improve getting started a bit

Browse Source
This commit is contained in:
Ciro Santilli 六四事件 法轮功
2018-10-05 00:00:00 +00:00
parent e9e2eb7e6c
commit e491ad4013
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.adoc
View File

@@ -65,7 +65,7 @@ The trade-offs are basically a balance between:
This is the best setup if you are on Ubuntu. We tend to test this repo the most on the latest Ubuntu, and on the latest Ubuntu LTS. This is the best setup if you are on Ubuntu. We tend to test this repo the most on the latest Ubuntu, and on the latest Ubuntu LTS.
Everything will likely also work on other Linux distros if you do what install the analogous required packages for your distro from link:configure[], but this is not currently well tested. Compatibility patches are welcome. You can also try <<docker>> if you are on other Linux distros. Native Windows is unlikely feasible because Buildroot is a huge set of GNU Make scripts + host tools, just use an Ubuntu VM in that case. Everything will likely also work on other Linux distros if you do what install the analogous required packages for your distro from link:configure[], but this is not currently well tested. Compatibility patches are welcome. <<docker>> should however just work on any distro. Native Windows is unlikely feasible because Buildroot is a huge set of GNU Make scripts + host tools, just do everything from inside an Ubuntu in VirtualBox instance in that case.
Reserve 12Gb of disk and run: Reserve 12Gb of disk and run:
@@ -81,7 +81,7 @@ cd linux-kernel-module-cheat
:; :;
.... ....
The first configure will take a while (30 minutes to 2 hours) to clone and build, see <<benchmark-builds>> for more details. The initial build will take a while (30 minutes to 2 hours) to clone and build, see <<benchmark-builds>> for more details.
If you don't want to wait, you could also try the following faster but much more limited methods: If you don't want to wait, you could also try the following faster but much more limited methods:
@@ -343,7 +343,7 @@ and can therefore be used to estimate system performance, see: <<gem5-run-benchm
The downside of gem5 much slower than QEMU because of the greater simulation detail. The downside of gem5 much slower than QEMU because of the greater simulation detail.
See <<gem5-vs-qemu,like QEMU>> for a more thorough comparison. See <<gem5-vs-qemu>> for a more thorough comparison.
==== gem5 Buildroot setup getting started ==== gem5 Buildroot setup getting started