WIP: [board/batocera] initial work to get clockworkpi gameshell support

[arthurlutz]

No description provided.

[arthurlutz]

Related forum posts : https://forum.batocera.org/d/7337-batocera-on-clockworkpi-gameshell-hardware & https://forum.clockworkpi.com/t/what-would-it-take-to-run-batocera-on-the-gameshell/8113

This is work in progress, but I'd like to submit it early to get some feedback and maybe some help on how to work on this.

[nadenislamarre]

it looks good.
for scummvm, why did you add !BR2_PACKAGE_BATOCERA_TARGET_ORANGEPI_PC ?

[arthurlutz]

For scummvm I feel like mouse point-n-click games on a devices that (by default) does not have a mouse would be OK. If once we get an initial image going someone comes along and says "hey I can plug in a mouse or use only the gamepad" then why not enable it.

[Hew-ux]

The approach is "for all systems that build, leave enabled", such that if the user decides they want to use it, then they can do so. If there are requirements for a system to be fully operational on a particular platform, then they can be mentioned in the wiki.

Example (which actually covers your device I believe): https://wiki.batocera.org/remapping_controls_per_emulator

[arthurlutz]

Suggested change

	select BR2_PACKAGE_SCUMMVM if !BR2_PACKAGE_BATOCERA_TARGET_RPI1 && !BR2_PACKAGE_BATOCERA_TARGET_RPIZERO2 && !BR2_PACKAGE_BATOCERA_TARGET_CLOCKWORKPI
	select BR2_PACKAGE_SCUMMVM if !BR2_PACKAGE_BATOCERA_TARGET_RPI1 && !BR2_PACKAGE_BATOCERA_TARGET_RPIZERO2

[arthurlutz]

I have two .dtb files that are not in the upstream linux kernel. Right now I'm copying them by hand from https://github.com/wolfallein/clockworkpi-debian/blob/master/bin/kernel/5.7/ or https://github.com/clockworkpi/Kernel/tree/master/CPI3_linux_4.20 to compile the kernel. What would be the recommended way of including those in the build process ? (I can't find any other examples where the dtb is not in the upstream kernel).

[Hew-ux]

I had to do this recently for RPi3 actually. Take a look at #5812

The DTB source code will usually have the instructions on what to do.

[nadenislamarre]

if you copy them to the kernel sources, the easier way is to do a patch.
or
like here : https://github.com/batocera-linux/batocera.linux/blob/master/configs/batocera-rk3326_defconfig#L51

[arthurlutz]

Thanks for your tips. I now get to compile and build the image (even though there are still some things I don't fully understand). The image doesn't boot on the device (yet), but I'll soon have an UART to figure out what is going on. When swapping the linux file (kernel) with the working one the screen turn on and flickers, so there is part of it working.

On the working image (clockworkOS) I have a /boot.src file, is that required with batocera or not ?