| | 267 | == I'm using mainline Linux, or do not have a GSC driver. What do I loose and is there a work around? |
| | 268 | |
| | 269 | Getting our GSC driver to be adopted by the mainline kernel community has been an up hill battle, hence the long delay in its implementation. Many of its features are still accessible using I2C commands and other methods: |
| | 270 | * The RTC is compatible with the standard Linux ds1672 RTC driver and thus works with the standard Linux RTC device API. |
| | 271 | * http://trac.gateworks.com/wiki/gsc#RealTimeClock |
| | 272 | * Voltage and temperature monitoring can be accomplished using I2C commands. |
| | 273 | * http://trac.gateworks.com/wiki/gsc#SystemTemperatureandVoltageMonitor |
| | 274 | * GPIO expansion does not require GSC drivers. |
| | 275 | * http://trac.gateworks.com/wiki/gsc#GeneralPurposeInputandOutputGPIO |
| | 276 | * http://trac.gateworks.com/wiki/gpio |
| | 277 | * You can achieve tamper protection using GPIO. |
| | 278 | * http://trac.gateworks.com/wiki/gsc#GeneralPurposeInputandOutputGPIO |
| | 279 | * Hardware watchdog, this is where you may run into trouble using GSC, though the CPU watchdog will be adequate in many cases. The issue here will be the inability for the GSC to disable board power. |
| | 280 | * http://trac.gateworks.com/wiki/gsc#HardwareWatchdog |
| | 281 | * Reset monitor, for this you will need a GSC driver. |
| | 282 | * http://trac.gateworks.com/wiki/gsc#ResetMonitor |
| | 283 | * Software field-upgradable firmware, sysupgrade is available in our pre-release of Gateworks-OpenWrt 18.0x and mainline OpenWrt 18.06 |
| | 284 | * http://trac.gateworks.com/wiki/OpenWrt/sysupgrade |
| | 285 | * Also, you can use TFTP to flash firmware from the boot loader |
| | 286 | * http://trac.gateworks.com/wiki/ventana/openwrt#InstallingFirmwareviaSerialEthernetTFTPusingthebootloader |
| | 287 | * None of these methods will allow you to update u-boot, or SPL. This must be done with Jtag, even when the GSC driver is available. |
