OK, tested on a v2 ASUS WL-500gP (BCM5354) and it really doesn't work. The reason is that the watchdog driver assumes that WDT is clocked by the SSB backplane clock (100/133MHz) and applies software prescaling to extend the WDT timeout to a useful range. This is true for some cores (4704, 5365, ...), but on 5354 the WDT seems to be clocked by a 32KHz clock, making the whole software prescaling logic unnecessary (I have established this empirically and would pretty much like if someone with access to 5354 datasheets could confirm).
The fix should be pretty straightforward, if I can determine whether software prescaling should be applied or not for a given core. So, if someone knows a reliable way to determine the WDT clock frequency based on the core revision and/or clock control registers, that would be much appreciated. I will hardcode a check for 5354 for now and, hopefully, have a patch ready in a few days. Regards, Aleksandar On 09/25/2010 07:57 PM, Alexey Loukianov wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > 25.09.2010 22:41, Aleksandar Radovanovic wrote: > >> Well, the thing is, I'm the developer of the original driver :) >> >> > I've been suspecting it :-). > > >> However, your assumptions about the way it works are wrong... >> If your kernel goes as well ... no hw wdt reset will be >> performed..., so it will expire and reset the board almost >> instantly. >> > Oh, it's good to know that I'd been wrong with it. > > Let's return to the original discussion. I've got some spare time to spend so > I > may try to debug the problem it you would give me some hints concerning how to > do it. Is it safe to build wdt driver as a module? What's about rmmod - is it > supported? Are there any dark kernel debuging voodoo tricks out there that > might > help to pinpoint the problem? > > - -- > Best regards, > Alexey Loukianov mailto:[email protected] > System Engineer, Mob.:+7(926)218-1320 > *nix Specialist > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEcBAEBAgAGBQJMnkYMAAoJEPB9BOdTkBULTA0H/3E9uJcLFWY8xc32TCk1fanX > q5y4It8SBqRPJP6rBtZ6/KlcqECQz10sqhLM+mVZQBpw0LgiO/c1kNJg7ab8kiNp > s5oUvkFK6xw1digzB69cBqQzKKWdgP46ufNO3WZ1tkSdGHlBwzXDplLqZq/Q8pFs > v0Qy43GXGTsDYHB/47l5qFteD6jYnw8Q6xIwb+xy+LsR2nSfVhcWPabfxXXcGDM5 > RLgWZpRtYT2t0rI9J3pgcN6AXZV7cHL/vv0QcSwMnnvEVuWH6oYpUWHNx//D4kQN > FcsCk4JzdtGcHBRunCD7yE3piF2r7n3N/i0eWAAOSj5Uq9Wi+DrmisirpWlJtMI= > =ZFaU > -----END PGP SIGNATURE----- > _______________________________________________ > openwrt-devel mailing list > [email protected] > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > > _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
