Changes between Version 23 and Version 24 of faq

08/24/2018 09:54:27 PM (4 years ago)
Bobby Jones

Corrected various bits of information in missing gsc driver related question.


  • faq

    v23 v24  
    265265No, this feature is not available on any Gateworks SBC.  In most cases using POE will be the most effective method of powering on and off the board with Ethernet. 
    267 == I'm using mainline Linux, or do not have a GSC driver.  What do I loose and is there a work around?
     267== I'm using a version of Linux without a GSC driver, what do I lose and is there a work around?
    269269Getting 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:
    275275 *
    276276 *
    277 * You can achieve tamper protection using GPIO.
    278  *
     277* Linux input event support will be lost, there is currently no work around for this.
     278 *
    279279* 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.
    280280 *
    281 * Reset monitor, for this you will need a GSC driver.
    282  *
    283 * Software field-upgradable firmware, sysupgrade is available in our pre-release of Gateworks-OpenWrt 18.0x and mainline OpenWrt 18.06
    284  *
    285  * Also, you can use TFTP to flash firmware from the boot loader
    286   *
    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.
     281* Field firmware updates (via gsc_update tool) do not depend on the gsc driver
     282 *