ChanServ changed the topic of #linux-msm to:
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
flto_ has joined #linux-msm
flto has quit [Ping timeout: 480 seconds]
flto_ has quit []
flto has joined #linux-msm
animist has quit [Read error: Connection reset by peer]
animist has joined #linux-msm
svarbanov has joined #linux-msm
cmeerw has joined #linux-msm
cmeerw has quit [Ping timeout: 480 seconds]
pevik has joined #linux-msm
animist has quit [Ping timeout: 480 seconds]
animist has joined #linux-msm
ahalaney has joined #linux-msm
Danct12 has quit [Quit: Quitting]
Danct12 has joined #linux-msm
Danct12 has quit []
ahalaney has quit [Quit: Leaving]
ahalaney has joined #linux-msm
Danct12 has joined #linux-msm
cmeerw has joined #linux-msm
svarbanov has quit [Ping timeout: 480 seconds]
svarbanov has joined #linux-msm
<gpiccoli> Hey folks! Did anybody see issues when running with ftrace on dragonboard 820c ?
<gpiccoli> specially after kernel 5.7 ...
<bamse> gpiccoli: what's the issue you're seeing?
<gpiccoli> o/ bamse - I can't boot the board
<gpiccoli> Not even with earlycon - I see nothing
<bamse> so your kernel boots unless you enable CONFIG_FUNCTION_TRACE?
<gpiccoli> I've bisected and found the responsible commits...I'm trying to understand *why* they're an issue for me, but not for multiple people
<gpiccoli> bamse, yes, and I'm adding the DYNAMIC_FTRACE stuff as well
<gpiccoli> I didn't test without the dynamic paraphernalia heheh
<gpiccoli> just setting TEXT_OFFSET to 0x0 broke my setup
<gpiccoli> but..only with ftrace! I could boot up to 5.15rc3 without ftrace hehe
<gpiccoli> I'm not sure if it might be related to the bootloader, I'm kinda new to ARM
<gpiccoli> BTW, ftrace is part of my investigation about the gpu thing you suggested me on ML =)
<bamse> hmm, i've used ftrace after 5.7 on that board...
Danct12 has quit [Quit: Quitting]
<gpiccoli> that's very weird! I'm using Inforce 6640 - it's a board based on db820c
<gpiccoli> Also, let me take the opportunity to ask you that bamse - I'm working a DT patch for this board...the reason is that the current dts allows only booting with UFS and serial, it's very limited. If I use the dts from db820c I can boot the board flawlessly, with all peripherals, like ethernet, SD, seems BT is also working, GPU
<gpiccoli> What is the best way to "fix" that? Just add the ifc6640 to dbc dts as compatible, or update the ifc6640.dts to match db820c?
svarbanov has quit [Ping timeout: 480 seconds]
<bamse> there's some differences between the boards, so there should be two dts files, each one describing the particular board
<bamse> but you can very well extend ifc6640.dts by "cherry picking" things from the db820c dts
<gpiccoli> ok, perfect! that's my goal, to extend the dts file including the missing pieces from db820c
<gpiccoli> tnx for the suggestion !
<bamse> i presume you have the schematics or data sheet...so try to go through all the components and use the names from the documentation and wire things up properly
<bamse> using db820c.dts as a reference
<gpiccoli> hmm..yeah, I have some documentation, but i'm not sure it is so detailed as dragonboard schematics, which is incredibly comprehensive
pevik has quit [Ping timeout: 480 seconds]
irungentoo has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
irungentoo has joined #linux-msm
irungentoo has quit [Remote host closed the connection]
irungentoo has joined #linux-msm
gpiccoli has quit [Quit: Bears...Beets...Battlestar Galactica]
gpiccoli has joined #linux-msm
jessica_24 has joined #linux-msm
svarbanov has joined #linux-msm
cmeerw has quit [Ping timeout: 480 seconds]
svarbanov has quit [Ping timeout: 480 seconds]
ahalaney has quit [Quit: Leaving]