Date: Mon, 29 Sep 1997 19:12:38 -0400 From: Randall Hopper <rhh@ct.picker.com> To: User Al Johnson <Al.Johnson@AJC.State.Net> Cc: freebsd-multimedia@FreeBSD.ORG Subject: Re: fxtv Message-ID: <19970929191238.29355@ct.picker.com> In-Reply-To: <342E6C50.B181CA2F@AJC.State.Net>; from User Al Johnson on Sun, Sep 28, 1997 at 09:40:16AM -0500 References: <342E6C50.B181CA2F@AJC.State.Net>
next in thread | previous in thread | raw e-mail | index | archive | help
User Al Johnson:
|This morning I decided to try to bring up my STB TV/PCI card under
|FBSD 2.2-STABLE. I've got the xftv 0.44 package installed, the bktr0
|and tuner0 devices created and I get video.... but...
(Amancio, ccing you on this regarding a few driver bugs to add to your list.)
Sounds like the group was able to get you going with 15bpp. On my STB
Velocity 3D 4MB w/ XFree 3.3.1 and S3V server using the 970604 driver off
the Fxtv home page, I find the following Fxtv resource settings useful:
! Video-mode specific stuff
Fxtv.bswap2Bpp: true
Fxtv.bswap3Bpp: true
Fxtv.bswap4Bpp: true
Fxtv.wswap4Bpp: true
Fxtv.disableDirectV: false
Fxtv.Bpp24bit: 3
Fxtv.Bpp32bit: 3
This'll give good results for 8, 15, 16, 24, and 32bpp as configured in
XF86Config, using direct video in 15 and 16bpp, and XImages in 8, 24, & 32.
Note that 24 & 32bpp are internally both 3Bpp; that is, 3 bytes per pixel
on the frame buffer with the S3V server.
These settings force XImages for 24- and 32-bpp mode because a driver
extension and fix is necessary to support direct video correctly for 3Bpp
(packed 24-bit).
You'll notice that with some video window widths, half of your window will
look ok while the other half will be too red-, blue-, or green-ish and
there'll be a black line running up the middle of the window. I believe
that's a bug in the driver building the Bt848 RISC program.
Also, you'll see that when your video window is situated so X % 3 == 0, the
window looks OK, whereas with X % 3 == 1, your video will be displayed with
RGB mapped to BRG, and with X % 3 == 2, RGB -> GBR. All that is changing
from the app side is the start address in PCI memory, but it somehow seems
that the pixel components aren't synchronized with this start address when
rolling out of the FIFO.
Anyway, here's an Fxtv patch in case you want to play with direct video in
24bpp. This shouldn't affect 8, 15, and 16bpp.
--- xutil.c.ORIG Mon Sep 29 18:21:43 1997
+++ xutil.c Mon Sep 29 18:21:51 1997
@@ -735 +735 @@
- XUTILGetVisualBpp( display, vi, &Bpp, NULL );
+ XUTILGetVisualBpp( display, vi, NULL, &Bpp );
Randall
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970929191238.29355>