eebrah_ has quit [Read error: Connection reset by peer]
eebrah_ has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
eebrah_ has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-rockchip
eebrah_ has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 265 seconds]
cnxsoft has joined #linux-rockchip
eebrah_ has quit [Ping timeout: 264 seconds]
rellla has joined #linux-rockchip
eebrah_ has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
hipboi_ has quit [Quit: Leaving]
<AstralixNB>
Does anyone have a Datasheet for companion chip RK618?
cnxsoft has quit [Ping timeout: 244 seconds]
eebrah_ has quit [Ping timeout: 272 seconds]
_massi_ has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
eebrah_ has joined #linux-rockchip
naobsd has joined #linux-rockchip
eebrah_ has quit [Ping timeout: 265 seconds]
naobsd has quit [Quit: Page closed]
cnxsoft has quit [Quit: cnxsoft]
deviker has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
RaYmAn has quit [Quit: switching teh servers]
hipboi has joined #linux-rockchip
eebrah_ has joined #linux-rockchip
<deviker>
Hi, I've been using a mk908 v3 stick for weeks without problems and I bought another one. It looks the same with the same rev number 2013.05.13 but it has DIFFERENT RAM chips. Now I've flickering allways. The only custom kernel I found working well is jjh_V_#135 but the latest jjhmod kernels give the same probem.
naobsd has joined #linux-rockchip
<deviker>
The stick that works well has GEIL 1331-1320 chips and the "faulty" one GEIL 1330-1324
<deviker>
both sticks have the same silkscreen (netxeon mk908 v3.0 2013.05.13)
<deviker>
the faulty one only works well with jjmod kernel jjh_v_#135 but it's /proc/config.gz is not different.
eebrah_ has quit [Read error: Connection reset by peer]
eebrah_ has joined #linux-rockchip
mosquito520 has quit [Read error: Connection reset by peer]
mosquito520 has joined #linux-rockchip
<mosquito520>
AstralixNB: what kind information that you need?
markm has joined #linux-rockchip
markm has quit [Client Quit]
hipboi has quit [Remote host closed the connection]
cnxsoft has quit [Remote host closed the connection]
<AstralixNB>
mosquito520: best would be a complete datasheet. I bet it is a HDMI interface as it replaces the ITE chip in some newer tablets.
eval- has quit [Ping timeout: 248 seconds]
eval- has joined #linux-rockchip
<mosquito520>
AstralixNB: well, first request has been reject...:p
<mosquito520>
AstralixNB: the second, it's not only HDMI transmitter, it combined some block that RK3188 does not include in:)
<mosquito520>
hm... I can't find it on google:~
<mosquito520>
:/
<AstralixNB>
believe me, I already used google before requesting it here
<mosquito520>
Ha, I mean...If I can find the exactly file name on google, maybe i can figure out which link that you need:)
eebrah_ has quit [Ping timeout: 244 seconds]
<AstralixNB>
It is more likely to find something on these chinese datasheet search / exchange engines. But I don't write enough chinese...
<arokux>
hi Astralix1
<arokux>
and hi AstralixNB :)
<arokux>
any progress with RK bootloader?
<AstralixNB>
hi
<mosquito520>
Hi arokux :)
<AstralixNB>
Too much work
<arokux>
I see
<AstralixNB>
actually I just did some small progress on the mainlining
<AstralixNB>
But it is progressing slowly cause I am despreately missing PMU and CRU documents
<AstralixNB>
the whole clock setup has to be reproduced by reverse engineering
<arokux>
AstralixNB: what about the released code?
<AstralixNB>
It is open source, just check me and mmind00 at github
<arokux>
AstralixNB: no-no, I mean, is chinese code not enough to understand clocking business?
<AstralixNB>
check the linux-rockchip repo and in that use the topgit/devel branch
<arokux>
AstralixNB: no-no, I mean, is chinese code not enough to understand clocking business?
<AstralixNB>
Sometimes yes, sometimes not.
<AstralixNB>
Problem is, that there are some bugs inside the SOC. Not really bugs, but if you see that some GPIO cofigs are reversed, compared to others...
<AstralixNB>
So if you look at the data sheet you just ignore this by scrolling it. But if you then see the code and see that there is additional logic implemented, you check the datasheet twice. And this combination brings you to the goal.
<arokux>
AstralixNB: same with Allwinner. one can see that the docs are not really full and are written on-demand.
<AstralixNB>
I got the comment from RK that they do not release some of the docs as they are still busy writing them, or they wrote them, but never checked validity
<arokux>
:)
<arokux>
AstralixNB: there have been rumors in this channel RK has added support to U-Boot
<arokux>
mosquito520 hinted at that :p
<arokux>
AstralixNB: do you know something about it?
<AstralixNB>
I heared only rumors
<arokux>
mosquito520 hinted at device which should have it, haven't checked it out yet.
<arokux>
AstralixNB: I've odered pins from Hongkong, but they haven't come yet :(