From: Devin Heitmueller <dheitmueller@kernellabs.com>
To: Eddi De Pieri <eddi@depieri.net>
Cc: linux-media@vger.kernel.org, Benjamin Larsson <benjamin@southpole.se>
Subject: Re: Trying to support for HAUPPAUGE HVR-930C
Date: Fri, 29 Jul 2011 14:10:25 -0400 [thread overview]
Message-ID: <CAGoCfiyoh1QSBgqFU6ym-co1QFdHanK3WJ_ese7Cv4ACRfDhrg@mail.gmail.com> (raw)
In-Reply-To: <CAKdnbx6O8JgMM37e28q1g9dt=AdJpAAjWHqxBnTXHZrcyBMKyQ@mail.gmail.com>
On Fri, Jul 29, 2011 at 7:15 AM, Eddi De Pieri <eddi@depieri.net> wrote:
> 2011/7/28 Benjamin Larsson <benjamin@southpole.se>:
>> 0x82 is the address of the chip handling the analog signals(?) Micronas
>> AVF 4910BA1 maybe.
>
> I don't have the schematic of hauppauge card, so I can't say you if
> 082 is the AVF 4910
Yes, it's an avf4910b. I did a Linux driver for the AVFA for the
Viewcast boards, but there isn't a driver for the AFVB at this time.
Should be pretty easy for you to whip one up though just by capturing
the register sets under Windows and then replaying them for each of
the three inputs.
Devin
>> So change the names so it is clear that this part
>> sends commands to that chip.
>
> As I already told my patch is a derivate work of Terratec H5 Patch.
> Mauro's patch should have the same issue
>
>> I'm not sure I understand the I2C addressing but my tuner is at 0xc2 and
>> the demod at 0x52.
Correct: the xc5000 is at 0xc2, the avf4910b is at 0x82 and the drx-k
is at 0x52.
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
next prev parent reply other threads:[~2011-07-29 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 8:53 Trying to support for HAUPPAUGE HVR-930C Eddi De Pieri
2011-07-28 12:13 ` Benjamin Larsson
2011-07-29 11:15 ` Eddi De Pieri
2011-07-29 13:03 ` Antti Palosaari
2011-07-29 18:10 ` Devin Heitmueller [this message]
2011-07-29 20:17 ` Daniel Glöckner
2011-08-04 6:36 ` Devin Heitmueller
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=CAGoCfiyoh1QSBgqFU6ym-co1QFdHanK3WJ_ese7Cv4ACRfDhrg@mail.gmail.com \
--to=dheitmueller@kernellabs.com \
--cc=benjamin@southpole.se \
--cc=eddi@depieri.net \
--cc=linux-media@vger.kernel.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.