summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhellekin <hellekin@dyne.org>2016-07-31 17:46:27 +0000
committerhellekin <hellekin@dyne.org>2016-07-31 17:46:27 +0000
commitfa1ec59f515e6159594f007e6ced5aefdd878001 (patch)
tree1226d7df4c0486b46ada7369d017fcd58a448841
parent4853f96e1fd50a58bd8bec209efe8556e96c53d0 (diff)
downloadwww-fa1ec59f515e6159594f007e6ced5aefdd878001.tar.gz
www-fa1ec59f515e6159594f007e6ced5aefdd878001.tar.bz2
www-fa1ec59f515e6159594f007e6ced5aefdd878001.zip
More WIP on dev with KiCad + progress
-rw-r--r--content/0021-migrating-away-from-eagle-to-kicad.html26
1 files changed, 25 insertions, 1 deletions
diff --git a/content/0021-migrating-away-from-eagle-to-kicad.html b/content/0021-migrating-away-from-eagle-to-kicad.html
index b5c8e21..5ef0f58 100644
--- a/content/0021-migrating-away-from-eagle-to-kicad.html
+++ b/content/0021-migrating-away-from-eagle-to-kicad.html
@@ -147,12 +147,36 @@
Hardware Initiative</a>, and there are discussions to share
codebase between the two projects [ref needed].</p>
+ <h4>How does the move to KiCad influence Neo900 development?</h4>
+
+ <p>The only major downside comes from the reduced access to
+ Nikolaus' OMAP know-how, although we hope Nikolaus will be able to
+ review our work. On the other hand, we're no longer slowed down
+ by uncertainty with regard to the future role of Golden Delicious
+ in Neo900: this caused change requests to pile up, and we used
+ white papers as a means of documenting what we couldn't change in
+ the schematics in a timely manner.</p>
+
+ <p>That gives us wings: with KiCad, we can now provide a more
+ transparent development process and can now operate in a more
+ schematics-centric mode, using white papers only where something
+ actually needs explaining.</p>
+
<p>We found out that KiCad's routing capabilities are superior to
Eagle's. [anything to add there?] </p>
- <p>...</p>
+ <h4>What's the progress on converting Neo900 schematics from Eagle
+ to KiCad?</h4>
+
+ <p>Progress is surprisingly fast. We already completed the bulk of
+ the conversion, and are now fixing bugs (some discovered during
+ the conversion,
+ and <a href="https://bugs.launchpad.net/kicad/+bug/1154131/comments/9">also
+ in KiCad</a>.)</p>
+ <p>In the coming weeks we're going to work on incorporating material <em>parked</em> in whitepapers (see above), [maybe leave that alone for now:] define the BB-mX interface for prototype v2 (...)</p>
+ <p>...</p>
<p>Thank you for your attention,</p>