diff README @ 110:6ed76fdb72d5

README: better explanation of current status and what needs to be done next
author Mychaela Falconia <falcon@freecalypso.org>
date Sat, 28 Jul 2018 06:37:29 +0000
parents af6b7fcf7823
children ee67197fd2e5
line wrap: on
line diff
--- a/README	Tue Jul 24 23:55:24 2018 +0000
+++ b/README	Sat Jul 28 06:37:29 2018 +0000
@@ -29,15 +29,15 @@
 * It is now possible to compile the full-featured fw with gcc without disabling
   GPRS (no more crash on boot), but actually using GPRS doesn't work: pppd
   establishes the point-to-point connection to the network's GGSN and gets an
-  IP address, but the trying to ping through this established connection causes
+  IP address, but then trying to ping through this established connection causes
   the fw to crash.
 
 * Voice, SMS and CSD appear to work in the gcc-built version, but this firmware
   is not as stable as Magnetite hybrid: I saw some occasional glitches which I
   did not investigate further.
 
-Compared to FC Citrine, the present FC Selenite firmware built with gcc offers
-the following:
+Compared to FC Citrine (our previous attempt at gcc-built fw), the present
+FC Selenite firmware built with gcc already offers the following:
 
 * CSD support;
 
@@ -46,6 +46,37 @@
 * Newer code: FC Selenite branched off Magnetite in 2018-07,
   whereas FC Citrine has been unmaintained since 2016-10.
 
-At the present time the Mother has no plans to do any further work on this
-experimental gcc-built fw, unless someone comes forth with a strong commercial
-interest backed by substantial funding.
+Because FC Selenite gcc already does everything that FC Citrine could do and
+more, and is no less free, FC Citrine is now officially fully retired.
+
+As the next step, someone needs to do the work of tracking down and debugging
+all of the issues seen in the gcc-built version, and make it work as well as
+the original TMS470-built configuration.  However, I (Mother Mychaela) am not
+currently allocating my time toward that work because I see other directions
+within the greater FreeCalypso family of projects as being more important.
+Specifically, I see the following as much higher priorities compared to
+gcc-built firmware:
+
+* Getting our FCDEV3B V2 boards made to prove my proposed fix for the sleep
+  mode bug, and if they work as expected, we'll need to make more FreeCalypso
+  modem hw in various form factors and put that hw into the hands of end users.
+  Software or firmware without hardware to run it on is useless no matter how
+  good or how free/libre it is, hence it makes no sense to me to worry whether
+  our fw is built with gcc or with TI's TMS470 compiler until the hardware
+  that's needed to run it is made in greater volume and placed into the hands
+  of people who would appreciate it.
+
+* Getting the digital voice channel over MCSI working, which is a prerequisite
+  before we can repackage our FreeCalypso modem into a module form factor which
+  could then be marketed to communities like Neo900 and Librem 5 as a drop-in
+  replacement for the 100% closed and proprietary modem modules they use
+  currently.
+
+* Building our long-planned FreeCalypso Libre Dumbphone hardware, so we can
+  have a complete phone without needing someone else like Neo900 or Librem 5 or
+  ZeroPhone to provide an application processor front-end to our modem.
+
+Anyone else who feels that whipping the gcc-built fw version into shape should
+be a higher priority has two options: either do the work themselves (the code
+is free for everyone), or pay Falconia Partners LLC to elevate the priority of
+this gcc-built fw work.