Searched full:exotic (Results 1 – 17 of 17) sorted by relevance
25 * Defer to the syscall for exotic requests. The vdso has answers in riscv_vdso_get_values()
21 * macros also produce sensible values for the exotic type _Bool. [The
126 documentation of it is absolutely minimal - thus some exotic keys may not
127 For more exotic systems I have even less to say...
20 choose which one to program the hardware to, starting from the more exotic
76 with standard bit-rates but may fail for exotic bit-rates or CAN
171 mmap()'ed buffers or something even more exotic.
525 * vDSO should defer to the kernel for exotic cpu masks. in complete_hwprobe_vdso_data()
23 * macros also produce sensible values for the exotic type _Bool. [The
507 * In addition some more exotic implementations like the Toshiba
722 // roll-around ... exotic case (and OHCI has in td_submit_urb()
374 see the partial frame (disregarding some exotic debugging scenarios).
139 something more exotic, such as the "host:/path" that NFS desires.
568 dependency. This is especially useful for drivers for more exotic hardware, as
1350 standard bit-rates but may *fail* for exotic bit-rates or CAN system
1706 // <https://doc.rust-lang.org/stable/nomicon/exotic-sizes.html#empty-types>. The Rust Reference
1382 rfe link. You can concoct more exotic examples, containing more than