Agreed. This looks like the perfect upgrade from the Raspberry Pi, assuming they get it right. A quad-core 64-bit CPU with USB 3.0 and Gigabit Ethernet are exactly what I'm looking for. And I'm sure the Intel Atom's USB controller won't be broken, unlike the one contained in all the Broadcom SoCs used in the various Raspberry Pis. Software workarounds never solved all of its problems.
No, they haven't completely resolved the multiple bugs with USB on the Raspberry Pi and I don't expect they ever will. Some of them seem to be completely unsolvable in software..
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
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.
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.
Ok, so you're saying that it makes sense to risk frying a $500 laptop instead of a $25 Pi? Riiiight.
Only an idiot would connect something capable of damaging their computer directly to it. This is what opto-isolators are for.
And when you say "underpowered", that's because you hadn't realised that the SoC was designed to go into hi-def PVRs or BluRay players, so it has a muscular GPU, and the "underpowered" ARM CPU was an afterthought...and you haven't kept up with the news,
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.
Hey Luc, why not drop round the Raspberry Pi forum and tell them about this. As you know they are a friendly bunch of guys and will want to offer you their congratulations.
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.
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.
Problematic is actually a good word to use to describe the Raspberry Pi. It certainly has problems, some of which will almost certainly go unsolved, e.g. its non-standard and woefully inadequate USB controller which can reasonably be characterised as being broken.
Your perception that one socket for power is better than another is ridiculous, BTW. A USB wall wart is no different to a wall wart with some 1.3mm connector.
I don't think he was referring to the physical design, rather to the very real issues regarding USB power. My argument is that if the Raspberry Pi was competently designed these issues would be much less of a problem than they are.
As for programmability, which is what actually matters, Mali 400 has no open source driver except some reverse-engineered garbage. The GPU on the Pi does, and it's code from the manufacturer.
Slashdot Mirror
No SD card slot = no purchase.
http://www.up-board.org/
UP board is AMAZING specs.
Agreed. This looks like the perfect upgrade from the Raspberry Pi, assuming they get it right. A quad-core 64-bit CPU with USB 3.0 and Gigabit Ethernet are exactly what I'm looking for. And I'm sure the Intel Atom's USB controller won't be broken, unlike the one contained in all the Broadcom SoCs used in the various Raspberry Pis. Software workarounds never solved all of its problems.
You can't just copy other peoples closed source hardware.
But the Odroid-W wasn't a copy of any of the Raspberry Pi boards, it was merely based around the same BCM2835 SoC they are.
But the USB problem remains due to the buggy controller in the BCM2835 SoC itself. Board level fixes can't work around this.
The Raspberry Pi's USB problems have been reduced but they will never be totally solved.
You could use a USB microphone.
You could and it might work, but it might not since the Raspberry Pi has problems with USB and isochronous transfers are particularly problematic.
No, they haven't completely resolved the multiple bugs with USB on the Raspberry Pi and I don't expect they ever will. Some of them seem to be completely unsolvable in software..
Incidentally, they've just started a beta test of the latest round of USB fixes: http://www.raspberrypi.org/php...
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 gives Nvidia the chance to demonstrate their new ARM strategy of fusing 64-bit ARM cores (ARMv8 - desktop class) with PC-class AAA GPU cores
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
Overall real world performance is something like a 300MHz Pentium 2
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.
Future samples are approved for sale as a standalone product because "they boot", which obviously qualifies them to ship.
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.
Ok, so you're saying that it makes sense to risk frying a $500 laptop instead of a $25 Pi? Riiiight.
Only an idiot would connect something capable of damaging their computer directly to it. This is what opto-isolators are for.
And when you say "underpowered", that's because you hadn't realised that the SoC was designed to go into hi-def PVRs or BluRay players, so it has a muscular GPU, and the "underpowered" ARM CPU was an afterthought...and you haven't kept up with the news,
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
Hey Luc, why not drop round the Raspberry Pi forum and tell them about this. As you know they are a friendly bunch of guys and will want to offer you their congratulations.
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.
Problematic is actually a good word to use to describe the Raspberry Pi. It certainly has problems, some of which will almost certainly go unsolved, e.g. its non-standard and woefully inadequate USB controller which can reasonably be characterised as being broken.
Your perception that one socket for power is better than another is ridiculous, BTW. A USB wall wart is no different to a wall wart with some 1.3mm connector.
I don't think he was referring to the physical design, rather to the very real issues regarding USB power. My argument is that if the Raspberry Pi was competently designed these issues would be much less of a problem than they are.
Plenty of LCD displays don't have any digital inputs, believe it or not.
As for programmability, which is what actually matters, Mali 400 has no open source driver except some reverse-engineered garbage. The GPU on the Pi does, and it's code from the manufacturer.
No it doesn't, they just made the source of a message passing interface available, i.e. it's just a shim, not an actual driver. See here: http://www.raspberrypi.org/archives/2221 and http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDk