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
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
camus1 has joined #linux-rockchip
camus1 is now known as kaspter
kaspter has quit [Ping timeout: 260 seconds]
vstehle has quit [Ping timeout: 260 seconds]
vagrantc has quit [Quit: leaving]
kaspter has joined #linux-rockchip
robmur01 has joined #linux-rockchip
robmur01 has quit [Ping timeout: 260 seconds]
vstehle has joined #linux-rockchip
kaspter has quit [Ping timeout: 258 seconds]
kaspter has joined #linux-rockchip
camus1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 265 seconds]
camus1 is now known as kaspter
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 246 seconds]
kevery1 is now known as kevery
mias has joined #linux-rockchip
camus1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 260 seconds]
camus1 is now known as kaspter
mayab76 has joined #linux-rockchip
kaspter has quit [Ping timeout: 260 seconds]
kaspter has joined #linux-rockchip
vicencb has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
maze-BUG has left #linux-rockchip [#linux-rockchip]
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-rockchip
ldevulder__ has joined #linux-rockchip
ldevulder_ has quit [Ping timeout: 246 seconds]
kaspter has quit [Ping timeout: 256 seconds]
kaspter has joined #linux-rockchip
mayab76 has quit [Ping timeout: 246 seconds]
mayab76 has joined #linux-rockchip
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 256 seconds]
kevery1 is now known as kevery
robmur01 has joined #linux-rockchip
camus1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 256 seconds]
camus1 is now known as kaspter
JohnDoe_71Rus has joined #linux-rockchip
ldevulder__ is now known as ldevulder
Kwiboo has joined #linux-rockchip
nlhowell has quit [Ping timeout: 244 seconds]
<topi`> so, everything interesting should be in 5.7 mainline kernel for rk3288?
<topi`> I'll go grab it. probably going to have to wrestle a bit with the .dts though
kaspter has quit [Ping timeout: 246 seconds]
kaspter has joined #linux-rockchip
<DuClare_> topi`: I mean it *probably* depends on what you consider interesting..
<DuClare_> Let's just say that I haven't looked at that vendor tree at all because mainline does what I need
<DuClare_> No idea whether that'd be the case for you :)
<topi`> the vendor tree for rk3288 is ancient
<topi`> it would be just crazy to build new products ont op of such trees
<DuClare_> Indeed
<topi`> there's still rk3288 hardware being sold/produced by some industrial vendors
<DuClare_> I now
<topi`> so I'm trying to see whether or not the mainline support is good enough
<DuClare_> I'm one of them :P
<topi`> to even bother
<topi`> or maybe just go with Intel Atoms
nlhowell has joined #linux-rockchip
<robmur01> meh, the vendor tree for *everything* is ancient :P
<robmur01> I've seen rumours somewhere that they're working to bump it from 4.4, but I'll believe that when I see it...
<DuClare_> I bet there are lots of crazy companies building on ancient trees
<mmind00> robmur01: porting 4 years of crazy patches from the 4.4 vendor tree to something new must be pretty overwhelming :-D
<topi`> we delivered an imx6 based solution to a customer 2 years ago and it was based on much newer 4.14 kernel )
<topi`> and that wasn't even the newest 4.x back then. But I digress...
<topi`> I'm fighting with a broken RTC now. It seems on 32bit systems the systemd is stuck during boot if the RTC returns a date in the future
<topi`> this is some funny effect of how the kernel space handles the time_t in 64 bits, but systemd only sees the lower 32 bits and will loop forever trying to set that time..
<topi`> some RTCs tend to return complete garbage if the battery is too low
<DuClare_> also some init systems tend to be complete garbage
* DuClare_ quacks
<robmur01> with mainline? If so, it might be the vDSO bug rather than a hardware RTC problem
<DuClare_> robmur01: Which bug?
<topi`> it was the 4.14 kernel
<topi`> with systemd 232
<topi`> but every systemd seems to be influenced, because Poettering blames the kernel folks and Alan Cox blames Poettering
<topi`> I was forced to do a small patch in kernel's rtc-lib.c
<robmur01> vDSO clock_gettime64 introduced in 5.5 turns out to be buggered on systems that don't set up the arch timer properly (including RK3288) - https://lore.kernel.org/linux-arm-kernel/CAK8P3a2Tw2w73ZkK-W6AA9veMK4-miLUx-TL1EuOdP7EdW-AmQ@mail.gmail.com/ https://lore.kernel.org/linux-arm-kernel/20200409050508.96753-1-jaedon.shin@gmail.com/
<mmind00> topi`: not everybody uses the vendor tree for products ;-) ... we're using 5.4 right now for Rockchip-based stuff ;-)
<robmur01> up-to-date libc and systemd see time jumpign all over the place and it's pretty much unusable
<DuClare_> mmind00: Meanwhile I just updated to 5.4 :)
<DuClare_> (Last week)
nlhowell has quit [Ping timeout: 260 seconds]
<mmind00> DuClare_: sucessfully? :-)
<DuClare_> I hit a little snafu
<DuClare_> But seems ok after I work around it
<DuClare_> Nothing related to rockchip though
nlhowell has joined #linux-rockchip
sb35 has joined #linux-rockchip
<tuxd3v> hello all,
<tuxd3v> is there any news on kernel 5.7 for rk3399?
nlhowell has quit [Ping timeout: 260 seconds]
<mmind00> tuxd3v: you'll need to be a little more specific .... in general it just works
<tuxd3v> mmind00, yes, well at least on rockpi4 it in general works :)
<tuxd3v> my question was in general, I mean for the Soc, if there are any improvements for rk3399 in k 5.7
<tuxd3v> drivers and such
<mmind00> tuxd3v: that's a hard question ... I'm on the road to 5.9 now, so remember what was in 5.7 is really difficult ... I guess video codec things might be in there, or that was only in 5.8
<mps> I don't see much improvements in 5.7 for rk3399
<mps> maybe nothing
<mps> well, nothing important, I mean
<mps> but except two problems I have with emmc and rockchip-dp it works quite good on my rk3399 machine
<tuxd3v> mmind00, mps, thanks
<tuxd3v> my idea is that yes it works quite well, but I have only a server rootfs..
<tuxd3v> I am planing for a desktop
<mps> tuxd3v: I'm using it as desktop
<tuxd3v> the Analog audio, does any one knows how to put it to work
<tuxd3v> I can't listen on analog jack :(
<mps> I made script with amixer to set all needed controls for this
<tuxd3v> somebody sometime ago, spoke about unmutte the chanells, but I find none mute :/
<tuxd3v> mps, nice
<tuxd3v> can you share, how to do it, if you don't mind?
<mps> ofc, wait a moment
<tuxd3v> thankyou very much :)
<tuxd3v> I tested at the time hdmi audio, and it indeed work, but couldn't get analog audio via jack
<tuxd3v> mps, what sbc are you using?
<mps> you will have to mute/unmute Headphone control and 'Playback Digital' control
<mps> I'm using samsung gru-kevin chromebook
<tuxd3v> I have rockpro64
<tuxd3v> but I will check again with your input, to see if its working :)
<mps> heh, this took me a time to find correct settings for alsa to work
<mps> script I posted is just a starting point, I think
<tuxd3v> mps, I understand that :)
<tuxd3v> I will dig a bit on it, and make some tests, to check audio ;)
<tuxd3v> thanks again
<mps> np
matthias_bgg has quit [Ping timeout: 256 seconds]
matthias_bgg has joined #linux-rockchip
field^Mop has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
vicencb has joined #linux-rockchip
nlhowell has joined #linux-rockchip
vagrantc has joined #linux-rockchip
robmur01 has quit [Remote host closed the connection]
robmur01 has joined #linux-rockchip
mayab76 has quit [Ping timeout: 264 seconds]
JohnDoe_71Rus has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
mias has quit [Ping timeout: 256 seconds]
mias has joined #linux-rockchip
maze-BUG1 has joined #linux-rockchip
maze-BUG1 is now known as maze-BUG
mias has quit [Remote host closed the connection]
flacks_ has joined #linux-rockchip
sb35 has quit [Ping timeout: 264 seconds]
maze-BUG1 has joined #linux-rockchip
maze-BUG has quit [Ping timeout: 260 seconds]
maze-BUG1 is now known as maze-BUG
matthias_bgg has quit [Ping timeout: 264 seconds]
robmur01 has quit [Ping timeout: 246 seconds]
adjtm_ has joined #linux-rockchip
adjtm has quit [Ping timeout: 256 seconds]
vagrantc has quit [Quit: leaving]
vicencb has quit [Quit: Leaving.]