On 08/22/17 16:29, Brijesh Singh wrote: > Thanks for detail explanation, I was trying driver unload and reload > from the UEFI shell but that did not trigger the BindStop hence I was > not sure how it all works.
*Unload* is a different thing. Clearly a driver can only be unloaded after all its currently bound devices are unbound, but there is no dependency in the other direction -- a UEFI_DRIVER module can perfectly well unbind devices *without* being unloadable. An edk2 driver module that is unloadable specifies the UNLOAD_IMAGE define in its INF file. Pretty few drivers do this. (None of the virtio drivers.) The "Driver Writer’s Guide for UEFI 2.3.1" writes about unloading in "7.6 Adding the Unload Feature" (and possibly elsewhere). > But your explanation makes sense. I will try connect and disconnect > to trigger the code path and make sure that all logical code path > have been tested before we commit the patch :) Sounds good, thanks! Laszlo _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
