From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] fbdev: Distinguish between interlaced and progressive modes
Date: Wed, 04 Jul 2018 17:07:31 +0000 [thread overview]
Message-ID: <1828178.vF6XXv5T2I@amdc3058> (raw)
In-Reply-To: <20180622183754.GB17701@localhost.localdomain>
Hi,
On Friday, June 22, 2018 08:37:54 PM Fredrik Noring wrote:
> With this change fb_find_mode can match interlaced and progressive
> modes equally well, and distinguish between for example 1920x1080i
> and 1920x1080p.
>
> Signed-off-by: Fredrik Noring <noring@nocrew.org>
Could you please give some examples of use cases that need this change
(i.e. which fbdev drivers need it for which modes etc.)?
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2018-07-04 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 18:37 [PATCH] fbdev: Distinguish between interlaced and progressive modes Fredrik Noring
2018-07-04 17:07 ` Bartlomiej Zolnierkiewicz [this message]
2018-07-04 19:08 ` Fredrik Noring
2018-07-24 14:38 ` Bartlomiej Zolnierkiewicz
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=1828178.vF6XXv5T2I@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=linux-fbdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox