psydroid has quit [Quit: Bridge terminating on SIGTERM]
Las[m] has quit [Quit: Bridge terminating on SIGTERM]
psydroid has joined #linux-amlogic
Las[m] has joined #linux-amlogic
<tolszak>
narmstrong: I'm sorry, I missed your message. I mean boot.scr instead of extlinux
<narmstrong>
tolszak: it would mean adding a recipe to generate a boot.scr while extlinux is already generated and does the job just fine
<narmstrong>
Boot.scr is on fact the legacy boot mode, the standard is extlinux and the modern is EFI
<narmstrong>
The 3 of them work out of the box with u-boot mainline so it’s a matter of adding the right files
<tolszak>
narmstrong: It does indeed, I'm just wondering if it is possible, customer has already uboot handling in its recipes for custom A/B partitioning, handling extlinux conf file is not a problem but add new bit to maintain
<narmstrong>
EFI needs GPT while we can’t mix u-boot and GPT with the same medium
<tolszak>
narmstrong: Thank you for clarification
<narmstrong>
tolszak: indeed it’s good point, but mender for example adds it’s own boot script for a/b
<narmstrong>
The problem would be for rauc where adding a boot.scr would be necessary with a FAT boot partition
<tolszak>
narmstrong: "EFI needs GPT while we can’t mix u-boot and GPT with the same medium" - is it because GPT layout is corrupted by writing hardkernel stuf in first 512 bytes of medium?
<narmstrong>
Yep
<tolszak>
narmstrong: I'm not 100% sure but I think I've used u-boot with gpt on rpi4
<narmstrong>
The solution is either to use different mediums (sd for u-boot, usb for fs) of flash I-boot on the emmc boot partitions
<tolszak>
narmstrong: The other usecase to not use extlinux may be petitboot and booting from USB, I think it expects boot.ini or something
<narmstrong>
On rpi the fw parses FAT, the amlogic bl0 loads the boot file at a fixed offset
<narmstrong>
You can perfectly boot from usb or whatever with extlinux, the problem how to pass the boot partition to linux
<narmstrong>
root=UUID only works reliably with gpt
<tolszak>
narmstrong: I know, petitboot just wouldn't boot such medium
<tolszak>
I;ve just checked
<narmstrong>
With msdos it’s hacky, and needs some Yocto wic hacking to achieve
<narmstrong>
Armbian has an initramfs which solves that, I need to find out how to do this cleanly for meta-meson
<tolszak>
narmstrong: I think you need to add --use-uuid to wks and provide partition uuid
<narmstrong>
Yes but the fdt file path is wrong because it was made for arm 32 but boards
<tolszak>
narmstrong: I see
<narmstrong>
I need to figure that out with limited time I have, help is welcome !
<tolszak>
tolszak: That's always the biggest problem hence me asking question here rather than reading code, buildin and checking which might take days
<f11f12>
narmstrong: is there any additional information on the DSI-MIPI output available?
Darkmatt- has joined #linux-amlogic
<narmstrong>
f11f12: what info do you need ?
<f11f12>
narmstrong: in mainline most of the timing related information seems hardcoded. I've attached a SN65DSI86 (mipi converter to eDP). To make this work I will have to understand more about the video pipeline (A311D in my case).
<f11f12>
Is there more public documentation about that part than only the datasheet?
<f11f12>
As far as I can tell by now it's currently not possible to use HDMI and MIPI
<f11f12>
at the same time
<narmstrong>
Dsi has been ported to mainline, I shared you the branch
<narmstrong>
But on mainline no dual display is not supported