--- On Thu, 26/3/09, Florian Fainelli <flor...@openwrt.org> wrote:
>
> now, the mainline
> kernel does not probably boot correctly on any RDC 321x SoC
> due to no way to
> set the tick rate properly with everything that it implies
> on the other
> peripherals.
I guess run-time detection is ideal, however not sure how it could be
done if it depends on clock speed.
In include/asm-x86/timex.h we seem to have a hard-coded value for R8610:
#elif defined(CONFIG_X86_RDC321X)
# define PIT_TICK_RATE 1041667 /* Underlying HZ for R8610 */
#else
So presumably it can be hard-coded for other RDC variants with a config
option. First thing I have to know is which number to use. I am running a
S3282 (see www.bifferos.com), which is register-identical to R8610/R321x, but
running at 150MHz with external 25MHz xtal.
I have mainline 2.6.27.5 with nothing more than LZMA patch booting with very
few issues aside from failure to get DHCP lease. If the tick might be causing
this problem, I'd be interested to fix this.
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
