[U-Boot-Users] CLI over Ethernet

[VanBaren, Gerald (AGRE)]

> -----Original Message-----
> From: u-boot-users-admin at lists.sourceforge.net
> [mailto:u-boot-users-admin at lists.sourceforge.net] On Behalf
> Of Srivatsan
> Sent: Monday, November 29, 2004 4:15 AM
> To: wd at denx.de
> Cc: u-boot-users at lists.sourceforge.net
> Subject: RE: [U-Boot-Users] CLI over Ethernet
>
> Hi all.

[snip]

>    Also I haven't asked for particular CLI (requirement with
> LLC) to be developed and given to me. What I have asked is
> the advantage of having CLI over Ethernet using LLC?

Nobody has done CLI over LLC for u-boot.  U-boot does support CLI over
UDP/IP/ethernet frames.  The conclusion is that to the current users of
u-boot, there is no advantage of CLI over LLC compared to CLI over
ethernet frames.

LLC isn't used much for 802.3 framing.  It has added complexity with no
obvious practical benefit.  I personally don't see any advantage of
using it and emperical evidence (e.g. not many are using it) would tend
to indicate others agree with my assessment.

For you with a requirement to do CLI over LLC, the equation is different
(unless you can talk your client into using "ethernet" 802.3 frames ;-).
Fortunately you have the source so you can do whatever CLI you wish over
any transport you care to write.  <applause>Open Source is
great.</applause>

gvb

[snip]

> With Best Regards,
> C.R.Srivatsan

******************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege.  If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager.  Please do not copy it for any purpose, or disclose its contents to any other person.  The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.  The recipient should check this e-mail and any attachments for the presence of viruses.  The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
******************************************