Dear Wolfram, in message <20111204114741.GA5788@xxxxxxxxxxxxxx> you wrote: > > > Description: OSDL CGL specifies that carrier grade Linux > > shall provide support for detecting a repeating reboot cycle > > due to recurring failures. This detection should happen in > > user space before system services are started. > > So, technically, a flag would be enough, not necessarily a counter? Although a > counter probably has more advantages... The real-life applications we have seen so far all required a counter. They all required to switch to a recovery mode or other alternative boot sequence after N failed boot attempts, with N > 1 in all cases. > > reg = <0x23060 0x20>; > > I assume that non-volatile memory would qualify as a boot-counter, so those > could be tied to I2C busses etc? reg would not fit then. Actually all kind of non-volatile storage can be used - it depends on specific hardware roperties. Some SoCs have registers that are guaranteed not to change theier value during a reset; on other systems we have storage or NVRAM in RTCs or similar, or we can use SRAM, or I2C or SPI attached EEPROM, or even storage on SDCard, USB or other storage devices. This binding covers the memory type only. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@xxxxxxx "There is nothing new under the sun, but there are lots of old things we don't know yet." - Ambrose Bierce -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
