Searched refs:good (Results 1 – 25 of 44) sorted by relevance
12
| /u-boot/include/ |
| A D | ata.h | 82 #define ATA_OK_STAT(stat,good,bad) (((stat)&((good)|(bad)))==(good)) argument
|
| /u-boot/scripts/coccinelle/iterators/ |
| A D | list_entry_update.cocci | 2 /// the list to the next, so it is usually not a good idea to reassign it.
|
| /u-boot/drivers/net/octeontx/ |
| A D | nicvf_queues.h | 163 u64 good; member
197 u64 good; member
|
| A D | nicvf_queues.c | 970 stats->rx.errop.good++; in nicvf_check_cqe_rx_errs()
1095 stats->tx.good++; in nicvf_check_cqe_tx_errs()
|
| /u-boot/scripts/ |
| A D | checkpatch.pl | 4519 my $good = $fix_elements[$n] . $fix_elements[$n + 1];
4581 $good = $fix_elements[$n] . trim($fix_elements[$n + 1]) . " ";
4599 $good = rtrim($fix_elements[$n]) . trim($fix_elements[$n + 1]);
4628 $good = rtrim($fix_elements[$n]) . trim($fix_elements[$n + 1]);
4630 $good = $fix_elements[$n] . trim($fix_elements[$n + 1]);
4633 $good .= " ";
4662 $good = $fix_elements[$n] . rtrim($fix_elements[$n + 1]);
4675 $good = $fix_elements[$n] . trim($fix_elements[$n + 1]) . " ";
4683 $good = rtrim($fix_elements[$n]) . trim($fix_elements[$n + 1]);
4690 $good = $fix_elements[$n] . trim($fix_elements[$n + 1]);
[all …]
|
| A D | Kbuild.include | 298 # This is a good hint that there is a bug in the kbuild file
|
| /u-boot/doc/driver-model/ |
| A D | serial-howto.rst | 37 This may be a good time to move your board to use device tree also. Mostly
|
| A D | i2c-howto.rst | 47 This may be a good time to move your board to use device tree also. Mostly
|
| /u-boot/net/ |
| A D | Kconfig | 64 1468 (MTU minus eth.hdrs) provides a good throughput with
|
| /u-boot/test/ |
| A D | Kconfig | 78 this is a good place to start.
|
| /u-boot/doc/ |
| A D | README.autoboot | 29 and waits forever for a command. That's a good thing if you pressed a
32 It's not so good if the key press was a stray character on the
|
| A D | README.ubi | 62 UBI: number of good PEBs: 8
126 UBI: number of good PEBs: 8
|
| A D | README.update | 82 file is a good, working image. Also make sure that the address in Flash
|
| A D | README.memory-test | 5 be a good idea to always test if the memory is working correctly,
|
| A D | README.generic-board | 88 I think it is a good target for this series. On the other hand, x86 is
|
| A D | README.chromium | 90 Breakpoints can be set in any U-Boot phase. Overall this is a good debugging
|
| /u-boot/arch/arm/lib/ |
| A D | vectors.S | 206 @ !!!! R8 NEEDS to be saved !!!! a reserved stack spot would be good.
|
| /u-boot/doc/develop/ |
| A D | testing.rst | 75 if other changes interact with it. A good mindset is that untested code
|
| /u-boot/arch/arm/dts/ |
| A D | tegra124-nyan.dtsi | 355 nvidia,cpu-pwr-good-time = <500>;
357 nvidia,core-pwr-good-time = <641 3845>;
|
| A D | tegra20-paz00.dts | 470 nvidia,cpu-pwr-good-time = <2000>;
472 nvidia,core-pwr-good-time = <3845 3845>;
|
| A D | tegra20-ventana.dts | 544 nvidia,cpu-pwr-good-time = <2000>;
546 nvidia,core-pwr-good-time = <3845 3845>;
|
| A D | tegra20-harmony.dts | 595 nvidia,cpu-pwr-good-time = <5000>;
597 nvidia,core-pwr-good-time = <3845 3845>;
|
| A D | tegra20-seaboard.dts | 729 nvidia,cpu-pwr-good-time = <5000>;
731 nvidia,core-pwr-good-time = <3845 3845>;
|
| /u-boot/examples/standalone/ |
| A D | README.smc91111_eeprom | 47 it is not a good idea to start doing things on the network before the
|
| /u-boot/doc/imx/common/ |
| A D | mxs.txt | 231 II) The NAND was already written with a good BCB
|
Completed in 71 milliseconds
12