From: "Christopher Hoover" <ch@murgatroid.com>
To: 'James Simmons' <jsimmons@infradead.org>
Cc: geert@linux-m68k.org, linux-fbdev-devel@lists.sourceforge.net
Subject: RE: [PATCH 2.5.68] Epson 1355 Rewrite for 2.5
Date: Wed, 7 May 2003 01:33:05 -0700 [thread overview]
Message-ID: <006801c31473$47bd51d0$7900000a@bergamot> (raw)
In-Reply-To: <Pine.LNX.4.44.0305070546590.2974-100000@phoenix.infradead.org>
The cfb generic code works wonderfully well on the EP7212 CPU/EPSON 1355
because the processor can do the math in 32-bits just fine, it just
needs to issue 16-bit reads and writes to the framebuffer memory. Since
you had that nice FB{READ|WRITE} abstraction in there, it was easy to
make a small tweak to be able to use my own FB{READ|WRITE} routines that
break each (aligned) FB{READ|WRITE} into two 16-bit reads/writes.
That's all that has to happen. I inlined the speical fb{read|write}
routines and got good code with decent performance.
What I'm hearing is that you woud prefer that I include my own routines
over the pre-processor hackery. Be warned that it is mostly going to be
a cut-n-paste job -- even if I wrote the routines totally from scratch I
would handle 32-bits of pixel(s) at a time.
I shall plow forward ...
-ch
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
next prev parent reply other threads:[~2003-05-07 8:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 21:04 [PATCH 2.5.68] Epson 1355 Rewrite for 2.5 Christopher Hoover
2003-05-02 9:27 ` Geert Uytterhoeven
2003-05-06 19:03 ` James Simmons
2003-05-06 19:26 ` Christopher Hoover
2003-05-07 5:04 ` James Simmons
2003-05-07 8:33 ` Christopher Hoover [this message]
2003-05-07 8:54 ` Geert Uytterhoeven
2003-05-07 21:57 ` James Simmons
2003-05-07 23:10 ` Christopher Hoover
2003-05-08 5:33 ` Geert Uytterhoeven
2003-05-13 22:32 ` James Simmons
2003-05-14 1:31 ` Christopher Hoover
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='006801c31473$47bd51d0$7900000a@bergamot' \
--to=ch@murgatroid.com \
--cc=geert@linux-m68k.org \
--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).