<phh>
too bad wzyy2 is not here, so that we can vote to have rockchip support ricoh619 :D
<PoueT>
+1 !
<moneymaker_>
the PMU is not my problem actually...
<moneymaker_>
i have the drivers for this
<moneymaker_>
but only downstream
<moneymaker_>
i have a, say semi-working kernel config for this device, but i got many kernel ooops, with adresses, and the rockchip-ion is not correctly initizialising...someone can help me with this?
<phh>
if you have a 3.10.x kernel, you have the matching defconfig I'm pretty sure
<phh>
and, too bad it's LVDS, it's not supported on mainline kernel :/
<phh>
mmm, after a second look, it seems like it is?!?
nighty- has quit [Quit: Disappears in a puff of smoke]
<mmind00>
phh: I don't think so ... I was working on the lvds driver 2 years ago, but then got sidetracked
<phh>
well, rockchip's rk3288 kernel for Android N has it as well
<phh>
and it has you as module_author, hence I thought it was mainlined
<mmind00>
phh: probably based on my earlier work ... but I don't have a device with lvds, so I somewhat lost interest
matthias_bgg has quit [Remote host closed the connection]
matthias_bgg has joined #linux-rockchip
nighty- has joined #linux-rockchip
<ayaka>
mmind00, the lvds for rk3228 has been ready for a few month
cyteen has quit [Ping timeout: 268 seconds]
cyteen has joined #linux-rockchip
<rperier>
I am the only person to have issues with emac_rockchip on rk3188 (radxa rock) when I try to use IP_PNP during boot ? (either static or dynamic)
<rperier>
it looks like there is autonego issues
<rperier>
I get Link up... Link down... Link up... Link down... in loop
<rperier>
I try to find the cause of the bug, I am trying with linux 4.6, all versions between 4.7 and 4.12 are affected
<rperier>
when I will have a working kernel, I will probably start a bisect
Aussie_matt has joined #linux-rockchip
PoueT has quit []
PoueT has joined #linux-rockchip
PoueT has quit [Remote host closed the connection]
PoueT has joined #linux-rockchip
Aussie_matt has quit [Read error: Connection reset by peer]
PoueT84 has joined #linux-rockchip
PoueT has quit []
PoueT84 has quit [Remote host closed the connection]
<moneymaker_>
PoueT if you read this, send me the connection detaisl
<diego71>
rperier: or some daemon try to doing things over the ethernet (dclient o network manager)
JohnDoe_71Rus has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 240 seconds]
<rperier>
diego71: no that's a direct link, network manager is configued as "shared" on this interface
<rperier>
and I use the same configuration with rk3288 and it's working
<rperier>
I don't know why, but I am the feeling that's related to what is done by the SPL/uboot (mainline) I have here ... with kernel 4.3.x same issue, I am sure that ethernet was working < 4.5... it does not make sense
<rperier>
s/I am / I have /
PoueT has joined #linux-rockchip
<mmind00>
rperier: there were reports of the emac having issues in the past (and even some patches if I remember correctly), but sadly I don't think there were many people caring about that issue
<mmind00>
rperier: and u-boot is not really at fault ... at most the emac driver is at fault for not initializing stuff it needs ;-)
<rperier>
I mostly remember about these issues, there were latencies, data loss ?
<mmind00>
rperier: not sure, I just remember patches that touched how the emac handled the packages
<beeble>
link managment is totaly out of band and would be a phy issue
<beeble>
in most cases
<rperier>
I will check with the prebuilt images for the rock, to be sure that's not an hw issue (just in case)
<rperier>
mmind00: I have also reverted locally all recent changes regarding emac_rockchip and emac, same issue :)
<rperier>
(if you are talking about these patches)
cnxsoft has quit [Quit: cnxsoft]
<BenG83>
has anyone used the analog audio codec on RK3328/Rock64?
<BenG83>
I think the dts looks ok, but my rk3328-codec device has no alsa mixer controls