Lines Matching refs:that
8 realize that this article describes the _in kernel_ interfaces, not the
10 the one that application programs use, the syscall interface. That
12 programs that were built on a pre 0.9something kernel that still work
14 that users and application programmers can count on being stable.
21 you get that only if your driver is in the main kernel tree. You also
31 It's only the odd person who wants to write a kernel driver that needs
38 that describes kernel drivers that do not have their source code
51 Assuming that we had a stable kernel source interface for the kernel, a
58 isn't that important, but the different data structure padding is
68 There is no way that binary drivers from one architecture will run
73 C compiler that the kernel was built with. This is sufficient if you
75 Linux distribution. But multiply that single build by the number of
78 different build options on different releases. Also realize that each
92 keep a Linux kernel driver that is not in the main kernel tree up to
98 that, they then fix the current interfaces to work better. When they do
102 at the same time, ensuring that everything continues to work properly.
110 increased the throughput of all USB drivers such that we are now
113 USB core by USB drivers so that all drivers now needed to provide
123 In both of these instances, all developers agreed that these were
124 important changes that needed to be made, and they were made, with
125 relatively little pain. If Linux had to ensure that it will preserve a
136 happens, all drivers that use the interfaces were also fixed at the
137 same time, ensuring that the security problem was fixed and could not
140 insuring that it could not happen again would not be possible.
143 current interface, it is deleted. This ensures that the kernel remains
144 as small as possible, and that all potential interfaces are tested as
152 So, if you have a Linux kernel driver that is not in the main kernel
164 ensures that your driver is always buildable, and works over time, with