From: "Morgan Collins [Ax0n]" <sirmorcant@morcant.org>
To: volodya@mindspring.com
Cc: xavier.bestel@free.fr, natedac@kscable.com,
livid-gatos@linuxvideo.org, video4linux-list@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [livid-gatos] [RFC] alternative kernel multimedia API
Date: Fri, 26 Oct 2001 09:38:23 -0700 (PDT) [thread overview]
Message-ID: <36895.24.255.76.12.1004114303.squirrel@webmail.morcant.org> (raw)
In-Reply-To: <Pine.LNX.4.20.0110260757190.10883-100000@node2.localnet.net>
In-Reply-To: <Pine.LNX.4.20.0110260757190.10883-100000@node2.localnet.net>
>
>
> 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
>
Might I suggest a single file interface then?
Say /dev/video0/config, which would hold
hue: 0
saturation: 0
brightness: 0
etc..
which one could open and read or write param: value to.
This, or with the linux wireless config tools, is how the airo module allows you to modify
card values and personally I like the simplicity of the approach.
>>
>> 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/
>>
--
Morgan Collins [Ax0n] http://sirmorcant.morcant.org
Software is something like a machine, and something like mathematics, and something like
language, and something like thought, and art, and information.... but software is not in
fact any of those other things.
next prev parent reply other threads:[~2001-10-26 16:39 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
2001-10-26 16:38 ` Morgan Collins [Ax0n] [this message]
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=36895.24.255.76.12.1004114303.squirrel@webmail.morcant.org \
--to=sirmorcant@morcant.org \
--cc=linux-kernel@vger.kernel.org \
--cc=livid-gatos@linuxvideo.org \
--cc=natedac@kscable.com \
--cc=video4linux-list@redhat.com \
--cc=volodya@mindspring.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®