Talk:USB compatibility list
I tried to make a table layout that is future proof an contains all information needed to connect a device to the Pandora. If you can come up with more necessary info, please add colums now as it will be more work later. It took a little guesswork to put in all the info for the two GSM modems so please correct me if I was wrong anywhere! OrR
Table looks good OrR. For the modems, I marked drivers as "not needed", because DJWillis confirmed this in his blog. I've also added two columns: Tested in Linux, and Tested on Pandora. This allows us to add products that we're 99% sure will work, before we can test them ourselves on Pandora. The Apple Ethernet adapter is one such example... there have been a few people asking about these, and it looks to be the perfect device.
I’ve also added a (very) general section for OTG adapters, hubs etc. Even though compatibility issues with these are very unlikely (making them a little out of place on a compatibility page), it’s handy to point people here for their adapters etc rather than continually post links on the forums. Think of it as a “recommended for Pandora” section.
28-10-09: The OTG adapter compatibility table was recently changed from "generic, untested" to "Nokia, tested". However the links still pointed to generic adapters on eBay and Amazon. I've restored the first row to "generic, untested" and added a second row for the Nokia. The Nokia info still needs to be verified (was a particular model tested on Pandora or Beagleboard hardware?) and a link provided. - Gruso
I am confused by the classification of generic/nokia adapters. I thought there are regular adaptors that are just that and OTG adaptors that ground the 5th pin (ID pin) to tell the device to go into host mode. I have a N800 and it supports both however I have only a regular adapter so I have to force the usb controller into host mode. So wouldn't all adapters be supported? Some working to boot with others requiring software to enable host mode. --Robotjohn 01:05, 31 December 2009 (MET)
Just wondering, how do we know what's compatible? Jourdy288 17:19, 19 January 2010 (MET)
E220 current draw
I see the current draw for E220 (and E160) is set to 250mA in the table. As far as I know it needs 500mA (and that's also what Wikipedia says). The one I own certainly needs some juice, I have to use the dual-USB cable on my USB 1.1 laptop or it won't get enough current to work. I wonder where the 250mA figure comes from? Is it official? Tor 16:54, 5 March 2010 (MET)
- Having no source makes the data rather invalid. I corrected the entry and related entries and made notes as appropriate. — spiralofhope / (talk) 01:57, 23 June 2011 (CEST)
Removing the Linux Column
Now that we can test on Pandora, maybe we should think about removing the 'linux' column, and just focus on 'not tested/works on pandora/not working'. I am also not sure if there is much value in having a column for 'Suggested connection to Pandora' when a 'USB2.0 HS' would show if it can work direct to the 'A' connector.
- The thing I noticed looking at this page is that it's not immediately obvious whether or not something works (there isn't even a "works" column, you have to go through the notes). I think it'd make sense to remove "Suggested connection to Pandora", "Tested in Linux", and "Tested on Pandora". Those could be replaced by one header "Works" where the options would be, "Yes", "Yes, through powered hub", "No", and "untested". You could probably even follow the colour scheme I made for the Emulator List page and forget the column altogether to save some space and make it easier to see at a glance.
- And yes, there's really no reason anymore to list whether or not it works on Linux now that they can be tested.
- --Cheese 01:55, 29 June 2010 (MEST)
- I've modified the external hard drive section to be works/doesn't work instead of tested/untested. Nobody has spoken up about this yet, so if there's no complaints for a few days I'll do the rest of the page.--Cheese 22:37, 11 July 2010 (MEST)
- I thought of this too. I've modified the rest of the page to use "Works". — spiralofhope / (talk) 01:32, 23 June 2011 (CEST)
- Nobody cares if something works on Linux or not. They care about things working on the Pandora. This isn't linuxcompatible.com. Removing the tested on linux stuff is a good idea, I'll do that now and modify things so that any particularly interesting linux testing notes aren't lost. — spiralofhope / (talk) 01:32, 23 June 2011 (CEST)
It looks as if the products listed in this post aren't included in the External Game Controllers list. I was about to add them but would like to do some further research first. However, as I don't yet have my Pandora, it'll have to wait. Anyway, by posting here I thought that someone else might want to have a look in the mean time. --Trevj 11:08, 20 January 2011 (MET)
One of the major points of this page is for a person to say "I want to buy one of x, which one do I buy?". The whole page needs to be designed around answering this question.
1) Changed "tested in/on" to "works in/on". The reader just wants to know "does it work". Fixed things up as needed.
2) Hideable text. I used the template to hide as much text as I felt was necessary. The less extra comment text there is, the nicer the table and this whole page looks.
3) Colours. I changed all tables to use the yes/no templates. I ONLY did this on the "works on pandora" column, because that is the only place where it actually matters. Putting it everywhere there is a yes/no would be a usability disaster.
4) Unknown. I changed references to unknown to also use the template colour. These are important little gaps which need to be filled in for completeness.
5) Links. I changed any links I could to be just simple numbered links like  and I moved them beside their relevant entry. This keeps things nice and neat.
6) Removed the "tested/works on on Linux" columns and shifted any relevant notes into the comments. We don't need to get into a breakdown of Linux compatibility. What's important is Pandora compatibility.
Some other observations:
- Some of these entries say "I", but the tester's name and a link to them needs to be added.
- Some of these entries have no reference. How can they be trusted when they say things like "Reportedly uses an ASIX AX88xxx chipset." .. "reported" by whom?
- Shouldn't the "Works on Pandora" column be moved right next to the item's name? A reader wants to read an entry in exactly that order.
- Product names look particularly bad when centered, especially the bottom "Compact USB Hubs". Why not left-align the first column?
- Hi... I just want to say, thanks A LOT for finally cleaning this page up! It badly needed it. Good call on removing the "tested in Linux" stuff; I think that was a holdover from the era when no Pandoras had been sent out, so people could only test devices on Linux. I've gone over through your edits and am pleased to see that you've been very careful, so I haven't had to correct any mistakes (aside from moving the introduction to be before the TOC). Esn 08:43, 24 June 2012 (CEST)
We need a simple testing guide to be created for every table of devices we have here, and every common device type we can predict.
- What program(s) need to be run, how to get, install and use them.
- How can the user get additional technical information?
- Model number, ID number, etc
- How can the user learn "current draw"?
- Look at the back of the device.
- Look for a tag on the cable.
- I have a webcam.. but I have no idea how to test it. I could find some random webcam software like cheese, but is there a thorough procedure I should follow?
- I have a gamepad which I can see working with my desktop using
jstest /dev/input/js0but what is the equivalent on the Pandora?
- What software should I use to test a microphone?
- I whipped up microphone testing
I'm already roughly hacking out some ideas, see overview. Even if it's all amateur, anything is better than nothing. I'll check if there are others who have been trying to do something like this.
This is inconsistent at the moment. Technically, every device requires a driver. What people care about is whether the driver is included in the default firmware, and what to do about it if not.
Could have a column for what the driver is, and another for whether it's included (with the firmware version it was added if known).
One column might be better since there are quite a lot of columns already, but I'm not sure what would be the best way to present it.