From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Date: Sat, 13 Jun 2009 14:37:00 +0200
Subject: [U-Boot] [PATCH 2/2] at91sam9263ek: active watchdog support	via
	at91sam9263ek_wdt_config
In-Reply-To: <h100hl$1oe$3@ger.gmane.org>
References: <1233505762-23290-1-git-send-email-plagnioj@jcrosoft.com>
	<1233505762-23290-2-git-send-email-plagnioj@jcrosoft.com>
	<20090308231923.C8F86832E8B8@gemini.denx.de>
	<h100hl$1oe$3@ger.gmane.org>
Message-ID: <20090613123700.GD3814@game.jcrosoft.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 12:52 Sat 13 Jun     , Giulio Benetti wrote:
> In this way the linux driver won't work(the one by Renaud CERRATO).
> Because it expects MR register not to be set, or to be set enabled.
it's work we have test it
you need to enable it in the at91bootstrap or in your lowlevel board config
> 
> After I don't agree refreshing watchdog inside atmel_usart.c
you MUST do it otherwise you board will be not usable at all
simple exammple
you stop the boot and get a prompt if you do not type any command you reboot
it's not what we expect
> If u-boot hangs there instead of execute bootcmd, then the machine lies
> there forever.
> In my opinion we should put WATCHDOG_RESET() inside main_loop and nand write
> and read.
> What do you think?
NACK for the main_loop

nand read write ok

but if we excecute the bootcmd we have finished and jump to the os
so it's over for u-boot

the OS will have to care about the watchdog

Best Regards,
J.