ChanServ changed the topic of #msm8937-mainline to: Boot Linux on your MSM8917/37/40 and QM215 mobile! | GitHub: https://github.com/msm89x7-mainline | Logs: https://oftc.irclog.whitequark.org/msm8937-mainline | Bridged to #msm8937-mainline:kde.org on Matrix
Otus9051[m] has joined #msm8937-mainline
<Otus9051[m]> Hello, I am getting a Lenovo Tab 4 8 LTE soon and it seems to be based on MSM8917. Is this the correct group for the chipset/device?
<Otus9051[m]> I am up for mainlining this device.
<Otus9051[m]> Since this is my first rodeo, I would like some guidance. I see that there are some DTS/DTSIs and I think that would make it a fairly easy transition?
<barni2000[m]> "Boot Linux on your MSM8917/20/37/40, QM215 and SDM429/SDM439 mobile!"
<barni2000[m]> yes this is the right room
<Otus9051[m]> Thanks for confirming.
<Otus9051[m]> Any guides to get started with porting stuff over?
<Otus9051[m]> The device is in transit and I should get it by today/tomorrow, and I think I can do some prelim bringup until the device arrives/+.
<Otus9051[m]> s//+././
<Andr[m]> start with lk2nd
<Otus9051[m]> seems like https://github.com/msm89x7-mainline/lk2nd is archived, do I have to use https://github.com/msm8916-mainline/lk2nd instead?
<Andr[m]> yes
<Otus9051[m]> Andr[m]: Is there an existing guide that I can follow? Or is it more of a learn-as-you-go approach?
<Otus9051[m]> Again, sorry for the rather stupid questions, this is my first time working with this stuff.
<Otus9051[m]> Eitherway, it seems MSM8917 is not in the lk2nd repo, however, MSM8916 is. Is there a need for a chipset bringup or is it going to be same with a few tweaks overall?
<barni2000[m]> <Otus9051[m]> "Is there an existing guide..." <- we are using lk2nd-msm8916 just msm8917 is under msm8952 platform
<Otus9051[m]> I will be making a PR for lk2nd as soon as I test it on the device. Apart from that, what seems to be working and not working on mainline?
<barni2000[m]> on 8917 almost everything is working but mesa have issues
<barni2000[m]> with next release GPS and modem will also working
<barni2000[m]> modem is working now just no device where it is enabled
<Otus9051[m]> <barni2000[m]> "on 8917 almost everything is..." <- Whats the problem with mesa?
<barni2000[m]> buggy on a3xx it has glitches on plamo, gnome and gles3 stuff can cause complete crash
<Otus9051[m]> mmm
<barni2000[m]> i have played with lunati, preformance is not bad
<Otus9051[m]> is it more of a firmware thing? or some clock going rogue somewhere?
<barni2000[m]> it is bugs in mesa adreno a3xx implementation
<barni2000[m]> s/it/those/, s/is/are/
<Otus9051[m]> hmm
<Otus9051[m]> lk2nd confirmed to be booting
<Otus9051[m]> will PR in a bit
<dr_shui[m]> i have flashed a eng firmware to bypass the BL-lock of my redmi5a
<dr_shui[m]> but when i flash lk2nd-msm8952 into it's boot partition, the screen turns black
<dr_shui[m]> if it is because the bootloader of eng firmware is different from normal xiaomi-firmware's and causes screen not checked from lk2nd?
<dr_shui[m]> how can i do some debug and or force lk2nd to use drivers for riva?barni2000
<dr_shui[m]> i tought lk2nd doesn't recognized my device is riva, so not using the right screen panel driver
<barni2000[m]> oreo or nougat variant?
<dr_shui[m]> i don't know, how to check it?
<dr_shui[m]> i found it can't boot into lk2nd, showing 900e, or system has been distroyed after i signed lk2nd-msm8952.img
<dr_shui[m]> maybe unlock from original xiaomi firmware is the only way , ENG firmware can't make it boot.
<barni2000[m]> you will only need to erase splash
<barni2000[m]> that is unlock riva afaik
<barni2000[m]> <barni2000[m]> "0xCAFEBABE: https://github.com/..."; <- you can try build lk2nd with this
<dr_shui[m]> i saw the little penguin logo for a very short time then the phone goes into 900e after i erase splash
<dr_shui[m]> interesting
<dr_shui[m]> is that means lk2nd have tried to boot on and failed for some reason?barni2000
<barni2000[m]> which lk2nd are you using?
<dr_shui[m]> msm8952 from there
<barni2000[m]> build it
<dr_shui[m]> <barni2000[m]> "you can try build lk2nd with..." <- i‘m compiling yours, `umeko@97df89c06e5c:~/lk2nd-msm8953$ make TOOLCHAIN_PREFIX=arm-none-eabi- lk2nd-msm8952`
<dr_shui[m]> i flashed lk2nd-msm8952.img built from yours git clone -b tiare/fixes https://github.com/barni2000/lk2nd-msm8953.git --depth 1 still goes into 900e after a penguin flashed
<dr_shui[m]> i see... the penguin is just splash partition , not really works
<dr_shui[m]> after i flashed boot.img from the ENG firmware, it boots normally into the ENG system
<dr_shui[m]> I got the ENG package here, I flash it into my riva from 9008 mode, https://androidfilehost.com/?fid=7161016148664812027
<barni2000[m]> what is eng firmware btw
<dr_shui[m]> ENG firmware seems have no BL limit, sometimes it can be used to bypass BL
<dr_shui[m]> it works on some mido, and all markw
<barni2000[m]> so xda is cens...
<barni2000[m]> it works for me
<dr_shui[m]> how it goes? since ENG firmware is not working ...
<dr_shui[m]> seems xda have blocked my proxy. turn off it then i got the page
<dr_shui[m]> is it need to append the lk2nd.img with 0x30, 0x83, 0x19, 0x89, 0x64 to boot it?
<barni2000[m]> yes afaik you will need to append something to lk2nd img
<dr_shui[m]> <barni2000[m]> "oreo or nougat variant?" <- is it different for riva? i can flash it into Android OS 7.1 by 9008, or any other version
<barni2000[m]> yes oreo bootloader is different even board-id are not same
<dr_shui[m]> then it's better to use nougat
<barni2000[m]> in your case ig
<barni2000[m]> i wonder why Redmi GO cannot boot from sd
<barni2000[m]> i think something is not completely fine in my implementation https://github.com/msm8916-mainline/lk2nd/commit/8a72bd6e70859b30ee52d6c0d7aeff81679e7c1e
<barni2000[m]> many device is working but tiare and pine are not