2009/6/22 Linus Torvalds <torva...@linux-foundation.org>: > > > On Mon, 22 Jun 2009, Thomas Hellström wrote: >> >> It would be very helpful if we could introduce an fbdev mutex that protects >> fbdev accesses to the kernel map and to the fbdev acceleration functions. > > Not going to happen. > > Why? 'printk'. > > If you can't handle printk, then you're basically useless. And printk > absolutely -has- to work in bad situations (the most important messages > could happen in any context).
What if we only guaranteed that the framebuffer is mapped when it's showing on the screen? printk doesn't need to write to the framebuffer immediately when X isn't running (since the framebuffer isn't shown) and presumably the framebuffer needs to be pinned somewhere when it's being displayed anyway. This would involve fbcon knowing how to buffer text to be shown later so that printk still works in interrupt context. --Andy ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
