[U-Boot-Users] CLI over Ethernet

[Srivatsan]

Hi all,

    Thanks for the reply Mr.Detlev Zundel.

    There is indeed a requirement to have CLI over Ethernet using LLC. I
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.

    If any one has tried out CLI over Ethernet using LLC or if anyone
has done a study on LLC, then please share your experiences with me. 

    I have one question to the uboot's design team, why was UDP chosen
for CLI on Ethernet?     

With Thanks and Best Regards,
C.R.Srivatsan

    

-----Original Message-----
From: Detlev Zundel [mailto:dzu at denx.de] 
Sent: Thursday, November 25, 2004 10:22 PM
To: Srivatsan
Cc: u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] CLI over Ethernet

Hi Srivatsan,

>     Greetings. There is a requirement to provide CLI over Ethernet in
> uboot.

Really?  There is a requirement?  Anyway, check doc/README.NetConsole.

>     1) The CLI works over LAN (not using TCP/IP) using Logical link
> control Layer. (Is this possible?)

It actually works over UDP.

>     2) Anyone who has done a similar stuff has any advice for us? (Not
> in negative :-))

I guess everything is in place - just use it.

>     3) Is there any documentation or RFC available which talks of
> (Ethernet) connectivity at LLC layer? 
>
> Thanks and Best Regards,
> C.R.Srivatsan 
>     
>
> -----Original Message-----
> From: u-boot-users-admin at lists.sourceforge.net
> [mailto:u-boot-users-admin at lists.sourceforge.net] On Behalf Of
> u-boot-users-request at lists.sourceforge.net
> Sent: Wednesday, November 24, 2004 8:43 PM
> To: u-boot-users at lists.sourceforge.net
> Subject: U-Boot-Users digest, Vol 1 #1106 - 13 msgs
>
> Send U-Boot-Users mailing list submissions to
> 	u-boot-users at lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.sourceforge.net/lists/listinfo/u-boot-users
> or, via email, send a message with subject or body 'help' to
> 	u-boot-users-request at lists.sourceforge.net
>
> You can reach the person managing the list at
> 	u-boot-users-admin at lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of U-Boot-Users digest..."
>
>
> Today's Topics:
>
>    1. RE: CONFIG_BOOTBINFUNC for AT91RM9200 (Friedrich, Lars)
>    2. question on drive (zhonglei)
>    3. boot problem (Alessio Raccis)
>    4. Re: question on drive (Marc Leeman)
>    5. boot problem (Alessio Raccis)
>    6. R: [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200 (Paolo
> Broggini)
>    7. Re: CONFIG_BOOTBINFUNC for AT91RM9200 (Wolfgang Denk)
>    8. Re: boot problem (Wolfgang Denk)
>    9. Re: question on drive (Wolfgang Denk)
>   10. Re: question on drive (Marc Leeman)
>   11. RE: CONFIG_BOOTBINFUNC for AT91RM9200 (Paugam Luc)
>   12. Re: CONFIG_BOOTBINFUNC for AT91RM9200 (Steven Scholz)
>   13. Re: CONFIG_BOOTBINFUNC for AT91RM9200 (Wolfgang Denk)

[...]

>
************************************************************************
****

Do you really think it neccessary to include the _whole digest mail_
in a question introducing a new thread?  Please think about that in
the future, even if it takes a few more keystrokes.

Cheers
  Detlev

-- 
Greenspun's Tenth Rule of Programming: "Any sufficiently complicated C
or Fortran program contains an ad-hoc, informally-specified bug-ridden
slow implementation of half of Common Lisp."




********************************DISCLAIMER**********************************

This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege of Deccanet Designs Ltd.
If you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you are strictly prohibited from retaining, using, copying, altering or
disclosing the contents of this message.

****************************************************************************