I had a quick look, and I'm fairly confused. That patch introduces a lot
of changes all over the place without any comment or explanation, in
code that has proven in the past to be fragile and prone to side
effects. Also, I see no explanation of the rationale for the resource
manager and it's API. At a minimum, the patch should be split into
- implementation of the resource manager with appropriate explanations
and documentation
- driver updates
I have no problem splitting the patch up into several parts. It was
addressing several problems. Plus I was doing some cleanups. Currently
we have sprite and pixmap for drawing images and the cursor. We also need
one for merging the font images for framebuffer console. I really didn't
want to add another fb_pixmap to struct fb_info. I will send some stuff
later.
Have you worked at all with the DRM folks ? We have a bad need to merge
DRM and fbdev as soon as possible and we need while doing so to impement
some kind of efficient memory manager for the card video RAM. I'm not
sure your proposal fits into this picture.
No. I haven't heard anything on this mailing list. Also I'm preparing for
a plug fest for work. So I will be gone for May 16-18. We have been
working like mad getting ready for it.
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20