From: Alexander Kern <alex.kern@gmx.de>
To: James Simmons <jsimmons@infradead.org>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Framebuffer work is coming back.
Date: Tue, 13 Jan 2004 18:37:29 +0100 [thread overview]
Message-ID: <200401131837.29304.alex.kern@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0401072236030.2265-100000@phoenix.infradead.org>
Am Mittwoch, 7. Januar 2004 23:58 schrieben Sie:
> > here is a one more patch for MACH64. This is an accelerated imgblit.
>
> Nice !!! ;-) Only one problem I found when testing. If you pick the sun
> 12x22 fonts at boot up some of the fonts are distorted. Once X starts
> and you go back to the console this problem goes away completely. This
> is using a non accelerated X server.
>
> P.S
> Also I noticed that in the accelerated function you have HOST_XBPP. I like
> to give it a try for color expension. This would be cool sine this means
> we could have the 4 bpp penguin shown on any depth display!!!
I trying to investigate this problem, but found nothing. I suspect the
bytealigning of images, are they all bytealigned, 12x22 too?
Cheers Alex
P.S. 4bpp penguin on any bpp will not work! Mach64 supports only monoblit
extension, colorblit only if source and destination have the same depth.
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
prev parent reply other threads:[~2004-01-13 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 17:41 Framebuffer work is coming back James Simmons
2004-01-07 21:44 ` Alexander Kern
2004-01-07 22:58 ` James Simmons
2004-01-13 17:37 ` Alexander Kern [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=200401131837.29304.alex.kern@gmx.de \
--to=alex.kern@gmx.de \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).