From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Michael Schmitz <schmitzmic@gmail.com>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
"Linux/m68k" <linux-m68k@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH/RFC v2] video: fbdev: atari: Fix TT High video mode
Date: Mon, 2 Nov 2020 09:39:47 +0100 [thread overview]
Message-ID: <CAMuHMdUMF4R91Nt6mv9Tqz0zSaNh7AV8mghUoKL+uO-_PUH2aQ@mail.gmail.com> (raw)
In-Reply-To: <874km91by4.fsf@igel.home>
Hi Andreas,
On Sun, Nov 1, 2020 at 1:47 PM Andreas Schwab <schwab@linux-m68k.org> wrote:
> On Nov 01 2020, Sam Ravnborg wrote:
> > 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.
TBH, I spotted that 7 years ago, but never got to looking up and calculating
the other values...
> > 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.
32000 ps is 31.25 MHz. Looks like these are bogus, too, and only
the VGA and Falcon video modes are correct?
> According to the Profibuch the pixclock should be about 95000.
95 ns? That's a 10.5 MHz pixel clock? Definitely too low.
The TTM195 manual says 128.85 MHz.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2020-11-02 8:40 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
2020-11-02 8:39 ` Geert Uytterhoeven [this message]
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=CAMuHMdUMF4R91Nt6mv9Tqz0zSaNh7AV8mghUoKL+uO-_PUH2aQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=schmitzmic@gmail.com \
--cc=schwab@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).