From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <642eaa23a96e09ed6e0e9b9cfad90944@hamnavoe.com> From: Dave MacFarlane Date: Mon, 30 May 2016 09:13:51 -0400 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11448a96d6a72905340f08bf Subject: Re: [9fans] More about /dev/draw Topicbox-Message-UUID: 95ae8fc2-ead9-11e9-9d60-3106f5b1d025 --001a11448a96d6a72905340f08bf Content-Type: text/plain; charset=UTF-8 On Mon, May 30, 2016 at 8:37 AM, Richard Miller <9fans@hamnavoe.com> wrote: > > It turns out that the interface 9pi used for querying framebuffer depth > > is also now broken. Setting framebuffer_depth=N in config.txt used to > > work for changing the pixel format, now it doesn't. > > OK, new 9pi and 9pi2 kernels in /n/sources/contrib/miller should now do > the right thing for 24bpp, which can be requested with framebuffer_depth=24 > in config.txt or vgasize=WxHx24 in cmdline.txt > I was pretty sure it was either a kernel or libmemdraw bug, but I don't know how you can possibly track these things down so quickly without even getting a proper bug report. - Dave --001a11448a96d6a72905340f08bf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On M= on, May 30, 2016 at 8:37 AM, Richard Miller <9fans@hamnavoe.com>= wrote:
> It t= urns out that the interface 9pi used for querying framebuffer depth
> is also now broken.=C2=A0 Setting framebuffer_depth=3DN in config.txt = used to
> work for changing the pixel format, now it doesn't.

OK, new 9pi and 9pi2 kernels in /n/sources/contrib/miller should now= do
the right thing for 24bpp, which can be requested with framebuffer_depth=3D= 24
in config.txt or vgasize=3DWxHx24 in cmdline.txt

<= /div>
I was pretty sure it was either a kernel or libmemdraw bug, but I= don't know how you can possibly
track these things down so q= uickly without even getting a proper bug report.=C2=A0
=C2= =A0
- Dave
--001a11448a96d6a72905340f08bf--