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: Tue, 6 May 2003 12:26:57 -0700 [thread overview]
Message-ID: <004001c31405$75d5e550$7900000a@bergamot> (raw)
In-Reply-To: <Pine.LNX.4.44.0305061957430.14356-100000@phoenix.infradead.org>
> Also please don't modify the cfb_* functions. I'm familiar with the
epson
> chipsets and the 16 bit access issue. I recommend you write your own
> acceleration functions. In fact I really recommend you use the
> hardware acceleration. I know thw epson 1385 chip I worked on had
> acceleration.
I wish! Unforunately there is no hardware acceleration on the 135*5*.
Perhaps you
are thinking of the 135*6* (and later chips like the 1385 as you say).
I can cut'n'paste the necessary cfb<mumble> code into epson1355fb.c, but
I
thought that to be a worse solution. But if you'd like, I'll do exactly
that.
Please let me know. I'd want to send you an acceptable patch and get
this into
the tree asap.
-ch
mailto:ch(at)murgatroid.com
mailto:ch(at)hpl.hp.com
-------------------------------------------------------
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-06 19:27 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 [this message]
2003-05-07 5:04 ` James Simmons
2003-05-07 8:33 ` Christopher Hoover
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='004001c31405$75d5e550$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).