I once owned a Ethernet PCMCIA Card and a USB PCMCIA Card. In both cases, most of the time I pulled the card out of the slot when I tried to unplug a cable. That was super anoying. A pheripherial Hardware Component doesn't seem much of an impact compared to a card that actually holds your core computing components.
Convince People at crowdsupply your Design doesn't do that and you're as good as funded. Convince People that whatever they're working on isn't lost when a child steps on an EOMA68 Card connected cable (like the card gets pulled out while in use) and you actually might have a nicely engineered Product. >
Copied in the below, from the Arm-netbook mailing list, at Luke's request. Edited both for typos and (at least minimally) for readability. --Christopher
Recent events may have forced the need for more clarity. Perhaps sooner that really needed. So far we've mostly done the technical issues.
I'm going to tap into the collective brain here.
In order to protect the EOMA standard: to what terms should a manufacturer/vendor follow, to become EOMA-compliant?
- Technical: Adhere to the physical dimensions, tolerance, heat.
- What would be a reasonable price/pricing structure
- Environmental footprint
...and how to deal with leeches, blacklists, etc.
I know the technical side is already coming along but if there is anything you would like to be mentioned, please write it down.
Firstly I'd like to refer to the Arduino-approach, which seems to be rather refined: 0) Official Arduino products 1) Certification: A certification program which strongly integrates the product in the official Arduino line of products. (https://arduino.cc/en/ArduinoCertified/) 2) Regulation: Via the Arduino AtHeart project. Some minimal requirements on technology and openness, a fee, and a marketing-deal benefiting both the regulator and the regulated. (https://arduino.cc/en/ArduinoAtHeart/) 3) Recommended: Single-sided plug by the Arduino-crew on their homepage. 4) Other related hardware: Arduino-maintained list of compatible products, covering all types and boards (https://playground.arduino.cc/Main/SimilarBoards) 5) Unregulated: Any party can call their products 'Arduino-compatible', like the Sparkfun RedBoard. (https://www.sparkfun.com/products/11575)
I assume that both regulation and certification would require certain technical compatibility although the officially stated requirements are quite limited.
What I like about that way of certification is that it is not a requirement, but if you do, it creates a synergistic relationship between both parties.
More overall requirements related to EOMA I would assume to be:
- Meeting consumer certifications (FCC, CE).
- Preventing faulty installation by way of enclosure (shifting pin-out or rotating the EOMA connector).
- Proper handling of signals when plugging.
- Withstanding power outages.
- Withstanding all possible operating states.
As for what low-level technical requirements are feasible and how to test them, I have no knowledge on that.
In this link they specified 'how to change U-boot for SDCARD/MMC boot of A1000 mele box. They said to download U-boot from git clone http://git.hands.com/u-boot.git And they said to change the file "include/configs/suni4.h" in U-Boot directory. But it wasn't available. Can any one say that the file(include/configs/suni4.h) is missing with my u-boot directory or some other procedure to change u-boot for SDCARD/MMC boot.
Thanks in advance
You typoed the filename -- it's include/configs/sun4i.h (with the 4 and the i the other way round).
Also, the instructions say git checkout lichee-dev -- that's the branch that the file exists on -- did you do that bit? --Phil
Structure of the wiki
how about having a defined wiki structure? un unstructured wiki can be a bit of a nightmare.
perhaps have two areas where unverified stuff goes in one area and verified in another?
people could add to the unverified or "work in progress" area until such time as it is reasonably solid and then copy to the verified area. --Simon
lkcl10jul2016: hmmm good idea, heck of a lot going on though. what i'll do is enable the "map" plugin
How about using #eoma on irc.freenode.net?
lkcl10jul2016: good idea... but we have arm-netbook it's historical reasons yeahh i know...