In message <[EMAIL PROTECTED]> you wrote: > > I tried to dig into this issue, and found that, U-Boot for NAND Flash is > designed the same way. The function "nand_init" gets invoked after > "env_init" and "serial_init", and sue to this U-Boot always uses the > default baudrate.
Thjis is a dilemma - U-Boot tries to support porting and debugging by enabling the serial console very, very early, typically long before relocation to RAM. In this state, we have only a verly limited environment - small stack, no writable data segment, no BSS, etc. This is not sufficient for the (pretty complicated) NAND flash driver. So U-Boot cannot read the baudrate setting from the environment in NAND... 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: [EMAIL PROTECTED] Remember, an int is not always 16 bits. I'm not sure, but if the 80386 is one step closer to Intel's slugfest with the CPU curve that is aymptotically approaching a real machine, perhaps an int has been implemented as 32 bits by some Unix vendors...? - Derek Terveer ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ U-Boot-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/u-boot-users
