On Thu, Aug 1, 2013 at 10:29 AM, Darren Etheridge wrote:
> Sebastian Hesselbarth wrote on Wed
> [2013-Jul-31 22:21:20 +0200]:
>> Darren,
>>
>> I now fully understand the issues of AM335x's LCD controller and your
>> fix for it. I suggest to clarify the comments you added to tilcdc to
>> allow
Sebastian Hesselbarth wrote on Wed
[2013-Jul-31 22:21:20 +0200]:
> Darren,
>
> I now fully understand the issues of AM335x's LCD controller and your
> fix for it. I suggest to clarify the comments you added to tilcdc to
> allow others to understand it more quickly.
>
Sebastian,
Thanks for
Sebastian Hesselbarth sebastian.hesselba...@gmail.com wrote on Wed
[2013-Jul-31 22:21:20 +0200]:
Darren,
I now fully understand the issues of AM335x's LCD controller and your
fix for it. I suggest to clarify the comments you added to tilcdc to
allow others to understand it more quickly.
On Thu, Aug 1, 2013 at 10:29 AM, Darren Etheridge detheri...@ti.com wrote:
Sebastian Hesselbarth sebastian.hesselba...@gmail.com wrote on Wed
[2013-Jul-31 22:21:20 +0200]:
Darren,
I now fully understand the issues of AM335x's LCD controller and your
fix for it. I suggest to clarify the
On 07/25/2013 09:32 PM, Rob Clark wrote:
On Thu, Jul 25, 2013 at 2:32 PM, Darren Etheridge detheri...@ti.com wrote:
[...]
This patch set inverts the hsync signal coming from the tilcdc so the NXP
is kept happy and then shifts the output to the right to compensate for the
sync timing issues.
On Wed, Jul 31, 2013 at 10:21:20PM +0200, Sebastian Hesselbarth wrote:
Should we prepare a new patch set comprising the following patches?
Russell King:
drm/i2c: nxp-tda998x: fix EDID reading on TDA19988 devices
drm/i2c: nxp-tda998x: ensure VIP output mux is properly set
drm/i2c:
On 07/25/2013 09:32 PM, Rob Clark wrote:
> On Thu, Jul 25, 2013 at 2:32 PM, Darren Etheridge
> wrote:
[...]
>> This patch set inverts the hsync signal coming from the tilcdc so the NXP
>> is kept happy and then shifts the output to the right to compensate for the
>> sync timing issues. Display
On Wed, Jul 31, 2013 at 10:21:20PM +0200, Sebastian Hesselbarth wrote:
> Should we prepare a new patch set comprising the following patches?
>
> Russell King:
> drm/i2c: nxp-tda998x: fix EDID reading on TDA19988 devices
> drm/i2c: nxp-tda998x: ensure VIP output mux is properly set
> drm/i2c:
On 07/25/2013 09:32 PM, Rob Clark wrote:
> On Thu, Jul 25, 2013 at 2:32 PM, Darren Etheridge
> wrote:
>> Russell King and Sebastian Hasselbarth had proposed some very good changes
>> for the tda998x HDMI encoder driver. But when those changes were tested
>> on BeagleBone Black against the
On 07/25/2013 09:32 PM, Rob Clark wrote:
On Thu, Jul 25, 2013 at 2:32 PM, Darren Etheridge detheri...@ti.com wrote:
Russell King and Sebastian Hasselbarth had proposed some very good changes
for the tda998x HDMI encoder driver. But when those changes were tested
on BeagleBone Black against the
On Thu, Jul 25, 2013 at 2:32 PM, Darren Etheridge wrote:
> Russell King and Sebastian Hasselbarth had proposed some very good changes
> for the tda998x HDMI encoder driver. But when those changes were tested
> on BeagleBone Black against the tilcdc driver many modes would no longer
> display
Russell King and Sebastian Hasselbarth had proposed some very good changes
for the tda998x HDMI encoder driver. But when those changes were tested
on BeagleBone Black against the tilcdc driver many modes would no longer
display correctly. After analyzing the sync signals from the TI lcd
Russell King and Sebastian Hasselbarth had proposed some very good changes
for the tda998x HDMI encoder driver. But when those changes were tested
on BeagleBone Black against the tilcdc driver many modes would no longer
display correctly. After analyzing the sync signals from the TI lcd
On Thu, Jul 25, 2013 at 2:32 PM, Darren Etheridge detheri...@ti.com wrote:
Russell King and Sebastian Hasselbarth had proposed some very good changes
for the tda998x HDMI encoder driver. But when those changes were tested
on BeagleBone Black against the tilcdc driver many modes would no longer
14 matches
Mail list logo
