Now that we have Kconfig, I think this check can disappear. Is there a
way
to un-define CONFIG_RAMTOP?
With RAMTOP being
config RAMTOP hex default 0x200000
it can't happen.
But I didn't want to change the rough logical flow with self-acked code, so I thought I better leave an error check too many in there ;-)
I agree that it's good to be careful.
I think it clutters this file to have so many checks. I wonder if there should be some central file for checking Kconfig variables.
Thanks, Myles