Dear C.R.Srivatsan,
in message 002901c4d5d0$c1447720$4501a8c0@bgcw301 you wrote:
There is indeed a requirement to have CLI over Ethernet using LLC. I
This may be a requirement for you, but please understand that it is a non-requirement for U-Boot.
wanted to know the best mechanism to provide CLI over Ethernet (Whether it is through UDP or through LLC). If it uses UDP then uboot already provides me with one alternatively if it uses LLC then it has to be rewritten.
I'm not sure if you actually mean what you say and how you say it, or maybe it's my limited understanding of the English language which makes me feel somewhat angry: this is free software, and instead of being thankful for finding a powerful tool for free yoiu come up with semi-mandatory staments like "there is a requirement" or "it has to be rewritten." I would not like this tone if I was your subordinate, which I definitely am not.
This is a free software poroject, so if you want to see it extended you can either cointribute yourself by submitting patches, or you can hire someone to implement what you want, but please do not expect that everybody on this list starts hacking just because you feel you have a requirement.
I have one question to the uboot's design team, why was UDP chosenfor CLI on Ethernet?
Why not? UDP is a common standard protocol. You can use existing standard tools to receive and send UDP messages (see netcat). Most of all, this way the implementation is compatible to the netconsole implementation used by Linux, so we have a standard console protocol for both U-Boot and Linux.
Best regards,
Wolfgang Denk