From owner-freebsd-multimedia Thu May 1 12:11:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA10355 for multimedia-outgoing; Thu, 1 May 1997 12:11:34 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA10350 for ; Thu, 1 May 1997 12:11:32 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id MAA16610; Thu, 1 May 1997 12:11:29 -0700 (PDT) Date: Thu, 1 May 1997 12:11:29 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Randall Hopper cc: multimedia@freebsd.org Subject: Re: Updated driver (bt848-970424) In-Reply-To: <19970501070521.63393@ct.picker.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-multimedia@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 May 1997, Randall Hopper wrote: > Ahhh, I think I know what's going on now. The Bt's 4Bpp format w/ no byte > swapping is: ARGB. With byte swapping, you get access to BGRA, GBAR, and > RABG. According to your visual's RGB masks (RGB: 0000FF,00FF00,FF0000) and > display frame buffer depth (4Bpp), seems you need an ABGR ordering. The Bt > can't do it, thus the drop-back to X images. Sorry about that. > > If the Mach64 server support changing the pixel component ordering for that > 4Bpp/24bpp mode to ARGB (I know the chip supports it at least), that should > get you going there. Otherwise 15/16bpp might be your best option. This is the best I've heard yet. :) At least you guys can stop banging on this then... Guess it's time to go bother xfree. Thanks all for helping me resolve this. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major