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
Soopaman has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Client Quit]
Soopaman has quit [Quit: Leaving.]
Astralix1 has joined #linux-rockchip
Astralix has quit [Ping timeout: 250 seconds]
<naobsd> mmmmm
naobsd has quit [Quit: Page closed]
naobsd has joined #linux-rockchip
<naobsd> mmm..... I tried cpufreq on devel/workbench, but same result, 1.2GHz works, 1.4GHz doesn't work :(
<naobsd> fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected!
<naobsd> VDD_CPU: 850 <--> 1350 mV at 1000 mV
<naobsd> 1.4GHz doesn't work -> freeze just after change
bengal has joined #linux-rockchip
<mmind00> naobsd: still a sympthom of the voltage not being high enough ... i.e. some sort of regulator problem
<mmind00> naobsd: try exchanging the fan53555 regulators (i.e. use the other one for the cpu)
<mmind00> naobsd: the cpufreq code itself was stress-tested by a lot of poeple already, so it is likely more a problem of the board-dts
<naobsd> board-dts or board itself ;)
<naobsd> I didn't try to exchange cpu<>gpu, I'll do it
<naobsd> mmm, exchanged, freezed :(
<naobsd> need more investigation...
<naobsd> or wait firefly ;)
<naobsd> try to fix vdd_cpu to 1.35 by default....
<naobsd> it works...
<naobsd> ah, opp in devel/workbench uses bit lower voltages...
<naobsd> use same voltages(not fixed) as 3.10 kernel -> freezed
<naobsd> confusing...
<naobsd> if all voltages in opp in rk3288.dtsi are changed to 1.35V, it doesn't work
<naobsd> if regulator-min-microvolt in vdd_cpu (syr827) changed to 1.35V (min == max)
<naobsd> if regulator-min-microvolt in vdd_cpu (syr827) changed to 1.35V (min == max) (and no opp change), it works
<naobsd> I can see "cpufreq_cpu0: failed to scale voltage down: -1" error on later case
<naobsd> so
<naobsd> mmm
<naobsd> changing voltage may not be stable on this board?
<naobsd> comment out cpu0-supply = <&vdd_cpu>; and use 1.35V for regulator-min-microvolt -> doesn't work :(
<naobsd> regulator-min-microvolt = 1.35v && all opp volts == 1.35v -> doesn't work
<naobsd> it works only when I can see "cpufreq_cpu0: failed to scale voltage down: -1"
<naobsd> (and "cpufreq_cpu0: failed to scale voltage up: -1" after cpu clock is up)
<naobsd> ah
<naobsd> well
<naobsd> I'm not sure clk_set_rate() is really done
<naobsd> it shouldn't be done if "failed to scale voltage up" occurred
<naobsd> hmm, ok,
<naobsd> my brain is not clear :(
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 seconds]
RayFlower has joined #linux-rockchip
arokux2 has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<arokux2> several noob questions. what is your mainline work flow? do you always flash the new kernel? or you copy it through ssh? once it paniced do you need to reflash? is there something like u-boot console with tftp/usb support etc?
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<naobsd> I'm flashing kernel for now
<arokux2> naobsd: like described here in the bottom? http://radxa.com/Rock/Linux_Mainline
<naobsd> yes
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<arokux2> naobsd: "rkflashtool w boot < boot.img" what address should be used here instead of boot for radxa?
<naobsd> arokux2: no address is needed in that case
<naobsd> or general answer is "it depends on partition layout in parameter"
<arokux2> naobsd: I see now after reading the code :)
<arokux2> naobsd: where do you normally document stuff? linux-rockchip.info ?
<naobsd> arokux2: I'm the person who don't write wiki...
<arokux2> naobsd: can radxa boot from sd card?
<arokux2> naobsd: can it boot the kernel from sd?
<naobsd> arokux2: everything include kernel can be placed on SD
<arokux2> naobsd: I've found this http://talk.radxa.com/topic/278/custom-sd-card-boot-image is this the last info available? I'm struggling to understand what is the current understanding of RK3188
<arokux2> naobsd: yes, but this page then sends to the forum which has more details
<arokux2> naobsd: but rkflashtool would flash NAND, so you do not flash sd card for you development?
<naobsd> more details?
<naobsd> well
<arokux2> naobsd: like some openssl comamnds..
<naobsd> for development, I can flash kernel with upgrade_tool/rkflashtool AND I can prepare SD card
<naobsd> well, I can use both NAND and SD
<naobsd> no reason not to use (one of them)
<arokux2> naobsd: right. I'm just exploring possibilities :)
<arokux2> firefly looks so similar to radxa!
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
Soopaman 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
<naobsd> hmm, fastboot mode doesn't work well :(
<naobsd> rkflashtool now supports "reboot to maskrom"
<naobsd> (if bootloader support it)
<naobsd> it's possible to add non-standard reset flag e.g. boot to recovery
<naobsd> but I don't do it for now
ganbold__ has joined #linux-rockchip
<naobsd> "fastboot boot" should be supported
<naobsd> to load kernel/ramdisk/dtb into RAM
<naobsd> please fix ;)
ganbold_ has quit [Remote host closed the connection]
<arokux2> naobsd: what is the hardware the rkflashtool is talking to?
<arokux2> naobsd: SoC in some special mode?
<naobsd> mask rom(very initial loader in CPU) and bootloader loaded from NAND/SD/USB/etc
<naobsd> bootloader specifically(=I could confirm) RK proprietary loader and u-boot on RK3188, u-boot on RK3288
<naobsd> there is another bootloader but I'm not sure it supports rockusb protocol
<naobsd> it's possible to implement rockusb protocol to another bootloader(actually, any software such as Linux kernel)
<naobsd> which is easy?: fix fastboot or implement read/write/exec RAM ;)
<naobsd> sleepy
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
lioka has joined #linux-rockchip
<arokux2> naobsd: why fastboot is broken? or it is rather not implemented?
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
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
akaizen has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
benja` is now known as benja
amstan has quit [*.net *.split]
karlp has quit [*.net *.split]
honx has quit [*.net *.split]
hramrach_ has quit [*.net *.split]
karlp_ has joined #linux-rockchip
honx has joined #linux-rockchip
amstan has joined #linux-rockchip
hramrach_ 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
nighty-_ has joined #linux-rockchip
Astralix1 has quit [Read error: Connection reset by peer]
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
karlp_ is now known as karlp
bengal has quit [Quit: Leaving]
nighty-_ has quit [Quit: Disappears in a puff of smoke]
benja is now known as benja`
Soopaman 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
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
arokux2 has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
hipboi_ has quit [Ping timeout: 255 seconds]