FreeCalypso > hg > fc-magnetite
view src/cs/drivers/drv_app/ffs/board/effs.c @ 636:57e67ca2e1cb
pcmdata.c: default +CGMI to "FreeCalypso" and +CGMM to model
The present change has no effect whatsoever on Falconia-made and Openmoko-made
devices on which /pcm/CGMI and /pcm/CGMM files have been programmed in FFS
with sensible ID strings by the respective factories, but what should AT+CGMI
and AT+CGMM queries return when the device is a Huawei GTM900 or Tango modem
that has been converted to FreeCalypso with a firmware change? Before the
present change they would return compiled-in defaults of "<manufacturer>" and
"<model>", respectively; with the present change the firmware will self-identify
as "FreeCalypso GTM900-FC" or "FreeCalypso Tango" on the two respective targets.
This firmware identification will become important if someone incorporates an
FC-converted GTM900 or Tango modem into a ZeroPhone-style smartphone where some
high-level software like ofono will be talking to the modem and will need to
properly identify this modem as FreeCalypso, as opposed to some other AT command
modem flavor with different quirks.
In technical terms, the compiled-in default for the AT+CGMI query (which will
always be overridden by the /pcm/CGMI file in FFS if one is present) is now
"FreeCalypso" in all configs on all targets; the compiled-in default for the
AT+CGMM query (likewise always overridden by /pcm/CGMM if present) is
"GTM900-FC" if CONFIG_TARGET_GTM900 or "Tango" if CONFIG_TARGET_TANGO or the
original default of "<model>" otherwise.
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Sun, 19 Jan 2020 20:14:58 +0000 |
parents | 945cf7f506b2 |
children |
line wrap: on
line source
/* This file is autogenerated --- do not edit. */ #include "ffs/ffs.h" char *ffs_strerror(effs_t error) { switch (error) { case EFFS_OK: return "ok"; /* 0 */ case EFFS_NODEVICE: return "flash device unknown"; /* -1 */ case EFFS_CORRUPTED: return "filesystem corrupted!?"; /* -2 */ case EFFS_NOPREFORMAT: return "ffs not preformatted"; /* -3 */ case EFFS_NOFORMAT: return "ffs not formatted"; /* -4 */ case EFFS_BADFORMAT: return "incompatible ffs version, re-format needed"; /* -5 */ case EFFS_MAGIC: return "bad magic"; /* -6 */ case EFFS_AGAIN: return "not ready, try again later"; /* -7 */ case EFFS_NOSYS: return "function not implemented"; /* -8 */ case EFFS_DRIVER: return "ffs device driver error"; /* -9 */ case EFFS_NOSPACE: return "out of data space"; /* -10 */ case EFFS_FSFULL: return "file system full, no free inodes"; /* -11 */ case EFFS_BADNAME: return "bad filename"; /* -12 */ case EFFS_NOTFOUND: return "object not found"; /* -13 */ case EFFS_EXISTS: return "object exists"; /* -14 */ case EFFS_ACCESS: return "access permission violation"; /* -15 */ case EFFS_NAMETOOLONG: return "filename too long"; /* -16 */ case EFFS_INVALID: return "invalid argument"; /* -17 */ case EFFS_DIRNOTEMPTY: return "directory not empty"; /* -18 */ case EFFS_NOTADIR: return "object is not a directory"; /* -19 */ case EFFS_SPARE: return "SPARE"; /* -20 */ case EFFS_FILETOOBIG: return "file too big"; /* -21 */ case EFFS_NOTAFILE: return "object is not a file"; /* -22 */ case EFFS_PATHTOODEEP: return "path too deep"; /* -23 */ case EFFS_NUMFD: return "Max number of open files reached"; /* -24 */ case EFFS_BADFD: return "Bad file descriptor"; /* -25 */ case EFFS_BADOP: return "Bad operation"; /* -26 */ case EFFS_LOCKED: return "The file is locked"; /* -27 */ case EFFS_TOOBIG: return "too big (tmffs buffer overflow)"; /* -30 */ case EFFS_MEMORY: return "out of memory"; /* -31 */ case EFFS_MSGSEND: return "message send failed"; /* -32 */ case EFFS_SIBLINGLOOP: return "directory sibling loop"; /* -40 */ case EFFS_NOBLOCKS: return "No more blocks!?"; /* -41 */ case EFFS_DBR: return "Data reclaim did not finish!?"; /* -42 */ default: return "unknown ffs error code!"; } }