+Using libcaptive for non-filesystem W32 drivers?

diff --git a/doc/FAQ b/doc/FAQ
index 1822bb0..e662add 100644 (file)
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -157,6 +157,15 @@ A: Although <a href="http://www.winehq.com/">Wine</a> has better development
    <code>KERNEL_BASE</code>) although this address doesn't apply in any way on
    reactos running in host-OS GNU/Linux when compiled for libcaptive.
 
+Q: Is libcaptive limited to filesystems? What about general W32 driver support?
+A: Yes, libcaptive implements W32 kernel subsystem (mostly by reactos)
+        in GNU/Linux. It should be possible to use it for any kernel-level W32
+        closed-source binary although you will need to extend the currently
+        filesystem-centric supported W32 kernel API functions and you may also need
+        to extend 'libcaptive/ps/signal.c' SIGSEGV handler to emulate possible W32
+        driver access to hardware (if not solved by some more straightforward access
+        permission).
+
 Q: What is Ordinal in the W32 library symbols import/export scope?
 A: Each exported symbol has its Ordinal specified - this number specifies the offset
    in the library symbol table. During the symbol import from a different module