Dear Kumar, in message <[EMAIL PROTECTED]> you wrote: > > > Well, we have states - here you code that a certain operation is not > > allowed unless something else has been done before. SImilar > > dependencies may follow - after uncompressing and loading the kernel > > image it might for example be not allowed any more to turn on > > interrupts, etc. Of course we can handle all this in a maze of > > conditional statements. Or we could use a small state machine. > > So I'm not sure I completely understand what this state machine would > look like that you are thinking about.
It would describe legal state changes - each sub-command would only be allowed in a certain set of states, and if run cause a transition into another state. > I get the issue, just not seeing the implementation you are thinking > about. He, implementation. The details are left to the reader :-) Sorry, I'm not even thinking about any actual code yet. 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] "We don't care. We don't have to. We're the Phone Company." _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
