ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | Wiki at http://linux-rockchip.info | Logs at http://irclog.whitequark.org/linux-rockchip | ML at http://groups.google.com/group/linux-rockchip
gb_master has quit [Quit: Leaving]
naobsd has joined #linux-rockchip
naobsd1 has joined #linux-rockchip
naobsd has quit [Read error: Connection reset by peer]
naobsd1 is now known as naobsd
kapouer has quit [Ping timeout: 256 seconds]
akaizen has quit [Remote host closed the connection]
naobsd has quit [Quit: naobsd]
akaizen has joined #linux-rockchip
gouwa has joined #linux-rockchip
gouwa has quit [Client Quit]
_whitelogger_ has joined #linux-rockchip
mrutland has joined #linux-rockchip
kodie has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
nashpa has joined #linux-rockchip
adj_ has quit [*.net *.split]
nashpa_ has quit [*.net *.split]
johnnyr has quit [*.net *.split]
libv has quit [*.net *.split]
tnn has quit [*.net *.split]
mmind00 has quit [*.net *.split]
bashintosh has quit [*.net *.split]
cnxsoft has quit [Ping timeout: 264 seconds]
tnn has joined #linux-rockchip
libv has joined #linux-rockchip
johnnyr has joined #linux-rockchip
bashintosh has joined #linux-rockchip
mmind00 has joined #linux-rockchip
adj_ has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
Ueno_Otoko has joined #linux-rockchip
Ueno_Otoko has quit [Ping timeout: 264 seconds]
_whitelogger has joined #linux-rockchip
Darkarnium has joined #linux-rockchip
<Darkarnium> Hello all :) I was wonder if there is someone about that would be able to point me in the right direction.
<Darkarnium> I have an RK3188 device which seems to be replying to an ReadLBA (via rkflashtool) with a crazy value.
<Darkarnium> Or, what appears to be a crazy value (much higher than MAX_PARAM_LENGTH)
<Darkarnium> I was wondering if this is something that has perhaps been encountered before with this package (RK3188)
Ueno_Otoko has joined #linux-rockchip
fireglow has quit [Quit: Gnothi seauton; Veritas vos liberabit]
fireglow has joined #linux-rockchip
Ueno_Otoko has quit [Ping timeout: 276 seconds]
fireglow has quit [Quit: Gnothi seauton; Veritas vos liberabit]
fireglow has joined #linux-rockchip
nighty^ has quit [Ping timeout: 265 seconds]
hipboi has quit [Quit: This computer has gone to sleep]
kapouer has joined #linux-rockchip
afaerber has joined #linux-rockchip
Ueno_Otoko has joined #linux-rockchip
VargaD has quit [Ping timeout: 250 seconds]
VargaD has joined #linux-rockchip
Ueno_Otoko has quit [Ping timeout: 260 seconds]
Wizzup_ has joined #linux-rockchip
gb_master has joined #linux-rockchip
<topi`> anyone here who's gotten a Geekbox? I ordered mine and am expecting it soon. Can I run the mainline kernel on it?
<topi`> I think the 3288 is better than the 3688, but I also want a) SATA and b) aarch64 for 64bit support so it was a natural choice
<topi`> the Devices category in linux-rockchip.info wiki doesn't have a Geekbox entry ... can I update that one? or is that wiki obsolete?
Ueno_Otoko has joined #linux-rockchip
kapouer has quit [Quit: kapouer]
sunilmohan has quit [Ping timeout: 264 seconds]
sunilmohan_ has joined #linux-rockchip
sunilmohan has joined #linux-rockchip
sunilmohan has quit [Changing host]
sunilmohan has joined #linux-rockchip
kapouer has joined #linux-rockchip
sunilmohan_ has quit [Ping timeout: 240 seconds]
<sjoerd> topi`: no dts for it on the mainline kernle,but given the schematics are available that shouldn't be too hard to add
<sjoerd> the sata is jut an usb->sata bridge though like on the rock2
naobsd has joined #linux-rockchip
sunilmohan has quit [Ping timeout: 250 seconds]
sunilmohan has joined #linux-rockchip
<topi`> yeah, pretty slow :/
<topi`> rockchip ought to have added usb3 for rk3368...
<topi`> does rk3288 already work with mainline?
Wizzup_ has left #linux-rockchip [#linux-rockchip]
<xming_> yes
JohnDoe_71Rus has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
JohnDoe8 has joined #linux-rockchip
Ueno_Otoko has quit [Ping timeout: 265 seconds]
JohnDoe_71Rus has quit [Ping timeout: 260 seconds]
gb_master has quit [Quit: Leaving]
<topi`> I wonder if rk3368 shares some blocks with 3288
<topi`> it usually makes it much easier to do mainlining :)
<sjoerd> 3367 support is mainline
<sjoerd> *3368
<topi`> ok, unfortunately linux-rockchip.org doesn't tell me that
dlezcano has quit [Ping timeout: 240 seconds]
dlezcano has joined #linux-rockchip
JohnDoe8 has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]
mrueg has quit [Remote host closed the connection]
mrueg has joined #linux-rockchip
ckeepax has quit [Ping timeout: 276 seconds]
ckeepax has joined #linux-rockchip
<mmind00> topi`: rk3368 and rk3288 share most of their IP blocks [sometimes with minimal differences]
kapouer has quit [Quit: kapouer]
ckeepax has quit [Ping timeout: 256 seconds]
ckeepax has joined #linux-rockchip
kapouer has joined #linux-rockchip
kapouer has quit [Quit: kapouer]
<Darkarnium> Hey all, I'm seeing some odd behaviour with an RK3188 based device. I'm trying to dump the flash before modifying anything (from factory), but reading the contents of the flash (rkflashtool r 0x0 0x1000000) is yielding an image that contains no data.
<Darkarnium> Any ideas? :)
<Darkarnium> I can't seem to find any documentation on the SoC / Package itself, so I'm guessing it's all under NDA (past a datasheet which has the ball layout and pin map, etc) :(
<sjoerd> Darkarnium: http://linux-rockchip.info/mw/index.php?title=RK3188 has a TRM for the 3188
<sjoerd> but the nand flash parts are indeed not publically available
<topi`> mmind00: so, adding device/platform support for mainline is surely just a simple .dts job?
<topi`> from 3288 -> 3368
<Darkarnium> sjoerd: thanks, I'll have a look :)
<mmind00> topi`: in essence yet ... we currently already have support for two rk3368 boards, so adding the geekbox is no real problem
<topi`> mmind00: I guess the guys behind Geekbox have already done some work
<mmind00> topi`: as always except graphics ... IP blocks are similar but some bits in the registers shifted, so need someone looking at that + iommu handling seems to have changed
<mmind00> topi`: I don't really think so ... all these chineese/whatever makers just seem to take the vendor kernel
<mmind00> topi`: and while Rockchip also does provide rk3368 patches now, the full-featured thing is currently still the vendor kernel
ckeepax has quit [Ping timeout: 265 seconds]
<Darkarnium> This may be a silly question, and I appologize if that is the case, but in rkflashtool the 'RKFT_CMD_' defines are register locations from which the data is being read (via usb), or is based on an API rather than direct access to registers?
<Darkarnium> Aka RKFT_CMD_READFLASHINFO at 0x8000061a
<Darkarnium> There is some additional data in protocol.txt on the flashtool tree that makes me thing this is an API?
libv_ has joined #linux-rockchip
libv has quit [Ping timeout: 246 seconds]
libv has joined #linux-rockchip
libv_ has quit [Ping timeout: 245 seconds]
libv_ has joined #linux-rockchip
libv has quit [Ping timeout: 245 seconds]
libv_ is now known as libv
sunilmohan has quit [Ping timeout: 245 seconds]
sunilmohan has joined #linux-rockchip
libv_ has joined #linux-rockchip
libv has quit [Ping timeout: 245 seconds]
libv_ is now known as libv
libv has quit [Remote host closed the connection]
robogoat has quit [Ping timeout: 265 seconds]
robogoat has joined #linux-rockchip
libv has joined #linux-rockchip
libv_ has joined #linux-rockchip
libv has quit [Ping timeout: 260 seconds]
libv_ is now known as libv