[mythtv] SMP and harware Recommendations

Chris Kleeschulte mythtv-dev@snowman.net
Thu, 19 Sep 2002 16:14:33 -0700


This is a multi-part message in MIME format.

------=_NextPart_000_0054_01C25FF7.A42FC4B0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have to mention something about the Geforce4MX...it has an integrated =
tv-out chip...not anything familiar like the bt869 which is used =
extensively on a lot of the other nvidia boards....I bought one and I am =
disappointed with it due to the tv-out chip's lack of configurability. =
The tv-out tool "nvtv" won't work with it because the tv-out is =
integrated into the GPU chipset on the GF4MX. I used the closed source =
driver from nvidia with it,which works OK...BUT there was no option to =
tweak the scan modes or anything like that. Something to think about =
when it comes to the GF4MX. This does not apply to other GF4's though, =
just the MX. If someone knows better, please clue me in :)



Chris


  ----- Original Message -----=20
  From: Isaac Richards=20
  To: mythtv-dev@snowman.net=20
  Sent: Thursday, September 19, 2002 12:36 PM
  Subject: Re: [mythtv] SMP and harware Recommendations


  On Thursday 19 September 2002 03:19 pm, mythtv@mcgerald.homelinux.com =
wrote:
  > My questions are
  >
  > 1.  Will MythTV take advantage of the Dual processors?

  It should, things are fairly heavily threaded -- 3 threads each for =
both=20
  playback and recording.  Of course, most of the really heavy =
computational=20
  stuff takes place in 1 thread each on record and playback, but having =
a=20
  dualie should still help. =20

  Memory contention/cache issues may impact performance, but I wouldn't =
think=20
  it'd be all that bad.  Depends on how the kernel schedules things, how =
much=20
  it bounces around between CPUs, etc.

  > 2.  Since the AIW card isn't going to be nice would a GF4MX and an =
ATI
  > TV-wonder be a good pair (I'm trying to stay near $100 to replace =
the AIW
  > and tigerdirect.com has both) or would I really be better off with =
the
  > GF4MX and a Hauppauge card?

  Yeah, the gf4mx and an ati tv wonder should work.

  Isaac
  _______________________________________________
  mythtv-dev mailing list
  mythtv-dev@snowman.net
  http://www.snowman.net/mailman/listinfo/mythtv-dev

------=_NextPart_000_0054_01C25FF7.A42FC4B0
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.2716.2200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DVerdana size=3D2>I have to mention something about the =

Geforce4MX...it has an integrated tv-out chip...not anything familiar =
like the=20
bt869 which is used extensively on a lot of the other nvidia boards....I =
bought=20
one and I am disappointed with it due to the tv-out chip's lack of=20
configurability. The tv-out tool "nvtv" won't work with it because the =
tv-out is=20
integrated into the GPU chipset on the GF4MX. I used the closed source =
driver=20
from nvidia with it,which works OK...BUT there was no option to tweak =
the scan=20
modes or anything like that. Something to think about when it comes to =
the=20
GF4MX. This does not apply to other GF4's though, just the MX. If =
someone knows=20
better, please clue me in :)</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DVerdana size=3D2>Chris</FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DVerdana size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dijr@po.cwru.edu href=3D"mailto:ijr@po.cwru.edu">Isaac =
Richards</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dmythtv-dev@snowman.net=20
  href=3D"mailto:mythtv-dev@snowman.net">mythtv-dev@snowman.net</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, September 19, =
2002 12:36=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [mythtv] SMP and =
harware=20
  Recommendations</DIV>
  <DIV><BR></DIV>On Thursday 19 September 2002 03:19 pm, <A=20
  =
href=3D"mailto:mythtv@mcgerald.homelinux.com">mythtv@mcgerald.homelinux.c=
om</A>=20
  wrote:<BR>&gt; My questions are<BR>&gt;<BR>&gt; 1.&nbsp; Will MythTV =
take=20
  advantage of the Dual processors?<BR><BR>It should, things are fairly =
heavily=20
  threaded -- 3 threads each for both <BR>playback and recording.&nbsp; =
Of=20
  course, most of the really heavy computational <BR>stuff takes place =
in 1=20
  thread each on record and playback, but having a <BR>dualie should =
still=20
  help.&nbsp; <BR><BR>Memory contention/cache issues may impact =
performance, but=20
  I wouldn't think <BR>it'd be all that bad.&nbsp; Depends on how the =
kernel=20
  schedules things, how much <BR>it bounces around between CPUs,=20
  etc.<BR><BR>&gt; 2.&nbsp; Since the AIW card isn't going to be nice =
would a=20
  GF4MX and an ATI<BR>&gt; TV-wonder be a good pair (I'm trying to stay =
near=20
  $100 to replace the AIW<BR>&gt; and tigerdirect.com has both) or would =
I=20
  really be better off with the<BR>&gt; GF4MX and a Hauppauge =
card?<BR><BR>Yeah,=20
  the gf4mx and an ati tv wonder should=20
  =
work.<BR><BR>Isaac<BR>_______________________________________________<BR>=
mythtv-dev=20
  mailing list<BR><A=20
  =
href=3D"mailto:mythtv-dev@snowman.net">mythtv-dev@snowman.net</A><BR><A=20
  =
href=3D"http://www.snowman.net/mailman/listinfo/mythtv-dev">http://www.sn=
owman.net/mailman/listinfo/mythtv-dev</A></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0054_01C25FF7.A42FC4B0--