From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] PMAG-AA frame buffer driver rework
Date: Sat, 27 Feb 2016 22:23:09 +0000 [thread overview]
Message-ID: <alpine.LFD.2.20.1602261423120.28664@eddie.linux-mips.org> (raw)
In-Reply-To: <56D033EB.7010506@ti.com>
Hi Tomi,
> > This is an update to the PMAG-AA frame buffer driver to adapt it to our
> > current APIs, which I promised a while ago (too much of a while, which I
> > apologise for).
>
> Interesting hardware. I like the names of these things. "Monolithic CMOS
> 64 x 64 Pixel Cursor Generator", "TURBOchannel Color Frame Buffer".
Indeed, it sounds so 1980s, doesn't it? It took me a while too to figure
out how to wire it to a monitor as the adapter has a TNC connector for its
output (the colour adapters from the line have a DA-3W3 connector each
instead). Fortunately at least video signalling is standard -- EIA-343A
-- so a modern VGA monitor can be used as long as it does sync-on-green.
> Also interesting to see the git history of a file going almost directly
> to the initial git commit.
FYI, for anything beyond you'd have to get at LMO's GIT history, e.g.:
$ git blame 66f0a432564b -- drivers/video/fbdev/pmag-aa-fb.c
on a checkout from <git://git.linux-mips.org/pub/scm/ralf/linux>.
Ralf had been running his MIPS tree in CVS since forever and consequently
had a slightly more detailed history of changes than Linus had with his
master copy. When the move from BitKeeper to GIT was made Ralf was kind
enough to go through the pain and converted his CVS repository to GIT
before merging with Linus.
There are older branches there as well, namely: linux-2.4, linux-2.2, and
linux-2.0 (anything beyond these is linear on master). Most operations on
the master branch are cut through at the initial Linus's commit though,
you need to name a commit preceding that point -- such as one immediately
before, which I referred to above -- to go past.
> Thanks, queued for 4.6.
Thanks.
I've since noticed blanking will need an update to interpret VESA modes
correctly, i.e. return errors for the unsupported ones. This is a minor
issue, so I'll group it with blanking support for the other two boards
which is missing for the Bt459 RAMDAC they use. The Bt459 can switch sync
generation off, so the full powerdown mode can be supported too in
addition to plain screen blanking (obviously you can't switch individual
sync signals in a composite signal).
Cursor support for the Bt459 would be good to have too; noted as a future
enhancement possibility.
Maciej
prev parent reply other threads:[~2016-02-27 22:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 1:54 [PATCH 0/7] PMAG-AA frame buffer driver rework Maciej W. Rozycki
2016-02-22 1:54 ` [PATCH 1/7] video: fbdev: pmag-aa-fb: Adapt to current APIs Maciej W. Rozycki
2016-02-22 1:55 ` [PATCH 2/7] video: fbdev: pmag-aa-fb: Enable building as a module Maciej W. Rozycki
2016-02-22 1:55 ` [PATCH 3/7] video: fbdev: pmag-aa-fb: Report video timings Maciej W. Rozycki
2016-02-22 1:55 ` [PATCH 4/7] video: fbdev: bt455: Remove unneeded colormap helpers for cursor support Maciej W. Rozycki
2016-02-22 1:55 ` [PATCH 5/7] video: fbdev: pmag-ba-fb: Fix and rework Bt455 colormap handling Maciej W. Rozycki
2016-02-22 1:55 ` [PATCH 6/7] video: fbdev: pmag-ba-fb: Optimize Bt455 colormap addressing Maciej W. Rozycki
2016-02-22 1:55 ` [PATCH 7/7] video: fbdev: bt431: Correct cursor format control macro Maciej W. Rozycki
2016-02-26 11:15 ` [PATCH 0/7] PMAG-AA frame buffer driver rework Tomi Valkeinen
2016-02-27 22:23 ` Maciej W. Rozycki [this message]
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=alpine.LFD.2.20.1602261423120.28664@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=ralf@linux-mips.org \
--cc=tomi.valkeinen@ti.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).