From: volodya@mindspring.com
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: Nate Dannenberg <natedac@kscable.com>,
livid-gatos@linuxvideo.org, video4linux-list@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [livid-gatos] [RFC] alternative kernel multimedia API
Date: Fri, 26 Oct 2001 07:58:48 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.20.0110260757190.10883-100000@node2.localnet.net> (raw)
In-Reply-To: <1004092530.10130.145.camel@nomade>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1042 bytes --]
On 26 Oct 2001, Xavier Bestel wrote:
> le ven 26-10-2001 à 01:14, volodya@mindspring.com a écrit :
>
> > > 05,HUE=7\n
> > > 07,some unrelated command
> > > +05\n # The HUE command was successful
> > > :07,reply to unrelated command
> > > :05,HUE=6\n # Driver reported the HUE parameter as
>
> I would prefer a proc-like interface to devices, e.g.:
>
> /dev/video0/hue
> /dev/video0/saturation
> ...
>
> more unix-like, no parsing involved.
This would be a problem as an application would need to open many files in
order to operate such interface. Additionally, you underestimate the
number of files needed. We'll need hue_range, hue_label, hue_comment and
something else..
Parsing is not that hard I believe.
Vladimir Dergachev
>
> Xav
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2001-10-26 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 17:06 volodya
2001-10-25 20:51 ` [livid-gatos] " Nate Dannenberg
2001-10-25 23:14 ` volodya
2001-10-26 10:35 ` Xavier Bestel
2001-10-26 11:58 ` volodya [this message]
2001-10-26 16:38 ` Morgan Collins [Ax0n]
2001-10-26 13:32 ` Pavel Machek
2001-10-27 1:04 ` [livid-gatos] " Mark Whitis
2001-10-27 4:06 ` volodya
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=Pine.LNX.4.20.0110260757190.10883-100000@node2.localnet.net \
--to=volodya@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=livid-gatos@linuxvideo.org \
--cc=natedac@kscable.com \
--cc=video4linux-list@redhat.com \
--cc=xavier.bestel@free.fr \
/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
all inboxes | Powered by JetHome®