On Wed, Feb 22, 2012 at 10:36 AM, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote: > On Wed, 22 Feb 2012 17:24:24 +0100, Daniel Vetter <daniel@xxxxxxxx> wrote: >> On Wed, Feb 22, 2012 at 04:03:21PM +0000, James Simmons wrote: >> > Fbcon scrolling at be painful at HD or better modes. Fbcon needs 3 >> > possible accels; copyarea, imageblit, and fillrect. The first two could be >> > hooked from the TTM layer. Its something I plan to experiment to see if >> > its worth it. >> >> Let's bite into this ;-) I know that fbcon scrolling totally sucks on big >> screens, but I also think it's a total waste of time to fix this. Imo >> fbcon has 2 use-cases: >> - display an OOSP. >> - allow me to run fsck (or any other desaster-recovery stuff). > 3. Show panics. > > Ensuring that nothing prevents the switch to fbcon and displaying the > panic message is the reason why we haven't felt inclined to accelerate > fbcon - it just gets messy for no real gain. and when doing 2d accel on a 3d core.. it basically amounts to putting a shader compiler in the kernel. Wheeee! > For example: https://bugs.freedesktop.org/attachment.cgi?id=48933 > which doesn't handle flushing of pending updates via the GPU when > writing with the CPU during interrupts (i.e. a panic). > -Chris > > -- > Chris Wilson, Intel Open Source Technology Centre _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
