Comment 2 for bug 574396

I have fixed this problem now, letting the initialization of the backend not do hardware detection if the backend is started via a search_driver() call with a hardware ID. Then only the databases get initialized so that the driver for the hardware item specified by the ID gets searched for. This makes the driver search significantly faster. The changes are done in a way that no APIs change to make sure that everything else of Jockey works as before. The fix is attached as a patch.