Date: Mon, 3 Mar 2014 09:44:18 -0800 From: Justin Hibbits <jhibbits@freebsd.org> To: freebsd-arch@freebsd.org Subject: Re: newcons fb driver Message-ID: <CAHSQbTBTq6EKD_crn=rvbeUcAEBn7E%2B=U8wRHeqchazF1LhjwQ@mail.gmail.com> In-Reply-To: <5314B2A2.3060100@pix.net> References: <42130.1393829535@critter.freebsd.dk> <5314B2A2.3060100@pix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 3, 2014 at 8:49 AM, Kurt Lidl <lidl@pix.net> wrote: >> In message <CAJ-Vmo=jCGUxXs_GBoCm581wTouozWE=AQ3x1wBKYM_J3_dGrg at >> mail.gmail.com> >> >> , Adrian Chadd writes: >> >>> .. i'm pretty sure there was a reason for why it's done in byte sizes. >>> Maybe speak to phk? >> >> >> Buggy video hardware, which does not do larger writes correctly, >> the most recent one being an Intel Laptop, but I can't remember which. >> >> At the very least, byte writes needs to be a boot-time option. > > > Intel Atom boards, as I recall: > > http://freshbsd.org/commit/freebsd/r237203 > > -Kurt All great knowledge, but really only answers half of what I'm looking for (always good to know potential pitfalls). Assuming a tunable/sysctl is added, what's the best way to optimize from my original post? Use a backing buffer (potentially with a tunable to not)? Or assume we don't support background images, and write the background color in the masked pixels? - Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHSQbTBTq6EKD_crn=rvbeUcAEBn7E%2B=U8wRHeqchazF1LhjwQ>