Searched refs:guess (Results 1 – 25 of 44) sorted by relevance
12
/Linux-v4.19/net/atm/ |
D | atm_misc.c | 30 int guess = SKB_TRUESIZE(pdu_size); in atm_alloc_charge() local 32 atm_force_charge(vcc, guess); in atm_alloc_charge() 37 atomic_add(skb->truesize-guess, in atm_alloc_charge() 42 atm_return(vcc, guess); in atm_alloc_charge()
|
/Linux-v4.19/drivers/char/ |
D | rtc.c | 854 char *guess = NULL; in rtc_init() local 986 guess = "SRM (post-2000)"; in rtc_init() 989 guess = "ARC console"; in rtc_init() 992 guess = "Digital UNIX"; in rtc_init() 996 guess = "Digital DECstation"; in rtc_init() 1000 guess = "Standard PC (1900)"; in rtc_init() 1003 if (guess) in rtc_init() 1005 guess, epoch); in rtc_init()
|
/Linux-v4.19/Documentation/fb/ |
D | pvr2fb.txt | 51 composite. If none is specified, we guess. 54 vga. If none is specified, we guess.
|
D | api.txt | 189 __u32 bits_per_pixel; /* guess what */
|
/Linux-v4.19/tools/usb/usbip/ |
D | .gitignore | 6 config.guess
|
D | INSTALL | 18 The `configure' shell script attempts to guess correct values for 148 message saying it cannot guess the machine type, give it the
|
/Linux-v4.19/arch/arm/include/debug/ |
D | vexpress.S | 28 @ Make an educated guess regarding the memory map:
|
/Linux-v4.19/Documentation/scsi/ |
D | sym53c500_cs.txt | 20 version of this driver, and I guess it worked for those users. It worked
|
/Linux-v4.19/Documentation/media/uapi/mediactl/ |
D | media-controller-intro.rst | 29 increasingly high number of those parameters, drivers need to guess what
|
/Linux-v4.19/Documentation/block/ |
D | queue-sysfs.txt | 62 to make an educated guess at when the IO will complete. Based on this 63 guess, the kernel will put the process issuing IO to sleep for an amount
|
/Linux-v4.19/Documentation/misc-devices/ |
D | eeprom | 66 specification, so it is guess work and far from being complete.
|
/Linux-v4.19/Documentation/w1/masters/ |
D | ds2490 | 66 host did not explain the problem. My guess is a bug in either qemu
|
/Linux-v4.19/arch/arm/boot/dts/ |
D | sun6i-reference-design-tablet.dtsi | 120 regulator-name = "vdd-cpus"; /* This is an educated guess */
|
D | sun6i-a31-m9.dts | 162 regulator-name = "vdd-cpus"; /* This is an educated guess */
|
D | sun6i-a31-mele-a1000g-quad.dts | 162 regulator-name = "vdd-cpus"; /* This is an educated guess */
|
D | sun6i-a31s-primo81.dts | 209 regulator-name = "vdd-cpus"; /* This is an educated guess */
|
D | gemini-dlink-dir-685.dts | 299 * I guess).
|
/Linux-v4.19/Documentation/i2c/ |
D | DMA-considerations | 15 around 8 bytes (as of today, this is mostly an educated guess, however). For
|
/Linux-v4.19/Documentation/ |
D | siphash.txt | 75 key is kept secret, it is impossible for an attacker to guess the outputs of
|
/Linux-v4.19/Documentation/kbuild/ |
D | kbuild.txt | 100 deb-pkg. Normally deb-pkg attempts to guess the right architecture based on
|
/Linux-v4.19/Documentation/arm/ |
D | README | 12 a good compiler. Fortunately, you needn't guess. The kernel will report
|
/Linux-v4.19/Documentation/core-api/ |
D | circular-buffers.rst | 132 situation will merely be a guess, and may even be negative.
|
/Linux-v4.19/Documentation/power/ |
D | power_supply_class.txt | 101 these ones should be used if hardware could only guess (measure and
|
/Linux-v4.19/Documentation/hwmon/ |
D | lm90 | 271 I guess reliability comes at a price, but it's quite expensive this time.
|
/Linux-v4.19/Documentation/sh/ |
D | new-machine.txt | 254 for reference instead of trying to guess what settings are supposed to be
|
12