From: bill murphy <gc2majortom@gmail.com>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Kaffeine commit b510bff2 won't compile
Date: Sat, 4 Mar 2017 13:57:28 -0500 [thread overview]
Message-ID: <1c5c2aed-f7c6-a189-6dc5-fd44007eefaa@gmail.com> (raw)
In-Reply-To: <20170304110743.7635879c@vento.lan>
That sounds good, would you like me to submit a good Frequency List to 'dtv-scan-tables'?
Maybe name it something like 'atsc/us-ATSC-center-frequencies-8VSB-06-2009', reflecting the
date since the spectrum was allocated that way?
Another Kaffeine related issue, I noticed in libdbv5 of v4l-utils, that there is no
"North American Standard" LNB configuration. I just modified the source to add
add one and recompiled. Since in North America, the FSS Band is from 11700 to 12200, and our LNBs are
designed with an LO Frequency of 10750 MHz. Kaffeine seems to work correctly now on my
Ku Band antennas. Would you like me to submit the patch, or just create a new bug report?
Thanks again,
Bill
On 03/04/2017 09:07 AM, Mauro Carvalho Chehab wrote:
> Em Sat, 4 Mar 2017 08:21:51 -0500
> bill murphy <gc2majortom@gmail.com> escreveu:
>
>> Hi Mauro,
>>
>> yes I can appreciate that, but why not just make one file for each
>> country that actually differs,
>>
>> rather than make the rest of us suffer?
>>
>> canada and the us are the same.
>>
>> atsc/us-ATSC-center-frequencies-8VSB
>>
>> So could add two files for mexico and korea.
>>
>> atsc/mx-ATSC-center-frequencies-8VSB
>> atsc/kr-ATSC-center-frequencies-8VSB
>>
>> can't be any worse that the hundreds of files being maintained for DVB-T
>> in various countries.
> That could be done, but newer updates to dtv-scan-tables
> (and projects that use it, like Kaffeine) would have regressions for
> people outside US that use it.
>
> What could be done, instead, would be to have another file for
> US new frequency set.
>
>>
>> On 03/01/2017 05:00 AM, Mauro Carvalho Chehab wrote:
>>> Hi Bill,
>>>
>>> Em Mon, 27 Feb 2017 23:46:09 -0500
>>> bill murphy <gc2majortom@gmail.com> escreveu:
>>>
>>>> Hi Mauro,
>>>>
>>>> Thanks for looking in to it. All is well now.
>>> Good! Thanks for testing.
>>>
>>>> On a sidenote, given 700 MHz is used for LTE, and not broadcasting
>>>>
>>>> anymore, would you folks consider removing ch 52 thru 69
>>>>
>>>> in the us-atsc-frequencies if I posted a simple patch to dtv-scan-tables?
>>> The problem is that, despite its name, this table is used on other
>>> Countries using atsc (like Mexico, Canada and South Korea):
>>>
>>> https://en.wikipedia.org/wiki/List_of_digital_television_deployments_by_country#/media/File:Digital_broadcast_standards.svg
>>>
>>> So, while the 700 MHz are still used on other ATSC Countries, we can't
>>> remove, as otherwise, it will not discover the channels at the upper
>>> frequency range there.
>>>
>>> Regards,
>>> Mauro
>
>
> Thanks,
> Mauro
next prev parent reply other threads:[~2017-03-04 18:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 1:57 Kaffeine commit b510bff2 won't compile bill murphy
2017-02-27 10:11 ` Mauro Carvalho Chehab
2017-02-28 4:46 ` bill murphy
2017-03-01 10:00 ` Mauro Carvalho Chehab
2017-03-04 13:21 ` bill murphy
2017-03-04 14:07 ` Mauro Carvalho Chehab
2017-03-04 18:57 ` bill murphy [this message]
2017-03-05 1:54 ` 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=1c5c2aed-f7c6-a189-6dc5-fd44007eefaa@gmail.com \
--to=gc2majortom@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@s-opensource.com \
/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