ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion
kilobyte_ch has quit [Ping timeout: 245 seconds]
archetyp has quit [Quit: Leaving]
kilobyte_ch has joined #linux-rockchip
stikonas has quit [Read error: Connection reset by peer]
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 265 seconds]
archetyp has joined #linux-rockchip
archetyp` has joined #linux-rockchip
archetyp has quit [Ping timeout: 245 seconds]
archetyp has joined #linux-rockchip
archetyp` has quit [Ping timeout: 265 seconds]
archetyp` has joined #linux-rockchip
archetyp has quit [Ping timeout: 245 seconds]
archetyp has joined #linux-rockchip
archetyp has quit [Client Quit]
archetyp` has quit [Ping timeout: 265 seconds]
matthias_bgg has joined #linux-rockchip
archetyp has joined #linux-rockchip
archetyp has quit [Ping timeout: 245 seconds]
archetyp has joined #linux-rockchip
dvergatal has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 245 seconds]
warpme__ has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
stikonas has joined #linux-rockchip
lopsided98 has quit [Remote host closed the connection]
lopsided98 has joined #linux-rockchip
anarsoul has quit [Ping timeout: 245 seconds]
anarsoul has joined #linux-rockchip
anarsoul has quit [Read error: Connection reset by peer]
anarsoul|2 has joined #linux-rockchip
lopsided98 has quit [Ping timeout: 252 seconds]
indy_ has quit [Ping timeout: 260 seconds]
indy has joined #linux-rockchip
indy has quit [Ping timeout: 265 seconds]
indy has joined #linux-rockchip
indy has quit [Ping timeout: 265 seconds]
indy has joined #linux-rockchip
warpme__ has quit [Quit: Connection closed for inactivity]
indy has quit [Read error: Connection reset by peer]
indy has joined #linux-rockchip
indy has quit [Ping timeout: 265 seconds]
warpme__ has joined #linux-rockchip
indy has joined #linux-rockchip
indy has quit [Ping timeout: 265 seconds]
lurchi_ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-rockchip
lurchi_ is now known as lurchi__
indy has joined #linux-rockchip
lurchi__ is now known as lurchi_
lurchi_ is now known as lurchi__
vagrantc has joined #linux-rockchip
clarity has quit [Ping timeout: 240 seconds]
robmur01_ has joined #linux-rockchip
amstan has quit [Ping timeout: 260 seconds]
LinuxHackerman has quit [Ping timeout: 260 seconds]
samueldr has quit [Ping timeout: 260 seconds]
ServerStatsDisco has quit [Ping timeout: 260 seconds]
csrpi[m] has quit [Ping timeout: 260 seconds]
robmur01 has quit [Ping timeout: 264 seconds]
mmind00 has quit [Ping timeout: 264 seconds]
mmind00 has joined #linux-rockchip
clarity has joined #linux-rockchip
LinuxHackerman has joined #linux-rockchip
amstan has joined #linux-rockchip
samueldr has joined #linux-rockchip
ServerStatsDisco has joined #linux-rockchip
lurchi__ is now known as lurchi_
lurchi_ has quit [Quit: Konversation terminated!]
lurchi__ has joined #linux-rockchip
csrpi[m] has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 265 seconds]
matthias_bgg has quit [Ping timeout: 265 seconds]
robmur01_ is now known as robmur01
norris has quit [Ping timeout: 260 seconds]
dianders has quit [Ping timeout: 250 seconds]
norris has joined #linux-rockchip
warpme__ has quit [Ping timeout: 265 seconds]
daniels has quit [Ping timeout: 252 seconds]
arnd has quit [Ping timeout: 246 seconds]
tucanae47_ has quit [Ping timeout: 264 seconds]
daniels has joined #linux-rockchip
warpme__ has joined #linux-rockchip
dianders has joined #linux-rockchip
arnd has joined #linux-rockchip
tucanae47_ has joined #linux-rockchip
<diederik> It looks like multi-channel audio broke with at least Rock64 with 5.14. It worked with 5.13. It's also broken in 5.14.6, but that's not part of the output: https://paste.debian.net/1214674/
<diederik> With daily builds of LibreELEC (version 11, with kernel 5.14, but now also with 5.14.9) when playing video's, you only see the video, but there is no sound. Playing audio files also results in no sound
<diederik> I'm now also trying to build a 5.14.10 kernel, but I assume it will also only have stereo and no multi-channel audio
<diederik> That 5.13.12-1~exp2 output doesn't have a SPDIF sound card is correct as then SND_SOC_SPDIF wasn't enabled yet.
<diederik> The sources can be found in the various rock64-audio-* branches, which are branched off the master branch, here: https://salsa.debian.org/diederik/linux/-/branches
<diederik> The dtb file in use is the same in all the test and is the one generated from the master branch. All other software is the same as well as well as the kernel config
<diederik> So afaict, the only change is in the upstream kernel source
<diederik> this is likely as far as I can 'debug' it (myself, at least for the time being)
<punit> Could you possibly run a bisect to identify the commit that broke things?
<diederik> I have heard of the term, but I have never done it before. I have recently learned how I can build a Debian (style) kernel based on upstream tags (with that I build the 5.14.0 kernel).
<diederik> But each build takes me about half a day. And I have no clue how to target it to specific commits (which I _think_ I need to do).
<diederik> So I expect that it'll probably take me weeks
<punit> For such work, I would recommend moving away from building kernels with debian config to ones with a more limited config
<punit> Regarding bisect, it's a feature of git and allows you to successively narrow down the range where a bad commit was introduced
indy has quit [Quit: ZNC 1.8.2 - https://znc.in]
<punit> "git bisect start" to start a bisect session
<punit> "git bisect good <commit-sha>" to mark a good commit
<punit> "git bisect bad <commit-sha>" to mark a bad commit
indy has joined #linux-rockchip
<punit> There'll be a lot better documentation if you do a quick search
<diederik> I had just done that and afaict that mean I possibly need to build 100s of kernels
<punit> I'd suggest trying the rc releases before starting the bisect
<punit> It'll help narrow down the range of bisect
<punit> Another way to narrow things down would be to look at commits that went into the broken driver
<punit> Maybe something jumps out and reverting it (assuming it's clean) helps fix the issue
<punit> Gives you enough to complain upstream with
<punit> Another time saving trick is if you can set up network boot in grub / uboot