public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Schinagl <oliver+list@schinagl.nl>
To: dirk@GNUmatic.de
Cc: "Hermann Ulrichskötter" <ulrichsk@gmx.de>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: [DTV Update] Re: Änderung der Sendefrequenzen bei KabelBW
Date: Wed, 03 Jul 2013 21:46:23 +0200	[thread overview]
Message-ID: <51D47F8F.10906@schinagl.nl> (raw)
In-Reply-To: <1372876350.31609.19.camel@twin.GNUmatic.de>

Pushed to the dtv-scan-tables tree. A package should be generated thanks 
to mauro soon, so if packagers download tomorrow, or pull from git now, 
they have the new version.

On 07/03/13 20:32, Dirk Ritter wrote:
> Hello Oliver! :-)
>
> Am Mittwoch, den 03.07.2013, 19:54 +0200 schrieb Oliver Schinagl:
>
>>> Ich habe in der Datei in dieser Datei die einzig relevante Zeile von "C
>>> 113000000 6900000 NONE QAM64" auf "C 114000000 6900000 NONE QAM256" korrigieren
>>> müssen, so dass der Scan wieder geklappt hat.
>> It looks like they changed frequencies.
>
> Yes.
>
>>   Their site confirms that a big
>> changeover happened in June. I have staged this commit and will push it
>> tomorrow unless anybody objects, Dirk, can you confirm/deny this being
>> correct?
>
> It is correct. I got an e-mail from Martin Klar who lives
> in a KabelBW area that got the change earlier than mine.
> I did wait for the change and can positively confirm it.
> Based on data available (I did try to make sense of his
> change beforehand) and based on testing done using Kaffeine
> just after KabelBW changed it in Stuttgart.
>
>> I already have it in my private repo [0]
>
> Life took it's toll, so I didn't manage to forward this.
> Martin already tried without any luck and that's why he
> contacted me so that I could try. It was a rather difficult
> story back then I first cooked it up since there was
> disagreement between documents floating around and actual
> frequencies used and as a result of further difficulties
> with different tables for different service levels we
> concluded it would be best to just have one frequency,
> especially since that worked across both levels, i.e. for
> both fully and partly populated network areas within KabelBW.
>
> I guess Martin would love to see the file changed as he
> did, see attachment... ;-)
>
> BTW - what about Kaffeeine? How do they handle it? I
> just changed it locally and it works, but I don't think
> they did update it either.
They probably maintain their own (bad).

>
> Hopefully, this will propagate fast...
>
> Cheers!
> Dirk
>
oliver

      parent reply	other threads:[~2013-07-03 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51D452EC.5090008@gmx.de>
2013-07-03 17:54 ` [DTV Update] Re: Änderung der Sendefrequenzen bei KabelBW Oliver Schinagl
     [not found]   ` <1372876350.31609.19.camel@twin.GNUmatic.de>
2013-07-03 19:46     ` Oliver Schinagl [this message]

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=51D47F8F.10906@schinagl.nl \
    --to=oliver+list@schinagl.nl \
    --cc=dirk@GNUmatic.de \
    --cc=linux-media@vger.kernel.org \
    --cc=ulrichsk@gmx.de \
    /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