Date: Sat, 9 Nov 2019 14:50:08 -0600 From: "Matthew D. Fuller" <fullermd@over-yonder.net> To: Niclas Zeising <zeising@freebsd.org> Cc: freebsd-x11@freebsd.org Subject: Re: drm-fbsd11.2-kmod on 12 Message-ID: <20191109205008.GD3169@over-yonder.net> In-Reply-To: <87da494d-207e-269c-f608-c6266c274384@freebsd.org> References: <20191103231435.GH86455@over-yonder.net> <3231b40d-1041-10d2-f062-eda237e07a02@freebsd.org> <20191106230916.GI86455@over-yonder.net> <77bac16b-0438-b7ed-0c44-fadc230e55f8@freebsd.org> <20191107220050.GA3169@over-yonder.net> <87da494d-207e-269c-f608-c6266c274384@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 08, 2019 at 09:46:43AM +0100 I heard the voice of Niclas Zeising, and lo! it spake thus: > > I don't know if it is simple or not. The code is there, if you can > get it running on 12.1 without breaking 11.3, then, by all means do > it. FWIW, just cherrypicking back 9e308e6a707bc29 (adding pcpu.h to one file) from the 4.16-12.0 branch sufficed to get it building and basically running. I also pulled back 324a27a734733 (DRM_SYSCTL_PRINT locking) and 148d05832cc12 (enable MSI) since they seemed like good things. Apart from a little trivial conflict resolution on the latter, it all Just Happened. In a solid 5 minutes of running it and testing a little video playing (on the system where 4.16 is stable aside from the videos), it hasn't blown up yet. I'll see if something happens over the next few days. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191109205008.GD3169>