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
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<naobsd> rperier: name of label should be changed https://www.kernel.org/doc/Documentation/leds/leds-class.txt
<naobsd> "devicename:colour:function"
FreezingDroid has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 272 seconds]
<naobsd> maybe state1/state2/sleep are devicename
<naobsd> btw, cpufreq support is already merged in mainline?
RayFlower has quit [Read error: Connection reset by peer]
FreezingDroid has quit [Quit: Out]
RayFlower has joined #linux-rockchip
FreezingCold has joined #linux-rockchip
<naobsd> hm, it's already in linux-next
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
cnxsoft 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
akaizen_ has quit [Remote host closed the connection]
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 258 seconds]
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
Tony_ has joined #linux-rockchip
<Tony_> naobsd, actually I don't used linux-nand-driver_Patch_V2.6.
<Tony_> RK said that the patch is correct for NEW device.
<Tony_> then I haven't tried the bootloader of the patch.
Astralix1 has joined #linux-rockchip
Astralix has quit [Ping timeout: 250 seconds]
<Tony_> I remember RK said the version 1.x and 2.x of bootloader are different.
<Tony_> I used only 1.x version.
<Tony_> There are new bootloaders and SD_Firmware_Tool_SDboots from RK. I will share it if you need it.
Tony_ has quit [Quit: Leaving]
akaizen has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
Tony_ has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<naobsd> I have SD_Firmware_Tool._v1.43
<Tony_> There are some new version loader which can be supported win8.
<Tony_> and SD_Firmware_Tool_1.4_with_sdboot_1.17&2.16.
<Tony_> That was from RK.
field2^Mop has joined #linux-rockchip
field^Mop has joined #linux-rockchip
field2^Mop has quit [Read error: Connection reset by peer]
field^Mop has quit [Client Quit]
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
gb_master 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
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
bengal 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
dlan has quit [Ping timeout: 244 seconds]
dlan has joined #linux-rockchip
field2^Mop has joined #linux-rockchip
<field2^Mop> hey
<field2^Mop> is this http://storage.armcloud.us/kernel-ci/next/next-20141121/arm-multi_v7_defconfig+CONFIG_ARM_LPAE=y/boot-rk3288-evb-rk808.html some kind of continous integration system? if so what is it? i' m intrigued as i don't know it yet. tia!
gb_master has quit [Quit: Leaving]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
Okitain has joined #linux-rockchip
<rperier> naobsd: no according to some dts files in arch/arm/boot/dts (sun4i, omap3-beagle) devicename should be the name of the board, so something like "radxarock:red:power", "radxarock:blue:mmc" and "radxarock:green:heartbeat" looks good
Okitain has left #linux-rockchip ["http://quassel-irc.org - Chat comfortably. Anywhere."]
<rperier> most of the time device_node are named to the color of the led and label are devicename:color:function where devicename is the name of the board, color the led color, and function is its description
<rperier> (but there are not real rules for the subnode name in the dts)
<rperier> (note that I just added label in this commit, the trigger stuffs is for you naobsd)
<rperier> (as this is your proposal and your ideas...)
<rperier> ;)
<naobsd> rperier: sleep is not color and radxa is not board name
<rperier> as I said, there are not real rules for the subnodes name
<rperier> so, you propose "rock:red:power" instead of "radxarock:red:power" ?
<rperier> (I just used the same "board name" as the dts file)
<naobsd> rperier: yes and no. I also saw several *.dts and my first concusion was to use board name for "device name" part
<naobsd> but "rock" (or "radxarock") doesn't have any information
<naobsd> so I'm thinking what's "devicename"...
<naobsd> it may be "eth0:green:link" "kbd0:red:caps"
<naobsd> ^just example, not for RR
<rperier> mmind00: Heiko ? opinion ?
Tony_ has quit [Quit: Leaving]
<karlp> openwrt normally has eithe rfull device name, ie, "radxarock:red:power" or sometimes just the brand, ie "radxa:red:power"
<karlp> and they've got _lots_ of leds consistently like that.
<karlp> (I've got no opinions on the device node labels)
<karlp> what's the green heartbeat led labelled on the box with?
<karlp> because you can use triggers to make it a heartbeat, but the led names normally match the physical text on the case or the pcb
markm_ has joined #linux-rockchip
<naobsd> no text on board
<rperier> yes, this is what I checked, I did not find text on board
<rperier> problem being that the trigger can be changed from userspace, so hardcode "heartbeat" in the interface name is not good, imho
* karlp agrees
<karlp> some of the openwrt boards just call unlabelled leds "user1" "user2" and so on.
<karlp> or "message"
<karlp> or "diag" ?
JohnDoe_71Rus has joined #linux-rockchip
nighty^ has joined #linux-rockchip
<naobsd> my idea is "rock:green:user1" "rock:blue:user2" "rock:red:power" or replace "rock" part with text in schematics
<naobsd> or gpioXXX:color:func ?
<naobsd> sleepy
<naobsd> my head is not clear...
<naobsd> rperier: you said you're using kexec, is it mainline kernel?
ganbold_ has quit [Remote host closed the connection]
<rperier> naobsd: I agree, that's a good idea (user1, user2 and power)
<rperier> I understand better why some dts files contain these interface names, now
JohnDoe_71Rus has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]
<rperier> naobsd: yeah it is in mainline , I use kexec to boot from *whatever* with a minimalistic initramfs and script shell (like from the network)
<rperier> (a kind of userspace bootloader)
<naobsd> rperier: thanks for the info. I want to setup rk3066 which loads kernel from non-NAND
<rperier> (in files)
<rperier> it works with rk3188 and rk3066
<rperier> I use kexec with rr and marsboard :)
<naobsd> rperier: I tried u-boot with SD boot configuration, but u-boot cannot find SD card for now
<naobsd> I guess board specific init is required to use SD on u-boot, but I have no info about my rk3066 board
<rperier> yeah probably
<naobsd> so I'm thinking to use kexec (but it also need board specific info...)
<rperier> kexec from uboot ?
<naobsd> no, what I want is "load kernel from SD card"
<naobsd> SD support on u-boot or kexec on mainline
<naobsd> I should get rk3066 device with board info/source ;)
<naobsd> I want to get PX2 board
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
cnxsoft1 has quit [Remote host closed the connection]
ganbold_ 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
bengal has quit [Quit: Leaving]
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
ganbold_ has quit [Remote host closed the connection]
<karlp> rperier: do you still want to call it "sleep" in the dts section label?
<karlp> can those nodes even just be anonymous?
AstralixNB has joined #linux-rockchip
<field2^Mop> rperier: what env is net-kexec_1.0.bb part of? sounds like busybox scripting.
<field2^Mop> if such a thing exists, that is
<field2^Mop> is that note regarding u-boot on radxa site still valid: do not flash this self-compiled .bin?
<rperier> field2^Mop: yes it is just a busybox script
<rperier> (which requires kexec tools in userspace and kexec support in the kernel)
<rperier> karlp: anonymous ? what do you mean ? without a name ?
<rperier> that's not possible in the devicetree, what we did is that we name these subnodes like in the schematic
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
irsol has quit [Ping timeout: 244 seconds]
irsol has joined #linux-rockchip
<karlp> rperier: yeah, I don't know devicetree well enough, and it seemed like those names for the blocks aren't used anyway,
irsol has quit [Ping timeout: 250 seconds]
irsol has joined #linux-rockchip
irsol has quit [Ping timeout: 265 seconds]
irsol has joined #linux-rockchip
irsol has quit [Ping timeout: 244 seconds]
<rperier> feel free to propose suggestions on the ML (in reply to my patch) ;)
irsol has joined #linux-rockchip
<field2^Mop> rperier: nice idea. when i was fiddling with an embd board last time it was a 2.6.3x kernel that hadn't the kexec feature. though i would've highly appreciated the functionality of your script.
irsol has quit [Ping timeout: 245 seconds]
irsol has joined #linux-rockchip
<mmind00> rperier: do you still need input? (the "ping" was quite some time ago)
irsol has quit [Read error: Connection reset by peer]
irsol has joined #linux-rockchip
<rperier> mmind00: no already sent to ML :)
irsol has quit [Ping timeout: 272 seconds]
irsol has joined #linux-rockchip
irsol has quit [Ping timeout: 255 seconds]
irsol has joined #linux-rockchip
nighty^ has quit [Remote host closed the connection]
irsol has quit [Ping timeout: 264 seconds]
irsol has joined #linux-rockchip
irsol has quit [Ping timeout: 255 seconds]
irsol has joined #linux-rockchip
field^Mop has joined #linux-rockchip
irsol has quit [Ping timeout: 272 seconds]
irsol has joined #linux-rockchip
field2^Mop has quit [Quit: Bye]
field2^Mop has joined #linux-rockchip
field2^Mop has quit [Client Quit]
irsol has quit [Ping timeout: 245 seconds]
<c0d3z3r0> hey guys I hope someone can help me. I'm always getting a kernel panic when using CONFIG_MMC_DW_ROCKCHIP with 3.18-rc5 and rk30_rk31_defconfig. http://pastebin.com/C5z5zhsM
<c0d3z3r0> any ideas?
irsol has joined #linux-rockchip
irsol has quit [Ping timeout: 245 seconds]
irsol has joined #linux-rockchip
irsol has quit [Ping timeout: 258 seconds]
irsol has joined #linux-rockchip
<c0d3z3r0> anyone?
<rperier> c0d3z3r0: do you have logs and a backtrace ?
<rperier> it might be useful
<c0d3z3r0> I only have the kernel messages from telnet
<field^Mop> rperier: what would be your preferred demarche if your serial login tells you after typing your username 'cannot start /bin/login'? network is not coming up, so no ssh.
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
<mmind00> c0d3z3r0: looks somehow a bit like https://lkml.org/lkml/2014/9/2/674
<c0d3z3r0> mmind00: thank you, the patch fixed it
<mmind00> c0d3z3r0: so maybe dianders knows what became of his "mmc: dw_mmc: Don't enable interrupts until we're ready" patch linked above, because the replies indicate that it wasn't the preferred solution
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
field^Mop has quit [Quit: leaving]
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
field^Mop has joined #linux-rockchip
field^Mop has quit [Quit: leaving]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
field^Mop has joined #linux-rockchip
field^Mop has quit [Client Quit]
<c0d3z3r0> dianders: after applying that patch from linux-next I got bad problems with the ethernet device http://pastebin.com/Dh0aB97E
<c0d3z3r0> the first patch was working perfectly
<amstan> well that's no fun
<dianders> You applied (5998ad0 mmc: dw_mmc: Remove old card detect infrastructure) and it caused an ethernet crash?
<dianders> Seems hard to believe...
<c0d3z3r0> dianders: yep, I didn't change anything other
<c0d3z3r0> the device wasn't reachable with ping; after a reboot that worked; at the second reboot I got that kernel panic
<dianders> c0d3z3r0: hmmm, not sure then. Sorry! I've been using that patch for a long time. Only guess is a timing issue...
<c0d3z3r0> and now another one while booting http://pastebin.com/M3uMYM8W
<amstan> c0d3z3r0: did you get any other patch since it happened? can you bisect it?
<dianders> unfortunately, I'm outta here for now. I'll be back online tomorrow...
<c0d3z3r0> the only patch I applied was that from linux-next uhm I didn't use bisect before and don't know how that works, I'm sorry
<c0d3z3r0> yeah me too. sleeping time now...
field^Mop has joined #linux-rockchip
field^Mop has quit [Client Quit]
field^Mop has joined #linux-rockchip
ganbold_ has joined #linux-rockchip
AstralixNB has quit [Ping timeout: 250 seconds]
field^Mop has quit [Quit: leaving]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip