Microsoft’s official statement is “Windows RT uses class drivers and in-box drivers exclusively, departing from a common driver added scenario on the x64 or x86 architectures.” (see Microsoft policies). There is no DDK. Officially, installing drivers on Windows RT is not supported.
That said, it turns out there is at least oneWindows ARM driver that exists (probably built and extracted from a full Windows RT platform development kit), and as a user you can install those drivers on a normal, unmodified Microsoft Surface device at least.
Whether Microsoft will close this mechanism in the future is unclear.
Below is a more complete list of all the Plugable devices which can and can’t be made to work with the surface today. Most use the drivers already built into the RT, so none of the above is a concern — but Windows RT is “special” so check for compatibility before assuming a device will work!
What devices work out of the box with ARM-based Windows RT (without a 3rd party driver install)?
Plugable Windows Easy Transfer Cable (Although Windows Easy Transfer is available on Windows RT devices, the driver for USB Easy Transfer cables is not. Kind of surprising since on Windows XP – 8, this is a driver developed and provided by Microsoft in the box)
What needs a driver package and has one available for ARM-based Windows RT devices
We recently received a Raspberry Pi at the Plugable offices and we have been using it to test how our various devices interact with it. The Raspberry Pi has 2 USB 2.0 Ports, and no USB 3.0 ports, so our testing was focused on USB 2.0 devices and a couple USB 3.0 storage devices.
All of these tests were carried out on a Raspberry Pi Model B using the latest version of Raspbian wheezy. Here’s a video of the full setup, followed by a bunch of detail about our tests:
Plugable USB 2.0 10 Port Hub with 2.5A Power Adapter – Causes the Raspberry Pi to reboot upon connection, because it supplements the 2.5A wall power with 500mA from the upstream port. This is too much for the Pi., but just at the moment it is plugged in. If you plug the 10 port hub in when the Pi is powered down, you can boot into the Pi and all will be well. But since there are better options (like the 7 port hub above), we don’t recommend our 10 port hub with the Pi.
USB2-2PORT – Causes the Raspberry Pi to reboot upon connection. This is simply because this is an unpowered hub. Only hubs with their own power adapter should be used with the Pi.
USB3-HUB7-81x – USB HID devices(Mice, Keyboards) are known not to work with this hub on the Raspberry Pi.
USB3-HUB81x4 - USB HID devices(Mice, Keyboards) are known not to work with this hub on the Raspberry Pi.
USB2-SWITCH2 – No issues
The common pattern with all devices is you must have one of the powered usb hubs above and connect the device through that. If you don’t, the Pi won’t be able to handle the power draw, and it will drop voltage and reset.
Listed below are our latest updates about how to make your Plugable products work on Mac OS X 10.8 Mountain Lion with all the caveats shared by customers. If you read this post before and notice changes, it’s because we’ve revised our advice based on differences between our test results and what many customers were reporting. For now, in all cases we are recommending the solutions that have worked for everyone.
Any Plugable products not listed below have not yet been tested or have no Mac support (USB 3.0 graphics adapters, USB 3.0 docking station, Windows Easy Transfer cable).
After installation and reboot, plug in the adapter.
Go to network settings. If a new USB Gigabit interface hasn’t been created, then click the plus button, and add a new interface for the USB Gigabit Ethernet adapter.
Click the gear button, choose to set the service order, and drag the Gigabit Ethernet interface to the top of the list to make it your primary network connection. Approve the change to return to the main network settings screen.
Click Apply in network settings.
If the status in network settings goes green with a good IP address (not 169.x.x.x), the adapter is working properly.
Uninstall any old DisplayLink drivers before upgrading from 10.7.x.After upgrade, download and install the production version of DisplayLink’s v1.8 driver (or later) for OS X at DisplayLink’s Mac driver page.
Note that the performance of USB graphics on Mac is not yet at the same level as Windows. And some customers have reported crashes and hangs after installing DisplayLink drivers on Mountain Lion. See DisplayLink’s Mac user forum for the latest details. There is a specific thread on possible causes of Kernel panics.
We are filing bugs with DisplayLink based on Plugable customer feedback. If your system is not performing properly once you have installed the latest DisplayLink drivers, please contact us at firstname.lastname@example.org for assistance.
10.8 has a regression where USB Hard Drives attached to a Mac through a USB hub may report “drive wasn’t ejected properly” on return from sleep. We have customer reports of this issue in particular with USB 3.0 hubs like USB3-HUB4
Please feel free to comment here or e-mail us at email@example.com with your findings, questions, or problems. We’re here to help.