From: "Rémi Denis-Courmont" <remi@remlab.net>
To: linux-media@vger.kernel.org
Subject: Re: [PATCH 0/5] Driver support for cards based on Digital Devices bridge (ddbridge)
Date: Sat, 16 Jul 2011 19:37:48 +0300 [thread overview]
Message-ID: <201107161937.48981.remi@remlab.net> (raw)
In-Reply-To: <4E21B3EC.9060709@linuxtv.org>
Le samedi 16 juillet 2011 18:53:16 Andreas Oberritter, vous avez écrit :
> > You are wrong, actually you can. At least here in Finland some cable
> > networks offers DVB-T too.
>
> I know that there are cable operators which use DVB-T, but they don't
> use DVB-C simultaneously. This wouldn't make sense, unless they didn't
> want their customers to receive their signals.
They do offer both simultaneously. DNA (formerly Welho) in Helsinki provides
both DVB-T and DVB-C on the same cable, obviously on different frequencies.
--
Rémi Denis-Courmont
http://www.remlab.net/
http://fi.linkedin.com/in/remidenis
next prev parent reply other threads:[~2011-07-16 16:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 21:21 [PATCH 0/5] Driver support for cards based on Digital Devices bridge (ddbridge) Oliver Endriss
2011-07-03 21:23 ` PATCH 1/5] ddbridge: Initial check-in Oliver Endriss
2011-07-03 21:24 ` [PATCH 2/5] ddbridge: Codingstyle fixes Oliver Endriss
2011-07-03 21:25 ` [PATCH 3/5] ddbridge: Allow compiling of the driver Oliver Endriss
2011-07-03 21:26 ` [PATCH 4/5] cxd2099: Fix compilation of ngene/ddbridge for DVB_CXD2099=n Oliver Endriss
2011-07-04 10:14 ` Bjørn Mork
2011-07-03 21:27 ` [PATCH 5/5] cxd2099: Update Kconfig description (ddbridge support) Oliver Endriss
2011-07-04 0:06 ` Walter Van Eetvelt
2011-07-03 22:27 ` [PATCH 0/5] Driver support for cards based on Digital Devices bridge (ddbridge) Mauro Carvalho Chehab
2011-07-03 23:24 ` Oliver Endriss
2011-07-04 0:17 ` Mauro Carvalho Chehab
2011-07-14 23:45 ` Oliver Endriss
2011-07-15 0:47 ` Mauro Carvalho Chehab
2011-07-15 2:11 ` Oliver Endriss
2011-07-15 4:01 ` Mauro Carvalho Chehab
2011-07-15 3:56 ` Mauro Carvalho Chehab
2011-07-15 5:17 ` Oliver Endriss
2011-07-15 8:26 ` Ralph Metzler
2011-07-15 13:25 ` Mauro Carvalho Chehab
2011-07-15 17:01 ` Andreas Oberritter
2011-07-15 17:34 ` Mauro Carvalho Chehab
2011-07-15 23:41 ` Antti Palosaari
2011-07-16 12:25 ` Mauro Carvalho Chehab
2011-07-16 14:16 ` Antti Palosaari
2011-07-16 14:54 ` Mauro Carvalho Chehab
2011-07-16 15:40 ` Andreas Oberritter
2011-07-16 15:44 ` Antti Palosaari
2011-07-16 15:53 ` Andreas Oberritter
2011-07-16 15:59 ` Antti Palosaari
2011-07-16 16:37 ` Rémi Denis-Courmont [this message]
2011-07-17 2:51 ` Andreas Oberritter
2011-07-17 7:51 ` Rémi Denis-Courmont
2011-07-17 0:56 ` Mauro Carvalho Chehab
2011-07-17 3:02 ` Andreas Oberritter
2011-07-17 3:59 ` Mauro Carvalho Chehab
2011-07-17 7:39 ` Rémi Denis-Courmont
2011-07-17 8:01 ` Mauro Carvalho Chehab
2011-07-17 1:07 ` Mauro Carvalho Chehab
2011-07-16 15:40 ` Oliver Endriss
2011-11-03 7:49 ` Steffen Barszus
2011-11-03 17:24 ` Lars Hanisch
2011-07-15 4:18 ` Mauro Carvalho Chehab
2011-07-15 5:21 ` Oliver Endriss
2011-07-15 12:40 ` Mauro Carvalho Chehab
2011-07-17 11:44 ` Oliver Endriss
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=201107161937.48981.remi@remlab.net \
--to=remi@remlab.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;
as well as URLs for NNTP newsgroup(s).