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
return0e_ has quit [Remote host closed the connection]
return0e has joined #linux-rockchip
lkcl has joined #linux-rockchip
kevery has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
matthias_bgg has quit [Ping timeout: 268 seconds]
field^Zzz4 has quit [Ping timeout: 268 seconds]
<flacks> hi all
<flacks> anyone have insight on mainline support of the pine64 wifi/bt chip for the rockpro64?
ganbold has quit [Remote host closed the connection]
ganbold has joined #linux-rockchip
lkcl has quit [Ping timeout: 258 seconds]
elektrinis has joined #linux-rockchip
elektirnis has quit [Read error: Connection reset by peer]
Kwiboo has quit [Quit: .]
lkcl has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
elektrinis has quit [Remote host closed the connection]
elektrinis has joined #linux-rockchip
Depau has quit [Ping timeout: 268 seconds]
Depau has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
elektrinis has quit [Remote host closed the connection]
elektrinis has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
<tuxd3v> fALSO. yeah me neither
<tuxd3v> one needs only to guess..who in this world would choose a 1500000 baudrate? :D
<anarsoul> tuxd3v: IIRC there's nothing faster between 38400 and 1500000 that has integer divider
<EmilKarlson> in general though higher rates are useful, since they allow you to debug more in certain cases, not just sufficiently useful
<anarsoul> EmilKarlson: my serial adapter (ft232-based) doesn't work at 115384 that you can get on rk3399
<tuxd3v> as a comunication protocol I agree its better, because its faster..
<anarsoul> you can't get 115200 out of 24mhz with integer divider
<tuxd3v> as a debugger, I think most humans cannot follow 115200 which is a lot lot lower..
<EmilKarlson> tuxd3v: there are logs and grep
<EmilKarlson> often you record for a minute and then investigate for a day
<EmilKarlson> on linux this also directly affects printk speed and as such race conditions
<EmilKarlson> trace is better in that regard, but qemu does not directly export traces
<EmilKarlson> would be cool to have hardware trace interface though
<EmilKarlson> if you don't have logs and have to interactively debug device that spews garbage to console, it's super painful
<tuxd3v> the serialits hardware bound to the 24Mhz oscillator?
_whitelogger has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
kevery has quit [Quit: kevery]
kevery has joined #linux-rockchip
lkcl has quit [Ping timeout: 268 seconds]
lkcl has joined #linux-rockchip
<mmind00> anarsoul: hmm, rk3399 chromeos devices do run on 115200 on uart2 ... and also the theobroma boards do use 115200 on uart0 in uboot and everywhere else
<EmilKarlson> I bet you also say your x86 computer runs windows because it was sold configured with one
field^Zzz4 has joined #linux-rockchip
stikonas has joined #linux-rockchip
lkcl has quit [Ping timeout: 240 seconds]
lkcl has joined #linux-rockchip
kevery has quit [Quit: kevery]
kevery has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
lkcl has quit [Ping timeout: 265 seconds]
lkcl has joined #linux-rockchip
Depau has quit [Ping timeout: 258 seconds]
Depau has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
return0e_ has joined #linux-rockchip
return0e has quit [Ping timeout: 258 seconds]
kevery has joined #linux-rockchip
Depau has quit [Ping timeout: 265 seconds]
Depau has joined #linux-rockchip
kevery has quit [Ping timeout: 258 seconds]
ldevulder__ has joined #linux-rockchip
ldevulder_ has quit [Ping timeout: 240 seconds]
kevery has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
lkcl has quit [Ping timeout: 258 seconds]
stikonas has joined #linux-rockchip
lkcl has joined #linux-rockchip
kevery has quit [Ping timeout: 268 seconds]
_whitelogger has joined #linux-rockchip
nsaenz has joined #linux-rockchip
nsaenz has quit [Remote host closed the connection]
_whitelogger has joined #linux-rockchip
Depau has quit [Ping timeout: 260 seconds]
Depau has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
<EmilKarlson> stikonas: FYI try nproc command
<EmilKarlson> stikonas: does grub support serial output for you on rockpro64?
JohnDoe_71Rus has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
<stikonas> EmilKarlson: grub does support serial output
<stikonas> EmilKarlson: what is that nproc for?
<EmilKarlson> ah thanks, you saved be years of effort
<stikonas> it shows 6 for me
<stikonas> which is the number of cores on rockpro64
<EmilKarlson> make -j$(cat /proc/cpuinfo | grep processor | wc -l)
<stikonas> oh i see
<EmilKarlson> and thanks for the article
<stikonas> haven't updated to newest kernel there...
<stikonas> EmilKarlson: I'm not on 5.4 without any patches
<stikonas> I do use one patch from anarsoul for u-boot
<EmilKarlson> sure, I don't care about most of the specifics, just having some simple guidelines is nice
<stikonas> exactly
<stikonas> that's why I haven't bothered to bump versions there yet...
<EmilKarlson> my system is pinebook pro and only moderately similar versions
<EmilKarlson> and I compile on debian etc
<stikonas> well, yeah, debian would have some minor differences on how you get your cross toolchain
<stikonas> but I guess more or less steps are very similar
<EmilKarlson> yes
<EmilKarlson> heh, everything seems to be possible, except booting something that gives any relevant feedback to serial or something
<EmilKarlson> most of the time u-boot gives no feedback whatsoever
<EmilKarlson> ie, I have no idea, whether my kernel actually supports EFI boot
<EmilKarlson> # CONFIG_EFI is not set
<EmilKarlson> apparently this is no problem for u-boot to boot anyhow
<stikonas> EmilKarlson: from grub?
<stikonas> grub can only boot efi kernels
<EmilKarlson> well mostly the problem is that blindly getting correct configuration of EFI is a tedious task
<EmilKarlson> though I could just install on vm, install custom kernel package and copy the image
<EmilKarlson> so having some output for each step would be very much appreciated
stikonas has quit [Remote host closed the connection]
cristian_c has quit [Ping timeout: 265 seconds]
cristian_c has joined #linux-rockchip
stikonas has joined #linux-rockchip
lkcl has quit [Ping timeout: 258 seconds]
lkcl has joined #linux-rockchip
<tuxd3v> I am wondering if is there any 2d graphic driver for rk3399..
<tuxd3v> for the GRA2 graphics
lkcl has quit [Ping timeout: 260 seconds]
lkcl has joined #linux-rockchip
lkcl has quit [Ping timeout: 265 seconds]
matthias_bgg has quit [Ping timeout: 258 seconds]