From: Michael Schmitz <schmitzmic@gmail.com>
To: Thorsten Glaser <tg@mirbsd.de>
Cc: linux-m68k@vger.kernel.org
Subject: Re: atafb and X/fbdev
Date: Sun, 08 Jul 2012 16:38:39 +1200 [thread overview]
Message-ID: <4FF90ECF.2090001@gmail.com> (raw)
In-Reply-To: <Pine.BSM.4.64L.1207071537230.13285@herc.mirbsd.org>
Thorsten Glaser wrote:
>>> The 16-bpp Falcon mode should be chunky and work.
>>>
>> That's video=atafb:falh16 ?
>>
>
> No, that's a 4bpp mode.
>
> From my reading of drivers/video/atafb.c there are
> no 16bpp modes?
>
There is a 16 bpp mode - look for 'hicolor' in the source. From my
understanding,
it has all been wired up right (to be honest, I did only rewrite the
fbcon interface
for 2.6 onwards, and touched as little of the business end of the driver
as possible).
The driver detects hicolor mode from bit 8 of f_shift:
else if (hw->f_shift & 0x100) /* hicolor */
var->bits_per_pixel = 16;
and uses the generic packed pixel cfb interface to draw characters to
the screen in this case.
Thanks for the hint, Geert - I would have claimed there's only mono and
interleaved planes otherwise.
Nothing like a trip down memory lane - I had totally forgotten that I
wrote Mac fbcon drivers back in the days.
I feel I should give the hicolor mode a test to see whether it does
actually work after all this time.
Cheers,
Michael
next prev parent reply other threads:[~2012-07-08 4:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 23:03 atafb and X/fbdev Thorsten Glaser
2012-07-07 3:41 ` schmitz
2012-07-07 7:54 ` Thorsten Glaser
2012-07-07 8:06 ` Geert Uytterhoeven
2012-07-07 9:18 ` Thorsten Glaser
2012-07-07 15:38 ` Thorsten Glaser
2012-07-08 4:38 ` Michael Schmitz [this message]
2012-07-10 22:57 ` Michael Schmitz
2012-07-14 3:42 ` Michael Schmitz
2012-07-14 8:44 ` Geert Uytterhoeven
2012-07-15 7:12 ` Michael Schmitz
2012-07-15 8:49 ` Geert Uytterhoeven
2012-07-17 2:59 ` Michael Schmitz
2012-07-08 3:47 ` Michael Schmitz
2012-07-08 19:09 ` Christian T. Steigies
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=4FF90ECF.2090001@gmail.com \
--to=schmitzmic@gmail.com \
--cc=linux-m68k@vger.kernel.org \
--cc=tg@mirbsd.de \
/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