Re: Which FreeBSD image file should be used in conjunction with idbloader.img and u-boot.itb ?

I'm trying to gather the necessary informations needed to produce a fix or
whatever :

a) your problem is probably here :

https://github.com/jaredmcneill/quartz64_uefi/blob/main/edk2-rockchip/Silicon/Rockchip/Rk356x/Drivers/DisplayDxe/DwHdmi.c
:

Code:

 /*
     * Driver doesn't know how to drive all modes yet. Restrict to known modes.
     */
    switch (PixelClock * 10) {
    case 594000:
    case 297000:
    case 148500:
    case 74250:
        break;
    default:
        DEBUG ((DEBUG_WARN, "HDMI: Unsupported pixel clock %u kHz for
%ux%u mode.\n",
                PixelClock * 10,
                Data[2] | ((Data[4] & 0xF0) << 4),
                Data[5] | ((Data[7] & 0xF0) << 4)));
        return FALSE;
    }

you may try a debug build or activate debug and see if you get this message

b) but the horizontal and vertical display timings are defined in
DisplayDxe.c

<https://raw.githubusercontent.com/jaredmcneill/quartz64_uefi/refs/heads/main/edk2-rockchip/Silicon/Rockchip/Rk356x/Drivers/DisplayDxe/DisplayDxe.c>
https://raw.githubusercontent.com/jaredmcneill/quartz64_uefi/refs/heads/main/edk2-rockchip/Silicon/Rockchip/Rk356x/Drivers/DisplayDxe/DisplayDxe.c


Code:

/* Fallback to 720p when DDC fails */
STATIC HDMI_DISPLAY_TIMING mDefaultTimings = {
    .Vic = 4,
    .FrequencyKHz = 74250,
    .HDisplay = 1280, .HSyncStart = 1390, .HSyncEnd = 1430, .HTotal =
1650, .HSyncPol = TRUE,
    .VDisplay = 720,  .VSyncStart = 725,  .VSyncEnd = 730,  .VTotal =
750,  .VSyncPol = TRUE,
};


vide .HDisplay = 1280 .vDisplay = 720I'

You know more than me what to do next ?

On Sun, May 18, 2025 at 11:30 AM Mario Marietto <marietto2008@gmail.com>
wrote:

> ---> The video you attached is rather blurry, I don't see it well. I can
> recognize something is running on the screen but I'm not quite sure what it
> is.
>
> What you aren't able to see well is xfce4 installed on FreeBSD 14.3-Stable
> running on the Radxa-3W. It works well on my big monitor that I keep at
> 1920x1080 of resolution,but it goes round and round like a carousel on my
> 720x720 display.
>
> I've grabbed two log files that I have attached to this email.
>
> The log called "log-big-monitor" comes from the monitor that I'm using
> right now at 1920x1080 resolution connected to the RadXA 3w via HDMI.
>
> The log called "log-720 x 720-display" comes from the 4x4 inches display
> that I've bought to use with the smartphone that I want to create.
>
> You will see that it thinks that the display is 1280x720 (720p) and that
> is wrong and will likely cause the display to not understand what it gets
> delivered…
>
> Someone should tweak EDK2 to use a 720x720 resolution. I don't have the
> skills to do this. Can you make something ?
>
> It's necessary to start hacking the EDK2 code at :
> https://github.com/jaredmcneill/quartz64_uefi
>
> Thanks.
>
>
> On Sun, May 18, 2025 at 10:36 AM 風來散人 <furaisanjin@gmail.com> wrote:
>
>> Hello Mario.
>>
>> 2025年5月18日(日) 16:26 Mario Marietto <marietto2008@gmail.com>:
>>
>>> ---> There is 16M free space. If you write u-boot by dd, u-boot is
>>> located in this free space. The option parameter "seek" of dd decides the
>>> actual location.
>>>
>>> This is what I'm interested in. I would like to make the image of this
>>> 16M :
>>>
>>>  34      32734       - free -  (16M)
>>>
>>> (stored on the SD card where I have installed Linux,because the HDMI
>>> works perfectly there) with dd,but I don't know how to do it.
>>>
>>> Can you write me the exact command to issue ? thanks.
>>>
>>
>> If you want to backup (or copy) this free block, then the command should
>> be
>>
>> dd if=/dev/xxx of=you_output_file seek=34 count=32734
>>
>> But I don't think you can use this for FreeBSD.
>>
>> The video you attached is rather blur, I don't see it well. I can
>> recognize something is running on the screen but not quite sure what is it.
>>
>> Best regards,
>> furaisanjin
>>
>
>
> --
> Mario.
>


-- 
Mario.