From dfc20aa0066cca2bc67f97e32fea93753ae02a4f Mon Sep 17 00:00:00 2001 From: Dmitry Ilyin <6576495+widgetii@users.noreply.github.com> Date: Sun, 17 May 2026 18:21:22 +0300 Subject: [PATCH] hi3520dv200: enable CONFIG_FB to fix hifb module load The vendor hifb.ko ships in the hisilicon-osdrv-hi3520dv200 package and is insmod'd by load_hisilicon at boot, but on the running camera it fails to resolve every framebuffer-core symbol it imports: hifb: Unknown symbol unregister_framebuffer (err 0) hifb: Unknown symbol framebuffer_alloc (err 0) hifb: Unknown symbol fb_dealloc_cmap (err 0) hifb: Unknown symbol register_framebuffer (err 0) hifb: Unknown symbol fb_alloc_cmap (err 0) hifb: Unknown symbol fb_pan_display (err 0) hifb: Unknown symbol framebuffer_release (err 0) Root cause: the per-board defconfig had `# CONFIG_FB is not set`, so drivers/video/fbmem.c and fbcmap.c are not compiled and those exports never enter kallsyms. hifb is itself the FB hardware driver - it only needs the FB core API, no CONFIG_FB_* sub-driver. The closest working DVR sibling, hi3536cv100, enables exactly CONFIG_FB=y with every CONFIG_FB_* / CONFIG_FRAMEBUFFER_CONSOLE / CONFIG_LOGO left unset; we mirror that minimum. Co-Authored-By: Claude Opus 4.7 (1M context) --- .../board/hi3520dv200/hi3520dv200.generic.config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/br-ext-chip-hisilicon/board/hi3520dv200/hi3520dv200.generic.config b/br-ext-chip-hisilicon/board/hi3520dv200/hi3520dv200.generic.config index a4950fea91..c7e64aa825 100644 --- a/br-ext-chip-hisilicon/board/hi3520dv200/hi3520dv200.generic.config +++ b/br-ext-chip-hisilicon/board/hi3520dv200/hi3520dv200.generic.config @@ -1120,7 +1120,7 @@ CONFIG_BCMA_POSSIBLE=y # CONFIG_ION is not set # CONFIG_VGASTATE is not set # CONFIG_VIDEO_OUTPUT_CONTROL is not set -# CONFIG_FB is not set +CONFIG_FB=y # CONFIG_FIRMWARE_EDID is not set # CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set