I'm working on an AVR32 with a funny system of warm boots caused by watchdog which don't fully reset the watchdog or real-time-counter hardware. I think the system allows RTC interrupts to be generated during or after the warm boot which can cause havoc with the existing code. It certainly means you have to rush to the watchdog and disable it within a second, or you'll loop.
but I have a modem which I need/want to handle in board-init, and it takes 1-second pulses to get it going.... I have found it reasonable to add an cpu_early_init leading into an clock_early_init. That means that board_early_init can run without any time pressure on it because WDT hasn't yet been stomped on. The early clock init can disable the WDT, then kill off RTC interrupts. Any good reason why I shouldn't upload a patch to cover this? Do I do it here, or on AVR32-specific u-boot list? David Collier www.dexdyne.com _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
