From: "Martin Bugge (marbugge)" <marbugge@cisco.com>
To: Soby Mathew <soby.mathew@st.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Preliminary proposal, new APIs for HDMI and DVI control in v4l2
Date: Wed, 30 May 2012 13:13:27 +0200 [thread overview]
Message-ID: <4FC600D7.1020203@cisco.com> (raw)
In-Reply-To: <loom.20120527T192755-466@post.gmane.org>
Hi Soby
On 05/27/2012 07:30 PM, Soby Mathew wrote:
> Martin Bugge (marbugge<marbugge<at> cisco.com> writes:
>
>>
>> This is a preliminary proposal for an extension to the v4l2 api.
>> To be discussed at the V4L2 'brainstorming' meeting in Warsaw, March 2011
>>
>> Purpose: Provide basic controls for HDMI and DVI devices.
>>
>>
> reposting the query since the earlier post did not appear in mailing list.
>
> Hi Martin,
> We are also in requirement of these controls as described by you. I did a
> search in the archives but could not find a suitable conclusion to the RFC. I
> could find that the dv_timings structure has been modified as a result of
> further discussions. But for many items like S_EDID, DV_CABLE_DETECT, Info
> frames etc , I could not find the logical conclusion to this RFC. Could please
> let me know the further updates on these requirements?
It has been on hold for a very long time, but just last week Hans
Verkuil posted a RFC
which is a follow up on this subject.
http://www.spinics.net/lists/linux-media/msg47671.html
So that thread has taken over.
>
>
> Thanks in Advance
> Best Regards
> Soby Mathew
>
Best regards
Martin Bugge
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-05-30 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 16:30 Preliminary proposal, new APIs for HDMI and DVI control in v4l2 Martin Bugge (marbugge)
2012-05-27 17:30 ` Soby Mathew
2012-05-30 11:13 ` Martin Bugge (marbugge) [this message]
2012-05-30 12:10 ` Hans Verkuil
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=4FC600D7.1020203@cisco.com \
--to=marbugge@cisco.com \
--cc=linux-media@vger.kernel.org \
--cc=soby.mathew@st.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