Date: Thu, 16 May 2024 06:43:05 +0200 From: pyrus aboris <pyrus@bsdmail.com> To: Ronald Klop <ronald-lists@klop.ws> Cc: freebsd-embedded@freebsd.org Subject: Re: Re: Broadcom VideoCore graphics acceleration on microboards Message-ID: <trinity-c8fe3dee-0272-4248-a6c2-96f9d7068151-1715834585369@3c-app-mailcom-lxa13> In-Reply-To: <1257336377.4939.1700048220450@localhost> References: <trinity-e3e761fa-e1ba-4359-ba8c-2bbcc07bdabc-1700035971787@3c-app-mailcom-lxa03> <1257336377.4939.1700048220450@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
There's a newer mention of this for Arm boards for Raspberry Pi a month lat= er in December, https://lists=2Efreebsd=2Eorg/archives/freebsd-arm/2023-December/003409=2E= html That mailing list is more fitting=2E =C2=A0 If I were good at this, I would be more helpful=2E Though letting more know about it, is a start, because the common assumption was that everything uses Intel, AMD and Nvid= ia=2E It also doesn't need to be advanced video acceleration=2E A common future requirement would be enough to play video well enough=2E I also thought, that since NetBSD had one VideoCore driver, some part of it was opensource=2E Now, I understand, that was the video driver for Raspberry Pi 3, which NetBSD has a video driver to=2E You were referring to another opensource driver (V3D) for Raspberry Pi 4= =2E Thank you for a response=2E It's just good that there is more awareness of this lack of driver ability= =2E > If you have the skills and time to do it I know you would make more peop= le happy=2E [1] > When clicking from that blog to the NetBSD Wiki (https://wiki=2Enetbsd= =2Eorg/ports/evbarm/raspberry_pi/#index5h1[https://wiki=2Enetbsd=2Eorg/port= s/evbarm/raspberry_pi/#index5h1]) it states: "X11 and GPU > Video acceleration currently only works with 32-bit (ARMv7 and ARMv6) ke= rnels due to the Broadcom code not being 64-bit clean=2E > Since applications require specialized support for the GPU, only a few a= pplications are normally accelerated=2E NetBSD/aarch64 normally uses llvmpi= pe to provide fast parallel CPU-driven support for OpenGL, so should be fas= ter when running normal applications=2E > The situation should be improved, ideally by writing a DRM/KMS driver=2E= " > So it is not always a bed of roses in NetBSD land either=2E > AFAIK this broadcom stuff is proprietary closed source so a bit hard to = work on I guess=2E Although the forums link [1] states that RPI4 has an ope= n source V3D driver=2E > Regards, > Ronald=2E >> It has come to my attention that FreeBSD doesn't have a kmod driver for= Broadcom VideoCore GPU's >> for graphics acceleration=2E We may have assumed that most boards use A= MD, Intel or Nvidia GPU's, >> but microboards typically use VideoCore IV hardware for graphics=2E =C2=A0 >> In comparison, NetBSD has support for graphics acceleration for VideoCo= re hardware, as can be >> seen at https://blog=2Enetbsd=2Eorg/tnf/entry/raspberry_pi_gpu_accelera= tion_in =C2=A0 >> Also on FreeBSD, drivers may also be lacking for the audio hardware fro= m microboards, which may be bcm devices=2E =C2=A0 >> Thank you [https://forums=2Efreebsd=2Eorg/threads/what-about-2d-3d-hardware-accelera= tion-and-audio-support-on-raspberry-pi=2E86341/]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?trinity-c8fe3dee-0272-4248-a6c2-96f9d7068151-1715834585369>