Skip to main content

Module native_unsafe_methods

Module native_unsafe_methods 

Source
Expand description

The kernel’s structures, request numbers and codes of the framebuffer and input interfaces (the port of NativeUnsafeMethods.cs), and the system calls on files as safe functions.

The functions of the C library are those of the libc crate. The structures of linux/fb.h are declared here, since that crate does not have them; the tests at the end hold them to the kernel’s sizes.

Modules§

abs_axis
The codes of absolute axes.
axis_event_code
The codes of relative axes.
ev_key
The key codes the reference names: the buttons.
ev_type
The types of input events.
fb_io_ctl
The request numbers of the framebuffer device.
syn_code
The codes of EV_SYN events. Not in the reference, which reads events through a library that handles them.
sys
The system calls, each as a safe function.
v_blank_flags
The flags of fb_vblank.

Structs§

fb_bitfield
fb_fix_screeninfo
fb_var_screeninfo
fb_vblank
input_absinfo
input_event
An input event as the kernel writes it, with the time as two 64-bit numbers on every architecture: the value the input thread hands to the UI thread.

Constants§

IOC_READ
IOC_WRITE

Functions§

ioc
The number of an ioctl request in the encoding most architectures use (x86, ARM, RISC-V): two bits of direction, fourteen of size, eight of type and eight of number. The request numbers of the reference (FBIO_WAITFORVSYNC, FBIOGET_VBLANK) are in this encoding too.