Home
last modified time | relevance | path

Searched refs:guess (Results 1 – 25 of 44) sorted by relevance

12

/Linux-v5.4/net/atm/
Datm_misc.c30 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-v5.4/drivers/char/
Drtc.c850 char *guess = NULL; in rtc_init() local
982 guess = "SRM (post-2000)"; in rtc_init()
985 guess = "ARC console"; in rtc_init()
988 guess = "Digital UNIX"; in rtc_init()
992 guess = "Digital DECstation"; in rtc_init()
996 guess = "Standard PC (1900)"; in rtc_init()
999 if (guess) in rtc_init()
1001 guess, epoch); in rtc_init()
/Linux-v5.4/Documentation/fb/
Dpvr2fb.rst52 composite. If none is specified, we guess.
55 vga. If none is specified, we guess.
/Linux-v5.4/tools/usb/usbip/
D.gitignore6 config.guess
DINSTALL18 The `configure' shell script attempts to guess correct values for
148 message saying it cannot guess the machine type, give it the
/Linux-v5.4/arch/arm/include/debug/
Dvexpress.S25 @ Make an educated guess regarding the memory map:
/Linux-v5.4/Documentation/scsi/
Dsym53c500_cs.txt20 version of this driver, and I guess it worked for those users. It worked
/Linux-v5.4/Documentation/media/uapi/mediactl/
Dmedia-controller-intro.rst36 increasingly high number of those parameters, drivers need to guess what
/Linux-v5.4/arch/arm/boot/dts/
Dsun6i-reference-design-tablet.dtsi106 regulator-name = "vdd-cpus"; /* This is an educated guess */
Dsun6i-a31-mele-a1000g-quad.dts142 regulator-name = "vdd-cpus"; /* This is an educated guess */
Dsun6i-a31-m9.dts142 regulator-name = "vdd-cpus"; /* This is an educated guess */
Dsun6i-a31s-primo81.dts188 regulator-name = "vdd-cpus"; /* This is an educated guess */
Dgemini-dlink-dir-685.dts301 * I guess).
/Linux-v5.4/Documentation/misc-devices/
Deeprom.rst75 specification, so it is guess work and far from being complete.
/Linux-v5.4/Documentation/w1/masters/
Dds2490.rst69 host did not explain the problem. My guess is a bug in either qemu
/Linux-v5.4/Documentation/i2c/
Ddma-considerations.rst15 around 8 bytes (as of today, this is mostly an educated guess, however). For
/Linux-v5.4/Documentation/block/
Dqueue-sysfs.rst82 to make an educated guess at when the IO will complete. Based on this
83 guess, the kernel will put the process issuing IO to sleep for an amount
/Linux-v5.4/Documentation/security/
Dsiphash.rst75 key is kept secret, it is impossible for an attacker to guess the outputs of
/Linux-v5.4/Documentation/kbuild/
Dkbuild.rst120 deb-pkg. Normally deb-pkg attempts to guess the right architecture based on
/Linux-v5.4/Documentation/arm/
Darm.rst13 a good compiler. Fortunately, you needn't guess. The kernel will report
/Linux-v5.4/Documentation/core-api/
Dcircular-buffers.rst132 situation will merely be a guess, and may even be negative.
/Linux-v5.4/Documentation/power/
Dpower_supply_class.rst115 if hardware could only guess (measure and retain) the thresholds of a
/Linux-v5.4/Documentation/hwmon/
Dlm90.rst395 I guess reliability comes at a price, but it's quite expensive this time.
/Linux-v5.4/Documentation/sh/
Dnew-machine.txt246 for reference instead of trying to guess what settings are supposed to be
/Linux-v5.4/arch/x86/
DKconfig.debug328 This option enables the "guess" unwinder for unwinding kernel stack

12