Action Item #1015
closed
Remove old component build configs.
100%
Description
Look under src in xcc, buildroot (including patches and packages)
Updated by Hammel 7 months ago
- Status changed from New to In Progress
- % Done changed from 0 to 20
While cleaning out and doing a test build I found that the upstream kernel had been bumped. This required updating the saved kernel config for rpi2, where I was doing the test build. That means I will also need to update the saved kernel config on rpi1 and rpi4 builds.
Updated by Hammel 7 months ago
- % Done changed from 50 to 80
Tested on RPi2 failed because a recent kernel update upstream broke the fbdev driver WRT the X.org fbturbo driver. The latter crashes with those upstream changes. I found I had to drop back to the third commit back on the upstream for things to work again. I've updated the build to use a specific commit hash for the kernel now.
This change was tested on RPi2 and works fine. Now building on RPi1 and RPi4 and will test on hardware.
Updated by Hammel 7 months ago
RPi1 test on Pi Zero W v1.1 passed using PiPlayer system.
RPi4 test on RPi4 with PiSentry failed. X.org does not start because PiSentry wants /dev/fb1 but there is no /dev/fb1, only /dev/fb0. The tft35a driver doesn't appear to be loaded. In fact, no drivers appear to be loaded. Something went wrong on install or reboot after install.
Updated by Hammel 7 months ago
TFT module naming has changed in the latest kernel. There is now a specific fbtft_<device> for each display. So instead of fbtft_device being loaded, I need to load the a display specific driver, as in the following.
$ find /lib/modules/6.1.54-v7l+/ -name "fb*"
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_agm1264k-fl.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_bd663474.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_hx8340bn.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_hx8347d.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_hx8353d.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_hx8357d.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_ili9163.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_ili9320.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_ili9325.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_ili9340.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_ili9341.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_ili9481.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_ili9486.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_pcd8544.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_ra8875.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_s6d02a1.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_s6d1121.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_sh1106.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_ssd1289.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_ssd1306.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_ssd1331.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_ssd1351.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_st7735r.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_st7789v.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_tinylcd.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_tls8204.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_uc1611.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_uc1701.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fb_upd161704.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/staging/fbtft/fbtft.ko.xz
/lib/modules/6.1.54-v7l+/kernel/drivers/video/fbdev
/lib/modules/6.1.54-v7l+/kernel/drivers/video/fbdev/core/fb_sys_fops.ko.xz
I also failed to remove the compression on drivers. It's possible just switching "fbtft_device" to "fbtft" in /etc/modules and uncompressing the driver modules might be all that's required for RPi4 with PiSentry. I should note that module compression is also not currently turned off on RPi1, so I need to do that and retest it as well.
Updated by Hammel 7 months ago
RPi4 build exposed a bug in the -preconfig target of the kernel build. The bug prevented the use of a local config file. This has been fixed and the RPi4 build has been tested on hardware and is working fine.
Fix is committed and pushed. It's been pulled on the RPi1 and RPi2 sandboxes and is being rebuilt for final testing on hardware.
Updated by Hammel 7 months ago
- Status changed from In Progress to Closed
- % Done changed from 80 to 100
RPi2 works fine. RPi1, on a Pi Zero W, works though there are some issues with, for example, Samba not finding other devices on the network. But that's a different issue. Pi Zero W's use cases are for Kiosk, AutoKiosk, PiSensors and the TBD PiGrrll project.
Code committed and pushed.
Closing issue.