All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tasslehoff Kjappfot <tasskjapp@gmail.com>
To: linux-omap@vger.kernel.org
Subject: Re: Patch to fix swapping of front and back porches when reading from modedb.c
Date: Wed, 08 Sep 2010 15:47:18 +0200	[thread overview]
Message-ID: <4C8793E6.4070103@gmail.com> (raw)
In-Reply-To: <AANLkTikkrkVMv0gwx6f8TRGEV8A8yCS1QRg1p7izfadF@mail.gmail.com>

  On 09/08/2010 03:38 PM, Russ Dill wrote:
> On Wed, Sep 8, 2010 at 6:39 AM, Tasslehoff Kjappfot<tasskjapp@gmail.com>  wrote:
>>
>> Hi list :-)
>>
>> I had trouble getting a standard 800x600@60Hz VGA signal to display
>> correctly on my monitors. Measuring the output showed that the front and
>> back porches were swapped both for hsync and vsync. After reading the source
>> I think I found the error in drivers/video/omap2/omapfb/omapfb-main.c. Patch
>> attached.
>>
>> http://www.xfree86.org/3.3.6/fbdev6.html shows the way it should be, but
>> todays code sets:
>>
>> hfp = left margin
>> hbp = right margin
>> vfp = upper margin
>> vbp = lower margin
>>
>> I tested a patched kernel with 800x600@60Hz on two different monitors and a
>> vga grabber, and it solved my issues.
> This looks good. Before this came up, I also thought that front porch
> meant left margin, and back porch meant margin, but margins are named
> in relation to pixel data, and porches are named in relation to sync
> pulses.
>
> You might want to add a Signed-off-by line
>
> Reviewed-by: Russ.Dill@gmail.com

Signed-off-by: tasskjapp@gmail.com


  reply	other threads:[~2010-09-08 13:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 13:39 Patch to fix swapping of front and back porches when reading from modedb.c Tasslehoff Kjappfot
2010-09-08 13:38 ` Russ Dill
2010-09-08 13:47   ` Tasslehoff Kjappfot [this message]
2010-09-09  8:28   ` Tomi Valkeinen

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=4C8793E6.4070103@gmail.com \
    --to=tasskjapp@gmail.com \
    --cc=linux-omap@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.