You may want to verify that parameter parsing routine that figures
out the memory size on EBSA285 actually returns correct size for
the size of DRAM. I noticed that for EBSA285 this is not being
done correctly if you don't pass the parameters explicitly in
boot parameter. This results in hard-to-debug bad behavior during
bootup sequence -- around memory mapping setting.
--
Hwa Jin Bae
PSO Systems Inc
[EMAIL PROTECTED]
http://www.pso.com
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
