Dear "kevin.morf...@fearnside-systems.co.uk", In message <4b1e76e9.2050...@fearnside-systems.co.uk> you wrote: > > I would've thought that you need a working stack before you can run > 'C' code so you'd need the RAM timing set up before you could run
In general this is correct, but then - what does a C program need a stack for? To push register contents and local variables on it. So if you make sure not to use any, it works even without a stack ;-) > C code hence you'd need to set the RAM timings up in assembler. This is not actually true. You _can_ do this in C even here. Also, some processors and some boards provide on-chip-memory and/or static RAM areas that can be used for an initial stack and data, and on some processors we can lock parts of the (data) cache and use it as RAM. There is many ways to do this. > At the moment the RAM timings for a specific board are set in the > board-specific lowlevel_init assembler code. Any change would > affect all s3c24x0 boards as well as the new edb93xx board. I don't see how an implementation for a specific CPU / board would cause changes to other processors? Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de I believe you find life such a problem because you think there are the good people and the bad people. You're wrong, of course. There are, always and only, the bad people, but some of them are on oppo- site sides. - Terry Pratchett, _Guards! Guards!_ _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
