public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Chubb <paulc@singlespoon.org.au>
To: Steven Toth <stoth@linuxtv.org>, linux dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] Why I need to choose better Subject: headers [was: Re: Why (etc.)]
Date: Sun, 14 Sep 2008 09:02:01 +1000	[thread overview]
Message-ID: <48CC4669.9060407@singlespoon.org.au> (raw)
In-Reply-To: <48CC3479.5080706@linuxtv.org>

Steven Toth wrote:
> Paul Chubb wrote:
>> Barry,
>> I drew the line at porting the xc3028 tuner module from mcentral.de 
>> into v4l-dvb, so no didn't solve the firmware issues. If you know 
>> what you are doing it should be trivial work - just linking in yet 
>> another tuner module and then calling it like all the others. For me 
>> because I don't know the code well it would take a week or two.
>
> No porting required.
>
> xc3028 tuner is already in the kernel, it should just be a case of 
> configuring the attach/config structs correctly.
>
> - Steve
>
Steve,
           I think we are talking about two different things. Yes the 
xc3028 tuner is supported via tuner-xc2028 and works for many xc3028 
based cards. This support uses the xc3028-v27.fw file that contains say 
80 firmware modules. This firmware was extracted from a Haupage windows 
driver.

I believe that the 1800H has some incompatibility with this firmware. 
The mcentral.de tree has a different firmware loading and tuner support 
module for xc3028 that loads individual firmware modules - you literally 
put twenty or thirty files into /lib/firmware. This firmware is the 
standard firmware from xceive before the card manufacturers get to it. 
Comparing the dmesg listing from a working mcentral.de setup and the 
non-working v4l tree the only thing that leaps out is the different 
firmware. If I was continuing the next step would be to port that tuner 
module into the v4l code and set it up in the normal way.

Cheers Paul

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-09-13 23:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-13  6:28 [linux-dvb] why opensource will fail Paul Chubb
2008-09-13  9:43 ` [linux-dvb] Why my binary-only Win95 closed-source drivers trump your puny free-as-in-beer etc. [was: Re: why (etc.)] barry bouwsma
2008-09-13 10:35   ` Paul Chubb
2008-09-13 11:55     ` [linux-dvb] Why I need to choose better Subject: headers [was: Re: Why (etc.)] barry bouwsma
2008-09-13 20:25       ` Paul Chubb
2008-09-13 21:45         ` Steven Toth
2008-09-13 23:02           ` Paul Chubb [this message]
2008-09-14 14:50             ` [linux-dvb] xc3028 config issue. " Steven Toth
     [not found]       ` <alpine.LFD.1.10.0809151122480.16872@areia.chehab.org>
     [not found]         ` <141058d50809150800l73fe8b67qbc845cd6e01eafe2@mail.gmail.com>
2008-09-15 15:28           ` Christophe Thommeret
2008-09-21 15:07     ` [linux-dvb] Why my binary-only Win95 closed-source drivers trump your puny free-as-in-beer etc. [was: Re: why (etc.)] Markus Rechberger
2008-09-13 10:38 ` [linux-dvb] why opensource will fail Igor M. Liplianin
2008-09-13 20:31 ` Steven Toth
2008-09-13 22:48   ` Paul Chubb

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=48CC4669.9060407@singlespoon.org.au \
    --to=paulc@singlespoon.org.au \
    --cc=linux-dvb@linuxtv.org \
    --cc=stoth@linuxtv.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