Date: Wed, 26 Feb 2020 03:48:05 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 236003] x11-drivers/xf86-video-intel: update to 2019-12-09 snapshot and refactor Message-ID: <bug-236003-7141-ZkRB1m5BIM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236003-7141@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236003 --- Comment #42 from Theron Tarigo <theron@freebsd.org> --- No, with your patches I have been able to use latest fbsd-12.0-kmod (4.12). Looks like I forgot to let you know when I first tried this and found that it is working. Also seems to work just as well with your latest patch (v7.3). I'm still using TearFree option, SNA, and no compositor daemon. The adapter is Intel(R) HD Graphics 530 (Skylake GT2) (0x191b) OpenGL works beautifully at 60fps, vsync, never tearing. However, nothing seems to play video at 60fps - Mplayer, Chromium, Firefox all drop frames, listed here in order of increasing severity. Can someone explain to me why "modesetting" is "the future" and xf86-video-intel is "legacy"? My experience has been that either Modesetting is fundamentally broken in design, or it really is just a bug for its entire existence that it allows frame-tearing. Probably not directly relevant, but both intel and modesetting waste about 4 watts of battery power compared to scfb driver, with everything else being equal, including drm module being loaded in all cases. I might actually save power overall by just using scfb and VirtualGL+Nvidia for OpenGL tasks when I need them. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236003-7141-ZkRB1m5BIM>