mirror of
https://github.com/cirosantilli/linux-kernel-module-cheat.git
synced 2026-01-22 17:55:57 +01:00
gem5 display: a bit more info on dp650
This commit is contained in:
36
README.adoc
36
README.adoc
@@ -3532,7 +3532,7 @@ and when we connect it shows a message:
|
||||
info: VNC client attached
|
||||
....
|
||||
|
||||
Alternatively, you can also view the frames with `--frame-capture`:
|
||||
Alternatively, you can also dump each new frame to an image file with `--frame-capture`:
|
||||
|
||||
....
|
||||
./run \
|
||||
@@ -3543,9 +3543,15 @@ Alternatively, you can also view the frames with `--frame-capture`:
|
||||
;
|
||||
....
|
||||
|
||||
This option dumps one compressed PNG whenever the screen image changes inside `m5out`, indexed by the cycle ID. This allows for more controlled experiments.
|
||||
This creates on compressed PNG whenever the screen image changes inside the <<m5out-directory>> with filename of type:
|
||||
|
||||
It is fun to see how we get one new frame whenever the white underscore cursor appears and reappears under the penguin.
|
||||
....
|
||||
frames_system.vncserver/fb.<frame-index>.<timestamp>.png.gz
|
||||
....
|
||||
|
||||
It is fun to see how we get one new frame whenever the white underscore cursor appears and reappears under the penguin!
|
||||
|
||||
The last frame is always available uncompressed at: `system.framebuffer.png`.
|
||||
|
||||
TODO <<kmscube>> failed on `aarch64` with:
|
||||
|
||||
@@ -3574,6 +3580,28 @@ git -C "$(./getvar linux_src_dir)" checkout -
|
||||
|
||||
This is because the gem5 `aarch64` defconfig does not enable HDLCD like the 32 bit one `arm` one for some reason.
|
||||
|
||||
==== gem5 graphic mode DP650
|
||||
|
||||
TODO get working. There is an unmerged patchset at: https://gem5-review.googlesource.com/c/public/gem5/+/11036/1
|
||||
|
||||
The DP650 is a newer display hardware than HDLCD. TODO is its interface publicly documented anywhere? Since it has a gem5 model and link:https://github.com/torvalds/linux/blob/v4.19/drivers/gpu/drm/arm/Kconfig#L39[in-tree Linux kernel support], that information cannot be secret?
|
||||
|
||||
The key option to enable support in Linux is `DRM_MALI_DISPLAY=y` which we enable at link:linux_config/display[].
|
||||
|
||||
....
|
||||
./build-linux
|
||||
git -C "$(./getvar linux_src_dir)" fetch https://gem5.googlesource.com/arm/linux gem5/v4.15:gem5/v4.15
|
||||
git -C "$(./getvar linux_src_dir)" checkout gem5/v4.15
|
||||
./build-linux \
|
||||
--arch aarch64 \
|
||||
--config-fragment linux_config/display \
|
||||
--custom-config-file "$(./getvar linux_src_dir)/arch/arm64/configs/gem5_defconfig" \
|
||||
--linux-build-id gem5-v4.15 \
|
||||
;
|
||||
git -C "$(./getvar linux_src_dir)" checkout -
|
||||
./run --arch aarch64 --dp650 --gem5 --linux-build-id gem5-v4.15
|
||||
....
|
||||
|
||||
==== Graphic mode gem5 internals
|
||||
|
||||
We cannot use mainline Linux because the <<gem5-arm-linux-kernel-patches>> are required at least to provide the `CONFIG_DRM_VIRT_ENCODER` option.
|
||||
@@ -9333,7 +9361,7 @@ since boot has already happened, and the parameters are already in the RAM of th
|
||||
Checkpoints are stored inside the <<m5out-directory>> at:
|
||||
|
||||
....
|
||||
"$(./getvar --gem5 run_dir)/m5out/cpt.<checkpoint-time>"
|
||||
"$(./getvar --gem5 m5out_dir)/cpt.<checkpoint-time>"
|
||||
....
|
||||
|
||||
where `<checkpoint-time>` is the cycle number at which the checkpoint was taken.
|
||||
|
||||
@@ -312,6 +312,10 @@ Use the docker download Ubuntu root filesystem instead of the default Buildroot
|
||||
'-L', '--linux-build-id', default=default_build_id,
|
||||
help='Linux build ID. Allows you to keep multiple separate Linux builds. Default: %(default)s'
|
||||
)
|
||||
parser.add_argument(
|
||||
'--linux-build-dir',
|
||||
help='Select the directory that contains the Linux kernel build. Overrides linux-build-id.'
|
||||
)
|
||||
parser.add_argument(
|
||||
'--machine',
|
||||
help='''Machine type.
|
||||
@@ -856,8 +860,11 @@ def setup(parser):
|
||||
|
||||
# Linux
|
||||
common.linux_buildroot_build_dir = os.path.join(common.buildroot_build_build_dir, 'linux-custom')
|
||||
if args.linux_build_dir is None:
|
||||
common.linux_build_dir = os.path.join(common.out_dir, 'linux', args.linux_build_id, args.arch)
|
||||
common.lkmc_vmlinux = os.path.join(common.linux_build_dir, "vmlinux")
|
||||
else:
|
||||
common.linux_build_dir = args.linux_build_dir
|
||||
common.lkmc_vmlinux = os.path.join(common.linux_build_dir, 'vmlinux')
|
||||
if args.arch == 'arm':
|
||||
common.linux_arch = 'arm'
|
||||
common.linux_image_prefix = os.path.join('arch', common.linux_arch, 'boot', 'zImage')
|
||||
|
||||
@@ -5,5 +5,7 @@ CONFIG_DRM_VIRTIO_GPU=y
|
||||
|
||||
## gem5
|
||||
CONFIG_DRM_HDLCD=y
|
||||
# DP650.
|
||||
DRM_MALI_DISPLAY=y
|
||||
# Only present in the gem5 fork.
|
||||
CONFIG_DRM_VIRT_ENCODER=y
|
||||
|
||||
11
test-gem5-graphics
Executable file
11
test-gem5-graphics
Executable file
@@ -0,0 +1,11 @@
|
||||
#!/usr/bin/env bash
|
||||
# Quick and dirty implementation, relies on configs.
|
||||
# Check that the third image matches a reference penguin SHA.
|
||||
# https://softwarerecs.stackexchange.com/questions/9774/command-line-tool-to-check-whether-two-images-are-exactly-the-same-graphically/9779#9779
|
||||
set -eux
|
||||
rm -rf "$(./getvar "$@" m5out_dir)/frames_system.vncserver"
|
||||
./run --eval 'm5 exit' --tmux "$@" -- --frame-capture
|
||||
gz="$(echo "$(./getvar m5out_dir)/frames_system.vncserver/fb.000002."*.gz)"
|
||||
png="${gz%.*}"
|
||||
gunzip --keep "$gz"
|
||||
[ "$(identify -format '%#' "$png")" = dc41b947487026acdceae8a757259d5a1a4752fd97c1da9ce6df9b49013babed ]
|
||||
Reference in New Issue
Block a user