diff options
authorhellekin <>2016-07-31 17:13:59 +0000
committerhellekin <>2016-08-09 20:11:34 +0000
commitc027137515e385497e5a8dccdf896797354a6d34 (patch)
parentb3ecbc2b86938e60813fc3811103f8f139560992 (diff)
More WIP on KiCad
1 files changed, 60 insertions, 3 deletions
diff --git a/content/0021-migrating-away-from-eagle-to-kicad.html b/content/0021-migrating-away-from-eagle-to-kicad.html
index 1886043..b5c8e21 100644
--- a/content/0021-migrating-away-from-eagle-to-kicad.html
+++ b/content/0021-migrating-away-from-eagle-to-kicad.html
@@ -24,6 +24,7 @@
<li><a href="#asn1-vulnerability">ASN.1 Vulnerability</a></li>
<li><a href="#more-n900-sourcing">More N900 Sourcing</a></li>
+ <li><a href="#neo900-whitepapers">Whitepapers Update</a></li>
<li><a href="#feature">From Eagle to KiCad</a><li>
@@ -35,7 +36,7 @@
billions of phone users worldwide. The proprietary software
vendor received a bug report via <em>plain text email</em> on
June, 1<sup>st</sup>, 2016, according to
- the <a href="">CVE-2016-5080</a>
+ the <a href="">CVE-2016-5080</a>
released on July, 18<sup>th</sup>, 2016 to the public in a
coordinated release with the vendor.</p>
@@ -85,18 +86,74 @@
units responding to our quality criteria for enduring the
metamorphosis into brand new Neo900 units for you lucky (and
patient) early birds. 20 more units are on the way, and we
- expect more to come. We're already at XXX units and
+ expect more to come. We're already at 70 units and
<p>Again, if you know where to find some affordable stocks of N900
please <a href="">contact
- us</a>!</p>
+ us</a>!</p>
+ <h3 id="neo900-whitepapers">Whitepapers Update</h3>
+ <p>While we're at it, and to continue building momentum for
+ our <a href="#feature">main feature</a> today, like if you were
+ too early at the movies, let's have a look at what our mad
+ scientists concocted since last June.</p>
+ <p>
+ <p>You can always follow our whitepapers updates directly from
+ Werner in
+ the <a href="">Neo900
+ Announcements</a> thread on, and access the whole
+ up-to-date whitepaper collection from
+ the <a href="">Resources section</a>
+ at</p>
+ <p>And now, without further ado, our main feature!</p>
<h3 id="feature">From Eagle to KiCad</h3>
+ <p>When Joerg took charge of the Neo900 project, the electronics
+ design was made with Eagle, and was updated using that tool ever
+ since. Nikolaus, of OpenPandora fame, was the Eagle virtuoso,
+ but our communication with his company, Golden Delicious, was
+ hampered for a long time by incompatible tools and workflow.</p>
+ <p>In 2016, Nikolaus faded away from Neo900, absorbed by Neo900's
+ sister project <a href="">Pyra</a>.
+ Just a few weeks ago he confirmed that he couldn't follow up on
+ the layout for Neo900, which prompted Joerg and Werner to
+ consider alternatives.</p>
+ <p>In the <abbr title="Electronics Design Automation">EDA</abbr>
+ market, besides Eagle, there's Altium. But Altium has the same
+ flaw as Eagle: it's proprietary, and moreover, it's quite
+ expensive. Our rationalizing mind wants to say there's cognitive
+ dissonance in using non-free software for a free hardware
+ project. And in hindsight, this sounds like a good
+ rationalization.</p>
+ <p>Among the open-source alternatives to Eagle (let's leave Altium
+ in its own class), <a href="">Fritzing</a>
+ didn't match our need for multilayer board support;
+ between <a href="">gEDA</a>
+ and <a href="">KiCad</a>, the choice was
+ easy: the latter is much more popular, backed up
+ by <abbr title="Centre Européen de Recherche
+ Nucléaire">CERN</abbr> as part of
+ the <a href="">Open
+ Hardware Initiative</a>, and there are discussions to share
+ codebase between the two projects [ref needed].</p>
+ <p>We found out that KiCad's routing capabilities are superior to
+ Eagle's. [anything to add there?] </p>
<p>Thank you for your attention,</p>
<p>&ndash; hellekin for the Neo900 team</p>