I’ve confirmed the bootloader works on an old OnePlus 6t I had laying around giving a full graphical UEFI environment. In THEORY, if it implements a full standard UEFI boot environment, Haiku ARM64 might MIGHT MIGHT at least try to boot under it.
Which means… Haiku running on a phone may not be that crazy after all.
Need to see if Renegade passes a proper FDT to the booted OS
We would need FDT discovered drivers for… everything
Need to figure out screen framebuffer support… though UEFI framebuffer might be “enough”
Need to figure out how to get debug data from the devices since all we get is “one USB port” on phones lol.
The process would be something like…
fastboot flash boot (EFI bootloader).img
fastboot flash userdata haiku.mmc
Keep in mind, everything above is theoretical. @davidkaroly might want to validate my statements above since he’s put more ARM64 work in than I have at this point
Also keep in mind, Haiku’s not Android. Literally nothing would function. This is purely a “wouldn’t it be neat” conversation
Thanks. Seeing the possible devices … I understand all above.
Well, it was just a faint, shallow hope for a usable mobile Haiku (tablet) device.
As HW the Galaxy Tab S8/S9 Ultra is an attractive device for me as a used one in the future.
This way I should turn to other, non Android, but Windows based, non ARM, mobile devices to check out for such purposes.
The main reason I had not spent a lot to an Android device the same – not possible to easily install an alternate OS after Android support had run out or I want to replace it.
Also I hate that previously when I had one … an another machine needed to upgrade to a newer version of Android.
I do not know how it goes nowadays - at last time I had Android with a 4.4.x.x versio. It had not upgraded just updated, but I would have a Windows PC with installed Sony SW to execute the upgrade - this way I used it with the original version. I’ve just updated the OS on it with OTA - using WiFi.
Now I have a different financial situation … so no fancy new goodies on the table. ;-))
Anyway , it was interesting – against the sobering reality :-j
Might also be worth looking into Tow-Boot as well as common firmware for ARM. It tries to be consistent feature-wise across supported hardware and has an interface for configuration. Tried it out on a PinePhone and it works rather well.
With regards to debuggability, perhaps targeting the PinePhone line would be a good idea? Their 3.5mm jacks can be set to serial with a HW switch and usable with a USB adapter. I do want to try and boot Haiku on a PinePhone and see how far it goes, what needs to be done to do this?
I think the problem will be more on the GUI side than on the kernel side. Phones are just smaller computer, so the hardware programming is the same or very similar, but the user interface conventions, not so much.
I guess let’s see if we get the kernel to run, and then we can talk about what to do with the GUI (if anything at all)?
Agree. However, it shows that the compatibility of our ARM64 port is already pretty strong. IF someone could find a nice ARM64 Android tablet (Maybe one with a pen input), and that has a UEFI bootloader, the use case is a lot stronger.
I have a nice Samsung Galaxy tablet, the blocker is no UEFI bios ports yet