Now
MAIN commitmail json YAML
src/sys/dev/rasops/rasops.c@1.115
/
diff
/
nxr@1.115
src/sys/dev/rasops/rasops.h@1.44 / diff / nxr@1.44
src/sys/dev/rasops/rasops15.c@1.35 / diff / nxr@1.35
src/sys/dev/rasops/rasops2.c@1.30 / diff / nxr@1.30
src/sys/dev/rasops/rasops24.c@1.47 / diff / nxr@1.47
src/sys/dev/rasops/rasops32.c@1.43 / diff / nxr@1.43
src/sys/dev/rasops/rasops4.c@1.25 / diff / nxr@1.25
src/sys/dev/rasops/rasops8.c@1.48 / diff / nxr@1.48
src/sys/dev/rasops/rasops_putchar_width.h@1.11 / diff / nxr@1.11
src/sys/dev/rasops/rasops.h@1.44 / diff / nxr@1.44
src/sys/dev/rasops/rasops15.c@1.35 / diff / nxr@1.35
src/sys/dev/rasops/rasops2.c@1.30 / diff / nxr@1.30
src/sys/dev/rasops/rasops24.c@1.47 / diff / nxr@1.47
src/sys/dev/rasops/rasops32.c@1.43 / diff / nxr@1.43
src/sys/dev/rasops/rasops4.c@1.25 / diff / nxr@1.25
src/sys/dev/rasops/rasops8.c@1.48 / diff / nxr@1.48
src/sys/dev/rasops/rasops_putchar_width.h@1.11 / diff / nxr@1.11
Stop allocating ri_buf and ri_stamp dynamically. As commented in
rasops.h, it is not safe to use kmem_alloc(9) in rasops_init();
rasops routines can be used for early putchar, which means that
UVM is not fully initialized.
Should fix a problem reported by macallan:
http://mail-index.netbsd.org/tech-kern/2019/08/02/msg025327.html
Instead of using ri_buf, inline function rasops_memcpy32() is
introduced to fill 32bit data efficiently.
Instead of using ri_stamp (per device stamp), stamp_ri is
introduced to distinguish for which device stamp is calculated.
rasops.h, it is not safe to use kmem_alloc(9) in rasops_init();
rasops routines can be used for early putchar, which means that
UVM is not fully initialized.
Should fix a problem reported by macallan:
http://mail-index.netbsd.org/tech-kern/2019/08/02/msg025327.html
Instead of using ri_buf, inline function rasops_memcpy32() is
introduced to fill 32bit data efficiently.
Instead of using ri_stamp (per device stamp), stamp_ri is
introduced to distinguish for which device stamp is calculated.