Date: Fri, 28 Sep 2018 13:38:23 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Warner Losh <imp@bsdimp.com> Cc: "Matthew D. Fuller" <fullermd@over-yonder.net>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: drm2 in base Message-ID: <20180928203823.GC2631@troutmask.apl.washington.edu> In-Reply-To: <CANCZdfq0E=euENS_ougvDXB_p5pji6vwOhf0nMCuN_jEQmg6hQ@mail.gmail.com> References: <20180928180002.GA957@troutmask.apl.washington.edu> <20180928194739.GH32731@over-yonder.net> <20180928200102.GA2631@troutmask.apl.washington.edu> <CANCZdfq0E=euENS_ougvDXB_p5pji6vwOhf0nMCuN_jEQmg6hQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 28, 2018 at 02:21:24PM -0600, Warner Losh wrote: > On Fri, Sep 28, 2018 at 2:02 PM Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > > > On Fri, Sep 28, 2018 at 02:47:39PM -0500, Matthew D. Fuller wrote: > > > On Fri, Sep 28, 2018 at 11:00:02AM -0700 I heard the voice of > > > Steve Kargl, and lo! it spake thus: > > > > > > > > I have a radeon HD 6450 video card (CAICOS firmware), and have been > > > > informed that the hardware is too old for graphics/drm-stable-kmod > > > > and that I should use graphics/drm-legacy-kmod. > > > > > > Well, please don't tell that to the 6450 I've got running on > > > drm-next-kmod (which also spent some time on drm-stable)... > > > > > > > See the URL I posted. > > > > How did you get around the "fence_wait returned with error -512" > > messages filling /var/log/messages. > > > > Ah, that thread... OK. I'm back with you... > > > It also does not get around the problem that > > drm-legacy-kmod has been advertised as the drop-in > > replacement for those that use drm2 and have older > > hardware. > > > > It should be. The fact that it's not is concerning and should be > addressed... > Yes, it is concerning, and the reason for my request to retain drm2 in head. I'm willing to work with Johannes and Niclas or whomever to get things working. Unfortunately, kernel hacking is a little beyond my skills. AFAICT, the drm-*-kmod ports all depend on the same gpu-firmware port, which as the name indicates holds all the firmware. It seems that drm-legacy-kmod needs to learn how to parse the new naming scheme (and may be a new scheme for packing the firmware into a *.ko file). -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180928203823.GC2631>