From: Dirk Thierbach <dthierbach-Mmb7MZpHnFY@public.gmane.org>
To: Sergej Pupykin <pupykin.s-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: tv-out on FX5700VE
Date: Mon, 14 Jul 2008 09:50:10 +0200 [thread overview]
Message-ID: <20080714075010.GA3574@feanor> (raw)
In-Reply-To: <2bb4a8220807121258x38c9adf8vf123588e8ba17153-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Sat, Jul 12, 2008 at 11:58:59PM +0400, Sergej Pupykin wrote:
> I am interested in nouveau tv-out support. I read
> http://nouveau.freedesktop.org/wiki/TestersWanted and make nvclock
> dump with working tv-out on nvidia drivers.
>
> xorg.conf and nvclock output are in attachments.
>
> I have free saturday evening every week, so feel free to instruct me,
> I like to help)
>
> Also I have some expirience in C and generic knowledge about xorg
> video drivers, so you may ask me to experiment with the code...
I'm not really associated with nouveau, though I maintain nvtv, which is
an independent tool for tv-out on nvidia cards. The main problem is
that we do not know what most of the registers involved mean. If you
do have access to an oscilloscope, most of them should be easy to find
out -- just hook up the scope, change some registers, and watch what
happens. "seventh guardian" contaced me some time ago and wanted to do
this, but somehow he disappeared :-)
So if you have a scope, if you're not afraid to possibly damage your
hardware, you can contact me off-list for details.
- Dirk
next prev parent reply other threads:[~2008-07-14 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-12 19:58 tv-out on FX5700VE Sergej Pupykin
[not found] ` <2bb4a8220807121258x38c9adf8vf123588e8ba17153-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-14 7:50 ` Dirk Thierbach [this message]
2008-07-14 11:01 ` Sergej Pupykin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080714075010.GA3574@feanor \
--to=dthierbach-mmb7mzphnfy@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=pupykin.s-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.