All of lore.kernel.org
 help / color / mirror / Atom feed
From: wk <handygewinnspiel@gmx.de>
To: BOUWSMA Barry <freebeer.bouwsma@gmail.com>
Cc: benjamin.zores@gmail.com, linux-media@vger.kernel.org
Subject: Re: [PATCH] add new frequency table for Strasbourg, France
Date: Tue, 17 Mar 2009 18:21:40 +0100	[thread overview]
Message-ID: <49BFDC24.8050905@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.00.0903170237550.4176@ybpnyubfg.ybpnyqbznva>


> Then there must be something ``wrong'' with `w_scan' making
> incorrect assumptions about the data which it's parsing.
>
>   
No - i do not think so.
All of the frequencies found are with 166kHz offset.
w_scan does not use any of these 166k offsets, that means this frequency 
data was transmitted as exactly such a number in some NIT w_scan parsed.

w_scan calculates DVB-T center freqs as "center freq = (306000000 + 
channel * 8000000) Hz" for this range.
And NIT parsing is the same as dvbscan.

> What has disturbed me is how this offset has been applied
> across the board by `w_scan',
Again, w_scan does not use these offsets.

Some dvbsnoop output as suggested and additional some scan with service 
names (either dvbscan or w_scan), vdr channels.conf would be fine, would 
really help to see whats going on here.


  reply	other threads:[~2009-03-17 17:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-14 17:56 [PATCH] add new frequency table for Strasbourg, France Benjamin Zores
2009-03-16  9:07 ` BOUWSMA Barry
2009-03-16 18:32   ` Benjamin Zores
2009-03-16 20:09     ` wk
2009-03-17  3:42       ` BOUWSMA Barry
2009-03-17 17:21         ` wk [this message]
2009-03-17 19:53           ` Benjamin Zores
2009-03-17 19:54             ` test C Khmer1
2009-03-17 21:16             ` [PATCH] add new frequency table for Strasbourg, France wk
2009-03-17 20:34         ` Benjamin Zores
2009-03-19 20:27           ` BOUWSMA Barry
2009-03-16 20:21     ` wk
2009-03-22 21:07 ` Christoph Pfister

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=49BFDC24.8050905@gmx.de \
    --to=handygewinnspiel@gmx.de \
    --cc=benjamin.zores@gmail.com \
    --cc=freebeer.bouwsma@gmail.com \
    --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.