John Baldwin ab59c4d9f1 Use MTX_SYSINIT for the VESA lock. ... vesa_init_done isn't a reliable guard for the mutex init. If vesa_configure() doesn't find valid VESA info it will not set vesa_init_done, but the lock will remain initialized. Revert r303076 and use MTX_SYSINIT to deterministically init the lock. Reviewed by: royger MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D7290		2016-07-23 14:38:09 +00:00
..
boot_font.c
creator_vt.c
creator.c	sys: use our nitems() macro when param.h is available.	2016-04-21 19:40:10 +00:00
creatorreg.h
fb_if.m
fb.c	sys: Make use of our rounddown() macro when sys/param.h is available.	2016-04-30 14:41:18 +00:00
fbd.c
fbreg.h
gallant12x22.c
gfb.h
machfb.c	sys/dev: minor spelling fixes.	2016-05-03 03:41:25 +00:00
machfbreg.h
s3_pci.c
splash_bmp.c
splash_pcx.c
splash_txt.c
splash.c	sys/dev: minor spelling fixes.	2016-05-03 03:41:25 +00:00
splashreg.h
vesa.c	Use MTX_SYSINIT for the VESA lock.	2016-07-23 14:38:09 +00:00
vesa.h
vga.c	sys/dev: minor spelling fixes.	2016-05-03 03:41:25 +00:00
vgareg.h