<mps>
anarsoul: gamiee: found which driver is needed for lima to work on A64 SoC, it is DRM_ANALOGIX_ANX6345
apritzel has joined #linux-sunxi
valyast has quit []
anarsoul has quit [Ping timeout: 480 seconds]
anarsoul has joined #linux-sunxi
Daanct12 has quit [Quit: Leaving]
cnxsoft1 has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 480 seconds]
dliviu has joined #linux-sunxi
cnxsoft1 has quit []
cnxsoft has joined #linux-sunxi
cnxsoft has quit []
JohnDoe_71Rus has quit []
JohnDoe_71Rus has joined #linux-sunxi
valyast has joined #linux-sunxi
macromorgan is now known as Guest2420
macromorgan has joined #linux-sunxi
Guest2420 has quit [Ping timeout: 480 seconds]
apritzel_ has joined #linux-sunxi
apritzel_ has quit [Ping timeout: 480 seconds]
<jakllsch>
mps: how is anx6345 related to lima on a64?
<gamiee>
This ^
<jakllsch>
they're independent parts of the SoC
<jakllsch>
(if there's even a 6345 in the soc)
<mps>
jakllsch: i have no idea but when enabled it lima works with with xorg
<jakllsch>
on what hardware?
<mps>
on olimex teres-i notebook
<jakllsch>
yeah, that's got a lvds/edp bridge chip...
<jakllsch>
(which is what the anx6345 is, iirc)
<mps>
I have same on the gru-kevin chromebook but with panfrost
paulk-bis has quit [Ping timeout: 480 seconds]
<jakllsch>
i'm just saying, lima does not inherently depend on ANX6345 drivers on A64
<jakllsch>
if your system's video ouput is via the 6345, then yes, you'll need that driver to have fully functional DRM/KMS
<jakllsch>
but there's no reason you'd need the 6345 driver if you don't have the chip in your system.
<mps>
jakllsch: drm worked without it, but lima didn't
<jernej>
mps: good!
<mps>
jakllsch: I mean sun4i-drm
<jakllsch>
mps: *on your system*
<mps>
jakllsch: right
<mps>
I have another olimex A64 board with hdmi, maybe I will check when I find some free time
<jernej>
mps: reason why it might work without that driver is because simple framebuffer driver was used instead sun4i-drm
<jernej>
some boards have implemented simple framebuffer mechanism, where U-Boot initializes very basic framebuffer and hands over info to Linux
<jernej>
but that lacks a lot of functionality
<jernej>
if all dependencies are satisfied, then sun4i-drm unloads simple framebuffer and replaces it with DRM stack
<jernej>
lima can only work with DRM stack, but not simple framebuffer, which afaik is still fbdev based
<mps>
jernej: I had to disable simpledrm
<mps>
ah, you mean simple FB not simple DRM
<jernej>
well, anything which loads for "simple-framebuffer" compatible
<jernej>
indeed, simpledrm handles that now, but IIRC it was some fbdev driver in the past
<jernej>
in theory, sun4i-drm should be able to unload simpledrm, maybe it's broken
<mps>
that could be true, in my testing I first put simpledrm to blacklist
valyast has quit []
paulk-bis has joined #linux-sunxi
<anarsoul>
mps: that's not for lima to work, that's for your display to work
<anarsoul>
mps: and nope, sun4i-drm can't drive LCD in your teres without anx6345
<anarsoul>
likely you were using simplefb and thus display was brought up by u-boot
vagrantc has joined #linux-sunxi
<mps>
anarsoul: thanks for explanation. I'm far from expert in this field
<apritzel>
mps: how is the keyboard connected on the Teres-1? I guess via USB?
<jakllsch>
yeah, usb
<mps>
yes, usb
<apritzel>
which port? and is that directly, or through an on-board hub?
<mps>
uh, have to boot it to see
<anarsoul>
apritzel: you can check schematics :)
<mps>
on board I think
<apritzel>
the only thing I see in U-Boot which could trigger this regression is this CONFIG_USB1_VBUS_PIN="PL7" in the defconfig, and the corresponding code in drivers/phy/allwinner/phy-sun4i-usb.c
<apritzel>
anarsoul: sure, or I can ask here ;-)
<mps>
apritzel: you are talking about u-boot keyboard bug?