DSS2 TV settings
Tomi,
I'm running your latest DSS2 tree and have some questions about the TV settings. The timings, as published, don't work all that well on our TV sets. When I display a frame buffer to the TV (using the recipe from the Documentation directory), some of the actual frame buffer does not show on the screen. In particular, if I have "tux" from the default system console framebuffer showing, the top of his head is chopped off, as is a fair amount of his left side. Further tests show that some amount of the frame buffer is not present on all margins.
Is this to be expected?
Can the timings be adjusted so that the whole frame buffer shows?
[not 100% related] The documentation says that TI is working on the V4L2 support. Do you know the status of this? where I might find it?
Thanks for your comments
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Hi,
Quoted 12 lines · ext Gary Thomas
Tomi,
I'm running your latest DSS2 tree and have some questions about the TV settings. The timings, as published, don't work all that well on our TV sets. When I display a frame buffer to the TV (using the recipe from the Documentation directory), some of the actual frame buffer does not show on the screen. In particular, if I have "tux" from the default system console framebuffer showing, the top of his head is chopped off, as is a fair amount of his left side. Further tests show that some amount of the frame buffer is not present on all margins.
Quoted 2 lines
Is this to be expected?
Can the timings be adjusted so that the whole frame buffer shows?
That is to be expected. I'm not an expert on analog TVs, but I think analog TVs always have non-visible areas. Some TVs show more of the total frame, and some show less.
You need to adjust the overlay position and size so that it's fully visible on the TV. I guess there are some sane defaults that are more or less ok for every TV out there, and omapfb could use those defaults, but I haven't really had time to study the TV out.
Quoted 4 lines
[not 100% related] The documentation says that TI is working on the V4L2 support. Do you know the status of this? where I might find it?
I cannot help you with this. There have been mails about it on linux-omap and v4l2 lists, so you could search those archives.
Tomi
Hi Thomas,
Quoted 6 lines
Quoted 3 lines
[not 100% related] The documentation says that TI is working on the V4L2 support. Do you know the status of this? where I might find it?
I cannot help you with this. There have been mails about it on linux-omap and v4l2 lists, so you could search those archives.
There is a public repository representing the V4L2 driver on the Tomi's DSS patches. Here is the link to that.
Quoted 43 lines · Tomi Valkeinen
Hi,
Quoted 12 lines · ext Gary Thomas
Tomi,
I'm running your latest DSS2 tree and have some questions about the TV settings. The timings, as published, don't work all that well on our TV sets. When I display a frame buffer to the TV (using the recipe from the Documentation directory), some of the actual frame buffer does not show on the screen. In particular, if I have "tux" from the default system console framebuffer showing, the top of his head is chopped off, as is a fair amount of his left side. Further tests show that some amount of the frame buffer is not present on all margins.
Quoted 2 lines
Is this to be expected?
Can the timings be adjusted so that the whole frame buffer shows?That is to be expected. I'm not an expert on analog TVs, but I think analog TVs always have non-visible areas. Some TVs show more of the total frame, and some show less.
You need to adjust the overlay position and size so that it's fully visible on the TV. I guess there are some sane defaults that are more or less ok for every TV out there, and omapfb could use those defaults, but I haven't really had time to study the TV out.
Quoted 4 lines
[not 100% related] The documentation says that TI is working on the V4L2 support. Do you know the status of this? where I might find it?
I cannot help you with this. There have been mails about it on linux-omap and v4l2 lists, so you could search those archives.
Tomi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 6 lines
Regards Manjunatha H -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 5 lines · halli manjunatha
Hi Thomas,
Quoted 3 lines
Quoted 3 lines
[not 100% related] The documentation says that TI is working on the V4L2 support. Do you know the status of this? where I might find it?
Quoted 8 lines
Quoted 2 lines
I cannot help you with this. There have been mails about it on linux-omap and v4l2 lists, so you could search those archives.
There is a public repository representing the V4L2 driver on the Tomi's DSS patches. Here is the link to that.
Thanks for the pointer.
Which board(s) has this been tested with (so I can look at the configs)? What are you using to test it with?
I noticed that your tree is 2.6.30-rc7, Tomi's is -rc8. There are quite a few differences (> 1MB patch file). How can I reconcile what you've changed with my working tree (which is based on Tomi's 2.6.30-rc8 tree)?
Thanks for any help
Quoted 33 lines
Quoted 31 lines · Tomi Valkeinen
Hi,
Quoted 12 lines · ext Gary Thomas
Tomi,
I'm running your latest DSS2 tree and have some questions about the TV settings. The timings, as published, don't work all that well on our TV sets. When I display a frame buffer to the TV (using the recipe from the Documentation directory), some of the actual frame buffer does not show on the screen. In particular, if I have "tux" from the default system console framebuffer showing, the top of his head is chopped off, as is a fair amount of his left side. Further tests show that some amount of the frame buffer is not present on all margins.
Quoted 2 lines
Is this to be expected?
Can the timings be adjusted so that the whole frame buffer shows?That is to be expected. I'm not an expert on analog TVs, but I think analog TVs always have non-visible areas. Some TVs show more of the total frame, and some show less.
You need to adjust the overlay position and size so that it's fully visible on the TV. I guess there are some sane defaults that are more or less ok for every TV out there, and omapfb could use those defaults, but I haven't really had time to study the TV out.
Quoted 3 lines
[not 100% related] The documentation says that TI is working on the V4L2 support. Do you know the status of this? where I might find it?
I cannot help you with this. There have been mails about it on linux-omap and v4l2 lists, so you could search those archives.
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 12 lines · Gary Thomas
Quoted 11 lines · halli manjunatha
Hi Thomas,
Quoted 5 lines
Quoted 3 lines
[not 100% related] The documentation says that TI is working on the V4L2 support. Do you know the status of this? where I might find it?
I cannot help you with this. There have been mails about it on linux-omap and v4l2 lists, so you could search those archives.
There is a public repository representing the V4L2 driver on the Tomi's DSS patches. Here is the link to that.
Quoted 7 lines
Thanks for the pointer.
Which board(s) has this been tested with (so I can look at the configs)? What are you using to test it with?
I have tested this on omap3 evm it's working fine. i just used some v4l2 test apps to test the
video output
Quoted 47 lines
I noticed that your tree is 2.6.30-rc7, Tomi's is -rc8. There are quite a few differences (> 1MB patch file). How can I reconcile what you've changed with my working tree (which is based on Tomi's 2.6.30-rc8 tree)?
Thanks for any help
Quoted 28 lines
Quoted 26 lines · Tomi Valkeinen
Hi,
Quoted 12 lines · ext Gary Thomas
Tomi,
I'm running your latest DSS2 tree and have some questions about the TV settings. The timings, as published, don't work all that well on our TV sets. When I display a frame buffer to the TV (using the recipe from the Documentation directory), some of the actual frame buffer does not show on the screen. In particular, if I have "tux" from the default system console framebuffer showing, the top of his head is chopped off, as is a fair amount of his left side. Further tests show that some amount of the frame buffer is not present on all margins.
Quoted 2 lines
Is this to be expected?
Can the timings be adjusted so that the whole frame buffer shows?That is to be expected. I'm not an expert on analog TVs, but I think analog TVs always have non-visible areas. Some TVs show more of the total frame, and some show less.
You need to adjust the overlay position and size so that it's fully visible on the TV. I guess there are some sane defaults that are more or less ok for every TV out there, and omapfb could use those defaults, but I haven't really had time to study the TV out.
Quoted 5 lines
Quoted 5 lines
Quoted 3 lines
[not 100% related] The documentation says that TI is working on the V4L2 support. Do you know the status of this? where I might find it?
I cannot help you with this. There have been mails about it on linux-omap and v4l2 lists, so you could search those archives.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
Signature · 6 lines
Regards Manjunatha H -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html