Domain: rhombus-tech.net
Stories and comments across the archive that link to rhombus-tech.net.
Comments · 64
-
Re:Yes, but...
... but it takes a massive amount of money to design and make chips. It's not going to happen "open source" unless some very wealthy individual or organization decides to do so for altruistic reasons.
funnily enough this is precisely what has happened, quite recently, in the form of the Indian "Shakti Project". we could, up until a couple of years ago, have dismissed the Indian Government's security "paranoia" as simply... well... "paranoia"... except that it's not paranoia if they *really are* out to Get You. and thanks to the Intel ME fiasco, we know that the NSA really is screwing everybody.
so the Indian Government has basically given the Shakti Project UNLIMITED resources to, and i quote, "Piss All Over ARM And Intel". the only thing they are not allowed to go after is Memory and NAND because if they did so it would annoy S.Korea, Taiwan *and* China, take away various Triads in those three countries main source of income, and those countries control the major Foundries... the Shakti Team would have a hard time making *anything*, anywhere. so: Memory and NAND is out... but everything else is Fair Game.
in speaking with the head of the team last month he is happy to extend the opportunity to the Libre Software and Libre Hardware community... for free. why? well, because if you want to be able to VERIFY the entire source and the actual hardware, the entire design right to the bedrock HAS to be completely open and transparent...
anyway i will be working with him to design a processor, anyone else is welcome to get in touch http://rhombus-tech.net/riscv/...
-
Re:How does an open source chip solve the problem?
Being open source doesn't magically prevent bugs from reaching the silicon stage of a chip's design, nor does it make it any easier to fix bugs baked into a completed design. There are only so many people in the world smart enough to even fully understand modern superscalar designs let alone contribute usefully to it.
interestingly the head of the shakti team, madhu, is an advocate of something called "bluespec". it's similar to Berkeley's "chisel" except that, because bluespec is writteen in Haskell it's possible to do *formal mathematical proofs on the designs*.
there was a talk at ccc just last week about doing mathematical proofs on designs, but it's much harder to do if the underlying programming language for the ASIC doesn't really support formal proofs.
anyway, this is extremely interesting timing as i am, puzzlingly, in a position to be the go-between to actually get this done http://rhombus-tech.net/riscv/...
-
Phonebloks disappointment is half the story
https://davehakkens.nl/news/re...
dave hakkens is the person who really inspired the modular smartphone movement and brought it to prominence (buglabs was the first to really implement the concept, almost a decade ago). however we don't really have an actual explanation of what went wrong with project ara. here's some hints (search in this document for "ara" obviously): http://rhombus-tech.net/whitep...
basically it's down to the fact that google has more money than they have creative sense. they therefore tried to use "financial brute force" to solve problems. the summary is: with their financial resources they created a "backbone standard" called MIPI UniPro... forgetting that in the process it would be patented by the partners, thus AUTOMATICALLY locking out ANY kind of interoperability and competition for the next 20 years. how, exactly, is that supposed to be "open"???
if we want modular smartphones to be successful, we need PROPERLY OPEN STANDARDs that have no vendor lock-in, but that are also properly protected by a Certification Mark (the standards-equivalent of a Trademark) and a Foundation (or CIC or Benefit Corporation), which is given the financial clout by its sponsors to jump on anyone who wrongly implements the standard in such a way as to cause short-circuits (and end up killing someone due to lithium battery fires for example). it's not like a software standard, where interoperability failures cause a segfault: a HARDWARE fault can genuinely be dangerous.
also the standard needs to be made up of *other* standards that are unencumbered and royalty-free, so that companies and makers alike are incentivised to create modules (using 3D printers and low-cost off-the-shelf circuits), for example this one, under development: http://elinux.org/Embedded_Ope... . Google *literally* did the total opposite of this strategy in every single conceivable way. paying companies to develop new chipsets (patented, proprietary) and saying "here! it's open! sign our NDA, agree to our policy, and you'll be fiiiine!" i'm just staggered by the naivety of a billion-dollar company that had to add me to a special list "stop phoning this person to invite them to interview, you've called them five times already over the past 10 years".
the other thing is, whilst i am delighted at dave's success in bringing the benefits of modularity to a wider audience, he doesn't have any technical knowledge. he views an *increase* in the number of companies on the phonebloks.com front page as being a good thing. the key question which illustrates the point without having to spell it out: are any of the products listed on the phonebloks page interoperable in *any* way?
so. if there is anybody who would like to see this done properly - in an open fashion so that the mistakes of both google and fairphone are not repeated (see http://blogs.fsfe.org/pboddie/...) do reach out on the arm-netbook mailing list http://lists.phcomp.co.uk/mail... i've been investigating and researching this for years and waiting for the right opportunity. often it's good to wait for "big" corporations to fail to deliver, because it means that the hugely-public lessons sink in. a "small person" saying "this ain't gonna work no matter how much money they throw at it" tends not to be believed until the predicted failure comes about.
just as i did with the successfully-crowd-funded modular libre eco-laptop i've set up a stub page (for now) http://rhombus-tech.net/commun... which is a hybrid phone that acts "dumb" and may be upgraded to "smart" by plugging in a computer-on-a-module in Compact-Flash form-factor. "peripher
-
Phonebloks disappointment is half the story
https://davehakkens.nl/news/re...
dave hakkens is the person who really inspired the modular smartphone movement and brought it to prominence (buglabs was the first to really implement the concept, almost a decade ago). however we don't really have an actual explanation of what went wrong with project ara. here's some hints (search in this document for "ara" obviously): http://rhombus-tech.net/whitep...
basically it's down to the fact that google has more money than they have creative sense. they therefore tried to use "financial brute force" to solve problems. the summary is: with their financial resources they created a "backbone standard" called MIPI UniPro... forgetting that in the process it would be patented by the partners, thus AUTOMATICALLY locking out ANY kind of interoperability and competition for the next 20 years. how, exactly, is that supposed to be "open"???
if we want modular smartphones to be successful, we need PROPERLY OPEN STANDARDs that have no vendor lock-in, but that are also properly protected by a Certification Mark (the standards-equivalent of a Trademark) and a Foundation (or CIC or Benefit Corporation), which is given the financial clout by its sponsors to jump on anyone who wrongly implements the standard in such a way as to cause short-circuits (and end up killing someone due to lithium battery fires for example). it's not like a software standard, where interoperability failures cause a segfault: a HARDWARE fault can genuinely be dangerous.
also the standard needs to be made up of *other* standards that are unencumbered and royalty-free, so that companies and makers alike are incentivised to create modules (using 3D printers and low-cost off-the-shelf circuits), for example this one, under development: http://elinux.org/Embedded_Ope... . Google *literally* did the total opposite of this strategy in every single conceivable way. paying companies to develop new chipsets (patented, proprietary) and saying "here! it's open! sign our NDA, agree to our policy, and you'll be fiiiine!" i'm just staggered by the naivety of a billion-dollar company that had to add me to a special list "stop phoning this person to invite them to interview, you've called them five times already over the past 10 years".
the other thing is, whilst i am delighted at dave's success in bringing the benefits of modularity to a wider audience, he doesn't have any technical knowledge. he views an *increase* in the number of companies on the phonebloks.com front page as being a good thing. the key question which illustrates the point without having to spell it out: are any of the products listed on the phonebloks page interoperable in *any* way?
so. if there is anybody who would like to see this done properly - in an open fashion so that the mistakes of both google and fairphone are not repeated (see http://blogs.fsfe.org/pboddie/...) do reach out on the arm-netbook mailing list http://lists.phcomp.co.uk/mail... i've been investigating and researching this for years and waiting for the right opportunity. often it's good to wait for "big" corporations to fail to deliver, because it means that the hugely-public lessons sink in. a "small person" saying "this ain't gonna work no matter how much money they throw at it" tends not to be believed until the predicted failure comes about.
just as i did with the successfully-crowd-funded modular libre eco-laptop i've set up a stub page (for now) http://rhombus-tech.net/commun... which is a hybrid phone that acts "dumb" and may be upgraded to "smart" by plugging in a computer-on-a-module in Compact-Flash form-factor. "peripher
-
Re:What are the success criteria?
Excellent and substantive response, though you ["ikcl", but not sure of your relationship to the project] sound a bit defensive about it. Considering the mixed success history of such projects (which both of us referenced), I certainly understand why.
yeah no i get it. here's the thing: i am happy to admit that i don't know what i'm doing: that's why i'm inviting people to participate and point things out. if it succeeds, it succeeds as a *group* project, and that's really valuable. the approach that i'm taking seems to be working: we got this far, y'know?
I followed http://rhombus-tech.net/crowds... and read some more, but it seems to me that your approach is too orthogonal to what I'm trying to describe. You have lots of detail about how you think you can deliver a certain product with certain capabilities within a certain budget. Those numbers seem too fuzzy for me to trust the totals, and I couldn't find the schedule. Other places it felt like you were diverted by details that should not be relevant at this relatively early stage.
i'm talking to the factory owner online, and planning to go to taiwan (and then to HK and Shenzen) in september. leading up to christmas the factories are *stupidly* busy, which is why i will go and collect components personally. the critical window of opportunity is between the two new years: that's when i'd like to get the majority of PCB manufacturing done.
but, part of the issue is: if we go beyond the capacity of the current factory, we'll actually have to find another one, and thus redo the entire schedule. i'll also be able to do injection-molding instead of 3d-printing the casework.... so i put down a best-estimate (it's on the crowd supply page at the end) and we see how it goes. i figured that people would be happy to be kept informed of what's going on.
-
Re:Missing question in their FAQ
"Why are you using a shitty old processor like an A20
answered in the update regarding processor selection - https://www.crowdsupply.com/eo...
and exclude the only two good things it has going for it, GbE and SATA?"
answered in depth on the FAQ section - look for "SATA and GbE" and a more in-depth answer on http://rhombus-tech.net/crowds... again search for the keyword "SATA".
Even the old Raspberry Pi 2 is much faster than the A20, being a quad core A7.
only available from broadcom - a hypocritical company that operates on unethical grounds and maintains cartelling business practices, ships proprietary arbitrary untrusted executables that boot the CPU *from* the GPU, and forces children to purchase licenses to watch films, for $2.50. what kind of hypocritical lesson is that, that kids may only educate themselves "so far", but beyond a certain point they can FUCK OFF. great. i think that's a great education. we should all teach kids that they are only allowed to learn up to a certain point and beynd that they're expected to be treated like cattle.
If they wanted to go cheap and Allwinner,
EOMA68 is a hardware standard. read the "processor selection" update as well as the "passthrough card" update.
there's the A80,
uses PowerVR which is known to cause enormous instability problems ever since it came out, on *every* architecture that ever uses it. why would i want to bring out something that i know for a fact would be severely problematic?
H3
not designed for low-power.
or A64.
GPL-violating SDK with a proprietary untrusted bootloader.
sorry dude - don't try to be too clever and sarcastic, and you'll get a much less curt answer. i got too much ground to cover - over 25 forums and increasing.
-
Re:What are the success criteria?
Excellent and substantive response, though you ["ikcl", but not sure of your relationship to the project] sound a bit defensive about it. Considering the mixed success history of such projects (which both of us referenced), I certainly understand why. (However, just to refer to another, I think Diaspora may have been the best idea to die for bad planning combined with overfunding from the crowd. Not sure if it should be "literally die", because that depends on the relationship of Diaspora to the visionary's suicide.)
I followed http://rhombus-tech.net/crowds... and read some more, but it seems to me that your approach is too orthogonal to what I'm trying to describe. You have lots of detail about how you think you can deliver a certain product with certain capabilities within a certain budget. Those numbers seem too fuzzy for me to trust the totals, and I couldn't find the schedule. Other places it felt like you were diverted by details that should not be relevant at this relatively early stage.
The way I'm thinking is different. A really short capsule summary might be something like:
If funding is confirmed by September 15, then beginning on October 1, in two months we plan to design a PCB motherboard with the following interfaces. This will involve two people working full time, both of whom have committed to do the work, and who have agreed to payment of $10,000 for their time. At least 5 prototype boards will be produced for testing. The success criteria are (1) that the boards can be mass produced (lot size 100) for a cost of $15 each, and (2) the prototypes will be tested and proved to satisfy the specifications in the table below. The total project cost is estimated at $30,000, calling for 3,000 supporters at $10 each.
Once you have the first project completed, you can start the next step, but I think it's important to keep control over what you're doing at each phase. There are several mechanisms to do that, but I'm getting too long for the slashdot channel...
-
Re:Because.se one size does not fit all
Not trying to be rude.
no offense taken: this is the internet... it's slashdot.... what you wrote is actually really helpful as a counterpoint: chris answered i think really well https://news.slashdot.org/comm...
, bill yourself as a fully open and environmentally friendly alt to the raspberry pi and similar.
*deep, deep breath*..... AAAAAAAAAAAgh no
:) *shudder* no, no, nOooo, and no.ok to explain my reaction, there: those are all SBCs (single-board computers). after six months of supernova-style popularity, they're dead. each manufacturer of each SBC has to scramble like mad to bring out *the next* SBC using whatever processor they can get their hands on, and the next, and the next, in a desperate cat-and-dog bitch-fight of popularity and unethical abuse of the word "open".
... am i painting a broad picture here of the *really* stark contrast between the approach taken by the embedded "educational" SBC clone market and what we're doing with EOMA68?by total contrast we're creating the beginning of a comprehensive eco-system of hardware re-use which *happens* (through direct correlation) to both save money for end-users and also reduce e-waste.
but more than that: if we took the EOMA68-A20 board and turned it into an SBC, it would *INSTANTLY* be perceived as being a tired total waste-of-time banana pi or cubieboard clone... when in fact the irony is that those products exist *because* of the reverse-engineering and persistence that i applied to Allwinner to obtain GPL compliance. the sunxi community then helped take that initiative over, they've been working non-stop now for years to pressurise allwinner, and i've been helping quietly in the background ever since.
this project has a completely different focus in other words, where it succeeds if there is a *huge* compatible eco-system (tablet, laptop, router, camera, gps, media centre, lcd tv, games console - everything you can see on here http://rhombus-tech.net/commun... and many more) and a huge compatible range of EOMA68 Computer Cards (and an FPGA card and a Pass-through Card and a DisplayLink Card) with a wide price-range and crucially a decades-long-term "just plug it in, it will work" *stable* standard.
... massive, massive difference. -
Re:Same stupidity from the 90's
"They envision a world where users upgrade their computers by simply popping in a new card "
Intel had the same idea... and it was a giant failure.
i'm not surprised. intel literally cannot make a low-enough processor without sacrificing their pride. they just had to abandon the entire smartphone and tablet market a few months ago because of their pride.
Unless the "card" is a whole new computer that slots into a thin plastic case, this is 100% impossible.
it's a whole new computer in credit-card-sized form-factor (5mm x 54mm x 86mm - it's PCMCIA casework after all). it's stainless steel thin casework (0.1mm thick). so... not impossible at all. in fact, so not impossible that i managed to do it on a budget of $20k (which i got down to $1800 by the 3rd revision, after teaching myself PCB CAD design).
pictures. here. http://s.4pda.to/9hDP9BsrgvB1a...
and here http://rhombus-tech.net/allwin...
and videos here https://www.youtube.com/result...and... you get the idea. it *exists*. it's not even 100% impossible, it's actually 100% *possible* i.e. *done* already.
... which still doesn't explain why the hell no major manufacturer hasn't even tried this exact same approach. -
Re:Why? Its the economy, Stupid!
Volume is king in electronics.
thanks anne - appreciate the informative post. amazingly the computer cards are around $35 in volumes of 250 which puts them still well within the "affordable" bracket @ a pledge level of $65. which is one key reason why i have gone with the modular strategy - to get the Computer Cards into people's hands at an early phase. it's part of the bootstrapping process to get up to those mass-volume levels where the Computer Cards would only be around $16 in 20k volumes and the Laptop Housing's BOM would be around $150 or possibly even less.
with a modular approach, many of the NREs associated with product development can be amortised over a far longer time-period or a far greater volume, depending on whether we're talking about housings or computer cards respectively. i outline this strategy in more detail in the ecocomputing whitepaper. http://rhombus-tech.net/whitep...
-
Re:Won't happen
Agreed. If computing devices running a fully FSF-approved software stack became wildly popular - 3% or more of the computing market - then the major players in proprietary computing and the surveillance industry would move to block them.
Until then, we're too small to care about and the bad publicity from actively blocking us would probably help us more than hurting us.
i'm counting on that
:) i am sooo looking forward to the streissand effect... :)but to clarify: it's important to emphasise that this is *NOT* restricted to FSF-approved software. it so happens that because it will be really hard for proprietary OSes to fully support all the Housings *unless* they are based around GNU/Linux driver stacks it's *really unlikely* that there will be any proprietary OSes installed on EOMA68-compliant Computer Cards, it's not totally out of the realm of possibility. but, more than that, EOMA68 is a *hardware* standard. it's perfectly possible to have an EOMA68-FPGA card, or an EOMA68 "DisplayLink" card, or a Pass-through card which i deliberately added to the list just to get this point across. boring name for a really exciting and flexible concept, but i'm a techie, what can i say? https://www.crowdsupply.com/eo...
The bigger risk is that the creator mis-estimates some of the financial or technical hurdles in the project and runs out of money before delivering most of the pledge rewards. Up until now, all of my crowd funding pledges have been for games and books.
i'm a software libre developer of over 20 years experience. i've seen open hardware projects rise up and fail. the whole project's run along fully-transparent lines because i loved that i could learn from the mistakes as well as the successes made by the openmoko, openpandora and many many more. i did a comparative analysis (of the laptop-related ones) here https://www.crowdsupply.com/eo...
now, when you know that i've held back from committing to several opportunities over the past five years, because the *standard* is more important than profit-maximisation, that i've designed the standard extremely carefully and comprenhsively and am on record as being committed to the standard's success for at least a decade, and you know that i'm a software libre developer with 20 years experience, and you know that i've evaluated a dozen different alternative standards, and decided *not* to go with kickstarter because they're not completely ethical, and many many other things, you should get the general feeling that i'll be not only making *sure* that i succeed at this, but that, thanks to the transparent way in which the project's run along TRULY software libre project management lines, i actually *want* help and for people to review what i'm doing, and to contribute in any way they feel comfortable. or uncomfortable, if it comes to it. if you feel like shouting at me with a genuine concern - something that could jeapordise the entire project - for god's sake get on the mailing list or the IRC channel #arm-netbook on freenode and do so.
regarding technical hurdles: i answered this in another comment (go to http://slashdot.org/~lkcl it's 2 back from this one) with a funny story about a successfully-funded team contacting a battery manufacturer asking them to violate the laws of physics. i've pretty much comprehensively covered all of the technical hurdles that i can think of - and documented them. and invited people to review them. because this really is an open and transparent project. do take a look: let me know if i missed anything. http://rhombus-tech.net/crowds... and google "eoma68" on youtube, review the videos.
-
Re:What are the success criteria?
Sounds interesting, but I'd have to see a complete proposal before I'd chip in. I'd want to see the schedule, the budget, the resources, and the success criteria to know if the project succeeded.
most of the information you've asked for, because this is a *genuinely* open and transparent project, is on http://rhombus-tech.net/crowds... - including the BOM, a full risk analysis, and much more. having been around for a long time, long enough to have seen the openmoko fail, and the pi-top team break their promises, and the shit-storm that resulted from the purism team's deceptive marketing, and the difficulties that the openpandora team had with R.F. and firmware: if you have any specific advice, TELL ME. i WANT TO KNOW. best place to do that is the mailing list because then other people can help evaluate your proposals and questions - http://lists.phcomp.co.uk/pipe...
The summary sounds way too grand, so I think I'd want to see it broken down into pieces that are small enough to understand, too.
it's been five years: that's a lot of time to think, plan and get everything lined up. if you're interested in the background as to *why* i am tackling this, it may help to read the background section (first question) http://lkcl.net/articles/eoma6...
"breaking it down into small pieces" it turns out is extraordinarily difficult. the simplest i've found is, "you know like a pause memory pause card? yeah? well this is a pause computer pause card. same benefits as memory cards except now you move the *whole computer*". but even that often is not conceptually enough. after repeating things about 200 to 250 times at hope2016 (and losing my voice on the first day) there's a live video which you can find at https://www.crowdsupply.com/eo... - i managed to get it down to *only* 3 minutes, to cover *a few* of the benefits. the rest (that i have been able to think of over the past five years) are covered here in the "scenarios" section: http://rhombus-tech.net/whitep...
Also important to make sure nothing is overlooked, such as sufficient testing. Be fine if the same organization that helped check the proposal evaluated and reported on the results (perhaps holding the money, too).
well - it's just me, self-auditing with an "always transparent GENUINELY open approach learned from software libre project management of 20 years" unless other people pop up to help. so, you and everyone else on the mailing list will just have to keep an eye on me. and help out with the testing... because it's a software libre project, and i can't do everything, so *need help*. funny and really cool story: a guy called albert contacted me last month, asked if there was any plans to do a french keyboard. i went (internally), "argh, haven't got time, let's point him at the git repo and tell him about the STM32F072 nucleo boards, see what happens" and surpriiise! turns out he's an embedded hardware engineer... so guess what? he's now joined the mailing list and is helping to do french keyboard firmware and much more! https://www.crowdsupply.com/eo... and you can check the mailing list archives as well.
P.S. I think this is a solution to the general problems with all of the crowdfunding systems that I have examined. No accountability or adequate planning.
you're telling me. i spoke to a battery manufacturer last year: we had a bit of a laugh as he explained that a *FUNDED* project for a head-wearable device contacted them and asked him to violate the laws of physics. they'd used a high
-
Re:What are the success criteria?
Sounds interesting, but I'd have to see a complete proposal before I'd chip in. I'd want to see the schedule, the budget, the resources, and the success criteria to know if the project succeeded.
most of the information you've asked for, because this is a *genuinely* open and transparent project, is on http://rhombus-tech.net/crowds... - including the BOM, a full risk analysis, and much more. having been around for a long time, long enough to have seen the openmoko fail, and the pi-top team break their promises, and the shit-storm that resulted from the purism team's deceptive marketing, and the difficulties that the openpandora team had with R.F. and firmware: if you have any specific advice, TELL ME. i WANT TO KNOW. best place to do that is the mailing list because then other people can help evaluate your proposals and questions - http://lists.phcomp.co.uk/pipe...
The summary sounds way too grand, so I think I'd want to see it broken down into pieces that are small enough to understand, too.
it's been five years: that's a lot of time to think, plan and get everything lined up. if you're interested in the background as to *why* i am tackling this, it may help to read the background section (first question) http://lkcl.net/articles/eoma6...
"breaking it down into small pieces" it turns out is extraordinarily difficult. the simplest i've found is, "you know like a pause memory pause card? yeah? well this is a pause computer pause card. same benefits as memory cards except now you move the *whole computer*". but even that often is not conceptually enough. after repeating things about 200 to 250 times at hope2016 (and losing my voice on the first day) there's a live video which you can find at https://www.crowdsupply.com/eo... - i managed to get it down to *only* 3 minutes, to cover *a few* of the benefits. the rest (that i have been able to think of over the past five years) are covered here in the "scenarios" section: http://rhombus-tech.net/whitep...
Also important to make sure nothing is overlooked, such as sufficient testing. Be fine if the same organization that helped check the proposal evaluated and reported on the results (perhaps holding the money, too).
well - it's just me, self-auditing with an "always transparent GENUINELY open approach learned from software libre project management of 20 years" unless other people pop up to help. so, you and everyone else on the mailing list will just have to keep an eye on me. and help out with the testing... because it's a software libre project, and i can't do everything, so *need help*. funny and really cool story: a guy called albert contacted me last month, asked if there was any plans to do a french keyboard. i went (internally), "argh, haven't got time, let's point him at the git repo and tell him about the STM32F072 nucleo boards, see what happens" and surpriiise! turns out he's an embedded hardware engineer... so guess what? he's now joined the mailing list and is helping to do french keyboard firmware and much more! https://www.crowdsupply.com/eo... and you can check the mailing list archives as well.
P.S. I think this is a solution to the general problems with all of the crowdfunding systems that I have examined. No accountability or adequate planning.
you're telling me. i spoke to a battery manufacturer last year: we had a bit of a laugh as he explained that a *FUNDED* project for a head-wearable device contacted them and asked him to violate the laws of physics. they'd used a high
-
Re:Because.se one size does not fit all
The reason that this isn't already a common approach in the industry is that forcing constraints on form factors for SoC devices has some intractable issues. If you have a powerful SoC it demands high power and needs to dissipate heat; so the upper bound of what you can achieve in the packaging and with the connector will be rapidly met u.nless it is massively over specified, and then it will be large and expensive.
we're dealing with that by setting a hard limit for the [re-used, pin-incompatible] PCMCIA "Type I" and "Type II" sockets which are 3.3mm and 5.0mm respectively: the hard limit for these two thinner card types is 5.0 watts. so at around 3.0 to 3.5 watts there's still absolutely no need for fans or any kind of special thermal considerations: passive cooling is all that's needed, and the SoC happens to be in contact with the stainless steel case, which happens to be in contact with the aluminium of the keyboard (in the case of the laptop).
just over that (up to 4.0 watts) and it is possible to use exactly the same graphite paper that's been developed for mobile phones. cheap, readily-available.
at around 4.5 watts it would be necessary to seal the package and flood it with thermal gel.
Also, display technology is not fixed in time, parallel interface signals are already quite out of date as an interface specification , although the actual limit here will probably be down to the PCMCIA connectors impedance discontinuity and consistency after numerous insertions when more modern differential display protocols are adopted.
.right. i spent five years analysing this and the impedance of PCMCIA (which, again, just to emphasise, we are *NOT* electrically or electronically compatible with: EOMA68 merely REUSES the PCMCIA connectors, housings, sockets and assemblies) is 100 ohms.
the EOMA68 standard uses RGB/TTL because that allows you to go all the way from 320x240 up to 1366x768 which works out to be around 80mhz. 80mhz over 100 ohm impedance is just about acceptable: you remember those "gold shields" on PCMCIA? those were designed to reduce EMI. the cards we're using for the initial prototypes have the metal case covering the entire connector, both sides.
why use RGB/TTL? this is covered in the eco-computing white paper in detail, section on "interface selection" http://rhombus-tech.net/whitep... basically if you consider the cost of 320x240 LCDs and take a look on http://panelook.com/ they're peanuts cost and they're *all* RGB/TTL. if you added a converter IC it would be a massively-disproportionate percentage addition to the BOM. however if you go up to a 1024x600 which costs $18 approx and you add a $1 SN75LVDS83b LVDS converter IC.... that's not so bad, is it?
-
Re:All in for transparency?
I'm all for a hardware manufacturer who creates and promotes 100% open hardware with public code provided.....................know any?
yeah, that'll be me.
http://rhombus-tech.net/commun...
https://www.crowdsupply.com/eo...i also have an RYF / FSF-Endorseable CPU Card under development:
http://rhombus-tech.net/ingeni...just so you know, i currently have a sponsor for the 15.6in laptop, i've been working on it for 14 months now. sponsorship works well for two reasons: firstly, investment is usually profit-driven, so the priority is on maximising the investor's profits instead of getting the product - and even more importantly the modular standard - right. secondly, sponsorship is absolutely fair and honest. i receive what i need to do the job, and the sponsor(s) get to be able to buy (or in the case of my main sponsor, sell) the end product(s).
so if you'd like to sponsor the development of these products, do contact me ok? love to hear from you.
-
Re:All in for transparency?
I'm all for a hardware manufacturer who creates and promotes 100% open hardware with public code provided.....................know any?
yeah, that'll be me.
http://rhombus-tech.net/commun...
https://www.crowdsupply.com/eo...i also have an RYF / FSF-Endorseable CPU Card under development:
http://rhombus-tech.net/ingeni...just so you know, i currently have a sponsor for the 15.6in laptop, i've been working on it for 14 months now. sponsorship works well for two reasons: firstly, investment is usually profit-driven, so the priority is on maximising the investor's profits instead of getting the product - and even more importantly the modular standard - right. secondly, sponsorship is absolutely fair and honest. i receive what i need to do the job, and the sponsor(s) get to be able to buy (or in the case of my main sponsor, sell) the end product(s).
so if you'd like to sponsor the development of these products, do contact me ok? love to hear from you.
-
affordability
"Both companies have argued that there are millions of people in developing countries that still use browsers and operating systems that do not support SHA-2, the replacement function for SHA-1, and will therefore be cut off from encrypted websites that move to SHA-2 certificates."
that's ok - because they can just throw away perfectly good hardware because the software's out-of-date, discarding the older stuff in the hope that it doesn't end up in landfill but ends up in the developing world just like we do. wait... we're *already* talking about the developing world. so that means there's no fall-back - no incentive for the endless cycle of high-profit-with-bugs-and-security-vulnerabilities-so-you-buy-a-new-one, because there's not enough profit made from the sale of newer hardware in the developing market to justify pursuing it.
i _would_ recommend, at this point, that modular phones would be a good idea... except that if you now look at phonebloks you'll see that there's currently *six* separate and distinct, totally incompatible and entirely *not* open (i.e. not royalty-free, not patent-licensing-free etc.) hardware or open standard modular interoperable mobile phones.
plus, phones are not the only products that are insecure here: what about desktops, laptops and so on? it's not just the proprietary phones and proprietary tablets that will be *unable* to be upgraded because in order to effect an upgrade, it's likely that the entire OS will need to be replaced, it's *all* the computing devices that are hit by this problem.
as techies here on slashdot we understand that software keeps getting more and more complex, and that to recompile just one component (a security library) whilst keeping all the other, older components exactly the same is an extremely time-consuming software engineering task that NO PROPRIETARY HARDWARE VENDOR is going to commit to. in many cases they literally can't, especially the chinese OEMs, because the "O" for "originality" is a total sham in china: they receive binary-only (GPL-violating) distributions from an extremely secretive SoC manufacturer's close handful of partners, along with a Hardware Reference Design... and that's the end of the matter. they don't *HAVE* the source code. they *CAN'T* make the software upgrades even if they had customers willing to pay for the software engineers to do it.
so the only remaining choice, if the software cannot be upgraded, is to upgrade the hardware. and there literally isn't anyone except myself working on modular upgradeable computing appliances like laptops, desktops and so on. i've been looking for years, and i've even approached large companies: they've *actively* stated that they're not interested - the only reason i can think of is that they perceive there isn't enough guaranteed profit in modular computing because a competitor could come along and wipe them out with a faster or better compatible upgrade than they could produce in time. especially a chinese clone manufacturer.
so we're caught between a rock and a hard place, here. the current manufacturing-consumer cycle is highly-optimised for us in the 1st world, and we're effectively sleep-walking as to the consequences for ourselves and the rest of the world (which is just as the manufacturers want it) i outline this in more detail in a white paper i've written (below) - if in reading this you fully understand both the consequences and the nature of the problem and would like to do something about it, do contact me: i have some sponsors already and am open to more.
-
modular computing
interesting timing. i've been working on designing modular computer products for the past five years, and just wrote up a white paper yesterday on exactly this topic
http://rhombus-tech.net/whitep...the fairphone 2 is designed as "modular" - it's not exactly "modular", it's (very unusually, for a smartphone) designed to be repairable. you have to have a screwdriver, but that's a lot better than a hermetically-sealed unit that needs a saw or scalpel followed by epoxy resin to undo the damage caused by getting into the device.
also... what happened to the "bloom laptop"? i know it was 5 years ago now, but the whole reason why they started the project was because the entire class of students and two professors were absolutely astounded that it took *three hours* to disassemble a standard laptop... into over 140 constituent parts.
-
Opinion on projects like OpenRISC, RISC-V, etc.
First of all, thanks for all of your amazing contributions to free software and free culture movements in general.
I would like to hear your opinion about projects to create free hardware, in particular CPUs like the OpenRISC and RISC-V, or projects striving to create full systems respecting the GPL and without binary blobs like Rhombus Tech's EOMA or lowrisc, or any other that you might know that goes beyond refurbishing existing computers.
In the case that you hold a favourable opinion, I also would like to know if the FSF is in touch (even informally) with any of the teams behind these projects and plan to support them in any way (other than accepting changes to GNU software so it can run in these systems), e.g. by working with them from early on to ensure that they can later be endorsed by Respects Your Freedom.
-
Re:Liberated? What about the hardware?
You have to take steps to make progress. You can take something useful and make it more open (like librem) or you could start from scratch and make something very basic that is completely open.
You can take bigger strides towards openness and get something like Novena, but then you make other sacrifices (size, cost, performance).
I guess if you had infinite money you could make a high spec, completely opensource laptop.
interesting that you should say this
:) i am taking a different approach. i am also developing a laptop where the goal is to reach FSF-Endorseability *and* high-end specs. i am doing it one phase at a time, as you suggest... however where instead of having infinite money i am instead using creativity and ingenuity (posh words for "persistent bloody-mindedness combined with desperation stroke eye-popping frustration").sooo, i decided to go the "modular" route, but had to first create a decent hardware standard - one that will still be here in 10 years time but is simple enough for the average person (or a 5-year-old, or an 80-year-old) to use. it's based on an old "Memory Card" standard - you may have heard how PCMCIA is no longer being used? well, the case-work is still around
:) so, re-using PCMCIA it is. and all the benefits of "Memory Card", you now get "Computer Card".. upgradeable, swappable, saleable, transferrable, storable "Computer" Card. ... but then, of course, because of that, yaay, you now have to design entirely new casework, not just a motherboard. talking to casework suppliers didn't um go so well, so i have to do it. bought a mendel90 6 months ago... ... but mendel90's don't do injection-moulded plastics, they do 3d-printed filament plastics. and when presented with a potential $USD 20,000 cost for creating injection-moulding (you send your STL files off, someone adapts them, CNCs out two steel halves and then a little *team* of chinese people sit there for weeks on end polishing out all the CNC burrs.... then you find out it's *completely wrong* and have *another* $USD 20,000 to pay... no wonder ODMs quote $USD 250,000 for developing laptops!!!) ... anyway so that's all completely insane, so i thought, "hmm, i wonder if you can create reverse-3d-printed moulds to do injection-mould prototyping" and it turns out that you can. so i could at least - on a low budget - make a few runs out of very-low-temperature plastic (so as not to burst the 3d-printed plastic under pressure), hell i could even use plasticine for goodness sake, just to get a proof-of-concept, *then*.... and this is the hilarious bit.... there's a girl who's been doing LostPLA home-grown aluminium casting.... *using 1500W microwave ovens* :)http://media.ccc.de/browse/con...
so in theory i could quite conceivably even try doing the casting of the inverse-moulds for plastic injection *myself*, out of landfill-designated aluminium bicycle rims. do watch that talk: julia is surprisingly subtly funny, there were lots of jokes that the audience didn't get (not a native english speaking audience), and a few later that they did.
bottom line it *can* be done... if you make the decision, and damn well stick at it until success. if you're interested to follow along, here's the links:
* micro-desktop (launching very soon) which has the first EOMA68 module: https://www.crowdsupply.com/eo...
* the 7in tablet (due to go to assembly this week) http://rhombus-tech.net/commun...
* the 15.6in laptop (currently developing the casework) http://rhombus-tech.net/commun...on the laptop - as yo
-
Re:Liberated? What about the hardware?
You have to take steps to make progress. You can take something useful and make it more open (like librem) or you could start from scratch and make something very basic that is completely open.
You can take bigger strides towards openness and get something like Novena, but then you make other sacrifices (size, cost, performance).
I guess if you had infinite money you could make a high spec, completely opensource laptop.
interesting that you should say this
:) i am taking a different approach. i am also developing a laptop where the goal is to reach FSF-Endorseability *and* high-end specs. i am doing it one phase at a time, as you suggest... however where instead of having infinite money i am instead using creativity and ingenuity (posh words for "persistent bloody-mindedness combined with desperation stroke eye-popping frustration").sooo, i decided to go the "modular" route, but had to first create a decent hardware standard - one that will still be here in 10 years time but is simple enough for the average person (or a 5-year-old, or an 80-year-old) to use. it's based on an old "Memory Card" standard - you may have heard how PCMCIA is no longer being used? well, the case-work is still around
:) so, re-using PCMCIA it is. and all the benefits of "Memory Card", you now get "Computer Card".. upgradeable, swappable, saleable, transferrable, storable "Computer" Card. ... but then, of course, because of that, yaay, you now have to design entirely new casework, not just a motherboard. talking to casework suppliers didn't um go so well, so i have to do it. bought a mendel90 6 months ago... ... but mendel90's don't do injection-moulded plastics, they do 3d-printed filament plastics. and when presented with a potential $USD 20,000 cost for creating injection-moulding (you send your STL files off, someone adapts them, CNCs out two steel halves and then a little *team* of chinese people sit there for weeks on end polishing out all the CNC burrs.... then you find out it's *completely wrong* and have *another* $USD 20,000 to pay... no wonder ODMs quote $USD 250,000 for developing laptops!!!) ... anyway so that's all completely insane, so i thought, "hmm, i wonder if you can create reverse-3d-printed moulds to do injection-mould prototyping" and it turns out that you can. so i could at least - on a low budget - make a few runs out of very-low-temperature plastic (so as not to burst the 3d-printed plastic under pressure), hell i could even use plasticine for goodness sake, just to get a proof-of-concept, *then*.... and this is the hilarious bit.... there's a girl who's been doing LostPLA home-grown aluminium casting.... *using 1500W microwave ovens* :)http://media.ccc.de/browse/con...
so in theory i could quite conceivably even try doing the casting of the inverse-moulds for plastic injection *myself*, out of landfill-designated aluminium bicycle rims. do watch that talk: julia is surprisingly subtly funny, there were lots of jokes that the audience didn't get (not a native english speaking audience), and a few later that they did.
bottom line it *can* be done... if you make the decision, and damn well stick at it until success. if you're interested to follow along, here's the links:
* micro-desktop (launching very soon) which has the first EOMA68 module: https://www.crowdsupply.com/eo...
* the 7in tablet (due to go to assembly this week) http://rhombus-tech.net/commun...
* the 15.6in laptop (currently developing the casework) http://rhombus-tech.net/commun...on the laptop - as yo
-
Re:Would it kill you to hint at what Improv is (wa
If only there was some way to get more information, perhaps with a sort of "link" of some kind to a more detailed description.
here is the [old] specification of the [revision 1] CPU Card:
http://rhombus-tech.net/allwin...the current revision 2 which i am looking for factories to produce (RFQs sent out already) we will try with 2gb of RAM. this is just a component change not a layout change so chances of success are high.
here is the [old] specification of the Micro-Engineering Board:
http://rhombus-tech.net/commun...that was our "minimal test rig" which helped verify the interfaces on the first CPU Cards (and will help verify the next ones as well, with no further financial outlay needed. ever. ok, that would be true if i hadn't taken the opportunity to change the spec before we go properly live with it!! you only get one shot at designing a decade-long standard.... i'd rather get it right)
this will be the basis of the planned crowd-funding campaign: it's more of a micro-desktop PC:
http://rhombus-tech.net/commun...the micro-desktop chassis is very basic: VGA, 2x USB, Ethernet, Power In (5.5 to 21V DC). all the other interfaces are on the CPU Card (USB-OTG, Micro-HDMI, Micro-SD). however unlike the Micro-Engineering Board, the power is done with a view to the average end-user (as is the VGA connector which means 2 independent screens, straight out the box).
does that help answer the question?
-
Re:Would it kill you to hint at what Improv is (wa
If only there was some way to get more information, perhaps with a sort of "link" of some kind to a more detailed description.
here is the [old] specification of the [revision 1] CPU Card:
http://rhombus-tech.net/allwin...the current revision 2 which i am looking for factories to produce (RFQs sent out already) we will try with 2gb of RAM. this is just a component change not a layout change so chances of success are high.
here is the [old] specification of the Micro-Engineering Board:
http://rhombus-tech.net/commun...that was our "minimal test rig" which helped verify the interfaces on the first CPU Cards (and will help verify the next ones as well, with no further financial outlay needed. ever. ok, that would be true if i hadn't taken the opportunity to change the spec before we go properly live with it!! you only get one shot at designing a decade-long standard.... i'd rather get it right)
this will be the basis of the planned crowd-funding campaign: it's more of a micro-desktop PC:
http://rhombus-tech.net/commun...the micro-desktop chassis is very basic: VGA, 2x USB, Ethernet, Power In (5.5 to 21V DC). all the other interfaces are on the CPU Card (USB-OTG, Micro-HDMI, Micro-SD). however unlike the Micro-Engineering Board, the power is done with a view to the average end-user (as is the VGA connector which means 2 independent screens, straight out the box).
does that help answer the question?
-
Re:Would it kill you to hint at what Improv is (wa
If only there was some way to get more information, perhaps with a sort of "link" of some kind to a more detailed description.
here is the [old] specification of the [revision 1] CPU Card:
http://rhombus-tech.net/allwin...the current revision 2 which i am looking for factories to produce (RFQs sent out already) we will try with 2gb of RAM. this is just a component change not a layout change so chances of success are high.
here is the [old] specification of the Micro-Engineering Board:
http://rhombus-tech.net/commun...that was our "minimal test rig" which helped verify the interfaces on the first CPU Cards (and will help verify the next ones as well, with no further financial outlay needed. ever. ok, that would be true if i hadn't taken the opportunity to change the spec before we go properly live with it!! you only get one shot at designing a decade-long standard.... i'd rather get it right)
this will be the basis of the planned crowd-funding campaign: it's more of a micro-desktop PC:
http://rhombus-tech.net/commun...the micro-desktop chassis is very basic: VGA, 2x USB, Ethernet, Power In (5.5 to 21V DC). all the other interfaces are on the CPU Card (USB-OTG, Micro-HDMI, Micro-SD). however unlike the Micro-Engineering Board, the power is done with a view to the average end-user (as is the VGA connector which means 2 independent screens, straight out the box).
does that help answer the question?
-
clarification
the micro-engineering board being referred to is this:
http://rhombus-tech.net/community_ideas/micro_engineering_board/
that's what's being shipped. although the tablet itself using rapid prototyping for the casework shouldn't be too far behind. -
modular devices
Upgrading the CPU. Replacing the battery. Adding more RAM. All these will be possible with the modular phone.
http://rhombus-tech.net/
http://aseigo.blogspot.nl/2013/04/the-luminosity-of-free-software-episode.html
http://www.golem.de/news/aaron-seigo-vivaldi-tablet-mit-austauschbarer-open-hardware-1304-98707.html
https://www.youtube.com/watch?v=Wq0Dx04PcHk -
Re:Definitions, please?
got a problem with that? then FUCK OFF and stay out of my way. you do your thing, with your thoughts; i'll do mine.
Excuse me? You're the one who keeps bringing your pointless stories about meaningless "progress" on your pie in the sky project to Slashdot. Last time you were asking for ten million dollars for a hopeless SoC project that you yourself knew nothing about. Now you're back here, what, trolling for pre-orders and funding? What kind of con artist are you?
And let's be clear, this isn't even really *your* project. You're throwing money at companies in China to get them to do the work for you, and you can't even answer their questions. You're nothing but a sales guy with a vague idea and a big ego. Come back when you're selling in volume, until then please quit wasting our time.
-
Re:Obsolete Processor
Keep the fingers crossed for EOMA68 (plus whatever boards you like): seems like an all-open hardware and software stack.
-
Re:Other Low Cost ARM Boards to Consider ...
Keep an eye on EOMA68 cards. Sometime in the future, the IO may be made extremely easy
-
How tasty is this pi?
512MB is nice and all but, other than the cute name, what does the relatively closed architecture of the Raspberry Pi have over other efforts such as the Rhombus A10 project?
-
Re:Semi-Accurate predicts horrible failure
Or he just needed the lowest-priced Android tablet
Are you kidding?
You could buy four AllWinner tablets for the price of one Nexus 7. The SoCs are selling for less than $10 in volume.
Free shipping,boxchip,ALLWinner A13, 7.0" Android 4.0;512MB/4GB, 5 points touch capacitiive touch.Tablet PC Price: US $42.00 - 53.50 / piece
-
design something better
that's what we're doing with the http://rhombus-tech.net/ project. the scope of the project has the goals of the raspberrypi foundation as a subset; CPUs that we are actively pursuing have to have full GPL compliance, and are as open as possible / practical. where binary blobs exist, reverse-engineered alternatives are encouraged to be created. the first CPU Card is based on the Allwinner A10 (ARM Cortex A8, 1ghz, overclockable to 1.5ghz). the binary startup blob which is essential to set the DDR3 RAM timings before continuing with the 2nd phase of the boot process was reverse-engineered a few months ago; the MALI GPU has the limadriver project on the case; efforts are underway to investigate the proprietary video hardware encode/decode engine. we were given full access to the GPL kernel and u-boot sources within 48 hours of asking (even though we did not have a GPL compliance request outstanding).
answering your question, archiebunker: designing something better is a bit harder than you might imagine. full access to technical datasheets is often denied: you are literally at the mercy of the SoC vendor and if they don't like the way you dress, or smell, or if you're not one of their pally-pal pals you can flat-out forget gaining access to the documentation. one of the key reasons is that they simply don't know if you have the expertise, or if you can be trusted not to pass on information to their competitors. so, if it turns out that you don't have the expertise, and you have to come to them with questions, you just cost them money. if you leak information to their competitors, you REALLY just cost them money - serious money.
so what we're doing with the EOMA-68 initiative is to make the hard part - the CPU+DDR3+NAND - be "just a mass-produced component" that you can literally buy off-the-shelf in a retail store. if it comes in a case, you get access to the EOMA-68 interfaces and whatever else the CPU Card has on the user-facing front edge; if you buy it without the case, you also get access to the internal jumpers and additional connectors, for educational and R&D purposes as well as factory-install purposes.
we're getting there. it's been a long haul, and we will not stop. the team behind the initiative will be sticking with this for the next decade, keeping it constantly up-to-date and ensuring that new CPU Cards are always available.
here's the previous article about it - actually it was the PCB layout that was completed - the schematics were completed 2 months ago:
http://hardware.slashdot.org/story/12/09/07/2322207/rhombus-tech-a10-eoma-68-cpu-card-schematics-completed -
Intel will fail at mobile
.. and the reason is not efficiency or performance.. Intel enjoys huge (50%+) margins on x86 CPUs that simply will not be tolerated by the tablet or mobile device vendors. Contrast this with the pennies that ARM and their fab partners make for each unit sold. Even Intel's excellent process tech can't save them cost wise when you can get a complete ARM SoC with integrated GPU for $7.
-
Re:WHAT?
An ARM laptop? Dare I ask which OS?
any OS you like: that's the whole point. A10-based devices are "unbrickable" and are always upgradeable. there's a link here:
http://rhombus-tech.net/allwinner_a10/hacking_the_mele_a1000/you can see from that that there are *eleven* variants on 5 main OSes available. openembedded covers a ton of options just on its own. debian, ubuntu, redsleeve (a fedora-ARM port), puppy linux, android 3, android 4.
the similarity between the Mele A1000 and the A10 EOMA-68 CPU card is very strong: it's the reason why the A1000 was picked. that and the fact that it was affordable for everyone who wanted to help out
:) -
Re:Allwinner board. OK
Gigabit Ethernet goes through 10 to 100 to 1000.
Does the Allwinner A10 support Gigabit Ethernet? Or is it the EOMA-68 that allows for future boards with GbE?
the latter.
http://elinux.org/Embedded_Open_Modular_Architecture/EOMA-68#Table_of_EOMA-68_pinouts
http://git.rhombus-tech.net/?p=eoma.git;a=blob;f=pcb/allwinner_a10/library/allwinner.lib;h=cd435ae32f3049d7b6dcb524af0fcc6ec1a6b77d;hb=dfaa27a0ec6db9eaaa8abc74c68849caa64b721b#l95
http://rhombus-tech.net/allwinner_a10/pcb/look at line 95 down to 113: you'll see that that's an MII interface. MII is only 10/100 (GMII and RGMII are 10/100/1000). another way to tell is from the use of the RTL8201CP (link to the datasheet from the pcb page) which is a 10/100 PHY chip. however the EOMA-68 interface we've specified as being up/down negotiable from 10 to 100 to 1000 so that yes, future CPU Cards can be Gigabit Ethernet. that's mainly so that people can consider making ultra-low-power server farms out of commodity off-the-shelf mass-volume CPU Cards in the future. which i'm really looking forward to.
-
Re:Allwinner board. OK
Gigabit Ethernet goes through 10 to 100 to 1000.
Does the Allwinner A10 support Gigabit Ethernet? Or is it the EOMA-68 that allows for future boards with GbE?
the latter.
http://elinux.org/Embedded_Open_Modular_Architecture/EOMA-68#Table_of_EOMA-68_pinouts
http://git.rhombus-tech.net/?p=eoma.git;a=blob;f=pcb/allwinner_a10/library/allwinner.lib;h=cd435ae32f3049d7b6dcb524af0fcc6ec1a6b77d;hb=dfaa27a0ec6db9eaaa8abc74c68849caa64b721b#l95
http://rhombus-tech.net/allwinner_a10/pcb/look at line 95 down to 113: you'll see that that's an MII interface. MII is only 10/100 (GMII and RGMII are 10/100/1000). another way to tell is from the use of the RTL8201CP (link to the datasheet from the pcb page) which is a 10/100 PHY chip. however the EOMA-68 interface we've specified as being up/down negotiable from 10 to 100 to 1000 so that yes, future CPU Cards can be Gigabit Ethernet. that's mainly so that people can consider making ultra-low-power server farms out of commodity off-the-shelf mass-volume CPU Cards in the future. which i'm really looking forward to.
-
Re:WHAT?
Uh, the Pi is meant an educational and hobby platform. It has a bunch of slots and connectors. This thing is obviously a commercial product without a lot of slots or connectors that's meant to be embedded in a larger product.
Not being an embedded systems person, I'd be grateful if somebody linked examples of the kind of system that uses this kind of CPU card.
can't do that. can link you to planned and discussed products though:
http://elinux.org/Embedded_Open_Modular_Architecture/EOMA-68#Example_Motherboards
http://rhombus-tech.net/community_ideas/the first will be a laptop. we have a deadline to meet of 10th october to get 25 prototype samples ready, for our client. yes. really. that soon.
-
Re:WHAT?
This CPU card might form the core of another product, like a tablet,
or a laptop, smartphone, PDA, workstation, desktop, power-saving server, router, All-in-One LCD computer, Media Centre, IPTV, All-in-One keyboard computer, upgradeable camera, upgradeable videorecorder, games console, and many many more that have been discussed and we're always on the lookout for more - feel free to make suggestions on this page:
http://rhombus-tech.net/community_ideas/
http://elinux.org/Embedded_Open_Modular_Architecture/EOMA-68#Example_Motherboardsit's also worthwhile pointing out that we've added a DIL2-44 (2.5in IDE size) expansion header which gives access to the more common "engineer's" GPIO functions, such as an extra USB 480mb/sec, as well as AC97/I2S, dual-channel LVDS, VGA out and more; as well as adding a more "factory-style" FPC-45 which provides access to the kinds of functions that you'd see in commercial IPTV and other products (Dual Transport Streams; GPS; Smart Card, TV-IN and so on).
obviously, that "factory / engineering" mode, you'd not be able to get the standard 5mm height PCMCIA case on, but that's ok, because it's either factory-installed or being used for engineering, R&D or educational purposes. i've documented the full pin-outs here: http://rhombus-tech.net/allwinner_a10/orders/
but as a minimum you'd need a docking station to connect to everything.
not "everything": that would mean that without the docking station you'd not be able to gain access to the HDMI port, USB-OTG port, SD/MMC socket or the Audio Jack
:) but i believe i know what you mean. you mean like this?
http://elinux.org/Embedded_Open_Modular_Architecture/EOMA-68/MiniEngineeringBoard -
Re:WHAT?
This CPU card might form the core of another product, like a tablet,
or a laptop, smartphone, PDA, workstation, desktop, power-saving server, router, All-in-One LCD computer, Media Centre, IPTV, All-in-One keyboard computer, upgradeable camera, upgradeable videorecorder, games console, and many many more that have been discussed and we're always on the lookout for more - feel free to make suggestions on this page:
http://rhombus-tech.net/community_ideas/
http://elinux.org/Embedded_Open_Modular_Architecture/EOMA-68#Example_Motherboardsit's also worthwhile pointing out that we've added a DIL2-44 (2.5in IDE size) expansion header which gives access to the more common "engineer's" GPIO functions, such as an extra USB 480mb/sec, as well as AC97/I2S, dual-channel LVDS, VGA out and more; as well as adding a more "factory-style" FPC-45 which provides access to the kinds of functions that you'd see in commercial IPTV and other products (Dual Transport Streams; GPS; Smart Card, TV-IN and so on).
obviously, that "factory / engineering" mode, you'd not be able to get the standard 5mm height PCMCIA case on, but that's ok, because it's either factory-installed or being used for engineering, R&D or educational purposes. i've documented the full pin-outs here: http://rhombus-tech.net/allwinner_a10/orders/
but as a minimum you'd need a docking station to connect to everything.
not "everything": that would mean that without the docking station you'd not be able to gain access to the HDMI port, USB-OTG port, SD/MMC socket or the Audio Jack
:) but i believe i know what you mean. you mean like this?
http://elinux.org/Embedded_Open_Modular_Architecture/EOMA-68/MiniEngineeringBoard -
Re:68 cores?
An odd number of cores. Perhaps they have 4 cores, each controlling 16 CPUs. Or 4 cores set aside for other purposes?
68 pins, not 68 cores
:) of course, if you'd like to create a server box containing 64 or even 68 EOMA-68 CPU Cards, please feel free to do so! the idea was raised here: http://rhombus-tech.net/community_ideas/cluster_server/i adapted the EOMA-68 standard after that discussion, and squeezed in 10/100/1000 Ethernet to make it more attractive. the Allwinner A10 doesn't have Gigabit Ethernet, but future CPU Cards definitely will.
-
Re:Highest bang-per-buck ratio of any SoC
-
Highest bang-per-buck ratio of any SoC
How does that Broadcom SoC compare to the current Shenzen's SoC king the disruptive $7 Allwinner-A10 SoC?
Bonus: comes with open source GPU driver, unlike RasPi. -
EOMA-68
This idea might be better implemented as an EOMA-68 to android phone converter. Then you could use any EOMA-68 compatible devices with it including, but not limited to, clamshell keyboard/screen/touchpad devices. (I.E. a netbook shell)
As far as the RPi; I'm much more interested in this EOMA-68 compatible card which uses the more powerful Allwinner A10 CPU. That gets you the capability to run a complete open source stack (including GPU) and a datasheet! (Something which Broadcom refuses to give you for the RPi even though it was designed by Broadcom employees!)
Shamelessly copy-pasted specs for the Allwinner A10:
1.2ghz Cortex A8 ARM Core
MALI400MP OpenGL ES 2.0 GPU
DDR3 Controller 800MHz 1GB max
2160p Hardware-accelerated Video playback (4x the resolution of 1080p)
a NAND Flash Controller that is capable of 8-way concurrent DMA (8 NAND ICs)
4 SDIO interfaces (SD 3.0, UHI class)
USB 2.0 Host as well as a 2nd USB-OTG Interface (USB-OTG can be reconfigured as USB 2.0 Host, automatically)
24-pin RGB/TTL as well as simultaneous HDMI out
SATA-II 3gb/sec
10/100 Ethernet (MII compatible)
a 2nd 24-pin RGB/TTL interface that is multiplexed (shared) on the same pins for a standard IDE (PATA) interface.
GPIO, I2C, PWM, Keyboard Matrix (8x8), built-in Resistive Touchscreen Controller, and much more. -
EOMA-68
This idea might be better implemented as an EOMA-68 to android phone converter. Then you could use any EOMA-68 compatible devices with it including, but not limited to, clamshell keyboard/screen/touchpad devices. (I.E. a netbook shell)
As far as the RPi; I'm much more interested in this EOMA-68 compatible card which uses the more powerful Allwinner A10 CPU. That gets you the capability to run a complete open source stack (including GPU) and a datasheet! (Something which Broadcom refuses to give you for the RPi even though it was designed by Broadcom employees!)
Shamelessly copy-pasted specs for the Allwinner A10:
1.2ghz Cortex A8 ARM Core
MALI400MP OpenGL ES 2.0 GPU
DDR3 Controller 800MHz 1GB max
2160p Hardware-accelerated Video playback (4x the resolution of 1080p)
a NAND Flash Controller that is capable of 8-way concurrent DMA (8 NAND ICs)
4 SDIO interfaces (SD 3.0, UHI class)
USB 2.0 Host as well as a 2nd USB-OTG Interface (USB-OTG can be reconfigured as USB 2.0 Host, automatically)
24-pin RGB/TTL as well as simultaneous HDMI out
SATA-II 3gb/sec
10/100 Ethernet (MII compatible)
a 2nd 24-pin RGB/TTL interface that is multiplexed (shared) on the same pins for a standard IDE (PATA) interface.
GPIO, I2C, PWM, Keyboard Matrix (8x8), built-in Resistive Touchscreen Controller, and much more. -
Re:Engadget review negative?
How about the fact that it is a Broadcom SoC and Broadcom won't give you the data sheet! (and also provides binary blobs of questionable code quality)
I think I've mentioned it before, but this EOMA-68 form factor board looks much more interesting. It will likely be cheaper and will have a faster Allwinner A10 SoC which features ARM's MALI400MP GPU which has open source drivers.
Did I mention the 2160p Hardware-accelerated Video playback and the array of interfaces? (USB, NAND, SATA-II, etc..)
I sincerely hope that this project or something similar produces hardware sometime soon and can overcome the hype so we aren't stuck with the Raspberry Pi as the defacto replacement for the AVR for the foreseeable future.
(No offense to the guys that made the R-Pi, you guys did good work, you just chose the wrong sock (I know the principal does work at Broadcom))
-
Re:Engadget review negative?
How about the fact that it is a Broadcom SoC and Broadcom won't give you the data sheet! (and also provides binary blobs of questionable code quality)
I think I've mentioned it before, but this EOMA-68 form factor board looks much more interesting. It will likely be cheaper and will have a faster Allwinner A10 SoC which features ARM's MALI400MP GPU which has open source drivers.
Did I mention the 2160p Hardware-accelerated Video playback and the array of interfaces? (USB, NAND, SATA-II, etc..)
I sincerely hope that this project or something similar produces hardware sometime soon and can overcome the hype so we aren't stuck with the Raspberry Pi as the defacto replacement for the AVR for the foreseeable future.
(No offense to the guys that made the R-Pi, you guys did good work, you just chose the wrong sock (I know the principal does work at Broadcom))
-
AMD G and Z Series in eoma68 Also ~$100 + coreboot
There are also eoma68 cards in the works using the AMD Fusion APU's that will only use open source firmware so you won't have to settle for EFI or a closed BIOS as you have to with Intel.
1ghz Dual-Core CPU with AMD Radeon HD 6250 GPU,
http://rhombus-tech.net./amd_g_series/AMD APUs for Notebooks, Netbooks & Tablets
http://www.amd.com/US/PRODUCTS/NOTEBOOK/APU/Pages/tablet.aspx#3AMD Embedded G-Series Platform
http://www.amd.com/us/products/embedded/processors/Pages/g-series.aspx
http://www.amd.com/us/Documents/49282_G-Series_platform_brief.pdf -
Re:The First Hurdle
I'm much more exicted about the EOMA-68 stuff. Particularly these guys who are making an EOMA-68 compliant board with a BOM of $15 and almost all the interesting signals broken out into easy to access headers. They are basing it on the Allwinner A10 1.2ghz ARM Cortex A8 which has great specs (SATA, USB, etc) and seems to have datasheets available (try to get those for the Broadcom chip) All the hardware can be run by open source drivers with the exception of the hardware MPEG decoder which you can just ignore if you don't need it.
-
Re:The First Hurdle
I'm much more exicted about the EOMA-68 stuff. Particularly these guys who are making an EOMA-68 compliant board with a BOM of $15 and almost all the interesting signals broken out into easy to access headers. They are basing it on the Allwinner A10 1.2ghz ARM Cortex A8 which has great specs (SATA, USB, etc) and seems to have datasheets available (try to get those for the Broadcom chip) All the hardware can be run by open source drivers with the exception of the hardware MPEG decoder which you can just ignore if you don't need it.
-
Plenty of room for competition
Although you're making a "glass half full" kind of prediction, it's not hard to imagine that the opposite of your guess might occur in the US: All the other ARM licensees might see this as a fantastic coup for Broadcom, and follow suit with their own competing $25 - $35 boards.
After all, Texas Instruments already has their own $5 SoC available and used in their BeagleBone, so they could quite easily remove features from that board and release something into the Raspberry Pi price niche for education. (The BeagleBone's $89 places it far outside the Raspberry Pi's price niche.)
The Chinese will of course follow suit with boards based on their wildly successful Allwinner A10 ARM device, which is far better than Broadcom's SoC (on specs) and only costs $7 in production volumes. Expect a pile of competitors from that quarter!