Lines Matching refs:kernel

1 Rules on how to access information in the Linux kernel sysfs
3 The kernel-exported sysfs exports internal kernel implementation details
4 and depends on internal kernel structures and layout. It is agreed upon
5 by the kernel developers that the Linux kernel does not provide a stable
7 may not be stable across kernel releases.
10 low-level userspace applications, with a new kernel release, the users
22   offer any abstraction, it exposes all the kernel driver-core
26   current kernel development. The goal of providing a stable interface
41   kernel implementation details which should not be expected by
46       - identical to the DEVPATH value in the event sent from the kernel
49       - the kernel's path to the device directory without the leading
55         kernel used at event time.
59     o kernel name (sda, tty, 0000:00:1f.2, ...)
84   Everything else is just a kernel driver-core implementation detail
85   that should not be assumed to be stable across kernel releases.
117   places, as the kernel is free to move a subsystem from one place to
132 - "device"-link and <subsystem>:<kernel name>-links
158   or the chain of parent devices. The kernel is free to insert devices into
167   the error handling implementation within the kernel.