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]
<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
<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>
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..