Home
last modified time | relevance | path

Searched full:very (Results 1 – 25 of 2616) sorted by relevance

12345678910>>...105

/openbmc/linux/net/mac80211/
H A DKconfig170 very verbose OCB debugging messages. It should not
181 very verbose IBSS debugging messages. It should not
191 Selecting this option causes mac80211 to print out very
204 Selecting this option causes mac80211 to print out very
217 Selecting this option causes mac80211 to print out very
230 Selecting this option causes mac80211 to print out very
243 Selecting this option causes mac80211 to print out very verbose mesh
254 Selecting this option causes mac80211 to print out very verbose mesh
265 Selecting this option causes mac80211 to print out very verbose mesh
275 Selecting this option causes mac80211 to print out very
[all …]
/openbmc/linux/drivers/misc/echo/
H A Decho.h40 things like modem line equalisers and line echo cancellers. There it works very
42 very poorly for things like speech echo cancellation, where the signal level
53 the NLMS algorithm works very well. However, speech has more low frequency than
56 final residual signal is not heavily biased towards high frequencies. A very
70 noise like, such as voice) the adaption works very well. If the adaption is
94 energy is that we must do this very quickly. Given a reasonably long sample of
99 needed which produces a fairly accurate result from a very short burst of far
/openbmc/linux/Documentation/devicetree/bindings/i2c/
H A Dnvidia,tegra20-i2c.yaml28 Tegra30 has 5 generic I2C controller. This controller is very much
39 Tegra114 has 5 generic I2C controllers. This controller is very much
52 Tegra124 has 6 generic I2C controllers. These controllers are very
57 Tegra210 has 6 generic I2C controllers. These controllers are very
73 (always-on) partition of the SoC. All of these controllers are very
78 (always-on) partition of the SoC. All of these controllers are very
/openbmc/linux/Documentation/virt/
H A Dparavirt_ops.rst25 known that the overhead of indirect call isn't very important.
30 very important.
35 them are very performance critical.
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/ipvsadm/ipvsadm/
H A D0003-ipvsadm-remove-dependency-on-bash.patch6 The save/restore scripts are very simple and don't depend on any BASH
26 # A very simple wrapper to restore IPVS rules
36 # A very simple wrapper to save IPVS rules
/openbmc/linux/Documentation/accounting/
H A Dcgroupstats.rst11 and attributes specific to cgroups. It should be very easy to
16 statistics on interesting events), should be very easy to add. Currently
25 To extract cgroup statistics a utility very similar to getdelays.c
/openbmc/linux/drivers/mtd/maps/
H A DKconfig168 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
208 BE VERY CAREFUL.
217 BE VERY CAREFUL.
226 BE VERY CAREFUL.
235 BE VERY CAREFUL.
244 BE VERY CAREFUL.
271 BE VERY CAREFUL.
/openbmc/linux/drivers/hid/
H A Dhid-holtekff.c43 * 1: very strong rumble
45 * 3: very strong rumble
51 * 9: very strong rumble
53 * b: very strong periodic rumble, very short intervals
/openbmc/linux/Documentation/process/
H A Dstable-api-nonsense.rst19 the syscall interface. That interface is **very** stable over time, and
69 very important.
146 Security issues are also very important for Linux. When a
147 security issue is found, it is fixed in a very short amount of time. A
178 time, with very little effort on your part.
180 The very good side effects of having your driver in the main kernel tree
/openbmc/u-boot/include/
H A Dlinker_lists.h112 * This function returns ``(_type *)`` pointer to the very first entry of a
138 * This function returns ``(_type *)`` pointer after the very last entry of
217 * This function returns ``(_type *)`` pointer to the very first entry of
218 * the very first linker-generated array.
240 * This function returns ``(_type *)`` pointer after the very last entry of
241 * the very last linker-generated array.
/openbmc/u-boot/doc/
H A DREADME.memory-test15 very fast, so running it for each reboot does not hurt. It is a
45 used for the exception vectors (usually at the very lower end of
47 these are usually at the very upper end of system memory). But
48 experience has shown that a very large number of ports use
H A DREADME.i2c15 minimal overhead and involves very little code. The scheme can survive
59 scheme works very nicely with very low contention. There is only a 10 us
/openbmc/linux/drivers/staging/vc04_services/interface/
H A DTODO34 kthreads, userspace, limitations) could be very helpful for reviewers.
38 There is a heavy use of memory barriers in this driver, it would be very
46 indentation deep making it very unpleasant to read. This is specially relevant
/openbmc/linux/Documentation/arch/ia64/
H A Defirtc.rst26 The original ideas was to provide a very simple driver to get access to,
32 the CMOS clock, we decided to expose an API that was very similar to the one
41 expose this new way of representing time. Instead we use something very
107 i.e. reboot. This is very different from the alarm provided by the legacy
/openbmc/linux/tools/power/cpupower/man/
H A Dcpupower-idle-info.126 statistics when it enters or leaves an idle state, therefore on a very idle or
27 a very busy system, these statistics may not be accurate. They still provide a
50 very soon and entering any real hardware idle state may result in a slight
/openbmc/qemu/tests/qemu-iotests/
H A D261.out19 Unknown extra data: very important data
44 Unknown extra data: very important data
79 Unknown extra data: very important data
106 Unknown extra data: very important data
134 Unknown extra data: very important data
178 Unknown extra data: very important data
/openbmc/u-boot/board/sbc8349/
H A DREADME34 two copies of U-Boot in flash; one at the very beginning, which set
35 the HRCW, and one at the very end, which was the image that was run.
77 This procedure is very similar to other boards that have U-Boot installed.
103 reason for choosing to not enable PCI would be if you had a very
/openbmc/linux/Documentation/fb/
H A Dudlfb.rst18 does not require any acks - the effect is very low latency that
23 setting is very flexible - able to set nearly arbitrary modes from any timing.
128 Enabled by default. Only disable on very low memory systems.
164 roll over very quickly. To get reliable results, design
165 performance tests to start and finish in a very short
/openbmc/openbmc/poky/meta/recipes-support/re2c/
H A Dre2c_4.0.1.bb1 SUMMARY = "Tool for writing very fast and very flexible scanners"
/openbmc/u-boot/arch/x86/cpu/ivybridge/
H A DKconfig55 emulation (which would be very slow).
60 will be unable to support virtualisation, or it will run very
/openbmc/linux/Documentation/locking/
H A Dpercpu-rw-semaphore.rst13 Locking for reading is very fast, it uses RCU and it avoids any atomic
15 writing is very expensive, it calls synchronize_rcu() that can take
/openbmc/linux/arch/powerpc/include/asm/
H A Dperf_event_fsl_emb.h31 * This isn't a very flexible method of expressing constraints,
32 * but it's very simple and is adequate for existing chips.
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/vsftpd/files/
H A Dinit6 # Short-Description: Very Secure Ftp Daemon
7 # Description: vsftpd is a Very Secure FTP daemon. It was written completely from
/openbmc/u-boot/arch/arm/mach-tegra/tegra124/
H A DKconfig26 The Colorado Engineering Tegra TK1-SOM is a very compact
36 Nyan Big is a Tegra124 clamshell board that is very similar
/openbmc/linux/include/linux/
H A Dedd.h11 * very similar to D1484 Revision 3 http://www.t13.org/docs2002/d1484r3.pdf
19 * is very sensitive to the size of these structures.

12345678910>>...105