Searched refs:tester (Results 1 – 9 of 9) sorted by relevance
94 u32 tester; member158 while ((dev->data.bits_left + 7 < (sizeof(dev->data.tester) * 8)) && in keyspan_load_tester()160 dev->data.tester += (dev->data.buffer[dev->data.pos++] << dev->data.bits_left); in keyspan_load_tester()197 remote->data.tester = 0; in keyspan_check_data()219 if ((remote->data.tester & SYNC_MASK) == SYNC) { in keyspan_check_data()220 remote->data.tester = remote->data.tester >> 14; in keyspan_check_data()225 remote->data.tester = remote->data.tester >> 1; in keyspan_check_data()252 if ((remote->data.tester & ZERO_MASK) == ZERO) { in keyspan_check_data()254 remote->data.tester = remote->data.tester >> 5; in keyspan_check_data()256 } else if ((remote->data.tester & ONE_MASK) == ONE) { in keyspan_check_data()[all …]
49 tristate "XZ decompressor tester"
172 codice nelle mani di un gruppo di *tester* molto più esteso. Anche se avete175 E, ovviamente, dove ci sono *tester*, ci saranno anche dei rapporti su
290 quella funzione. Revisori e tester vogliono invece avere accesso alle
113 If you are a developer or tester and want to ensure the requested124 If you are a developer or tester and want to ensure the headers134 If you are a developer or tester and want to ensure the exported
708 tristate "Ring buffer benchmark stress tester"
670 tristate "Powerpc64 vpmsum hardware acceleration tester"
1968 tristate "kmod stress tester"
1395 D: /proc/cpuinfo, reboot on panic , kernel pre-patch tester ;)
