public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Michael Krufky <mkrufky@kernellabs.com>
Cc: VDR User <user.vdr@gmail.com>, LMML <linux-media@vger.kernel.org>
Subject: Re: Details about DVB frontend API
Date: Sat, 05 Dec 2009 15:30:28 -0200	[thread overview]
Message-ID: <4B1A98B4.3050606@infradead.org> (raw)
In-Reply-To: <37219a840912041259w499f2347he1b25c16550d671f@mail.gmail.com>

Michael Krufky wrote:
> On Fri, Dec 4, 2009 at 3:02 PM, VDR User <user.vdr@gmail.com> wrote:
> I have stated that I like Manu's proposal, but I would prefer that the
> get_property (s2api) interface were used, because it totally provides
> an interface that is sufficient for this feature.
> 
> Manu and I agree that these values should all be read at once.
> 
> I think we all (except Mauro) agree that the behavior within the
> driver should fetch all statistics at once and return it to userspace
> as a single structure with all the information as it all relates to
> each other.

You're contradicting yourself: by using S2API, the userspace API won't
be using a single structure, since S2API will break them into pairs of
attributes/values.

Nothing limits that the in-kernel API will group those values into a struct,
but the internal API should be smart enough to not return to userspace
the values that weren't requested by the call.

Cheers,
Mauro.


  reply	other threads:[~2009-12-05 17:30 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22 19:13 Details about DVB frontend API Jean Delvare
2009-10-22 19:27 ` Devin Heitmueller
2009-10-22 19:38   ` VDR User
2009-10-23 12:47   ` Jean Delvare
2009-10-22 20:10 ` Mauro Carvalho Chehab
2009-10-22 20:29   ` Manu Abraham
2009-10-23  0:12     ` Markus Rechberger
2009-10-23  1:00       ` Manu Abraham
2009-10-23 19:02     ` VDR User
2009-10-23 23:34       ` Markus Rechberger
2009-11-17 19:46     ` Mauro Carvalho Chehab
2009-11-17 19:55       ` Devin Heitmueller
2009-11-17 21:48         ` Jean Delvare
2009-11-17 22:53         ` Mauro Carvalho Chehab
2009-11-18  9:32           ` Devin Heitmueller
2009-11-18 14:04             ` Mauro Carvalho Chehab
2009-11-18 15:17               ` Devin Heitmueller
2009-11-18 15:35                 ` Michael Krufky
2009-11-18 15:35               ` Devin Heitmueller
2009-11-20  9:29       ` Manu Abraham
2009-11-20 11:37         ` Julian Scheel
2009-11-20 16:08           ` Manu Abraham
2009-11-20 23:40             ` Julian Scheel
2009-12-04 20:02               ` VDR User
2009-12-04 20:59                 ` Michael Krufky
2009-12-05 17:30                   ` Mauro Carvalho Chehab [this message]
2009-12-05 17:42                     ` Michael Krufky
2009-12-05 19:29                       ` Mauro Carvalho Chehab
2009-12-07 21:00                   ` Mauro Carvalho Chehab
2009-12-07 21:23                     ` Mauro Carvalho Chehab
2009-10-23 12:53   ` Jean Delvare
2009-10-23  5:11 ` Mike Booth
2009-10-23 15:47 ` Jean Delvare
2009-10-23 16:45   ` Michael Krufky
2009-10-24 16:31 ` David T. L. Wong
  -- strict thread matches above, loose matches on Subject: below --
2009-10-22 22:18 Hans Verkuil
2009-10-23  2:17 ` Steven Toth

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=4B1A98B4.3050606@infradead.org \
    --to=mchehab@infradead.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mkrufky@kernellabs.com \
    --cc=user.vdr@gmail.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