From: "Martin Bugge (marbugge)" <marbugge@cisco.com>
To: "Daniel Glöckner" <daniel-gl@gmx.net>
Cc: linux-media@vger.kernel.org
Subject: Re: [RFC] HDMI-CEC proposal
Date: Wed, 02 Mar 2011 10:34:14 +0100 [thread overview]
Message-ID: <4D6E0F16.5090809@cisco.com> (raw)
In-Reply-To: <20110301233806.GA4969@minime.bse>
On 03/02/2011 12:38 AM, Daniel Glöckner wrote:
> On Tue, Mar 01, 2011 at 10:59:07AM +0100, Martin Bugge (marbugge) wrote:
>
>> CEC is a protocol that provides high-level control functions between
>> various audiovisual products.
>> It is an optional supplement to the High-Definition Multimedia
>> Interface Specification (HDMI).
>> Physical layer is a one-wire bidirectional serial bus that uses the
>> industry-standard AV.link protocol.
>>
> Apart from CEC being twice as fast as AV.link and using 3.6V
> instead of 5V, CEC does look like an extension to the frame format
> defined in EN 50157-2-2 for multiple data bytes.
>
> So, how about adding support for EN 50157-2-* messages as well?
> SCART isn't dead yet.
>
> EN 50157-2-1 is tricky in that it requires devices to override
> data bits like it is done for ack bits to announce their status.
> There is a single message type with 21 bits.
>
> For EN 50157-2-2 the only change necessary would be to tell the
> application that it has to use AV.link commands instead of CEC
> commands. In theory one could mix AV.link and CEC on a single
> wire as they can be distinguished by their start bits.
>
> EN 50157-2-3 allows 7 vendors to register their own applications
> with up to 100 data bits per message. I doubt we can support
> these if they require bits on the wire to be modified.
> As they still didn't make use of the reserved value to extend the
> application number space beyond 7, chances are no vendor ever
> applied for a number.
>
> Just my 2 cents.
>
> Daniel
>
Hi Daniel and thank you.
I haven't read these standards myself but will do so as soon as I get
hold of them.
But this sounds like a good idea since cec is based on these protocols.
I will look into it.
Regards,
Martin
next prev parent reply other threads:[~2011-03-02 9:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 9:59 [RFC] HDMI-CEC proposal Martin Bugge (marbugge)
2011-03-01 12:28 ` Mauro Carvalho Chehab
2011-03-01 14:38 ` Hans Verkuil
2011-03-01 15:20 ` Mauro Carvalho Chehab
2011-03-01 15:49 ` Hans Verkuil
2011-03-01 16:19 ` Mauro Carvalho Chehab
2011-03-01 17:09 ` Hans Verkuil
2011-03-01 13:47 ` Andy Walls
2011-03-01 14:59 ` Martin Bugge (marbugge)
2011-03-01 17:31 ` Hans Verkuil
2011-03-01 17:52 ` Alex Deucher
2011-03-02 9:13 ` Hans Verkuil
2011-03-02 15:49 ` Alex Deucher
2011-03-01 23:38 ` Daniel Glöckner
2011-03-02 9:34 ` Martin Bugge (marbugge) [this message]
2011-03-03 10:37 ` Laurent Pinchart
2011-03-03 12:11 ` Martin Bugge (marbugge)
-- strict thread matches above, loose matches on Subject: below --
2012-04-12 15:24 Florian Fainelli
2012-04-12 20:36 ` Oliver Schinagl
2012-04-13 5:03 ` Hans Verkuil
2012-04-13 9:27 ` Florian Fainelli
2012-04-17 13:31 ` Anssi Hannula
2012-04-17 13:44 ` Oliver Schinagl
[not found] <CAH-Z1=WtUrS0HYMsOb9CarAcXhR72cO8QWAnUJdP+zDuj92Rxg@mail.gmail.com>
2012-05-10 11:43 ` Florian Fainelli
2012-05-10 12:11 ` 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=4D6E0F16.5090809@cisco.com \
--to=marbugge@cisco.com \
--cc=daniel-gl@gmx.net \
--cc=linux-media@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.