search

crondog / kernel_msm

Other
0 stars 3 forks source link

Fixes framebuffer console. #1

Closed willcast closed 10 years ago

willcast commented 10 years ago

This worked on d2vzw (Samsung Verizon Galaxy S3, model SCH-i535), which has very similar SoC (MSM8960 vs. APQ8064), also with 3.4.x.

Note that it doesn't fix it completely; the scrolling seems to intersperse pixels from each frame. It's still readable if you let it sit. I imagine that's also a simple fix, but I don't know where to look. ![Uploading IMG_20140310_234126.png . . .](screen shot from second device)

willcast commented 10 years ago

Sorry about the image. img_20140310_234126

crondog commented 10 years ago

Hmm you seemed to revert some of the code needed to make it work...like leaving the CONFIG_FRAMEBUFFER_CONSOLE=y ....

Anyway i got to this stage too (by compiling fbcon as a module and then loading it later because i would get a "pm_runtime: fail to wake up" error if i didn't) But the late_initcall is way better at fixing that :)

I'll have to take a look at this again during the week when I have more time to see where it is failing. It has an issue blitting or something

willcast commented 10 years ago

I reverted the other commit because I got missing-symbol errors (do_take_over_console() and do_unregister_con_driver(), which apparently showed up in 3.9) when compiling fbcon otherwise. I assumed you hadn't pushed the whole thing.

crondog commented 10 years ago

Ok all fixed