On 23.12.2024 2:07 PM, Pengyu Luo wrote:
> On Mon, Dec 23, 2024 at 8:25 PM Konrad Dybcio <konrad.dybcio@xxxxxxxxxxxxxxxx> wrote:
>> On 21.12.2024 8:57 AM, Pengyu Luo wrote:
>>> Messing up, reply again to fix thread.
>>>
>>> On Sat, Dec 21, 2024 at 5:14 AM Konrad Dybcio <konrad.dybcio@xxxxxxxxxxxxxxxx> wrote:
>>>> On 20.12.2024 5:05 PM, Pengyu Luo wrote:
>>>>
>>>
>>> [...]
>>>
>>>>> + chosen {
>>>>> + #address-cells = <2>;
>>>>> + #size-cells = <2>;
>>>>> + ranges;
>>>>> +
>>>>> + framebuffer0: framebuffer@c6200000 {
>>>>> + compatible = "simple-framebuffer";
>>>>> + reg = <0x0 0xc6200000 0x0 0x02400000>;
>>>>> + width = <1600>;
>>>>> + height = <2560>;
>>>>> + stride = <(1600 * 4)>;
>>>>> + format = "a8r8g8b8";
>>>>> + };
>>>>> + };
>>>>
>>>> I still don't understand why efifb doesn't work for you.
>>>>
>>>
>>> In v1, you asked me
>>
>> Ahh sorry, I churn through a lot of emails and sometimes forget things.
>>
>>>
>>>> Very very weird. Are you booting with clk_ignore_unused pd_ignore_unused
>>>> in kernel cmdline?
>>>
>>> I said yes, as Johan suggested in here (see [1]). I am adding Johan.
>>>
>>>> Could you share your .config file?
>>>
>>> Here please, https://pastebin.com/UKew61ZC
>>
>> All the things one would expect for efifb to show up seem to be there.
>>
>> Maybe try earlycon=efifb video=efifb?
>
> Not work, whether or not adding clk_ignore_unused pd_ignore_unused.
I am utterly confused then, maybe it's one of those devices where calling
exit boot services kills the display.
Either way, let's not worry about it anymore
Konrad
