4 ms·
> Supporting hardware with drivers is purely a software decision, its not as though software adds noteworthy weight to a device. But writing drivers still take
by azdle 9y ago
> Supporting hardware with drivers is purely a software decision, its not as though software adds noteworthy weight to a device.
But writing drivers still takes engineering time and costs money. Why bother writing two different drivers for two different interfaces when they do the same thing?
- StudentStuff 9y ago> Why bother writing two different drivers for two different interfaces when they do the same thing? Reliability and quality, the hardware is already there, why would you hamstring the product's reliability?
- azdle 9y agoBecause a failure that causes one interface to fail, but not the other seems really unlikely. Plus it wouldn't just be another driver to write, you also have to come up with some logic that determines if one has failed and use the other instead. This isn't linux where you can reasonably tell users "oh just blacklist this kernel driver and it'll use the other instead."
- StudentStuff 9y ago> a failure that causes one interface to fail, but not the other seems really unlikely. Go follow that link in my original post. Its a fairly common water damage issue for Macbooks where the SPI bus will be damaged, but the USB connection will be fine. > come up with some logic that determines if one has failed and use the other instead. Once again, go follow that link. Apple already built the logic, just instead of switching to USB, it begs you to pair a bluetooth keyboard!
- azdle 9y agoAh, sorry, I wasn't somewhere I could watch the video. If that's the case, I take back what I said, it could probably make sense to include both drivers then.
- StudentStuff 9y agoNo worries, I avoid linked videos like the plague myself. This one is decently short (for these types of repair videos) at 11 minutes, and is pretty easy to jump through if your pressed for time.