Re: Questions About SM8550 Support

[Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>]

On 1/30/26 6:13 PM, Aaron Kling wrote:
> On Fri, Jan 30, 2026 at 5:01 AM Konrad Dybcio
> <konrad.dybcio@oss.qualcomm.com> wrote:
>>
>> On 1/27/26 11:48 PM, Aaron Kling wrote:
>>> I am working on the AYN Odin 2 qcs8550 series of devices, specifically
>>> for Android, using mainline kernel drivers. I have come across some
>>> missing functionality and failures that I would like to inquire about.
>>>
>>> * ABL fails to load a dtbo using a baseline dtb unmodified from
>>> mainline. Using changes described in the gunyah watchdog thread [0], a
>>> dtbo loads and the devices boot as expected. If any of the changes in
>>> that post don't exist in the base dtb, abl will fail to load the dtbo
>>> and go to the bootloader menu. This appears to be an issue in the
>>> baseline abl code, affecting all devices of that generation. Would it
>>> be allowable to merge a change adding those changes to the sm8550
>>> dtsi, allowing an unmodified mainline dtb to work with overlays?
>>
>> ABL is.. picky.. to say the least
>>
>> Could you please try to check if what once worked for me on a
>> 8550-based Sony phone would happen to work for you too?
>>
>> 39c596304e44 ("arm64: dts: qcom: Add SM8550 Xperia 1 V")
> 
> Is the question if the devices boots without dtbo? Yes, that works.

That's nice!

> And fastboot erase even works too, though that may be because I'm not
> using appended dtb, I'm using dtb in vendor_boot. The setup I'm trying
> to use is a base dtb that has all the common nodes for the AYN qcs8550
> devices, then a device specific dtbo for the diverging parts of the
> four devices.

I'm not sure if that's a good idea if the bootloader is (effectively)
broken

I'd consider building full DTBs for each device

Konrad