I meant make it into two separate device drivers, not just split the files.
Then the user could load base+DRI, base+FB or base+FB+DRI. This would minimize
the RAM footprint and let the DRI people avoid the problem of mapping the
framebuffer into kernel space.
Nice. That is what struct xxx_par was for. The idea was that in the future
a core could be implemented xxx_par that could be shared by both DRI and
fbdev.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf