Message-ID: <FF1AF5A9FC464B45B799972E4DBF5450@Tyr>
From: "Christopher Karel" <kare0028@tc.umn.edu>
To: <ivtv-users@ivtvdriver.org>
Date: Sun, 1 Apr 2007 12:58:57 -0500
MIME-Version: 1.0
Subject: [ivtv-users] Correcting for overscan in X with a PVR350?
Precedence: list
Reply-To: User discussion about IVTV <ivtv-users@ivtvdriver.org>
Content-Type: multipart/mixed; boundary="===============3666850481193695767=="
Sender: ivtv-users-bounces@ivtvdriver.org
Errors-To: ivtv-users-bounces@ivtvdriver.org
Status: O

This is a multi-part message in MIME format.

--===============3666850481193695767==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0031_01C7745D.8276E900"

This is a multi-part message in MIME format.

------=_NextPart_000_0031_01C7745D.8276E900
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

  Can anyone help with compensating for overscan in X-windows running =
ivtv 10.1 on a PVR350 ?  At the moment, significant chunks of X is lost =
to it.  I can manually compensate on the MythTV frontend, but I still =
don't see all the buttons correctly.=20

    I've seen some mention of fbset and editing configuration files, but =
I couldn't actually get much to change.  (using fbset -upper/left just =
makes the screen flicker, without actually impacting anything)

  Are there any decent resources out there for playing with this?  Or =
can someone point me to some commands/config files to play with?


--Christopher Karel
------=_NextPart_000_0031_01C7745D.8276E900
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16414" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>&nbsp; Can anyone help with =
compensating for=20
overscan in X-windows running ivtv 10.1 on a PVR350 ?&nbsp; At the =
moment,=20
significant chunks of X is lost to it.&nbsp; I can manually compensate =
on=20
the&nbsp;MythTV frontend, but I still don't see all the buttons=20
correctly.&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; I've seen some =
mention of fbset=20
and editing configuration files, but I couldn't actually get much to=20
change.&nbsp; (using fbset -upper/left just makes the screen flicker, =
without=20
actually impacting anything)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp; Are there any decent resources =
out there for=20
playing with this?&nbsp; Or can someone point me to some commands/config =
files=20
to play with?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>--Christopher =
Karel</FONT></DIV></BODY></HTML>

------=_NextPart_000_0031_01C7745D.8276E900--


--===============3666850481193695767==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
--===============3666850481193695767==--