ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
kevery has joined #linux-rockchip
stikonas_ has quit [Remote host closed the connection]
vstehle has quit [Ping timeout: 264 seconds]
maze-BUG has quit [Ping timeout: 240 seconds]
urjaman has quit [Ping timeout: 250 seconds]
vstehle has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
maze-BUG has joined #linux-rockchip
JohnDoe_71Rus has quit [Ping timeout: 264 seconds]
JohnDoe_71Rus has joined #linux-rockchip
JohnDoe_71Rus has quit [Ping timeout: 264 seconds]
field^Zzz2 has joined #linux-rockchip
ldevulder_ is now known as ldevulder
vagrantc has quit [Quit: leaving]
maze-BUG has quit [Remote host closed the connection]
maze-BUG has joined #linux-rockchip
maze-BUG has quit [Ping timeout: 260 seconds]
maze-BUG has joined #linux-rockchip
urjaman has joined #linux-rockchip
Cruft has quit [Quit: Leaving]
kevery has quit [Ping timeout: 250 seconds]
stikonas has joined #linux-rockchip
kevery has joined #linux-rockchip
kevery has quit [Ping timeout: 258 seconds]
mrueg has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
mrueg has joined #linux-rockchip
<robmur01_> nomis: without knowing what exactly yocto is producing and from what sources it's hard to say, but seeing no output whatsoever suggests that the initial loader (miniloader/idbloader.img depending on which u-boot flow) isn't getting flashed, since that normally says *something* even if it fails to progress to the main bootloader stage
<robmur01_> for boxes that stick closely to the reference design with LPDDR3 and RK805 PMIC, upstream u-boot for the EVB config should be close enough to at least boot from eMMC or SD (certainly that's the case on my Beelink) - for LPDDR4 or the cheapo boards that use PWM regulators instead of a PMIC I'm not so sure
<robmur01_> also, mixing upstream and downstream images on the same eMMC/SD card can lead to weirdness where you flash all the new images to the right places yet it still somehow boots the old downstream crap from somewhere - zeroing out the entire first 8MB of the device cleans that up.
<nomis> robmur01_: I am a little bit embarrassed to admit it, but I've confused rk3328 and rk3288. I think I've built a wrong bootloader.
<nomis> (right now trying to massage the u-boot for the rk3288 to build. It does not yet)
<nomis> robmur01_: yeah, that the "Loader" mode of the bootloader silently does not erase the start of the emmc on the "ef" command confused the heck out of me.
<robmur01_> oh yes, 3328 code on 3288 will be very dead as it's the wrong ISA :)
<nomis> well, it was 3288 code on a 3328, but I guess the same is valid there :)
<robmur01_> heh, well FWIW the other day I brought my 3288 box back to life with current upstream u-boot, and can confirm that that works too :)
<nomis> I am right now a bit in a pickle, since my yocto-tree is still based on the "thud" release which still has this "u-boot-rockchip_20171218.bb" recipe which fails to build for me.
<nomis> I wonder if I should just bite the bullet and switch to dunfell.
matthias_bgg has joined #linux-rockchip
ddas has joined #linux-rockchip
rperier has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
rperier has joined #linux-rockchip
ldevulder has quit [Remote host closed the connection]
chewitt has quit [Read error: Connection reset by peer]
chewitt_ has joined #linux-rockchip
chewitt_ is now known as chewitt
ldevulder has joined #linux-rockchip
return0e_ has quit [Read error: Connection reset by peer]
return0e has joined #linux-rockchip
dp has quit [Ping timeout: 258 seconds]
dp has joined #linux-rockchip
armoon has joined #linux-rockchip
chewitt has quit [Read error: Connection reset by peer]
chewitt has joined #linux-rockchip
sphalerite has quit [Quit: WeeChat 2.7.1]
sphalerite has joined #linux-rockchip
daniels has quit [Ping timeout: 272 seconds]
daniels has joined #linux-rockchip
armoon has quit [Remote host closed the connection]
ddas has quit [Remote host closed the connection]
Cruft has joined #linux-rockchip
adjtm has quit [Remote host closed the connection]
adjtm has joined #linux-rockchip
<JPEW> nomis: The rockchip support has improved significantly since thud
<JPEW> especially for rk3288 and rk3399
<nomis> JPEW: should I just use master?
<JPEW> either master or dunfell should be fine
<Cruft> Does the RK3399 take well to undervolting the big cores?
<Cruft> I noticed in tablet usage coreboot settings some places bumped the little core voltage and lowered big, but i wanted to know if both lows are acceptable and people are just being conservative
Cruft has quit [Ping timeout: 256 seconds]
Cruft has joined #linux-rockchip
maze-BUG1 has joined #linux-rockchip
damex has joined #linux-rockchip
maze-BUG has quit [Ping timeout: 256 seconds]
maze-BUG1 is now known as maze-BUG
lkcl__ has joined #linux-rockchip
lkcl_ has quit [Ping timeout: 264 seconds]
Cruft has quit [Read error: Connection reset by peer]
Cruft has joined #linux-rockchip
field^Zzz2 has quit [Ping timeout: 240 seconds]
matthias_bgg has quit [Ping timeout: 256 seconds]
mraynal has quit [Remote host closed the connection]
vstehle has quit [Ping timeout: 265 seconds]
mraynal has joined #linux-rockchip
vstehle has joined #linux-rockchip
tuxd3v has quit [Quit: Leaving]
ldevulder_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 258 seconds]
tuxd3v has joined #linux-rockchip
tuxd3v has quit [Quit: Leaving]
tuxd3v has joined #linux-rockchip