public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Michael Krufky <mkrufky@kernellabs.com>
Subject: DVBv5 frontend library
Date: Wed, 09 Nov 2011 17:01:59 -0200	[thread overview]
Message-ID: <4EBACE27.8000907@redhat.com> (raw)

Hi,

As I've commented with some at the KS, I started writing a new DVB library, based on DVBv5.
It is currently at very early stages. Help and suggestions are welcome.

It is at:
	http://git.linuxtv.org/mchehab/experimental-v4l-utils.git/shortlog/refs/heads/dvb-utils

It currently doesn't do much, but the hole idea is to offer a library that can easily
upgraded to support new standards, and based on DVBv5.

The new stuff is under utils/dvb dir.

For now, it has only a few files:

gen_dvb_structs.pl: Extracts DVBv5 API information from dvb/frontend.h.
Just as a commodity, for now, the DVB API spec were copied as dvb_frontend.h
inside the tree.

dvb-v5.h: a file, generated from dvb/frontend.h using the perl script.
It basically defines a name for each enum value inside the dvb/frontend.h header.

The frontend library is inside:
	dvb-fe.c  
	dvb-fe.h 

And the pertinent parameters needed by each delivery system is provided into
a separate header:
	dvb-v5-std.h  

There's a small test tool that currently just queries the DVB capabilities,
at:
	dvb-fe-tool.c  

The test tool currently does nothing but querying the device capabilities, identifying
the supported delivery systems.

I hope this could be helpful for the ones working with DVBv5. Patches, suggestions, etc
are welcome.

Regards,
Mauro

             reply	other threads:[~2011-11-09 19:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 19:01 Mauro Carvalho Chehab [this message]
2011-11-10  7:08 ` DVBv5 frontend library Rémi Denis-Courmont
2011-11-10 12:05   ` Mauro Carvalho Chehab
2011-11-10 12:56     ` Andreas Oberritter

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=4EBACE27.8000907@redhat.com \
    --to=mchehab@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mkrufky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox