Date: Thu, 18 Jul 2019 07:50:09 -0600 From: Sergey Manucharian <sm@ara-ler.com> To: Oleksandr Tymoshenko <gonzo@bluezbox.com>, freebsd-arm@freebsd.org Subject: Re: Writing to /dev/fb0 Message-ID: <20190718135009.GX2903@eldorado> In-Reply-To: <20190718131525.GJ2342@funkthat.com> References: <CAFgkNAkVHccLg15aq9RY5CaT1qV=Bku2KpqOZiLjaNhJJF%2B8=A@mail.gmail.com> <20190621170845.GD2903@eldorado> <20190621171343.GE2903@eldorado> <CAFgkNAmw3cyhacK2RT2bHn=pNjRTE39o=bAR7aeuJPRb6W1dyQ@mail.gmail.com> <20190621190502.GA35692@bluezbox.com> <20190621193419.GG2903@eldorado> <20190624213339.GM2903@eldorado> <20190718131525.GJ2342@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Excerpts from John-Mark Gurney's message from Thu 18-Jul-19 06:15: > > As I already mentioned, these messages > > > > WARNING: Device driver fb has set "memattr" inconsistently (drv 0 pmap 3). > > > > flood console. So, the actual performance is very poor because of that, > > Looks like those messages need to be rate limited... There's > counter_ratecheck and ratecheck functions that can be used to easily > fix this.. That sounds good, but shouldn't this be fixed in the fb driver to "set memattr consistently"? -- Thanks, Ϟϻ
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190718135009.GX2903>