Searched full:quite (Results 1 – 25 of 218) sorted by relevance
123456789
| /Documentation/admin-guide/ |
| D | cpu-load.rst | 21 In most cases the ``/proc/stat`` information reflects the reality quite
44 (only to be awaken quite soon)
52 will lead to quite erratic information inside ``/proc/stat``::
|
| D | reporting-issues.rst | 290 distributors are quite distant from the official Linux kernel as distributed by
294 Most of these vendor kernels are quite unsuitable for reporting issues to the
310 issue in question. Your chances are quite good if the distributor applied only
558 various issues in one report also makes it quite difficult for others to tear
600 it. Quite a few programmers for example only care for just one driver, for
753 quite a few other lists miss a way to search the archives. In those cases use a
767 or even more time can save you and others quite a lot of time and trouble.
822 quite busy then and might have no spare time to deal with issue reports. It's
823 also quite possible that one of the many changes applied during the merge
860 But you are in luck if you are using a popular Linux distribution: for quite a
[all …]
|
| /Documentation/locking/ |
| D | pi-futex.rst | 34 can see it in the kernel [which is a quite complex program in itself],
67 [this is a quite common scenario for most non-trivial RT applications],
79 mutexes involves no kernel work at all - they behave quite similarly to
114 there is no prior 'registration' of a PI-futex. [which is not quite
|
| /Documentation/devicetree/bindings/net/ |
| D | via-velocity.txt | 10 devices quite often set this data in uboot and do not provide an eeprom.
|
| /Documentation/filesystems/ |
| D | romfs.rst | 7 This is a quite dumb, read only filesystem, mainly for initial RAM
42 filesystems, like the quite large ext2fs module, which can then be
55 bytes. This is quite rare however, since most file names are longer
87 the source. This algorithm was chosen because although it's not quite
184 - Compression might be an useful feature, but memory is quite a
|
| D | ubifs.rst | 38 It should be quite obvious why UBIFS is very different to traditional
63 it possible to fit quite a lot of data to the flash.
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | binman.yaml | 14 partition. There are quite a number of binman-specific entry types, such as
|
| /Documentation/arch/arm/nwfpe/ |
| D | notes.rst | 10 registers f4-f7 to be preserved over a function call. The compiler quite
|
| /Documentation/driver-api/media/drivers/ |
| D | rkisp1.rst | 26 quite a bit of research.
|
| /Documentation/filesystems/ext4/ |
| D | about.rst | 42 Also see https://www.nongnu.org/ext2-doc/ for quite a collection of
|
| /Documentation/devicetree/bindings/iio/light/ |
| D | capella,cm3605.yaml | 15 The CM3605 is an entirely analog part. However, it requires quite a bit of
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | interface.txt | 4 quite much similar to the basic gate-clock [2], however,
|
| /Documentation/devicetree/bindings/clock/ |
| D | qcom,sdm845-dispcc.yaml | 22 # NOTE: sdm845.dtsi existed for quite some time and specified no clocks.
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-dv.rst | 85 standard correctly (unfortunately quite common for HDMI and DVI-D).
144 standard correctly (unfortunately quite common for HDMI and DVI-D).
|
| /Documentation/arch/powerpc/ |
| D | cpu_features.rst | 24 particular feature bit. This is done in quite a few places, for example
|
| /Documentation/networking/ |
| D | arcnet.rst | 51 individual chipset drivers, and the source files aren't quite so packed with
269 quite the way Linux does (actually, it doesn't multitask AT ALL) but
302 interface quite nicely with TCP/IP-based WfWg or Lan Manager
366 smaller than the Internet "requirement," so it's quite
494 It's quite fortunate that I set things up like this the first time (cough
551 which is obviously quite big.
|
| /Documentation/driver-api/media/ |
| D | v4l2-intro.rst | 22 connecting to sub-devices themselves. Some of this is quite complicated
|
| /Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 59 GFP_KERNEL allocations deep inside the allocator which are quite non-trivial
|
| /Documentation/misc-devices/ |
| D | apds990x.rst | 26 might vary quite much depending the spectrum of the light source.
|
| /Documentation/sound/soc/ |
| D | overview.rst | 17 event). These are quite common events on portable devices and often require
|
| /Documentation/sound/cards/ |
| D | bt87x.rst | 27 video data, so it's quite possible that audio recording may not work
|
| /Documentation/process/ |
| D | 8.Conclusion.rst | 42 the shelves for a while now. Still, there is quite a bit of good
|
| D | 4.Coding.rst | 144 slow execution dramatically. Inline functions, as a rule, should be quite
242 potential errors. Quite often, these warnings point to real problems.
272 There are quite a few other debugging options, some of which will be
317 problems. Quite a few "semantic patches" for the kernel have been packaged
|
| /Documentation/fb/ |
| D | tgafb.rst | 61 quite slow. Support for acceleration is being progressively integrated in
|
| /Documentation/scsi/ |
| D | FlashPoint.rst | 95 discover that the FlashPoint was not supported and would not be for quite
128 take quite a while for a usable driver to be written, especially since I'm
|
123456789