public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Benjamin Larsson <benjamin@southpole.se>,
	linux-media@vger.kernel.org, Eddi De Pieri <eddi@depieri.net>
Subject: Re: PCTV 520e on Linux
Date: Fri, 14 Oct 2011 10:19:33 -0300	[thread overview]
Message-ID: <4E9836E5.6040601@redhat.com> (raw)
In-Reply-To: <CAGoCfixwp-iVFJysEG=UjN63-U_P4mdFWt+8hCwFW7fYeADvuw@mail.gmail.com>

Em 13-10-2011 20:19, Devin Heitmueller escreveu:
> On Thu, Oct 13, 2011 at 7:06 PM, Benjamin Larsson <benjamin@southpole.se> wrote:
>> On 10/13/2011 07:48 PM, Devin Heitmueller wrote:
>>> On Thu, Oct 13, 2011 at 12:19 PM, Antti Palosaari <crope@iki.fi> wrote:
>>>>> You were close:  em2884, drx-k, xc5000, and for analog it uses the
>>>>> afv4910b.
>>>> Then it should be peace of cake at least for digital side.
>>> I don't think we've ever done xc5000 on an em28xx before, so it's
>>> entirely possible that the xc5000 clock stretching will expose bugs in
>>> the em28xx i2c implementation (it uncovered bugs in essentially every
>>> other bridge driver I did work on).
>>>
>>> That, and we don't know how much is hard-coded into the drx-k driver
>>> making it specific to the couple of device it's currently being used
>>> with.
>>>
>>> But yeah, it shouldn't be rocket science.  I added support for the
>>> board in my OSX driver and it only took me a couple of hours.
>>>
>>> Devin
>>>
>>
>> Eddi De Pieri has patches for the HVR-930C that works somewhat. The
>> hardware in that stick is the same.
>>
>> MvH
>> Benjamin Larsson
> 
> While the basic chips used are different, they are completely
> different hardware designs and likely have different GPIO
> configurations as well as IF specs.

The IF settings for xc5000 with DRX-K are solved with this patch:
	http://patchwork.linuxtv.org/patch/7932/

Basically, DRX-K will use whatever IF the tuner uses.

I've sent to Eddi to get some feedback, but he never returned back.

> 
> Devin
> 


  reply	other threads:[~2011-10-14 13:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 14:49 PCTV 520e on Linux Claus Olesen
2011-10-13 15:57 ` Devin Heitmueller
2011-10-13 16:07   ` Antti Palosaari
2011-10-13 16:15     ` Devin Heitmueller
2011-10-13 16:19       ` Antti Palosaari
2011-10-13 17:48         ` Devin Heitmueller
2011-10-13 23:06           ` Benjamin Larsson
2011-10-13 23:19             ` Devin Heitmueller
2011-10-14 13:19               ` Mauro Carvalho Chehab [this message]
2011-10-14 13:28                 ` Devin Heitmueller
2011-10-14 14:01                   ` AW: " Sönke Brandt
2011-10-14 14:04                     ` Devin Heitmueller
2011-10-14 16:14                       ` Mauro Carvalho Chehab
2011-10-14 16:41                         ` Devin Heitmueller
2011-10-14 17:39                           ` Mauro Carvalho Chehab
2011-10-14 18:38                             ` Devin Heitmueller
2011-10-14 14:03                   ` Mauro Carvalho Chehab

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=4E9836E5.6040601@redhat.com \
    --to=mchehab@redhat.com \
    --cc=benjamin@southpole.se \
    --cc=dheitmueller@kernellabs.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox