linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 13:07:17 +0100	[thread overview]
Message-ID: <CAMuHMdUUzkCzr+BG+=adMr6iU5zD6D-C=wcHJekBDN_8wL359A@mail.gmail.com> (raw)
In-Reply-To: <87eelc127t.fsf@igel.home>

Hi Andreas,

On Mon, Nov 2, 2020 at 11:29 AM Andreas Schwab <schwab@linux-m68k.org> wrote:
> On Nov 02 2020, Geert Uytterhoeven wrote:
> > But 95 MHz sounds too low to me, and doesn't match the monitor docs.
> > Given the TT runs at 32 MHz, 32 * 4 = 128 MHz sounds reasonable.
>
> Since it is not programmable, the actual value doesn't matter anyway.

It does, to implement fbdev mode rounding rules.

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

  reply	other threads:[~2020-11-02 12:07 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
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 [this message]
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='CAMuHMdUUzkCzr+BG+=adMr6iU5zD6D-C=wcHJekBDN_8wL359A@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).