Searched full:knowing (Results 1 – 25 of 171) sorted by relevance
1234567
72 Userspace applications interested in knowing the name of85 Userspace applications interested in knowing the details of
8 Knowing the EC GPE one can watch the amount of HW events related to
191 Userspace applications interested in knowing the203 Userspace applications interested in knowing the219 Userspace applications interested in knowing the
17 received data. However, there is no specified way of knowing if the sent
16 However, there is no specified way of knowing if the sent data has been read
28 * inferred by reading the chip's value and knowing the last value written
62 * disable bh. Knowing this, it is possible to detect softirq based in task_get_classid()
41 Userspace is interested in knowing "this LED can produce arbitrary
8 low/high value, without knowing the last value written since the chip came out
77 have always used the old ARCnet driver without knowing what type of
10 The following symbol definitions rely on you knowing the translation that
23 * related to) the actual interrupt number they use. So knowing the IRQ
136 /* initialize mcfslt_cnt knowing that slice timers count down */ in hw_timer_init()
71 knowing how things are done will make the process of getting your changes
94 * number, knowing this would reduce the number of cache entries to be in __flush_dcache_page()
77 * printed backtrace as knowing what instance of input in input_setup_polling()
119 * means that tools like valgrind end up knowing about the mapped
44 firmware knowing how they're used).
103 Another key information point in forensic analysis is knowing who the metadata105 and/or corrupted, and how long ago that it was last modified. Knowing the owner
163 * read the buffer knowing that the state will not change from in xfs_trans_log_inode()
29 * - Knowing the correlation between dma channels and the
126 mark, knowing that it's part of the real backtrace.
62 * explicitly defined as additional exit points. Knowing all exit points is89 * explicitly defined as additional exit points. Knowing all exit points is
204 * The advantage of this is that it can be done without knowing about
123 Knowing how MacOS is based on BSD and BSD is an Open Source it is