Date: Mon, 03 Mar 2014 07:29:23 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Adrian Chadd <adrian@freebsd.org> Cc: Justin Hibbits <jhibbits@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: newcons fb driver Message-ID: <51906.1393831763@critter.freebsd.dk> In-Reply-To: <CAJ-Vmokv0r-rTCg15iWKLDcDLR8Hoh0WVgf3CDLNxz%2BONZ5EnQ@mail.gmail.com> References: <20140302085511.6354f9ac@zhabar.gateway.2wire.net> <CAJ-Vmo=jCGUxXs_GBoCm581wTouozWE=AQ3x1wBKYM_J3_dGrg@mail.gmail.com> <42130.1393829535@critter.freebsd.dk> <CAJ-Vmokv0r-rTCg15iWKLDcDLR8Hoh0WVgf3CDLNxz%2BONZ5EnQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <CAJ-Vmokv0r-rTCg15iWKLDcDLR8Hoh0WVgf3CDLNxz+ONZ5EnQ@mail.gmail.com> , Adrian Chadd writes: >> 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. > >Is there a way to detect this? Ie, writing to video memory and then >reading it back a byte at a time to see if the patterns match? Never tried that. Given that the display was bogus, it would probably work. Maybe do a "verify" on the first 10 screen updates ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51906.1393831763>