#[non_exhaustive]pub enum Source {
Udev,
Kernel,
}Expand description
Where the uevents are read from.
Not a detail on the machines drmkit is for. A desktop has udevd, which applies its rules and only then republishes the event – by which point the device node exists with the right permissions. A minimal embedded init often has no udevd at all, and a monitor waiting for one to republish waits forever, so the display that was plugged in is never noticed.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.
Udev
What udevd republishes. The right answer where udevd runs.
Kernel
The kernel’s own netlink broadcast, which arrives whether or not anything else is listening.
Trait Implementations§
impl Copy for Source
impl Eq for Source
impl StructuralPartialEq for Source
Auto Trait Implementations§
impl Freeze for Source
impl RefUnwindSafe for Source
impl Send for Source
impl Sync for Source
impl Unpin for Source
impl UnsafeUnpin for Source
impl UnwindSafe for Source
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more