public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "ChaosMedia > WebDev" <webdev@chaosmedia.org>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] libdvbapi multiproto patch ?
Date: Mon, 05 May 2008 13:24:12 +0200	[thread overview]
Message-ID: <481EEE5C.1050009@chaosmedia.org> (raw)
In-Reply-To: <E1Jsvjz-000OP1-00.goga777-bk-ru@f190.mail.ru>



Igor wrote:
>
> you can see the new multiproto API in http://jusst.de/hg/multiproto/file/b5a34b6a209d/linux/include/linux/dvb/frontend.h
> You can compare it (diff) with existing frontend.h from dvb-v4l
>   
humm yeah but it seems that multiproto frontend.h just takes the whole 
regular frontend, for backward compatibility i guess, and puts its own 
declarations for the same values and its new ones at the bottom.

Not sure i need to go over it though if i can hide function calls from 
the libdvbapi using macros as it was done in other examples.

i'll probably need to update the api with missing dvb-s2 declarations, 
as the api's supposed to act as a layer between the driver and the 
application, and then update the api to access them or do it in the 
application, i don't really know..

Marc



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

      parent reply	other threads:[~2008-05-05 11:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05  7:54 [linux-dvb] libdvbapi multiproto patch ? ChaosMedia > WebDev
2008-05-05 11:00 ` Christoph Pfister
2008-05-05 11:47   ` ChaosMedia > WebDev
2008-05-07 16:39     ` Christoph Pfister
     [not found] ` <E1Jsvjz-000OP1-00.goga777-bk-ru@f190.mail.ru>
2008-05-05 11:24   ` ChaosMedia > WebDev [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=481EEE5C.1050009@chaosmedia.org \
    --to=webdev@chaosmedia.org \
    --cc=linux-dvb@linuxtv.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