3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-23 02:05:57 +01:00
Code Issues Releases Wiki Activity

x11: wait, now it works? I'm totally confused

Browse Source
This commit is contained in:
Ciro Santilli
2018-06-05 22:16:51 +01:00
parent 87a1f724a0
commit 84f88cbd5c
1 changed files with 6 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.adoc
View File

@@ -2267,16 +2267,6 @@ Build and run:
./run -x
....
TODO broken as of: 9e450f0da3dedddfd5f0a23160cffa26bc98c272. Now the graphic window shows normally, until an init script starts X at startup automatically, prints `Starting Xorg:` and the screen is completely black.
Also present on upstream: https://github.com/cirosantilli/buildroot/tree/501de462548ada83652ede6278d65d1929814270
If we put a terminal on the serial as explained at <<tty>>, and run `dmesg`, we see a <<bug_on>>:
....
[ 2.809104] WARNING: CPU: 0 PID: 51 at drivers/gpu/drm/ttm/ttm_bo_vm.c:304 ttm_bo_vm_open+0x37/0x40
....
Before updating Buildroot to 2018.05, this is what happened:
We don't build X11 by default because it takes a considerable amount of time (about 20%), and is not expected to be used by most users: you need to pass the `-x` flag to enable it.
@@ -2300,6 +2290,12 @@ More details: https://unix.stackexchange.com/questions/70931/how-to-install-x11-
Not sure how well that graphics stack represents real systems, but if it does it would be a good way to understand how it works.
TODO as of: c2696c978d6ca88e8b8599c92b1beeda80eb62b2 I noticed that `startx` leads to a <<bug_on>>:
....
[ 2.809104] WARNING: CPU: 0 PID: 51 at drivers/gpu/drm/ttm/ttm_bo_vm.c:304 ttm_bo_vm_open+0x37/0x40
....
=== X11 mouse not moving
TODO 9076c1d9bcc13b6efdb8ef502274f846d8d4e6a1 I'm 100% sure that it was working before, but I didn't run it forever, and it stopped working at some point. Needs bisection, on whatever commit last touched x11 stuff.