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
dlezcano has quit [Ping timeout: 260 seconds]
isle has joined #linux-rockchip
Tony_ has joined #linux-rockchip
RayFlower_ has joined #linux-rockchip
<Tony_> Interesting. the 3.10 version kernel can works fine. just use rkcrc make zImage-dts -> kernel.img. :P
<Tony_> And rkflashkit is very easy. I like it.
naobsd has quit [Quit: Page closed]
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
hipboi_ has quit [Ping timeout: 250 seconds]
Avagetto has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
hipboi has joined #linux-rockchip
benja` has quit [Ping timeout: 250 seconds]
benja` has joined #linux-rockchip
Astralix has joined #linux-rockchip
Astralix1 has quit [Ping timeout: 250 seconds]
isle has quit [Ping timeout: 246 seconds]
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
Avagetto has quit [Ping timeout: 255 seconds]
naobsd has joined #linux-rockchip
Avagetto has joined #linux-rockchip
Bludot has quit [Quit: Connection closed for inactivity]
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
dlezcano has joined #linux-rockchip
Avagetto has quit [Quit: Leaving.]
GriefNorth has joined #linux-rockchip
Avagetto has joined #linux-rockchip
Avagetto has quit [Client Quit]
Avagetto has joined #linux-rockchip
<Tony_> Anyone want to talk about linux 3.10 ?
dlezcano has quit [Ping timeout: 258 seconds]
Avagetto has quit [Quit: Leaving.]
dlezcano has joined #linux-rockchip
<Tony_> I saw many posts about Linux 3.10.
<Tony_> naobsd want to remove 3.10 branch ever.
<naobsd> yes
<naobsd> I don't stop someone use it
<naobsd> I just drop it from linux-rockchip repo
<naobsd> ^want to
<Tony_> Yeah, I can see your attitude about linux3.10 from your act.
<Tony_> You won't use it. will you ?
<naobsd> I will not use _that branch_
dlezcano has quit [Ping timeout: 260 seconds]
dlezcano has joined #linux-rockchip
<naobsd> I don't say I have no interest about 3.10
<Tony_> And which high version kernel(than 3.0.36) do you use ?
<naobsd> removing _that branch_ is not only my _attitude_
<Tony_> oh. a big deal ?
<naobsd> for example you can see "I was waiting this kernel support sdcard" at that topic
<naobsd> waiting == "I do nothing. hey you, you do it for me"
<naobsd> I cannot see someone "I do it", this is the reason I want to remove that branch
<naobsd> about the version I "use"
<naobsd> I don't have specific project, I don't "use" any version
<Tony_> Yeah, clear. they do nothing.
<naobsd> rkchrome's 3.10 is relatively old
<naobsd> 3.10 in rk3288 sdk is newer
<naobsd> this is another reason to remove _that branch_
<Tony_> Actually, I want to learn the new feature about kernel. such as dts(device tree) etc. that's the reason why I want to finding a high version kernel. :)
<Tony_> but I will do it if there are some bug. I won't like them. :P
Avagetto has joined #linux-rockchip
<naobsd> I recommend mainline
<Tony_> there should be a version at least.
<naobsd> mainline is latest version
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<Tony_> You wan to me modify from zero ? :-(
<Tony_> *want
<naobsd> mainline supports rk3188
hipboi_ has joined #linux-rockchip
<Tony_> is there a specific high version kernel we can develop _together_ ?
<Tony_> We can talk about it in here ?
hipboi has quit [Ping timeout: 255 seconds]
<rperier> hi all
<amstan> you guys are aware that we(google) are working with rockchip to get mainline supported nicely?
<Tony_> amstan, I haven't head that. can you talk about it ? how about details ?
<amstan> haven't you seen a ton of commits from both rockchip and chromium.org addresses in the linux kernel?
<amstan> we have a 3.14 kernel, your milage might vary on other boards other than the one we have
<amstan> but mainline works well on our board too, and it's getting better and better
<Tony_> amstan, That's a pretty good news.
antoinemaillard has joined #linux-rockchip
akaizen_ has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
<naobsd> Tony_: mainline, it is the version we(here) develop together
<naobsd> see discussion on here carefully, we'are talking about mainline.
<Tony_> Your mainline meas repo of linus ?
<naobsd> things like 3.0 kernel and my sd boot are little off-topic here
<Tony_> *means
<amstan> Tony_: linux next
<amstan> not sure what mainline actually means here, sorry, i got confused
<naobsd> amstan: no problem
<naobsd> _very strictly_ speaking, mainline will be only linus's linux repo
<Tony_> amstan, naobsd: okay clear now.
RayFlower_ has quit [Read error: Connection reset by peer]
<naobsd> but "currently in development for mainline" things are in linux-next and many other repos per subsystem/arch/etc
<naobsd> ^are also
RayFlower_ has joined #linux-rockchip
<Tony_> naobsd, but I can find a correct branch from https://github.com/linux-rockchip/kernel_rockchip/branches.
<Tony_> can't
<Tony_> *can't
<amstan> Tony_: yeah.... don't go from that, most rockchip people are using the chrome repo for development
<naobsd> Tony_: it's for Android SDK based kernel, it's not mainline
AstralixNB has joined #linux-rockchip
<amstan> but whatever's upstreamable goes on mailing lists and evetually on linux next
<Tony_> amstan, I think this one is you said. https://github.com/rkchrome/kernel/
<Tony_> naobsd, I fork from https://github.com/torvalds/linux.
<Tony_> ?
<amstan> latest commit there is aug 7, they don't use github anymore
<naobsd> Tony_: github/rkchrome is not updated
<naobsd> Tony_: if you don't want "in development" thing, try torvalds/linux
<Tony_> Oh, I think there should be a Guild about repo.
<amstan> guild?
<naobsd> well?
<Tony_> *guide.
<Tony_> sorry.
<amstan> what repo?
<amstan> repo as in the chromeos tool?
<naobsd> I think "git repository"
<amstan> ok
<naobsd> Tony_: "repo" is also command name
<naobsd> Tony_: it's not clear
<Tony_> okay. noted.
<amstan> Tony_: anyway, can you rephrase that?
<amstan> a guide about a repository? what repository?
<Tony_> naobsd is right. my "repo" is mean "git repository".
<amstan> ok, which repository?
<Tony_> I just confused that there are so many git repository, I don't know which one is correct.
<Tony_> So, I say that there should be a guide.
<amstan> Tony_: each one has its own purpose
<amstan> for different areas of the kernel
<naobsd> torvalds/linux is the last stop
<amstan> i still suggest linux next
<naobsd> MAINTAINERS will be a guide
<Tony_> I thought github's repository is correct before. but I'm clear now.
<amstan> i don't really know the address offhand
mrcan has joined #linux-rockchip
<naobsd> amstan: yes, for development
<amstan> naobsd: in this case, for something where we're still enabling things you probably still want linux next
<amstan> also... either way you need to maintain a dts file
eebrah has quit [Remote host closed the connection]
eebrah has joined #linux-rockchip
mrcan has quit [Read error: Connection reset by peer]
mrcan has joined #linux-rockchip
<Tony_> I will finish it.
<amstan> Tony_: 3 is the same as 2, you should remove it
<naobsd> I don't recommend 1
<amstan> no, stay far away from 1, it's not even mainline like
<Tony_> amstan, okay, I will add it.
<amstan> there's also that
<Tony_> naobsd, "I don't recommend 1" is means "you don't recommend the explaintion" ?
<naobsd> Tony_: dead repository shouldn't be listed
<amstan> Tony_: that whole repository seems to be just an import of what we had in the chrome repository: https://github.com/rkchrome/kernel/commit/f57ea419e8d19dceb9b00abc2c0de2341e295881
<Tony_> But I think I need to tell everybody because we can't stop they get it and confused. :)
<amstan> going to sleep
<naobsd> there are many many "don't use it" forks...
<naobsd> amstan: good night
<Tony_> amstan, okay good night.
RayFlower_ has quit [Quit: RayFlower_]
<AstralixNB> good morning :)
<Tony_> good afternoon :P
<AstralixNB> good ${your_personal_daytime}
mrcan has quit [Read error: Connection reset by peer]
mrcan has joined #linux-rockchip
antoinemaillard has quit [Ping timeout: 250 seconds]
dlan has quit [Ping timeout: 272 seconds]
dlezcano has quit [Ping timeout: 264 seconds]
dlezcano has joined #linux-rockchip
Guest89439 has joined #linux-rockchip
eebrah has quit [Remote host closed the connection]
eebrah has joined #linux-rockchip
Guest89439 has quit [Quit: leaving]
dlezcano has quit [Ping timeout: 250 seconds]
dlezcano has joined #linux-rockchip
<Tony_> naobsd, I updated the GUIDE.
<Tony_> And would you like to talk about: https://github.com/linux-rockchip/kernel_rockchip
<Tony_> I post the link again. here:https://drive.google.com/open?id=0B6NGoH-iSqrKVUNfUmNHYmJNNW8&authuser=0
wildea01 has joined #linux-rockchip
<karlp> particularly in the "mainline" section of that page
<karlp> guide looks good though :)
<Tony_> karlp, thank you. i want to but I can't .
<karlp> why not?
ZZambia has quit [Read error: Connection reset by peer]
<Tony_> oh, got it. I will do that. :P create a accout and post it.
<Tony_> I thought I have no permission.
<Tony_> before.
<karlp> :)
<karlp> edit at will
<Tony_> okay.
Avagetto has quit [Ping timeout: 245 seconds]
dlezcano has quit [Quit: Leaving]
dlezcano_ has joined #linux-rockchip
dlezcano_ is now known as dlezcano
Avagetto has joined #linux-rockchip
Avagetto has quit [Quit: Leaving.]
antoinemaillard has joined #linux-rockchip
<naobsd> Tony_: 3. and 4. are same
<Tony_> okay.
<naobsd> Tony_: "<amstan> you guys are aware that we(google) are working with rockchip to get mainline supported nicely?" "<amstan> haven't you seen a ton of commits from both rockchip and chromium.org addresses in the linux kernel?" "<amstan> but mainline works well on our board too, and it's getting better and bette" are about 3.
<naobsd> Tony_: I think picking random message from IRC is not "guide"
<Tony_> okay, It is not "guide", but I think it will be useful to somebody who is new here.
<naobsd> Tony_: at least you're confusing which message for which
<naobsd> Tony_: I recommend to drop 1
<naobsd> Tony_: at least 1. shouldn't be first
<Tony_> okay, I will move it.
<Tony_> naobsd, "<amstan> we have a 3.14 kernel, your milage might vary on other boards other than the one we have"
<Tony_> I think he is talking about 3.14 not linux-next.
<Tony_> see "<amstan> but mainline works well on our board too, and it's getting better and bette"
<naobsd> Tony_: I didn't claim about "<amstan> we have a 3.14 kernel, your milage might vary on other boards other than the one we have" because it's about 5. please read IRC log carefully
<naobsd> again, picking random IRC message make confusion, it's not guide.
<Tony_> for "picking random IRC message make confusion, it's not guide."
<Tony_> in you opinion, how to write it ?
<naobsd> understanding them, then write summary/digest
<karlp> yeah, well, write once, write again.
<karlp> if he hadn't written that down at all, there'd be nothing at all beyond an unsearchable irc log
<Tony_> okay, I will try to do that. And how about this time. IRC_LOG(not guide so far). https://drive.google.com/open?id=0B6NGoH-iSqrKVUNfUmNHYmJNNW8&authuser=0
<Tony_> <naobsd>, If it's okay, would you like to talk about: https://github.com/linux-rockchip/kernel_rockchip
antoinemaillard has quit [Ping timeout: 244 seconds]
<naobsd> Tony_: others a. is about 4, drop it
<naobsd> Tony_: others b. is git repository for "linux-rockchip community"
<Tony_> okay.
<naobsd> btw kernel_rockchip and u-boot-rockchip on github/linux-rockchip shouldn't be fork from rkchrome... at that time rkchrome was most better repository, but now github/radxa has more better repos :(
<naobsd> better = has a history from RK
<Tony_> Yeah.
<naobsd> radxa branches on linux-rockchip will be moved(actually, already moved) to github/radxa
<naobsd> and active branches on linux-rockchip is not so many
<naobsd> it might be ok to rebase... but I already rebased some times, not good at all ;)
<Tony_> okay.
dlezcano has quit [Ping timeout: 255 seconds]
<naobsd> (probably I will not rebase unless some people request to do it strongly)
dlezcano has joined #linux-rockchip
<Tony_> github/linux-rockchip is most like github.com/rkchrome/ in the feature. right ?
<naobsd> why? rkchrome seems dead, we are not dead
<Tony_> okay, clear . can you give me some name of active branches ?
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
<naobsd> Tony_: about kernel tree? or whole github/linux-rockchip?
<Tony_> naobsd> and active branches on linux-rockchip is not so many
<naobsd> I talked about whole github/linux-rockchip, not about your guide
<Tony_> oh.... clear.
akaizen has quit [Ping timeout: 255 seconds]
dlezcano has quit [Ping timeout: 258 seconds]
dlezcano has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 245 seconds]
FreezingCold has joined #linux-rockchip
Tony_ has quit [Quit: Leaving]
dlezcano has quit [Ping timeout: 265 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 272 seconds]
naobsd has quit [Quit: Page closed]
nighty^ has joined #linux-rockchip
Tony__ has joined #linux-rockchip
Avagetto has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 244 seconds]
dlezcano has joined #linux-rockchip
Avagetto has quit [Quit: Leaving.]
Avagetto has joined #linux-rockchip
Tony__ has quit [Quit: Leaving]
FreezingCold has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 244 seconds]
LinuxBot__ has joined #linux-rockchip
hramrach_ has quit [Ping timeout: 250 seconds]
hramrach_ has joined #linux-rockchip
<LinuxBot__> anyone working on buildroot for rockchip ?
cosm has quit [Quit: Leaving]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<Avagetto> Buildroot == rootfs?
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 244 seconds]
provel_ has joined #linux-rockchip
provel_ has quit [Client Quit]
<LinuxBot__> avagetto : yes
AstralixNB has quit [Ping timeout: 250 seconds]
Linux_Bot has joined #linux-rockchip
FreezingCold has joined #linux-rockchip
<Avagetto> what you need? how i can help
<Avagetto> I have a couple of system images
<Avagetto> usually i download ubuntu core img and them install packages
FreezingCold has quit [Ping timeout: 265 seconds]
<rperier> However there is a working yocto bsp meta layer for rockchip
<rperier> naobsd maintains miniroot, it is based on buildroot if I remember correctly
<rperier> when you see "ethernet@10204000" in the devicetree, it is for memory mapped devices. Where did you get these base address ? I don't find these in the datasheet
<karlp> TRM page 89?
<karlp> (for rk30xx at least)
<karlp> the mac section oddly only includes offsets, but doesn't mention the base address again.
<rperier> looking
<karlp> page 78 in the TRm v1.3 for rk3188
<rperier> yep, you're right
<rperier> I have probably mud in my eyes :D
<rperier> thanks
<karlp> least I can do :)
<Linux_Bot> Avagetto: i need build rootfs for own
<Linux_Bot> rperier: yes. i saw. need build my own rootfs for 3066 board
<rperier> which board ?
<Linux_Bot> if we setup buildroot config for rockchip devices. so users can build rootfs. it will get small footprint
<Linux_Bot> rk3066
<rperier> rk3066 is the SoC
<Linux_Bot> yes
<Linux_Bot> now.. android, ubuntu and some other linux versions are working fine.
<Linux_Bot> but if we build , our own linux. its easy to reduce rootfs size
<rperier> because, in meta-rockchip for example support for marsboad-rk3066 was added recently. rk3066 is supported but you might need to add some stuffs to support another board (that's not really difficult if you have a defconfig for your kernel or if you know how to configure the kernel for this board)
<rperier> (well, I forgot the devicetree too, depending on the board it might works with mainline kernel...)
<Linux_Bot> rperier: do you have link for yocto meta download ?
antoinemaillard has joined #linux-rockchip
<rperier> yes
<Linux_Bot> ok.. i will this
<rperier> the master branch contains support for the 3.0.36 kernel. We actively develop in the mainline branch
<rperier> (which works with linux-next)
<rperier> have a look at "miniroot" too
<rperier> karlp: naobsd works on miniroot, right ?
<rperier> (for rockchip)
AstralixNB has joined #linux-rockchip
<karlp> the androtab.info miniroot? yeah, that's his work.
<Linux_Bot> rperier: ok bro. i will try that too
<Linux_Bot> karlp: yes, http://androtab.info/miniroot/
AstralixNB has quit [Quit: Leaving.]
antoinemaillard has quit [Ping timeout: 260 seconds]
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
eebrah has quit [Quit: leaving]
FreezingCold has joined #linux-rockchip
Avagetto has quit [Ping timeout: 260 seconds]
FreezingCold has quit [Ping timeout: 244 seconds]
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
Avagetto has joined #linux-rockchip
FreezingCold has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
RayFlower_ has quit [Quit: RayFlower_]
akaizen has joined #linux-rockchip
dlezcano has quit [Ping timeout: 255 seconds]
bengal has joined #linux-rockchip
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 255 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 245 seconds]
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 240 seconds]
dlezcano has joined #linux-rockchip
<Linux_Bot> is there any guide for u-boot on rockchip 3066 for linux ?
dlezcano has quit [Ping timeout: 250 seconds]
dlezcano has joined #linux-rockchip
akaizen_ has joined #linux-rockchip
akaizen has quit [Ping timeout: 244 seconds]
dlezcano has quit [Ping timeout: 244 seconds]
dlezcano has joined #linux-rockchip
nighty^ has quit [Quit: Disappears in a puff of smoke]
dlezcano has quit [Ping timeout: 245 seconds]
dlezcano has joined #linux-rockchip
bengal has quit [Quit: Leaving]
dlezcano has quit [Ping timeout: 264 seconds]
dlezcano has joined #linux-rockchip
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
<Linux_Bot> rperier: getting error, on yocto
<Linux_Bot> ERROR: Error: The image creation script '/home/linuxbot/poky/build/tmp/work/mars_board-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/create_image.rockchip-update-img' returned 1:
<Linux_Bot> error: could not load ramdisk 'initrd.img'
<Linux_Bot> WARNING: /home/linuxbot/poky/build/tmp/work/mars_board-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/create_image.rockchip-update-img:1 exit 1 from
<Linux_Bot> mkbootimg --kernel zImage --ramdisk initrd.img -o boot.img
<Linux_Bot> ERROR: Function failed: do_rootfs
<Linux_Bot> ERROR: Logfile of failure stored in: /home/linuxbot/poky/build/tmp/work/mars_board-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.32264
<Linux_Bot> ERROR: Task 7 (/home/linuxbot/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1'
naobsd has joined #linux-rockchip