Hi, In a private communication Thomas Wood recommended the use of igt_warn() over my initial igt_debug(), since the lack of /dev/tty0 "could indicate a problem". Unfortunately I have no idea what kind of problem this could indicate outside ChromeOS. On the other hand, I'm fairly sure that systematically printing a warning on every single ChromeOS release going forward will create a "cry wolf" problem, reducing users' attention to warnings and discouraging QA from collecting them. The top priority is obviously the ability to run the tests at all - thus the current patch. But if someone can think of a silver and relatively cheap bullet that would suit all usecases then please let me/us know ASAP. Cheers, Marc Marc Herbert (1): lib/igt_kms.c: remove tests dependency on VT /dev/tty0 lib/igt_kms.c | 20 +++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) -- 1.9.3 _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
