<ncrmnt>
although fbdev is damn laggy with loads of artifacts...
<deweydb>
nice
nighty-_ has quit [Quit: Disappears in a puff of smoke]
<ncrmnt>
Btw, what about 2d acceleration under X.org on rk3188? Did anyone manage to get that working?
FreezingCold has quit [Ping timeout: 246 seconds]
JochenKauz has quit [Quit: Leaving.]
avRoogh3 has joined #linux-rockchip
ganbold_ has quit [Remote host closed the connection]
avRoogh3 has quit [Ping timeout: 246 seconds]
avRoogh3 has joined #linux-rockchip
ncrmnt has quit [Ping timeout: 260 seconds]
<deweydb>
when flashing with linux rkflashktool, and i have a parm.bin dump like: CMDLINE: initrd=0x62000000,0x00800000 init=/sbin/init root=/dev/mtdblock2 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),0x00008000@0x0000A000(kernel),-@0x00012000(system)
<deweydb>
what do i use for the offset and size ?
<deweydb>
since it has '-' as one of those parameters in the dump, so i am confused.
naobsd has joined #linux-rockchip
<naobsd>
deweydb: unit of offset/size is 512byte. "-" is remaining area
<naobsd>
rkflashtool uses unit (not byte) as unit for offset/size
<deweydb>
so how do i specify that? ./rkflashtool w 0x12000 0xFFFFFFFFF < system.img ?
<deweydb>
or maybe i did do it right just now
<deweydb>
i took the size of the system.img
<deweydb>
divided by 512
<deweydb>
and converted to hex
<deweydb>
like so: ./rkflashtool w 0x12000 0x2423F0 < ../picuntu/system.img
<naobsd>
size of source file divided by 512 should be enough
<deweydb>
oh, don't convert to hex?
<naobsd>
hex is ok too
<deweydb>
ok good. thanks!
<naobsd>
reading/writing will be rounded up to 16KiB, but basically no need to care about it
<deweydb>
w0000000oooo0o0o0o0o0o0o0o
<deweydb>
holy crap
<deweydb>
it booted
<deweydb>
i have been working on this for 24 hours
<deweydb>
i was going to lose my mind
<deweydb>
weird, so i guess i wasn't doing anything wrong, it was just that the rkandroidtool.exe in windows kinda blows