Is there a section where I can hire a programmer to fix the jared mcneill quartz64_uefi code that does not work on my 720x720 diisplay on the Radxa3W

Hello.

Is there a section where I can hire a programmer ? I need to assign a job to someone more experienced than me to be able to proceed with my project. And I'm available to pay a reasonable amount of money. What I don't know is if here there is a place where I can look for someone to hire.

Thanks.
 
I'm working on the creation of a FreeBSD based smartphone.


I've installed FreeBSD 14.3-Stable on my Radxa-3W. It works well on my HDMI big monitor that I keep at 1920x1080 of resolution,but it goes round and round like a carousel on my 720x720 display (to show you I have attached a small recorded video :


this one :

https://www.waveshare.com/4inch-hdmi-lcd-c.htm


I've grabbed two log files that I have attached.


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 can tweak EDK2 to let me use my display at 720x720 resolution ? Please,I don't have the skills to understand what parameters to change inside the EDK2 code that's stored here :

https://github.com/jaredmcneill/quartz64_uefi

Give a look and make a quote. I need to understand if I can afford the price. Thanks.
 

Attachments

your problem is probably here
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
 
I don't know how to do that. I need a deep help. Something like : you explain what to do carefully and with patience and I do it.
I know that it will take you time to help me finding an hack,so I'm available to pay your bill.
If I don't find a solution to this problem,my project will end here.
Maybe we can speed up the procedures to fix it if I buy a display like mine and I will send it to you ? So you can work directly with the hardware. At the end me and you will save a lot of time doing like this.
 
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…

but the horizontal and vertical display timings are defined in 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 = 720
 
That's nice. so,What should I do to hack the code,so that it can accept my 720x720 display ? Is there something that I can do ?
 
you could start by calculating the 720x720 timings and add it to the driver code.
The timings_calculator also provides pixel clock frequencies.

I am just beginning C/C++, so i'm not the right person to instruct you of how to proceed.
I'm not going to overstep my bounds, even if i am able to offer the correct data.
I do not feel comfortable doing so as a newbie to C/C++

You could ask someone at a C programming forum. I'm sure that you can get instructions from a proper programmer somewhere online. Refer to this post and say please :)
 
Back
Top
OSZAR »