<Adrian[m]> <soupborsh[m]> "Here is my latest attempt:..." <- > <@soupborsh:matrix.org> Here is my latest attempt:... (full message at <https://matrix.org/oftc/media/v1/media/download/AcaHlwc05D91dlEzx9PrFczuu8DfGCXgEi0AV9oTVqp9f76YydO7D0uHaCfwx5S11JsZF_2DlIs5P6kZX536t4ZCeWIoe_hgAG1hdHJpeC5vcmcvdWpIREdHSWRQd052emJHZGhOb0NEcUFY>)
<Adrian[m]> there are a bunch of cmdline parameters that the android kernel expects to be set by the bootloader
<Adrian[m]> notably your panel name
<Adrian[m]> you'll have to pass them to the Android kernel from U-Boot
<soupborsh[m]> <Adrian[m]> "> <@soupborsh:matrix.org> Here..." <- Hello, is that my attempt somewhat correct? If I add every cmdline from /proc/cmdline should it work?
<soupborsh[m]> I will be glad if you could tell the correct way to boot Android kernel.
<Adrian[m]> the correct way to boot Android is to build your Android so it can be booted by grub or systemd-boot and use that instead
<Adrian[m]> that's what the virtio targets in LineageOS do at the moment and is the most standard you can get with an Android boot process
<soupborsh[m]> I would like to utilize big amount of already built android ROM's for surya. Is there a way to boot them with minimal changes?
<soupborsh[m]> Also I found that /proc/iomem is the memory map
<soupborsh[m]> * minimal changes? Maybe some kernel changes.
<soupborsh[m]> <Adrian[m]> "the correct way to boot Android..." <- Sorry, I meant by correct way to boot is working way to boot not the perfect/preferrable one. No matter how hacky it will be now, it is just for proof of concept, it can be improved later.
<soupborsh[m]> * minimal changes? Maybe some kernel changes. Rebuilding whole Android is horrible.
<z1r343l2[m]> <Adrian[m]> "that's what the virtio targets..." <- Are those virtio targets a separate device? Never saw them when building los for sweet
<ungeskriptet[m]> <z1r343l2[m]> "Are those virtio targets a..." <- https://wiki.lineageos.org/libvirt-qemu
<z1r343l2[m]> Meh
<z1r343l2[m]> <Adrian[m]> "> <@soupborsh:matrix.org> Here..." <- What device?
<z1r343l2[m]> Cust lies at scsi 0 33 on my end but I cannot access after formatting to fat
<soupborsh[m]> You can verify if that is that partition by using scsi part
<soupborsh[m]> and then fatls scsi DEVICE:PARTITION
<soupborsh[m]> I do not remember how I formatted cust
<soupborsh[m]> Maybe I did it using fastboot format cust, I can try it now.
<z1r343l2[m]> <soupborsh[m]> "and then fatls scsi DEVICE:..." <- That already not work
<soupborsh[m]> What is it outputting
<soupborsh[m]> * it outputting?
<z1r343l2[m]> Yeah, I couldn't format as fat32 because the part is too small so I had to go with fat16 maybe that's the problem
<z1r343l2[m]> soupborsh[m]: Nothing but also no error
<soupborsh[m]> I guess you can use cache partition. However I have seen some recovery and magisk logs here.
<z1r343l2[m]> How about external sd
<z1r343l2[m]> It shows as mmc 2
<soupborsh[m]> For me external sd does not work
<soupborsh[m]> I did fastboot format:ext4 cust, then in UMS added file and can see them using ext4ls scsi 0:7
<soupborsh[m]> Fastboot refused to format it to vfat or fat32
<z1r343l2[m]> You sure it's ext4?
<soupborsh[m]> cust is ext4, my sd card is pmos rootfs and boot partition left from old installation
<z1r343l2[m]> Ooh
<soupborsh[m]> I can format it if needed.
<soupborsh[m]> * if needed, but I think it should work in U-Boot as is no matter what is on it.
<z1r343l2[m]> If I just knew how to build pmos for swee
<z1r343l2[m]> The generic one does not work for sweet
<z1r343l2[m]> Well maybe with u-boot?
<z1r343l2[m]> Since the only problem seems that boot doesn't fit on the partition
<soupborsh[m]> From U-boot I plan to boot LineageOS from phone emmc and PostmarketOS from SD card.
<z1r343l2[m]> Makes sense I only booted pmos from userdata yet, what falls flat alongside android ofc
<z1r343l2[m]> Any idea yet how to start pmos with u-boot
<soupborsh[m]> I need Android for camera, gps, microphone and some android game. I will probably boot into GNU/Linux when I am at home.
<soupborsh[m]> <z1r343l2[m]> "Any idea yet how to start pmos..." <- IDK exactly but maybe modify that bootpartition to include your dtb and flash it to cache or cust. And flash userdata to userdata. Maybe something needs to be modified to load your dtb.
<z1r343l2[m]> Yeah but I think exactly that is the ptoblem
<z1r343l2[m]> Say is sweet deprecated from sm7150 mainline or nah
Lvmilmvl[m] has joined #sm7150-mainline
<Lvmilmvl[m]> <soupborsh[m]> "Here is my latest attempt:..." <- > <@soupborsh:matrix.org> Here is my latest attempt:... (full message at <https://matrix.org/oftc/media/v1/media/download/AdI59YECdxFFibq8hHFMszNWSvNXbFMBxtgB285Mf8w3mww7CWUMX9BYGAPWjsv4indbcVQUyfNpdFSX8ZpFYbxCeWJXMm4QAG1hdHJpeC5vcmcvQU1TWnpnYU1hbE9KZFZIaklVald4ZWNY>)
<z1r343l2[m]> On? Surya too?
<z1r343l2[m]> Oh I see what you did there
<z1r343l2[m]> <Lvmilmvl[m]> "1000007721.png" <- is uInitrd Same Thing as ramdisk.cpio?
<Lvmilmvl[m]> <z1r343l2[m]> "is uInitrd Same Thing as ramdisk..." <- yes.
<Lvmilmvl[m]> uInitrd - processed by a special utility (mkimage) so that u-boot can use it.
<Lvmilmvl[m]> <z1r343l2[m]> "On? Surya too?" <- Surya
<z1r343l2[m]> Ty for the Infos
<Lvmilmvl[m]> * uInitrd - ramdisk.cpio processed by