quoted

From what I understand about sysfs, you can only have one type per file,

so each field will have to be in separate files.  

Correct.

To synchronize, we can
perhaps use a file ('sync', 'lock', 'update' or whatever) which is
similar in function to fb_var_screeninfo.activate. Only when the user
writes to this file that the new settings are synchronized and we call
fb_set_var() or whatever.

This doesn't bother me. I cna live with that. Actually it is a good idea 
to do it that way. THis way if we have graphics clients we can invalidate 
them when switch the entire graphics state. The accel engine will switch 
behavior on changing the video mode.

How do you think sysfs support will be written?  Will this mean that the
framebuffer system has to register its own kobject as the top level
entry in sysfs, no?  

I think so. I haven't looked down this aveue yet. This is a latter time 
project.

This would also mean that we need something similar
for the console subsystem if it has to support additional features, ie
rotation?

I'm not to thrilled about this idea.




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf