2.6.65 + matrox framebuffer: life is good!
Quoted 10 lines · James Simmons
Quoted 8 lines
Quoted 3 lines
Its for testing and it hasn't been fully ported over yet. Its close. I was busy fixing higher level bugs but now that most are fixed I can work on the matrox driver again.
There are still some open problems (text mode, hardware cursor), and I missed something somewhere, as czech font works only on VT1 console with mga-2.5.65 (on other VTs there is some font loaded, but character mapping looks broken). I have no idea whether it is my problem or James's...
I have tested font changing. It works.
I'll have to look into my changes then :-(
Quoted 6 lines
Quoted 3 lines
Probably worst problem currently is cursor code: it calls imgblit from interrupt context, and matroxfb's accelerated procedures are not ready to handle such thing (patch hooks cursor call much sooner for primary mga head).
Fixed now. Also I have a patch that properly fixes image.depth = 0 hack. I will post for people to test. Folks please test the code.
AFAIK you only fixed kmalloc problem. Or is cursor callback disallowed while doing imgblit/copyarea/fillrect ?
Petr Vandrovec
Quoted 10 lines
Quoted 7 lines
Quoted 4 lines
Probably worst problem currently is cursor code: it calls imgblit from interrupt context, and matroxfb's accelerated procedures are not ready to handle such thing (patch hooks cursor call much sooner for primary mga head).
Fixed now. Also I have a patch that properly fixes image.depth = 0 hack. I will post for people to test. Folks please test the code.
AFAIK you only fixed kmalloc problem. Or is cursor callback disallowed while doing imgblit/copyarea/fillrect ?
Take a look at fb_get_buffer_offset in fbmem.c and tell me if it is enough for you. I do plan to move to using a semaphore instead of a spinlock tho.