abelvesa has quit [Remote host closed the connection]
Guest25534 has quit [Remote host closed the connection]
abelvesa has joined #linux-msm
<loki666>
I'm looking for a edk2 with sm8650 support (for dual booting with Android)
pespin has quit [Remote host closed the connection]
dliviu has quit [Write error: connection closed]
kcxt- has quit [Write error: connection closed]
rmsilva has quit [Write error: connection closed]
aklimov has quit [Remote host closed the connection]
enok_ has joined #linux-msm
aklimov_ has joined #linux-msm
nashpa has joined #linux-msm
kcxt_ has joined #linux-msm
rmsilva- has joined #linux-msm
aklimov_ is now known as aklimov
enok has quit [Ping timeout: 480 seconds]
enok_ is now known as enok
<Mis012[m]>
what's wrong with u-boot?
Caterpillar2 has joined #linux-msm
<loki666>
Mis012[m]: you mean installing u-boot as the ABL, will I still be able to boot Android in internal and linux on SD ?
<Mis012[m]>
if you have sb off (or more bluntly, if you actually own the device) you should be able to put u-boot instead of ABL, yes
<loki666>
qtestsign works fine on my board yes
<Mis012[m]>
u-boot can in principle boot android, but I don't think a lot of people are doing that in practice
<loki666>
currently I have a convoluted setup, with abl2esp -> grub -> original LinuxLoader.efi or linux Kernel
<Mis012[m]>
you can probably also boot ABL with u-boot since it's just an efi app, but I doubt anyone ever did that
<loki666>
but it forces me to keep a SD card inserted ofc
<Mis012[m]>
as in, LinuxLoader
<Mis012[m]>
guess someone did do that? fun
<loki666>
:p
<Mis012[m]>
the issue with doing a boot menu with u-boot1st (that is, no XBL ever running) is that nobody ported the mdss driver from Linux (yet?)
<Mis012[m]>
but you could also chainload LinuxLoader -> u-boot -> LinuxLoader fwiw
<Mis012[m]>
probably anyway
<loki666>
yes but for that I need to patch LinuxLoader right ? that was my first idea... LinuxLoader -> grub (if ESP part detected)
<loki666>
but Id need a working LinuxLoader for SM8650
<loki666>
I mean I need source code of a LinuxLoader for SM8650
<Mis012[m]>
LinuxLoader->u-boot works, since that's what people do who don't own their device and can't put u-boot where it belongs
<Mis012[m]>
it should be fully possible to port the mdss driver, u-boot seems to have facilities for porting drm drivers, but most people don't own their devices these days so it's far from being a priority
<Mis012[m]>
loki666: but what I meant was LinuxLoader->u-boot->either grub or LinuxLoader
<Mis012[m]>
but yeah, I now realize you were running LinuxLoader still under qcom's EFI
<Mis012[m]>
so still not sure if it would work fine under u-boot's
<Mis012[m]>
loki666: if you were fine with hacking in blind selection into u-boot (so "hold volume button during boot to boot android"), then you wouldn't need working display I guess
<loki666>
well currently abl2eps -> grub does show on the device panel via the framebuffer
kcxt_ is now known as kcxt
<Mis012[m]>
yes, because abl has a driver
<Mis012[m]>
the edk2 part
<Mis012[m]>
u-boot does not
<Mis012[m]>
and it can't use the edk2 one (without a bunch of hacks anyway)
<loki666>
ah ok it's the "packaging" step of abl2eps that bundle edk2 drivers into the unsigned elf ?
<loki666>
but there is packaging script that depends on edk2
<loki666>
I only flashed the abl partitions
<Mis012[m]>
loki666: ah, is LinuxLoader not the only part of ABL?
<Mis012[m]>
I thought ABL was mainly just LinuxLoader
<loki666>
it was, I just extracted the raw LinuxLoader.efi of the original abl partition
<loki666>
so I can chainload it from grub (to get back to Android)
<Mis012[m]>
yeah, so the "proper" approach would be to replace the whole EDK2 part of XBL with u-boot
<Mis012[m]>
but then no display
<Mis012[m]>
not sure how u-boot would feel about being put in ABL since for chainloading it expects boot services to not be a thing anymore
<Mis012[m]>
but if that worked you would have display
<Mis012[m]>
since the framebuffer is not part of boot services, it's still up
<Mis012[m]>
from when the edk2 part initializes it
abelvesa has quit [Remote host closed the connection]
<loki666>
mmmh... I feel like this conversation got me even more confused at the boot process... Also EFI is also rabbit hole, I didn't found the exit yet
<Mis012[m]>
loki666: ah, 8650
<Mis012[m]>
is too new
<Mis012[m]>
so the EDK2 part is signed by qcom
<Mis012[m]>
still could be argued you own it, if we pretend TME doesn't exist, assuming you're willing to boot over JTAG :P
<Mis012[m]>
otherwise eh sad stuff
<loki666>
my device is not secure boot enabled, not sure if that's what you mean
<loki666>
and qtestsign -v7 worked
<Mis012[m]>
well, you see
<Mis012[m]>
some stuff is locked down by qcom straight out of the factory
<Mis012[m]>
and iirc on 8650 that "some stuff" is a lot of stuff
<loki666>
you mean source code for LinuxLoader ?
<Mis012[m]>
but in theory you should be able to bypass stuff other than TME with JTAG on a fully unfused device, which is however the exact opposite of what you wanted because it needs more external stuff
<Mis012[m]>
loki666: I meant the ability to run any non-qcom-approved code at all
<loki666>
but I just ran a self signed ABL
<Mis012[m]>
and by approved I mean qcom-developed, because ain't no way they will sign something for you
<Mis012[m]>
loki666: ABL runs at a very late stage in the boot process with very little privileges
<loki666>
ok, but for my use-case dual booting a linux kernel on SD, or fallback to android boot image, that's all I need no ?
<Mis012[m]>
well, for doing it in a stupid way that is only necessary because qcom are assholes, yes
<Mis012[m]>
again, you may be able to put u-boot into ABL
<Mis012[m]>
idk how much it cares about efi boot services still existing
<Mis012[m]>
it may just work
abelvesa has joined #linux-msm
<Mis012[m]>
the second part is whether LinuxLoader will like u-boot's efi implementation
<Mis012[m]>
loki666: but I still don't understand why your current solution requires an sdcard
<Mis012[m]>
can't you repartition to make an ESP on the UFS
<Mis012[m]>
and make abl2efs boot that
<loki666>
yes, but I'd like to keep the internal untouched as much as possible
<loki666>
so currently abl2eps need the SD card, or the device is stuck
<Mis012[m]>
you clearly need to stuff grub and LinuxLoader somewhere
<Mis012[m]>
if you want that to be internal storage, you have to make a partition for it
<loki666>
I want my linux to be on the SD card alone, and Android in UFS (only overwritting ABL) to add the dual-boot logic
<Mis012[m]>
or, if the ABL partition has free space, you can patch abl2efs to include LinuxLoader inside it and use it as a fallback
<loki666>
yes that's waht I'm thinking
<loki666>
pretty sure I have enough space
<Mis012[m]>
you don't need an "edk port" for that (and it wouldn't fit anyway)
<Mis012[m]>
you can just put the LinuxLoader as an elf segment with linker magic and load it from there
<Mis012[m]>
loki666: I was about to explain the boot process to you, but idk if you care since it's not required knowledge for your task
<Mis012[m]>
TME boots up PBL (bootrom) on the actual arm cores (one of them anyway), which you may be able to break in with JTAG on an unfused SoC (well, as unfused as you can get)
<Mis012[m]>
on older stuff PBL is actually the first core, on very old stuff it's not but you probably don't care about anything that old
<Mis012[m]>
*code
<Mis012[m]>
and arm the first code
<Mis012[m]>
*core
<Mis012[m]>
smh
<loki666>
Mis012[m] thanks. indeed not very relevant for me. I've mostly worked on simple Allwinner SoC so far... Qcom is really something else
<Mis012[m]>
older stuff was actually reasonable with sb off