From: Andreas Schwab <schwab@linux-m68k.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Michael Schmitz <schmitzmic@gmail.com>,
linux-fbdev@vger.kernel.org, linux-m68k@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH/RFC v2] video: fbdev: atari: Fix TT High video mode
Date: Sun, 01 Nov 2020 13:46:59 +0100 [thread overview]
Message-ID: <874km91by4.fsf@igel.home> (raw)
In-Reply-To: <20201101112915.GB1263673@ravnborg.org> (Sam Ravnborg's message of "Sun, 1 Nov 2020 12:29:15 +0100")
On Nov 01 2020, Sam Ravnborg wrote:
> Hi Geert.
>
> On Sun, Nov 01, 2020 at 11:29:41AM +0100, Geert Uytterhoeven wrote:
>> The horizontal resolution (640) for the TT High video mode (1280x960) is
>> definitely bogus. While fixing that, correct the timings to match the
>> TTM195 service manual.
>>
>> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
>> ---
>> Untested on actual hardware, hence the RFC.
>>
>> v2:
>> - Use correct base.
>> ---
>> drivers/video/fbdev/atafb.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/video/fbdev/atafb.c b/drivers/video/fbdev/atafb.c
>> index f253daa05d9d3872..5ecf3ec9f94cb720 100644
>> --- a/drivers/video/fbdev/atafb.c
>> +++ b/drivers/video/fbdev/atafb.c
>> @@ -495,8 +495,8 @@ static struct fb_videomode atafb_modedb[] __initdata = {
>> "tt-mid", 60, 640, 480, 31041, 120, 100, 8, 16, 140, 30,
>> 0, FB_VMODE_NONINTERLACED | FB_VMODE_YWRAP
>> }, {
>> - /* 1280x960, 29 kHz, 60 Hz (TT high) */
>> - "tt-high", 57, 640, 960, 31041, 120, 100, 8, 16, 140, 30,
>> + /* 1280x960, 72 kHz, 72 Hz (TT high) */
>> + "tt-high", 57, 1280, 960, 7761, 260, 60, 36, 4, 192, 4,
>> 0, FB_VMODE_NONINTERLACED | FB_VMODE_YWRAP
>
> Well-spotted. The change of 640 => 1280 is surely right.
> I have a harder time understanding why the change of pixclock from 31041
> to 7761 is correct. All other modes have a pixclock close to or equal
> to 32000 - so it looks strange this one is off.
According to the Profibuch the pixclock should be about 95000.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-11-01 12:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 10:29 [PATCH/RFC v2] video: fbdev: atari: Fix TT High video mode Geert Uytterhoeven
2020-11-01 11:29 ` Sam Ravnborg
2020-11-01 12:46 ` Andreas Schwab [this message]
2020-11-02 8:39 ` Geert Uytterhoeven
2020-11-02 9:38 ` Andreas Schwab
2020-11-02 10:11 ` Geert Uytterhoeven
2020-11-02 10:29 ` Andreas Schwab
2020-11-02 12:07 ` Geert Uytterhoeven
2020-11-02 9:40 ` Andreas Schwab
2020-11-02 18:52 ` Michael Schmitz
2020-11-09 8:38 ` Geert Uytterhoeven
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=874km91by4.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=schmitzmic@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).