From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@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, 02 Nov 2020 11:29:26 +0100 [thread overview]
Message-ID: <87eelc127t.fsf@igel.home> (raw)
In-Reply-To: <CAMuHMdX4dferHsLJ_z7GOC3R=LxZMKUBvhE-ff+jtw2H8x2MtQ@mail.gmail.com> (Geert Uytterhoeven's message of "Mon, 2 Nov 2020 11:11:39 +0100")
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.
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."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michael Schmitz <schmitzmic@gmail.com>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.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, 02 Nov 2020 11:29:26 +0100 [thread overview]
Message-ID: <87eelc127t.fsf@igel.home> (raw)
In-Reply-To: <CAMuHMdX4dferHsLJ_z7GOC3R=LxZMKUBvhE-ff+jtw2H8x2MtQ@mail.gmail.com> (Geert Uytterhoeven's message of "Mon, 2 Nov 2020 11:11:39 +0100")
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.
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."
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-11-02 10:29 UTC|newest]
Thread overview: 22+ 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 10:29 ` Geert Uytterhoeven
2020-11-01 11:29 ` Sam Ravnborg
2020-11-01 11:29 ` Sam Ravnborg
2020-11-01 12:46 ` Andreas Schwab
2020-11-01 12:46 ` Andreas Schwab
2020-11-02 8:39 ` Geert Uytterhoeven
2020-11-02 8:39 ` Geert Uytterhoeven
2020-11-02 9:38 ` Andreas Schwab
2020-11-02 9:38 ` Andreas Schwab
2020-11-02 10:11 ` Geert Uytterhoeven
2020-11-02 10:11 ` Geert Uytterhoeven
2020-11-02 10:29 ` Andreas Schwab [this message]
2020-11-02 10:29 ` Andreas Schwab
2020-11-02 12:07 ` Geert Uytterhoeven
2020-11-02 12:07 ` Geert Uytterhoeven
2020-11-02 9:40 ` Andreas Schwab
2020-11-02 9:40 ` Andreas Schwab
2020-11-02 18:52 ` Michael Schmitz
2020-11-02 18:52 ` Michael Schmitz
2020-11-09 8:38 ` Geert Uytterhoeven
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=87eelc127t.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 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.