I can't even find a reliable way to figure out, given that a device I have is usable in
Linux, what module to load as its device driver. In the Windows world you can just go to the
vendor's website, look up the model number, and grab it.
Unless the device in question is something archaic, like a pre-PNP era ISA board, or you are
hand-rolling a tiny Linux distro with minimal tools for some embedded hardware - you don't
need to figure this out, the module system will do it for you automatically.
Driver modules contain aliases like (pci:v000010B9d00005288sv*sd*bc*sc*i*) which match the
hotplug events generated when such a device is inserted or noticed at boot-up.
e.g. type 'modinfo ahci' and you'll see it has aliases for a number of devices which we know
support AHCI, plus a line which matches any unknown PCI (or PCIe, ExpressCard, mini-PCI etc.)
device which claims to offer the AHCI sub-class.
When you "go to the vendor's website and grab it" usually you get a bundle which may contain
two or more drivers, and that bundle also contains the equivalent plug-and-play information
for Windows to perform this same driver matching trick, so there's no difference here.
If you mean it would be nice to know where to look on the web for that driver, well, for
ordinary users that's not very helpful because they don't want to download an out-of-tree
Linux driver and learn how to compile it, so they're mostly going to wait until their vendor
includes it at which point it ought to Just Work.