All of lore.kernel.org
 help / color / mirror / Atom feed
From: Devin Heitmueller <dheitmueller@kernellabs.com>
To: Steven Toth <stoth@kernellabs.com>
Cc: linux-media@vger.kernel.org, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] EPG (Electronic Program Guide) Tools
Date: Wed, 27 May 2009 11:03:04 -0400	[thread overview]
Message-ID: <829197380905270803s2ea5abceh579ef1dc101dc6df@mail.gmail.com> (raw)
In-Reply-To: <4A1D54A5.40602@kernellabs.com>

On Wed, May 27, 2009 at 10:56 AM, Steven Toth <stoth@kernellabs.com> wrote:
> Chris,
>
> You'd expect to be able to get 3-4 days of advanced data to populate a guide
> with, in reality you can often get as little a six hours and that's it. The
> mandatory side of the spec is weak in this area. six hours is fine for Now /
> Next but of little use for anything else.
>
> Depending on your needs, your mileage may vary.
>
> Regards,
>
> - Steve

Steve,

The spec requires that at a minimum EIT-0 thorugh EIT-3 be sent
(discussed on page 41 of A/65C).  Of course, I don't know if
broadcasters actually comply with the requirement (although I suspect
they could be liable for FCC fines if they do not).  I will get a
better idea when I start working on EIT support for Kaffeine.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

  reply	other threads:[~2009-05-27 15:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 17:51 [linux-dvb] EPG (Electronic Program Guide) Tools Chris Capon
2009-05-26 18:05 ` Devin Heitmueller
2009-05-26 19:18   ` Jonathan Isom
2009-05-26 19:31     ` Devin Heitmueller
2009-05-26 19:39       ` Jonathan Isom
2009-05-27  0:20         ` Chris Capon
2009-05-27 14:56   ` Steven Toth
2009-05-27 15:03     ` Devin Heitmueller [this message]
     [not found] <mailman.1.1243418401.15557.linux-dvb@linuxtv.org>
2009-05-27 12:07 ` Adam Charrett

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=829197380905270803s2ea5abceh579ef1dc101dc6df@mail.gmail.com \
    --to=dheitmueller@kernellabs.com \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-media@vger.kernel.org \
    --cc=stoth@kernellabs.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 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.