Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
Forum Thread Details
  • Replies 358 replies
  • Subscribers 674 subscribers
  • Views 39910 views
  • Users 0 members are here
Related

Pi vs BeagleBone-Black

Former Member

So, just over a year on from the initial availability of the R-Pi and the new BeagleBone Black is upon us.  They've obviously taken a leaf out of the RPF's playbook and produced a cost reduced version at a price only marginally above the Pi.

 

I find it interesting that the compromises are very different, for example there's a proper PMIC and the ethernet is not troubled by being connected to USB, however the on-board HDMI seems less capable.

 

Other differences are in the documentation, I'm currently viewing the pcb gerbers for the beaglebone..  Have yet to see any sign of those for the R-Pi a year later. There's even an up to date devicetree capable kernel too.

 

Technology has also moved on somewhat, we get a 1GHz Cortex A8 which is better than the Pi, along with various other stuff and lots more GPIO's too.

 

Ok, so it's clear that I like the look of the new beaglebone, and given the price I'm likely to put any further R-Pi plans on hold until I have a chance to play with this. It's also making things like the Olinuxino-maxi I bought recently look very slow/expensive while still being cheaper than the similarly specced Olinuxino-A13

 

Some details of the beaglebone-black here http://circuitco.com/support/index.php?title=BeagleBoneBlack

 

What do the rest of you think ?   I don't expect this to displace the Pi anytime soon, but I expect it to be very attractive to those people who don't simply want to put XBMC on it and duct tape it to the back of the TV..

Parents

  • I'm pretty sure ARM are ecstatic with their profit stream. Whther the mali stuff is open or not is irrelevent. Their business models work and works well. trhey dont need to change it. I don;t reckon they have made any mistakes in their business pla. You dont get chips in the majority of embedded devices with a bad business model. To say arm got it wrong is wrong. They got it right and good on em.

     

    SOmething people seem to be misunderstand here. You don't need an open gpu.You need a gpu that supports the standard interfcaes, which means directx, opengl, and whatever flavour of acceleration google keep changing for android. ANd that's it. Because by supoprting open interfaces (or actually, just android) you win. the need for open source gpus is limited to hobbiest people liek the people here. noone who matters wants to reinvent the wheel when they are working their butts off byon guis and ***, working on gpu code. They want opengl or whatever. Let the experts work on gpus, and provide interfaces that make all gpus look the same even though they are all completely different underneath. The argument about being able to fix bugs if you have the code is bs. if their are bugs in the code, the customer get the supplier to fix them - that why the suppliers have huge teams of engineers working on this stuff. by the time the gpu get to you lot, there are so few bugs in the api's its irrelevent.

     

    OPen interfaces is where its at. Not buried in obscure gpu code that only works on one model of gpu. You want education - teach people to use the open interfaces, there are a hell of alot more jobs there than there are in writing the gpu code itself. Thera re probably less that 10000 people in the world at any one time working on gpu code and getting paid for it. Thats not a big job market. And people who know the interfaces can move in to gpu code as and when they get experience.

Reply

  • I'm pretty sure ARM are ecstatic with their profit stream. Whther the mali stuff is open or not is irrelevent. Their business models work and works well. trhey dont need to change it. I don;t reckon they have made any mistakes in their business pla. You dont get chips in the majority of embedded devices with a bad business model. To say arm got it wrong is wrong. They got it right and good on em.

     

    SOmething people seem to be misunderstand here. You don't need an open gpu.You need a gpu that supports the standard interfcaes, which means directx, opengl, and whatever flavour of acceleration google keep changing for android. ANd that's it. Because by supoprting open interfaces (or actually, just android) you win. the need for open source gpus is limited to hobbiest people liek the people here. noone who matters wants to reinvent the wheel when they are working their butts off byon guis and ***, working on gpu code. They want opengl or whatever. Let the experts work on gpus, and provide interfaces that make all gpus look the same even though they are all completely different underneath. The argument about being able to fix bugs if you have the code is bs. if their are bugs in the code, the customer get the supplier to fix them - that why the suppliers have huge teams of engineers working on this stuff. by the time the gpu get to you lot, there are so few bugs in the api's its irrelevent.

     

    OPen interfaces is where its at. Not buried in obscure gpu code that only works on one model of gpu. You want education - teach people to use the open interfaces, there are a hell of alot more jobs there than there are in writing the gpu code itself. Thera re probably less that 10000 people in the world at any one time working on gpu code and getting paid for it. Thats not a big job market. And people who know the interfaces can move in to gpu code as and when they get experience.

Children
No Data