Date: Thu, 27 Aug 2020 17:56:03 -0700 From: Chris <bsd-lists@bsdforge.com> To: Jan Beich <jbeich@freebsd.org> Cc: x11@freebsd.org Subject: Re: deprecation of drm-legacy-kmod Message-ID: <ef2f44d79947acf20a4ecb87aea12e46@bsdforge.com> In-Reply-To: <7dtj-pssq-wny@FreeBSD.org> References: <e770c456-c6fa-924c-0f1e-1d69ce80846f@freebsd.org> <caefaea84e701f966bc3b5dd9a0d7bef@bsdforge.com> <7dtj-pssq-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-08-27 16:34, Jan Beich wrote:
> Chris <bsd-lists@bsdforge.com> writes:
>
>> On 2020-08-24 15:21, Niclas Zeising wrote:
>>> It is time to deprecate drm-legacy-kmod, since it is taking too much
>>> time to maintain and are holding off changes in other areas.
> [...]
>> If this were pulled today. What are the ramifications? IOW what (A)GPUs
>> would
>> no longer be available for use on FreeBSD?
>
> (Disclaimer: I'm not part of the graphics team and don't hack kernel code)
>
> GPUs from ~20 years ago maybe limited to xf86-video-{vesa,scfb}.
> OpenGL acceleration have already been missing for ~8 years.
>
> https://gitlab.freedesktop.org/mesa/mesa/-/commit/e4344161bde2
>
> drm-legacy-9691917/src/dev/drm/drm_pciids.h:
> #define r128_PCI_IDS \
> {0x1002, 0x4c45, 0, "ATI Rage 128 Mobility LE (PCI)"}, \
> [...]
> #define mga_PCI_IDS \
> {0x102b, 0x0520, MGA_CARD_TYPE_G200, "Matrox G200 (PCI)"}, \
> [...]
> #define mach64_PCI_IDS \
> {0x1002, 0x4749, 0, "3D Rage Pro"}, \
> [...]
> #define sis_PCI_IDS \
> {0x1039, 0x0300, 0, "SiS 300/305"}, \
> [...]
> #define tdfx_PCI_IDS \
> {0x121a, 0x0003, 0, "3dfx Voodoo Banshee"}, \
> [...]
> #define viadrv_PCI_IDS \
> {0x1106, 0x3022, 0, "VIA CLE266 3022"}, \
> [...]
> #define savage_PCI_IDS \
> {0x5333, 0x8a20, S3_SAVAGE3D, "Savage 3D"}, \
>
> Everything else should still work but GPUs from ~10 years ago may hit bugs.
> One may need to help debugging and fixing those on drm-devel-kmod and
> then backport to drm-fbsd12.0-kmod. For example, Intel iGPUs predating
> SandyBridge were unstable in drm-fbsd11.2-kmod but not in drm-fbsd12.0-kmod
> until https://github.com/FreeBSDDesktop/kms-drm/pull/226
Thank you for your detailed reply, Jan. It covers it well. :-)
FTR I did'nt mean to sound like I was complaining. I was just looking to get
a feel for what I could expect FreeBSD to support when dealing with customer
equipment.
Thanks again!
--Chris
>
>> Does one need to join a Linux Graphics list to find out what's
>> currently supported?
>
> Linux still has r128, savage, etc. disabled by default. Userland support
> maybe hard to find as popular distros aim for modern hardware.
>
> https://github.com/torvalds/linux/commit/d92d9c3a1448
> https://www.phoronix.com/scan.php?page=news_item&px=Debian-Dropping-Old-Drivers
>
> Note, NetBSD also has r128, savage, etc. DRM drivers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ef2f44d79947acf20a4ecb87aea12e46>