ChanServ changed the topic of #linux-msm to:
lumag_ has quit [Remote host closed the connection]
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
cmeerw has joined #linux-msm
cmeerw has quit [Ping timeout: 480 seconds]
svarbanov has joined #linux-msm
sus has joined #linux-msm
sus has quit [Remote host closed the connection]
lumag_ has joined #linux-msm
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
svarbanov has quit [Ping timeout: 480 seconds]
<bamse> link2xt: apq8064 is a derrivative of 8960, so there's definitely some room for being inspired, but they aren't the same
<bamse> link2xt: no i was thinking about the sony "Mint" phone on the "Blue" platform - which i know i have booted mainline linux on at some point, but i can't find the dts for it :/
lumag_ has quit [Remote host closed the connection]
cmeerw has joined #linux-msm
<minecrell> bamse: Who is responsible to pick up ARM mach-qcom patches? This one has been sitting on the list for quite some time: https://lore.kernel.org/linux-arm-msm/20210606201612.100752-1-bartosz.dudziak@snejp.pl/
Daanct12 has quit [Quit: Quitting]
Danct12 has joined #linux-msm
<konradybcio> bamse colour me a stalker but i know precisely where all your old DTs are https://github.com/andersson/kernel/commits/next/arch/arm/boot/dts
<bamse> konradybcio: ahh, but i named the file sony-blue-mint.dts...no wonder i didn't find it when looking, thanks
<bamse> minecrell: that would be me...and https://patchwork.kernel.org/project/linux-arm-msm/patch/20210606201612.100752-3-bartosz.dudziak@snejp.pl/ tells us that i somehow deamed it not to be on my plate
<bamse> minecrell: let me correct that...
<bamse> minecrell: now they are back in my todo list!
<link2xt> bamse: thanks
<link2xt> problem, is, i can't make it boot at all, even added "board" file and compiled it in trying to enable ramconsole
<bamse> link2xt: it's been a while, but i'm quite certain that when you boot using a dtb then it will match the the board on the machien .dt_compat, which in this case would be the generic board.c in mach-qcom
<bamse> link2xt: and as you can see, the board file is "empty"...because all the stuff that used to go in the board file should go in the dts
<bamse> link2xt: and just as a general suggestion, you should probably expect to have quite a bit of low level debugging infront of you, so having a uart would probably be very desirable
<link2xt> yes, i suspect i should add ramconsole node to the dts and configure everything there, but want to get at least one dmesg out of this kernel first somehow
<link2xt> will add .dt_compat now, thanks
<link2xt> as for uart, will look into it before trying to bring up usb probably, as sony-blue-mint.dts doesn't have usb either
<link2xt> added sony-blue-mint.dts here for reference: https://wiki.postmarketos.org/wiki/Qualcomm_Snapdragon_S4_Plus_(MSM8960)
<bamse> link2xt: rather than adding a dt_compat, rely on your compatible being "your-board", "qcom,msm8960"...that way the generic mach-qcom/board.c will be picked
<link2xt> but there is no mach-qcom/board.c at all
<link2xt> there is only mach-qcom/platsmp.c
<bamse> link2xt: ahh right, it went away later...
<bamse> well you don't need to add a board.c...
<link2xt> this board-ville is a ville-specific hack to initialize its ramconsole
<link2xt> basically a copy-paste of https://wiki.postmarketos.org/wiki/User:Knuxfanwin8/Enabling_pstore_and_ramoops#Android_ram_console_driver_setup which is an earlier copy-paste of somewhere else
<link2xt> otherwise i have to add proper devicetree reading support to ramoconsole driver
<bamse> right, but as no one else runs with a board file it's probably much more better to enable it using the dts...given that you don't have uart to debug what you add
<bamse> ahh, because it's ramconsole and not ramoops and you don't have ramoops in your other kernel?
<link2xt> yes, downstream has only ramconsole
<link2xt> and it was board-* all the way down
<bamse> not sure what might be the best way out of this...
<bamse> it's been a long time since i poked at that, and i tend to get my hands on hardware with uart
<bamse> link2xt: wish i had the time to resurrect that mint device, but my todo list is a little bit too long already :/
<bamse> but it has some sentimental value, being the platform where i really started my mainline work
<konradybcio> bamse: any plans on upstreaming leo after all? :P
<konradybcio> iirc there was even a panel driver or two for it
<bamse> konradybcio: 8974 definitely has more sentimental value than 8960...so that comes much higher up on the todo list
<konradybcio> i too, should refactor my fixups and finally send them, eh..
svarbanov has joined #linux-msm
cmeerw has quit [Ping timeout: 480 seconds]