2012/9/6 Hans Verkuil hverkuil@xs4all.nl:
On Thu 6 September 2012 12:29:17 Jun Nie wrote:
2012/9/6 Hans Verkuil hverkuil@xs4all.nl:
On Thu September 6 2012 06:09:44 Jun Nie wrote:
2012/9/5 Hans Verkuil hverkuil@xs4all.nl:
On Wed 5 September 2012 10:04:41 Jun Nie wrote:
Is there any summary for this summit or presentation material? I am looking forward for some idea on CEC. It is really complex in functionality. Maybe other guys is expecting simiar fruite from summit too.
Yes, there will be a summit report. It's not quite finished yet, I think.
With respect to CEC we had some useful discussions. It will have to be a new class of device (/dev/cecX), so the userspace API will be separate from drm or v4l.
And the kernel will have to take care of the core CEC protocol w.r.t. control and discovery due to the HDMI 1.4a requirements.
I plan on starting work on this within 1-2 weeks.
My CEC presentation can be found here:
http://hverkuil.home.xs4all.nl/presentations/v4l2-workshop-cec.odp
Regards,
HansThanks for quick response! It's good to know that CEC is independent with DRM/V4L for my HDMI implementation is FB/lcd-device based. CEC is also deserved to have independent management in both hardware signal and functionality. Someone also expressed similar thoughts before. Will remote control protocal parsing are done in userspace reference library? Or not decided yet?
Are you referring to the remote control pass-through functionality? I don't know yet whether that will go through a userspace library or through the RC kernel subsystem, or possibly both.
I mean all the feature that can involved in handhold remote control, one touch play, standby, on screen display, etc, such as play/pause/poweroff. I want to mention all non CDC features that can be implemented in user space. They are hard to be covered by any sub-system and user space library is more proper. Just like your metaphor, kitchen sink for CEC. I like your words.
Yes, that will all be userspace.
My plan is to have the CEC adapter driver handle the core CEC protocol, allow other drivers to intercept messages that are relevant for them and send messages themselves, and anything that remains will be available to userspace for which a new library will be created.
Now, don't ask me about any of the details, since I don't have them yet :-) My plan is to start working on this next week or the week after.
Are you willing to test early versions of this work? Can you test HDMI 1.4a features as well? Testing this might well be one of the harder things to do.
I am willing to test or contribute to the library. But my hardware does not include HEAC. So my test scope limites to the features that can be implemented in user space.
Regards,
Hans