Thread (11 messages) 11 messages, 3 authors, 2003-05-13

RE: [PATCH 2.5.68] Epson 1355 Rewrite for 2.5

From: James Simmons <hidden>
Date: 2003-05-13 22:33:18

quoted
I have put alot of though and even tested some raw code for this. The 
issue with just replacing the FB_WRITE and FB_READ stuff is more than one 
card could be present and each would require a different FB_WRITE. This 
would conflict. So what do we do? Ah the answer is use struct pixmap to 
It would not conflict with multiple cards, since if you set some defines and
#include the cfb* sources, you would get routines with slightly different
names, cfr. Christopher's approach.
  I have some code but I realized it is more of a challege than I thought. 
I don't see how one can nearly use the same code as in cfb*.c files for 16 
bit access since the whole idea behind the cfb*.c files is to write 32/64 
bit data at a time to the framebuffer. It would require a very different 
logic. There is just to many BITS_PER_LONG and stuff in the code. 
  At present I moved the code over to using the struct pixmap fields. In 
theory just changing the scan_align value should work. It doesn't tho :-(
Chris coudl you send me what you have tho. Just merge in your version of 
the cfb* functions into your driver for now. 
  Currently I'm trying to push a bunch to Linus. So I like to push your 
driver.
 



-------------------------------------------------------
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help