Nope, doesn't help. Hot-plugging a USB device on a Raspberry Pi without USB polyfuses (which are only present on the first version of the Pi) can cause the Pi to reset or crash. I tried putting this infomation on the Raspberry Pi page on Wikipedia but it was reverted, see: http://en.wikipedia.org/w/index.php?title=Raspberry_Pi&diff=559064643&oldid=559049166

Tegra 5 uses ARM's A15-Cortex 32-bit ARMv7 core. Tegra 6 will be Nvidia's first SoC to use their custom designed 64-bit ARMv8 core.

If I wasn't interested I wouldn't have asked the question. I'm definitely not the only person who is curious about this situation.

Thanks for replying, but you didn't answer my question. I want to know why you are no longer a Raspberry Pi Foundation trustee. Why did you resign?

Eben, why were you terminated as a director of the Raspberry Pi Foundation?

http://opencorporates.com/filings/180901240

The Pi is similar in power to the original Xbox GPU-wise but not CPU-wise. From the FAQ, here: http://www.raspberrypi.org/faqs

This simply isn't true. XBMC on the Raspberry Pi is actually a rather poor experience. The Ouya is reputed to be powerful enough to decode H.264 in at least 1080p24 (using the ARM CPUs NEON instructions on all four of its cores) if need be, i.e. no video decode hardware acceleration necessary This ability might come in handy with some non-standard H.264 content that the Pi can't play.

Isn't that the same criteria the Raspberry Pi Foundation used?

Liz can be just so incredibly abrasive sometimes. She once implied I was a lunatic when I complained about the Raspberry Pi's USB issues. How a person like her ends up doing PR is beyond me, although she appears to have done a good job with the media side of things.

Only an idiot would connect something capable of damaging their computer directly to it. This is what opto-isolators are for.

You're making an incorrect assumption. I say the Raspberry Pi is underpowered because there are similar SoCs available that have ARM Cortex A8 or A9 CPUs in them which are clocked higher than the older ARM1176JZF-S CPU in the Pi and which support the newer ARMv7 architecture versus the Pi's ARMv6. This is a big deal since ARMv7 CPUs can run at their full potential using standard armhf Linux distributions.

Also, the GPU in the Pi isn't as powerful as the Raspberry Pi Foundation would have people believe. Just look at the results Luc Verhaegen has achieved with the supposedly much weaker GPU in the Allwinner A10.

Instead of putting up with the buggy and underpowered Raspberry Pi you could just spend $15 and use GPIO with your existing computer: http://www.hardkernel.com/renewal_2011/products/prdt_info.php?g_code=G135390529643

For the benefit of those who don't realize it, this is sarcasm. Read this and see both Eben and Liz Upton at their "charming" best and you'll understand: http://www.raspberrypi.org/archives/2221

It's a pity the mainstream media haven't mentioned these sorts of events which have occurred numerous times on their forums. The Raspberry Pi Foundation and the Raspberry Pi apologists ought to brace themselves though, the PR bubble and hype surrounding the Pi won't last forever. Eventually reality will prevail.

The Ouya will provide a greatly superior XBMC experience I'm sure. XBMC is simply too sluggish to be truly usable on the Pi.

While there have been quality control problems recently which the Raspberry Pi Foundation has downplayed the USB issues are inherently a result of the notorious USB controller in the BCM2835 SoC that the Pi uses. They've actually just hired a Broadcom employee full-time now to address these problems after many months of complaints, see this thread: http://www.raspberrypi.org/phpBB3/viewtopic.php?t=30764&p=270951

They are long overdue in taking this issue seriously but better late than never. Hopefully they'll have some success but I would be extremely surprised if the isochronous transfer problems are ever solved.