[erlang-questions] driver_async() marks driver as permanent?

[Paul Fisher]

Does using driver_async() from within a linked-in driver mark the driver
as permanent automatically?  I am seeing an {error, permanent} out of
erl_ddll:unload_driver/1 even after all of the processes which called
open_port/2 have exited, and therefore all of the port instances using
the driver have stopped.

If this is done automatically, is there a way to "unmark" it, so that I
can still unload the driver?

If such automatic marking is is not done, can someone confirm?


--
paul