Please build for kernel 5.15.34

[jplarochecps]

Hi,

The Poky Kirkstone release is recent and has the 5.15.84 kernel with the 4.0.7 release. However to use it on the raspberry pi the meta-raspberrypi layer is required and this layer wants a kernel version of 5.15.34. I have tried forcing it to use the 5.15.84 kernel but it keeps using 5.15.34.

Since Waveshare has not released the source code for this driver I can't build the driver for my specific kernel version. This is very frustrating.

If this could be done quickly by the end of the week and the github updated with the new 5.15.34 driver that would be great as we may be buying thousands of 10.1in Waveshare displays but if we can't get the driver working on our system we will just go with a different lcd vendor and write our own driver.

Thanks,

[6by9]

If you're after an open source driver for these panels, could you try raspberrypi/linux#5433 ?

It's been verified on the 2.8", 7", 7.9", 8.0" and 10.1" panels.

[talksik]

@6by9 can you please help me by explaining what you mean by try that file? I am a linux noob. Do you mean that I don't need the script to copy over and load the modules? I see panel-waveshare-dsi.ko.xz in my /lib/modules/6.1.54-v8/kernel/drivers/gpu/drm/panel/, but I don't understand what to do with it.

I get "exec format error" on my device that runs kernel 6.1.54. I tried installing the drives in this repo for 6.1.0, 6.1.21, and 6.1.58. All of them failed as expected.

What can I do to work around this without trying to compile yocto with a different kernel version because then I will have trouble maintaining parity with other peripherals hardware.

[6by9]

If you are running 6.1.54 built from the https://github.com/raspberrypi/linux repo, then adding dtoverlay=vc4-kms-dsi-waveshare-panel,<panel_variant> to config.txt should configure your system to look for the appropriate Waveshare panel.

See the Waveshare wiki at https://www.waveshare.com/wiki/2.8inch_DSI_LCD#For_Bookworm_and_Bullseye_System (or as appropriate for your panel), as they have now adopted and documented using those drivers instead of having their own closed source ones.

[talksik]

I believe my issue might be that I am using yocto (meta-raspberrypi) which doesn't include the overlay to control the driver?

I am going to try compiling the yocto image with additional configuration sometime this week as suggested here.

I appreciate the help @6by9 !