Home
last modified time | relevance | path

Searched refs:good (Results 1 – 25 of 106) sorted by relevance

12345

/f-stack/freebsd/netgraph/bluetooth/l2cap/
H A DTODO21 Resource manager is not good because it uses MTX_DEF mutexes,
34 L2CAP can support about 65000 channels. Need define some good way
37 to pass 65Mbytes of data from kernel to user space. Not good.
/f-stack/tools/libxo/tests/core/saved/
H A Dtest_02.T.out6 close -1 returned Bad file descriptor good
7 close -1 returned Bad fi good
H A Dtest_02.JP.out12 "test": "good",
15 "test": "good",
H A Dtest_02.J.out1 …"abcdef","fd":-1,"error":"Bad file descriptor","test":"good","fd":-1,"error":"Bad fi","test":"good…
H A Dtest_02.X.out4 …fd>-1</fd><error>Bad file descriptor</error><test>good</test><fd>-1</fd><error>Bad fi</error><test…
H A Dtest_02.E.out12 op string: [test] [good] [0]
15 op string: [test] [good] [0]
H A Dtest_02.XP.out17 <test>good</test>
20 <test>good</test>
/f-stack/freebsd/contrib/device-tree/Bindings/arm/tegra/
H A Dnvidia,tegra20-pmc.yaml82 nvidia,cpu-pwr-good-en:
85 CPU power good signal from external PMIC to PMC is enabled.
96 nvidia,cpu-pwr-good-time:
98 description: CPU power good time in uSec.
104 nvidia,core-pwr-good-time:
108 Core power good time in uSec.
313 "nvidia,core-pwr-off-time": ["nvidia,core-pwr-good-time"]
314 "nvidia,cpu-pwr-off-time": ["nvidia,cpu-pwr-good-time"]
332 nvidia,cpu-pwr-good-time = <0>;
334 nvidia,core-pwr-good-time = <4587 3876>;
/f-stack/freebsd/mips/conf/
H A DDIR-825B1.hints97 # usb tested good
107 # blue power tested good
112 # wps tested good
117 # orage globe tested good
/f-stack/dpdk/devtools/
H A Dcheck-git-log.sh184 good="Fixes: $hash "$(git log --format='("%s")' -1 $hash 2>&-)
186 good="reference not in current branch"
188 printf "$fixtag" | grep -v "^$good$"
/f-stack/dpdk/doc/guides/sample_app_ug/
H A Dintro.rst33 programming framework a good place to start is with the Hello World
37 good way to test if the DPDK environment is compiled and set up properly.
82 example. This is also a good example of an application using the DPDK
/f-stack/app/redis-5.0.5/utils/graphs/commits-over-time/
H A DREADME.md11 The generated HTML is quite broken but good enough to grab a screenshot
/f-stack/freebsd/contrib/openzfs/module/zfs/
H A Dzfs_fm.c786 const uint64_t *good; in annotate_ecksum() local
839 good = (const uint64_t *) abd_borrow_buf_copy((abd_t *)goodabd, size); in annotate_ecksum()
844 if (good[idx] == bad[idx]) { in annotate_ecksum()
871 abd_return_buf((abd_t *)goodabd, (void *)good, size); in annotate_ecksum()
889 set = ((~good[idx]) & bad[idx]); in annotate_ecksum()
891 cleared = (good[idx] & (~bad[idx])); in annotate_ecksum()
914 abd_return_buf((abd_t *)goodabd, (void *)good, size); in annotate_ecksum()
/f-stack/freebsd/contrib/device-tree/Bindings/mtd/
H A Dlpc32xx-mlc.txt11 Hz, to make them independent of actual clock speed and to provide for good
/f-stack/dpdk/doc/guides/prog_guide/
H A Dbuild_app.rst45 The default makefile provided with the Hello World sample application is a good starting point.
/f-stack/freebsd/contrib/device-tree/Bindings/pinctrl/
H A Dmarvell,dove-pinctrl.txt70 core-pwr-good Pin is used for CORE_PWR_GOOD (Pins 0-7 only)
71 cpu-pwr-good Pin is used for CPU_PWR_GOOD (Pins 8-15 only)
/f-stack/freebsd/contrib/device-tree/src/arm64/nvidia/
H A Dtegra210-p2180.dtsi287 nvidia,cpu-pwr-good-time = <0>;
289 nvidia,core-pwr-good-time = <4587 3876>;
/f-stack/freebsd/contrib/device-tree/Bindings/
H A DABI.rst23 1) Maintainers, don't let perfect be the enemy of good. Don't hold up a
/f-stack/freebsd/contrib/device-tree/src/arm/
H A Dtegra20-trimslice.dts319 nvidia,cpu-pwr-good-time = <5000>;
321 nvidia,core-pwr-good-time = <3845 3845>;
H A Dtegra20-tamonten.dtsi475 nvidia,cpu-pwr-good-time = <5000>;
477 nvidia,core-pwr-good-time = <3845 3845>;
/f-stack/freebsd/contrib/device-tree/Bindings/pci/
H A Ddesignware-pcie.txt30 - reset-gpio: GPIO pin number of power good signal
/f-stack/freebsd/contrib/openzfs/etc/init.d/
H A DREADME.md6 And it is a good one.
/f-stack/freebsd/contrib/zstd/
H A DCONTRIBUTING.md82 * Write a good pull request description:
132 …t additional static analyzers once in a while (and we do), but it's not a good idea to multiply th…
135 - A good CI policy is "zero-warning tolerance". That means that all issues must be solved, includin…
174 is a good place to start.
207 and then hand picking a good threshold after which the variance in results seems to stabilize.
224 4. Use a profiler with a good high resolution timer. See the section below on profiling for
268 Say you have an idea for a change that you think will provide some good performance gains
/f-stack/freebsd/contrib/device-tree/Bindings/mmc/
H A Dfsl-imx-esdhc.txt32 to select a proper data sampling window in case the clock quality is not good
/f-stack/freebsd/contrib/device-tree/Bindings/ptp/
H A Dptp-qoriq.txt30 Here is how to figure good values:

12345