From: Aivils <ai...@un...> - 2004-05-26 05:41:55
|
> Hi, > I'm looking at '[PATCH] fbdev: mode switching fix.' from > 2004/05/22 10:37:52 (it is present in 2.6.7-rc1), and I cannot > understand how these changes are supposed to work. Would you mind > explaining to me how multihead is supposed to work after these "fixes"? > > Long ago, when multihead worked, each head had its own display_fg > variable, which was pointed to by all VCs displayed on that head (through > vc's vc_display_fg pointer). All infrastructure depends on it, namely > IS_VISIBLE and CON_IS_VISIBLE. > > Now that change (without mentioning it in changelog) removed display_fg > from fb_info completely, leaving all VCs pointing to one global > master_display_fg variable. Thus turning my multihead system which could > update two screens at once into system which thinks that it has only > one visible display. > > Are there any plans to fix this behavior and restore multihead support? In abstract. Two postulats used by James Simmons 1) fbdev print inhuman graphic into hardware video memory. 2) fbcon send human friendly graphic primitives to fbdev. Your request breaks 1st postulat, because fbdev must not know console status. In practice. I think James does not have PC in his held. You keep separate kernel tree typicaly called "just another kernel hack from hundreds" :) Aivils Stoss |