akaizen has quit [Remote host closed the connection]
<lautriv>
naobsd, and another USB-Host ... but why did they revert to SD ( instead µSD ) ?
<naobsd>
they? tronsmart? I'm not tronsmart
<rperier>
naobsd: so as an hacking device, it seems to be correct. ok cool. when you say "I can extract dtb from device" you mean extract the dtb binary and then decompile the devicetree ? there is no the devicetree source somewhere ? :/
<rperier>
which rk kernel is used btw with rk3368 ?
<naobsd>
rperier: dts is in SDK/kernel/arch/arm64/boot/dts, but old, not for my R68G
<naobsd>
rperier: 3.10
<naobsd>
rperier: origin should be same as firefly lollipop kernel tree
<naobsd>
I compared them. FF tree has some updates but basically same (+ board specific changes)
<bashintosh>
naobsd: 5.1 SDK for Firefly comes with kernel 3.10.79 - previous 4.4 SDK was 3.10.49. See Makefile in the kernel root dir.
<bashintosh>
Rockchip 5.1 SDK (not Firefly) is 3.10.49 - so maybe only FF has a 3.10 kernel with updates.
<lautriv>
bashintosh, that rockchip 5.1 does contain older SoC ?
<bashintosh>
lautriv: mmh, rk312x (so older), then rk3288 and rk3368
<lautriv>
heh -> Access from your area has been temporarily limited for security reasons
<naobsd>
rk312x is not old
<naobsd>
minor version number may not be correct... e.g. rk30/31 3.0.36 contains newer updates from >.36
<naobsd>
but it shouldn't be so important
<naobsd>
btw Orion R68 SDK is also 3.10.79. (as I said, it's almost same as FF SDK)
<naobsd>
unfortunately I don't have Rockchip original lollipop SDK
<naobsd>
no idea how they differ
<bashintosh>
3552 files differ between 3.10.49 and 3.10.79 (not Rockchip, both FF SDKs)
lautriv_ has joined #linux-rockchip
<naobsd>
both FF SDKs?
<naobsd>
4.4 <> 5.1?
<bashintosh>
correct
lautriv has quit [Disconnected by services]
lautriv_ is now known as lautriv
markm has quit [Ping timeout: 252 seconds]
markm_ has joined #linux-rockchip
<naobsd>
fireprime kernel is 3.10.49. it should be based on earlier RK 5.1 SDK. no idea when kernel is updated
<naobsd>
anyway, changes from upstream is not so important for me...
<lautriv>
at least since they lack your gigabit support.
<naobsd>
well, my GbE issue is unrelated to base version of SDKs
<naobsd>
at least Tronsmart SDK is 3.10.79 as same as FF
<naobsd>
and changes from upstream shouldn't fix my issue too.
<naobsd>
just a matter of seriousness of Tronsmart ;)
<naobsd>
anyway I have no problem about my issue. I can fix it.
<rperier>
mhhhh... so perhaps it would be interesting for me to buy this tv box to hack a bit with mainline, as most of informations seems to be available...
<naobsd>
I already confirmed that GbE is working on mainline
<rperier>
yeah yeah I know, that's why I said this :)
<naobsd>
if someone want to use Rikomagic MK68 for development, I may be able to ask/get some information
<naobsd>
but I hope
<naobsd>
dev board with rk3368 will be available ;)
<lautriv>
i consider to get newer ones if the 3188 is able to obey.
<naobsd>
I have a lot of todos from rk3066-rk3288...
<lautriv>
arms could have way more success if they won't stick on androshit.
<sjoerd>
That's a soc vendor thing though
* sjoerd
must say he's quite happy to see rockchip is contributing directly upstream these days
<lautriv>
sjoerd, unfortunately all vendors behave the same.
<sjoerd>
Not really
nighty-_ has joined #linux-rockchip
yyjia has quit [Ping timeout: 246 seconds]
maz has joined #linux-rockchip
naobsd has quit [Quit: naobsd]
mmind00 has quit [Ping timeout: 256 seconds]
Helle has quit [Ping timeout: 244 seconds]
mmind00 has joined #linux-rockchip
Helle has joined #linux-rockchip
naobsd has joined #linux-rockchip
Helle has quit [Ping timeout: 272 seconds]
Helle has joined #linux-rockchip
Helle has quit [Ping timeout: 255 seconds]
Helle has joined #linux-rockchip
naobsd has quit [Quit: naobsd]
maz has quit [Ping timeout: 240 seconds]
maz has joined #linux-rockchip
maz has quit [Ping timeout: 240 seconds]
maz has joined #linux-rockchip
tony_ has quit [Ping timeout: 240 seconds]
Kodacci has joined #linux-rockchip
Kodacci has quit [Client Quit]
leming has quit [Ping timeout: 264 seconds]
leming has joined #linux-rockchip
ssvb has quit [Ping timeout: 240 seconds]
naobsd has joined #linux-rockchip
premoboss has quit [Ping timeout: 250 seconds]
ssvb has joined #linux-rockchip
GriefNorth has quit [Quit: WeeChat 1.3]
rory096 has joined #linux-rockchip
rory096 has joined #linux-rockchip
<naobsd>
oh, latest rk u-boot supports resource.img on ram...fastboot boot should be useful
<naobsd>
and it supports usb mass storage but handle it speciall (like as emmc)
<naobsd>
we can put parameter and partitions on usb mass storage ;)
<lautriv>
naobsd, since when do we need any of them on SD ? used to be partitioned without parameters anyway.
<lautriv>
s/SD/USB/
maz has quit [Quit: Leaving]
gb_master has joined #linux-rockchip
tony_ has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
dlezcano has quit [Quit: Leaving]
akaizen has joined #linux-rockchip
tony_ has quit [Remote host closed the connection]
akaizen has quit [Remote host closed the connection]
apritzel has quit [Ping timeout: 264 seconds]
gb_master has quit [Remote host closed the connection]
<rperier>
mmind00: the patch '[PATCH v2 8/9] ARM: rockchip: add support smp for rk3036' duplicates some code no ? I am thinking to the cpu kill/die support which is already implemented and works for all SoCs
<mmind00>
rperier: it is the wrong approach anyway ... i.e. the smp bringup is the same as on the rk3288 ... only that the rk3036 cannot control its powerdomains [they are always on]
<mmind00>
its big brother the rk3128 (quad-core A7) can again control its powerdomains
<rperier>
I did not say that I disagree with your comment ... that's just another remark :)
<rperier>
(well, in any case the patch is not correct so... )
<mmind00>
rperier: I have to confess, after I saw that mapping of the cru in there I didn't really want to dig deeper at that point ;-)