如何使Windows ADB驱动程序像现有的Linux ADB驱动程序一样简单？
由于某些原因，在 Windows 上，您需要为每个设备使用不同的驱动程序才能与 ADB 配合使用。在 Linux 中，您只需将 ID 添加到文件中即可。我们一直在尝试找出如何为 Windows 制作一个更通用的 ADB 驱动程序，因为我们在一个包含桌面组件和 Android 组件的两部分程序中使用 ADB。我们不想安装 100 个不同的设备驱动程序来确保我们的程序适用于每个设备，但是我们需要 Windows 操作系统，因此我们不能只切换到 Linux。
为什么在 Linux 上让 ADB 在各种设备上工作如此简单（只需将 manu ID 添加到文件中），但在 Windows 上我们需要为每个设备使用不同的设备驱动程序？我们可以采取什么方向来设计一个通用的 ADB 驱动程序，它可以像在 Linux 上一样适用于 Windows 上的每个 Android 设备？
非常感谢，如果不清楚，请告诉我我可以做些什么来澄清。
For some reason on Windows you need a different driver for every device to work with ADB. In Linux you just add the ID's to a file. We have been trying to figure out how to make a more universal ADB driver for windows, as we use ADB in a 2 part program that has a desktop component and an android component. We do not want to install 100 different device drivers to make sure our program works for every device, however we have Windows OS as a requirement so we can't just switch to Linux.
Why is it so simple to make ADB work on all kinds of devices on Linux (by simply adding the manu ID to a file), but on Windows we need a different device driver for every single device? What direction can we take to come up with a universal ADB driver that works for every android device on Windows as it already does on Linux?
Thanks very much, please let me know what I can do to clarify if this is unclear.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
虽然我无法提供明确的答案，但我可以提供这些可能提供一些解释的文字：
摘自 Linux 设备驱动程序，第 3 版，O'Reilly，第 1 章“设备和模块类”
从 Linux 用户的角度来看，这意味着他们经常会发现 Linux 系统现在经常“识别”给定设备，而不需要特定的驱动程序，或者（希望）至少会自动提供基本的操作系统支持对于这些设备，使应用程序能够使用它们。我不是 Windows 方面的专家，在 Vista 崩溃之后我就转向了 Linux（并且从未回头），但我总是记得每当我获得一个新设备时都必须加载设备驱动程序，即使它是一个记忆棒（但已经使用过其他设备）计算机上的记忆棒类型！）
我相信这就是 Windows 的设计方式，但我不知道为什么会采用这种特定方式。因此，我假设在 Linux 下，ADB 可以识别一种设备类型下的所有 Android 设备，而 Windows 则不能，因此 Windows 中需要大量的设备驱动程序。
While I cannot provide a definitive answer I can offer these words that may provide some explanation:
Taken from Linux Device Drivers, 3rd Edition, O'Reilly, Chapter 1 "Classes of Devices and Modules"
From a Linux User's point of view what this means is that very often they will find that a Linux system will very often now 'recognise' a given device without need for specific drivers, or (hopefully) at least basic OS support will automatically be provided for these devices enabling applications to use them. I'm no expert on Windows having moved to Linux after the Vista debacle (and have never looked back) but I ALWAYS remember having to load device drivers whenever I got a new device even if it were a memory stick (yet had already used other types of memory stick on the computer!)
I believe it's just the way Windows was designed but why that particular way I do not have any idea. I would assume therefore that under Linux, ADB recognises all Android devices under one device type whereas Windows cannot hence the need for numerous device drivers in Windows.