RE: [PATCH 2.5.68] Epson 1355 Rewrite for 2.5

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.

All the cfb_* functions where optimized to transfer data the size of a 
unsigned long at a time across the bus. So at say 8 bpp on a 32 bit 
machine we draw 4 pixels at one time. Not only that but the code was
designed to write data on dword boundaries. So say the first pixel data 
didn't align at a dword boundary we move the data around so it would. 
Say the first pixel is at address C00001 with the size of unsigned long
at 32 at 8 bpp. The first data to be transfered across the bus would be

------------- 
|__|**|**|**|

Now you have to ask yourself what is the best requirement for my hardware.
From what you described you don't need that fancy of functions.



-------------------------------------------------------
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