Quoting ville.syrjala@xxxxxxxxxxxxxxx (2017-09-06 14:04:01) > From: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx> > > "echo 1 > vtconN/bind" doesn't actually do anything. Looks like the only > way to rebind fbcon is to unbind the current console. > > I suppose the failure to rebind might be a kernel bug, but I can't be > bothered to decode the vt.c spaghetti so let's just try to handle this > in igt. For simplicity let's assume the currently bound console is the > dummy console and unbind that when we want to rebind fbcon. That works > for me. > > With rebinding not working we can't really tell wich console is going > to get bound anyway, so there's no way to make this code really robust, > assuming we ever had more than these two console drivers involved. > > Signed-off-by: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx> Ok, if it works in one direction, it should work in the other... And pragmatically if it works, it works. However, I do worry if that if we have been measuring our test runtimes with never having to rebind fbcon if we suddenly get a slowdown... Reviewed-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
