<WoeyJonkers[m]>
hello, is this kernel far enough along that i'm able to use it for porting an MSM8917 device?
<Danct12[m]>
maybe
<Danct12[m]>
i haven't tested 8917 because i have none of the 8917 devices
<Danct12[m]>
and also i'm currently taking a break waiting for the new redmi 4x touch screen :P
<Danct12[m]>
i'll be back next week
<Danct12[m]>
msm8917 should be in a better shape than 8937 now as it only has one cluster
<Danct12[m]>
<WoeyJonkers[m]> "hello, is this kernel far enough..." <- BTW, check if the android kernel is 64-bit, if it's not then you're out of luck for now
<Danct12[m]>
as we only support qcom running on 64-bit mode
Daanct12 has quit [Quit: WeeChat 4.1.2]
f_ has quit [Ping timeout: 480 seconds]
f_ has joined #msm8937-mainline
<WoeyJonkers[m]>
you mean the one it was shipped with? 32-bit
<WoeyJonkers[m]>
does that mean i'm screwed
<WoeyJonkers[m]>
screwed as in not able to use this kernel, there's stil a lineageos port i can use instead, i was just hoping to get my hands on that shiny new 6.6 kernel
<WoeyJonkers[m]>
s/stil/still/
<barni2000[m]>
which device is it?
<WoeyJonkers[m]>
samsung-gta2swifi
<Danct12[m]>
WoeyJonkers[m]: do you have the kernel file for it? you can unpack the boot.img and run `file` on zImage
<barni2000[m]>
maybe this samsung with muic could works
<barni2000[m]>
s/works/work/
<Danct12[m]>
rip
<barni2000[m]>
afaik lk2nd will be needed
<Danct12[m]>
see what's after arch/? :P
<Danct12[m]>
it's arm not arm64
<barni2000[m]>
it is just idiotic 3.18
<barni2000[m]>
they have symlinking the dts befor 4.9
<barni2000[m]>
* they have been symlinking the
<barni2000[m]>
* they have been symlinking the dts before 4.9
<Danct12[m]>
yeah, but the kernel is built for arm32
<Danct12[m]>
i am not sure if it can boot arm64 but worth a try
<Danct12[m]>
BTW, lk2nd is arm32
<Danct12[m]>
minecrell[m]: do you think it's possible? you seem to know a lot about msm8916 samsung ^
<Sid_key[m]>
Danct12[m]: That doesn't matter
<Sid_key[m]>
It would still boot ig
<Sid_key[m]>
Tiare (Redmi Go) shipped with arm kernel
<minecrell[m]>
There is a check in lk2nd which tells you if booting arm64 is possible. I would strongly expect any 8917 can do it because only ancient Android 4.4 firmware on 8916 can't
<Sid_key[m]>
But boots fine 64 bit
<Sid_key[m]>
Even samsung shipped with arm boot arm64
<Sid_key[m]>
Sid_key[m]: Even more
<Sid_key[m]>
Redmi Go has tz with 64 bit pg support for cb21
<Sid_key[m]>
While M/N fw devices doesn't have that
<WoeyJonkers[m]>
ok thanks i will try that later today
<Danct12[m]>
i would recommend start porting lk2nd first since this will be a hard dependency
<Danct12[m]>
for anyone else here wondering why this will be a hard dependency, this is because lk2nd can parse bootloader cmdline and modify the device tree when needed - e.g. different display model
<Danct12[m]>
there are many devices with the same qcom,board-id and it's also a good idea to unify them, so we only need one boot.img for all devices with the same id
<Danct12[m]>
* there are many devices with the same qcom,board-id and it's also a good idea to unify them, so we only need one lk2nd build for all devices with the same id
<barni2000[m]>
and what about same display names?
<barni2000[m]>
whit different panels
<barni2000[m]>
btw we have one build with multiple dtb it contains every device
<barni2000[m]>
i think you mean unified in one dt
<Danct12[m]>
<barni2000[m]> "and what about same display..." <- as in?
<Danct12[m]>
if bootloader says qcom,mdss_dsi_nt35596_1080p_video then it's gonna be this panel
<barni2000[m]>
Danct12[m]: in every device what using this compatible string
<barni2000[m]>
* compatible string?
<Danct12[m]>
this was just an example ^
<barni2000[m]>
i just say it should be investegated
<barni2000[m]>
btw qcom-board-id could contain more ids afaik so we could unify almost every device what don't need device specific quirks
<barni2000[m]>
but it depends on the devices' bootloader
<WoeyJonkers[m]>
<Danct12[m]> "i would recommend start porting..." <- so... hypothetically, if i had no idea what i was doing... how would i go about doing that
<barni2000[m]>
you need to create a minimal dt for your device
<barni2000[m]>
ok sorry for do this more complex than it is
<barni2000[m]>
so make a new folder place your dt there and make an rules.mk
<barni2000[m]>
after you should build lk2nd-msm8952
<WoeyJonkers[m]>
still same errors
<WoeyJonkers[m]>
there's probably something extremely simple and obvious that i'm missing and i just somehow can't figure it out
<barni2000[m]>
yes one -
<barni2000[m]>
make TOOLCHAIN_PREFIX=arm-none-eabi- -j4 lk2nd-msm8952
<barni2000[m]>
it missing after eabi
<WoeyJonkers[m]>
<WoeyJonkers[m]> "still same errors" <- ^
<WoeyJonkers[m]>
is it this?
<WoeyJonkers[m]>
missing MEMBASE or MEMSIZE variable, please set in target rules.mk
<WoeyJonkers[m]>
ok i tried building for something that was already there and i still got those errors, maybe if i just start from the beginning, re-clone everything, and go through it again maybe then it will build
<WoeyJonkers[m]>
AHAHAHAHAHAHAHAAA
<WoeyJonkers[m]>
YUP
<WoeyJonkers[m]>
ok well i still got an error but it was after it already compiled a bunch of stuff