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
vickycq has quit [Ping timeout: 240 seconds]
c0d3z3r0 has quit [Ping timeout: 246 seconds]
c0d3z3r0 has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
linux-rockchip has quit [Ping timeout: 240 seconds]
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 244 seconds]
cnxsoft1 is now known as cnxsoft
wadim_ has joined #linux-rockchip
premoboss has joined #linux-rockchip
dlezcano has quit [Remote host closed the connection]
premoboss has quit [Read error: Connection reset by peer]
premoboss has joined #linux-rockchip
dlezcano has joined #linux-rockchip
ganbold has quit [Ping timeout: 250 seconds]
nighty has quit [Quit: Disappears in a puff of smoke]
premoboss has quit [Quit: Sto andando via]
nighty has joined #linux-rockchip
nighty has quit [Remote host closed the connection]
nighty has joined #linux-rockchip
sunilmohan has quit [Quit: No Ping reply in 180 seconds.]
sunilmohan has joined #linux-rockchip
sunilmohan has quit [Ping timeout: 260 seconds]
cosm has quit [Ping timeout: 260 seconds]
nighty has quit [Quit: Disappears in a puff of smoke]
nighty has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
wadim_ has quit [Remote host closed the connection]
sonodivenutomort has joined #linux-rockchip
sunilmohan has joined #linux-rockchip
pietrushnic has quit [Quit: Coyote finally caught me]
sonodivenutomort has quit [Quit: Sto andando via]
ganbold has joined #linux-rockchip
steev has quit [Remote host closed the connection]
steev has joined #linux-rockchip
rory096 has joined #linux-rockchip
paulk-collins has joined #linux-rockchip
rory096 has quit [Ping timeout: 250 seconds]
matthias_bgg has quit [Quit: Leaving]
Kruppe has quit [Quit: ZNC - http://znc.in]
Kruppe has joined #linux-rockchip
diego71 has joined #linux-rockchip
paulk-collins has quit [Quit: Leaving]
<karlp> bleh, can't even get this mxq 4k+ box to even turn up on lsusb.
<karlp> ah, there we go
<karlp> as soon as you say something it starts to work :)
sunilmohan has quit [Ping timeout: 260 seconds]
sunilmohan has joined #linux-rockchip
<karlp> so, rk3229 is weird then, is it really meant to be an rk32xx device or an rk30xx? device
sunilmohan has quit [Ping timeout: 260 seconds]
<karlp> any nice tips on getting adb over wireless/ethernet? I need to hack some android stuff before I can try hacking linux on it.
<karlp> I've tried some "ADB Manager" which claims to autostart adb server, but it's not starting up, or at least, I can't connect to ti
<karlp> heh, "/dev/block/rknand_baseparamer" nice spelling there guys
<naobsd> karlp: what's weird? adb tcp connection doesn't work?
<karlp> needed root to get something that could turn on adb tcp on boot for me.
<karlp> got it now.
<karlp> just trying to ponder next steps.
<karlp> Should I be able to rkunpack a dd image of the boot partition?
<karlp> or should I use upgrade_tool/rkflashtool to dump the partition instead?
<naobsd> there is no difference
<naobsd> probably boot should be ANDROID! image, you need to use proper tool for "unpack". there is no difference for "dump"
<karlp> yeah, just found it's got a proper ANDROID! header,
<karlp> so I should be able to use the adnroid sdk tools for that then.
<karlp> ah, abootimg was what I'd forgotten
<naobsd> android sdk tools?
<naobsd> if you are talking about tools for ANDROID! image, you need to use mkbootimg in Rockchip SDK for packing. you may use any unpacking tool for ANDORID! image
<naobsd> mkbootimg for _Rockchip_ in Rockchip SDK or somewhere else
<naobsd> as same as past Rockchip SoCs.
<naobsd> nothing is changed
<karlp> yes, I think it's just that in the past I'd used rkflashtool/Upgrade_Tool to dump partitions, but this time I'd used dd from within android, so I was only seeing the direct ANDROID! image format this time.
<naobsd> any dumping tool doesn't convert image format
<naobsd> do't you have USB A-A cable?
<karlp> oh yeah, and that's how I got it up, but I want to put it back in another room,
<karlp> I know I'll hav eto use usb for any real reflashing.
<karlp> did you ever try mmind's tree or any mainline kernel on the mxq4k you got?
<naobsd> I tried rk3228-evb configuration in linux-next, and it worked
<naobsd> if your board is T066, there are UART2 holes for console
<karlp> oh, neat I don't think you'd gotten that far last time.
<karlp> that was with the kernel+dtb flashed to boot partition?
<karlp> ethernet/usb working?
<naobsd> boot.img with kernel+ramdisk+dtb will work, but I think I used kernel/boot(ramdisk)/resource(dtb) separately
<naobsd> I cannot remember detail. rk3228/3229 support was very few when I tried (February? March?) and I don't try anything lately
<naobsd> please check rk3228 dts. you can see what's supported
<naobsd> sorry, I have to leave now
<naobsd> if you want to use UART2, default bootloader binaries set console speed something not 115200
<karlp> ok, thanks for the notes
<naobsd> RK u-boot can be recompiled with 115200. you can use 115200 on kernel. other binary blobs (e.g. DDR init, trust) cannot be changed so you will see some garbage very beginning
<karlp> hrm, rk3228 in linux-next only has emmc and tsadc.