Lines Matching full:that
15 Please realize that this article describes the **in kernel** interfaces, not
18 The kernel to userspace interface is the one that application programs use,
19 the syscall interface. That interface is **very** stable over time, and
20 will not break. I have old programs that were built on a pre 0.9something
21 kernel that still work just fine on the latest 2.6 kernel release.
22 That interface is the one that users and application programmers can count
30 you get that only if your driver is in the main kernel tree. You also
40 It's only the odd person who wants to write a kernel driver that needs
47 that describes kernel drivers that do not have their source code
60 Assuming that we had a stable kernel source interface for the kernel, a
68 isn't that important, but the different data structure padding is
81 There is no way that binary drivers from one architecture will run
86 C compiler that the kernel was built with. This is sufficient if you
88 Linux distribution. But multiply that single build by the number of
91 different build options on different releases. Also realize that each
105 keep a Linux kernel driver that is not in the main kernel tree up to
111 that, they then fix the current interfaces to work better. When they do
115 at the same time, ensuring that everything continues to work properly.
124 increased the throughput of all USB drivers such that we are now
127 USB core by USB drivers so that all drivers now needed to provide
137 In both of these instances, all developers agreed that these were
138 important changes that needed to be made, and they were made, with
139 relatively little pain. If Linux had to ensure that it will preserve a
150 happens, all drivers that use the interfaces were also fixed at the
151 same time, ensuring that the security problem was fixed and could not
154 insuring that it could not happen again would not be possible.
157 current interface, it is deleted. This ensures that the kernel remains
158 as small as possible, and that all potential interfaces are tested as
166 So, if you have a Linux kernel driver that is not in the main kernel
177 place. This ensures that your driver is always buildable, and works over