Searched refs:accurate (Results 1 – 23 of 23) sorted by relevance
| /linux-2.4.37.9/scripts/ksymoops/ |
| D | README | 5 with patches to other utilities in order to give more accurate Oops
|
| /linux-2.4.37.9/arch/i386/math-emu/ |
| D | README | 74 a value of pi which is accurate to more than 128 bits. As a consequence,
75 the reduced argument is accurate to more than 64 bits for arguments up
76 to a few pi, and accurate to more than 64 bits for most arguments,
78 80486, which uses a value of pi which is accurate to 66 bits.
243 accurate to 64 bits can result in a relative accuracy in cos() of
273 for pi which is accurate to more than 128 bits precision. As a
299 pi/2) the emulator is more accurate than an 80486 FPU. For very large
300 arguments, the emulator is far more accurate.
317 results which are in error (i.e. less accurate than the best possible
|
| /linux-2.4.37.9/drivers/hil/ |
| D | Config.in | 25 # This is not accurate but for now it will save confusion.
|
| /linux-2.4.37.9/include/linux/ |
| D | jffs.h | 94 __u8 accurate; /* The inode is obsolete if accurate == 0. */ member
|
| /linux-2.4.37.9/fs/jffs/ |
| D | intrep.c | 1053 tmp_accurate = raw_inode.accurate; in jffs_scan_flash()
1055 raw_inode.accurate = 0; in jffs_scan_flash()
1059 raw_inode.accurate = tmp_accurate; in jffs_scan_flash()
1173 if (raw_inode.accurate) { in jffs_scan_flash()
1871 raw_inode->accurate = 0; in jffs_write_node()
1875 raw_inode->accurate = 0xff; in jffs_write_node()
2540 raw_inode->accurate)); in jffs_print_raw_inode()
2746 raw_inode.accurate = 0xff; in jffs_rewrite_data()
2834 raw_inode.accurate = 0; in jffs_rewrite_data()
|
| /linux-2.4.37.9/Documentation/ |
| D | wolfson-touchscreen.txt | 139 For accurate touchpanel measurements, some settling time may be
|
| D | stallion.txt | 390 The information contained in this document is believed to be accurate and
|
| D | Configure.help | 7347 MHz) that is used for very accurate reception timestamps. Because
8847 These statistics are not very accurate due to the low frequency
|
| /linux-2.4.37.9/Documentation/arm/nwfpe/ |
| D | TODO | 24 method would be to use accurate table methods for these routines. I have
|
| /linux-2.4.37.9/Documentation/x86_64/ |
| D | boot-options.txt | 77 makes some profiling using performance counters more accurate.
|
| /linux-2.4.37.9/arch/m68k/fpsp040/ |
| D | setox.S | 150 | more accurate computation of the function EXPM1.
556 fadds (%a1),%fp0 | ...accurate 2^(J/64)
|
| /linux-2.4.37.9/Documentation/filesystems/ |
| D | affs.txt | 205 The bitmap valid flag in the root block may not be accurate when the
|
| /linux-2.4.37.9/Documentation/sound/ |
| D | vwsnd | 93 and SNDCTL_DSP_GETOPTR are accurate to a few samples.
|
| /linux-2.4.37.9/Documentation/networking/ |
| D | vortex.txt | 347 Maintainers find that accurate and complete problem reports are
|
| /linux-2.4.37.9/Documentation/telephony/ |
| D | ixj.txt | 85 accurate, the information contained here may be unreliable and there
|
| /linux-2.4.37.9/Documentation/crypto/ |
| D | descore-readme.txt | 82 (my time measurements are not as accurate as his).
|
| /linux-2.4.37.9/drivers/scsi/ |
| D | README.tmscsim | 179 NegoPeriod more accurate (4ns) than the SyncSpeed (1 / 25ns). I don't know
|
| /linux-2.4.37.9/drivers/scsi/aic7xxx/ |
| D | aic79xx.seq | 535 * LASTSCB and CURRSCB are accurate.
559 * but MAXCMDCNT is accurate. If we stop part way through
|
| /linux-2.4.37.9/drivers/char/ftape/ |
| D | RELEASE-NOTES | 708 Gary Anderson (without his accurate reports and unreliable
|
| /linux-2.4.37.9/Documentation/s390/ |
| D | Debugging390.txt | 695 If using gdb & you would like accurate displays of registers &
|
| /linux-2.4.37.9/arch/m68k/ifpsp060/src/ |
| D | fplsp.S | 6808 # give much more accurate computation of the function #
7190 fadd.s (%a1),%fp0 # accurate 2^(J/64)
|
| D | fpsp.S | 6914 # give much more accurate computation of the function #
7296 fadd.s (%a1),%fp0 # accurate 2^(J/64)
|
| /linux-2.4.37.9/drivers/pci/ |
| D | pci.ids | 6 # welcome (if they are accurate), we're eagerly expecting new entries,
|