Date: Sat, 17 Nov 2018 09:41:22 +0100 From: Niclas Zeising <zeising@freebsd.org> To: Tobias Kortkamp <tobik@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r484941 - head/graphics/drm-devel-kmod Message-ID: <12e38147-8d10-63a2-8fa1-870c0490729d@freebsd.org> In-Reply-To: <1542237219.290523.1577323056.21E82AF1@webmail.messagingengine.com> References: <201811142012.wAEKCcn4021442@repo.freebsd.org> <1542237219.290523.1577323056.21E82AF1@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/15/18 12:13 AM, Tobias Kortkamp wrote: > On Wed, Nov 14, 2018, at 21:12, Niclas Zeising wrote: >> Author: zeising >> Date: Wed Nov 14 20:12:38 2018 >> New Revision: 484941 >> URL: https://svnweb.freebsd.org/changeset/ports/484941 >> >> Log: >> graphics/drm-devel-kmod: Fix runtime >> >> Fix runtime after stolen memory handling was comitted. Use FreeBSD 1200086 >> as delimiter, since FreeBSD versions wasn't bumped for the stolen memory >> commit. > > Was there supposed to be a OSVERSION bump in the commit? Does it > still work reliably with >= 1200067 or only with >= 1200086 ? > Hi! I think Johannes wanted a version bump when the stolen memory handling went in to FreeBSD base. The version number is used internally in the source, that's why there's no bump in the ports makefile. drm-devel-kmod might work on versions lower than 1200086, it mostly depends on how bios handles stolen memory, and on your GPU. I've had trouble with it, before this change, but I know others where it worked. In any case, to use the -devel kmod you are expected to track a somewhat recent current in most cases. Regards -- Niclas Zeising
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12e38147-8d10-63a2-8fa1-870c0490729d>