quoted

http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz

quoted

[off-list ref] (03/09/17 1.1267.40.1)
   Add new API framebuffer_alloc and framebuffer_release.
   
   Framebuffer info structure (ie. struct fb_info) must be obtained from
   framebuffer_alloc. When it is no longer needed (after unregister_framebuffer
   and clean up) it can be released using framebuffer_release.
   
   If the framebuffer is not registered yet (eg. on error path) then fb_info must
   be released via kfree. 

Are we sure that we want this for 2.6? Greg KH has a much less intrusive
patch, maybe you should take that instead and keep my work 2.7.

If you decide to go with framebuffer_alloc then I have more patches for
you ;)

I have been using it for awhile on various cards. 




-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html