All of lore.kernel.org
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CLI over Ethernet
Date: Mon, 29 Nov 2004 19:39:46 +0100	[thread overview]
Message-ID: <87mzx0o5xp.fsf@deepthought.outer.space.org> (raw)
In-Reply-To: <003601c4d5f3$ec391670$4501a8c0@bgcw301> (srivatsan@deccanetworld.com's message of "Mon, 29 Nov 2004 14:45:08 +0530")

Hi Srivatsan,

> Had I mentioned requirement for the group or the code has to rewritten
> by uboot group which I know is ethically wrong then I would have made a
> mistake. But I just required all your help to give me a head start with
> the available resources for my problem.

Don't worry - It was simply kind of amusing that you told us "there is
a requirement to support ...." without the "in our project" part that
I expected.  Lets get back to (hopefully) solid facts.

>    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? 

This is an interesting question and probably you have an answer for
us?  Reading up on LLC I am not really sure what a CLI implementation
would give us - despite the need for a completely separate set of
tools to work with this protocol.  Using UDP (belonging to the IP
family) we can simply use the heapload of utilities available -
especially "netcat" comes to mind.

The netconsole support was written with this in mind to support (as
Wolfgang said) a seamless networking console for the U-Boot / Linux
combination.  The Linux netconsole support predates the netconsole in
U-Boot so it was clear that we would go for compatibility with this
implementation.

> This group is not for showing emotions.

[complete quote snipped]

It is also not for posting complete quotes.  Please try to understand
that it is a waste of bandwidth and of our time to include these
completely useless text parts.  I can always look up the old mails if
I want to see these bits - E-Mail can be very efficient so please try
to use it in this spirirt - even if this entails the 15 minutes it
takes to read the netiquette.

Cheers
  Detlev

-- 
Once the  implementation is  up and running,  it is still a trick to keep it
running.  In a normal,  closed implementation,  this is not a problem;  in a
system with metaobject protocols [..] there is the potential for spectacular
failure modes if certain situations are not properly anticipated.
                                       -- The Art of the Metaobject Protocol

  reply	other threads:[~2004-11-29 18:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1CWyul-0005AO-59@sc8-sf-list1.sourceforge.net>
2004-11-25 10:13 ` [U-Boot-Users] CLI over Ethernet Srivatsan
2004-11-25 16:52   ` Detlev Zundel
2004-11-29  5:03     ` Srivatsan
2004-11-29  8:27       ` Wolfgang Denk
2004-11-29  9:15         ` Srivatsan
2004-11-29 18:39           ` Detlev Zundel [this message]
2004-12-22  9:24             ` [U-Boot-Users] Uboot Netconsole support Srivatsan
2004-12-22 11:06               ` Wolfgang Denk
2004-12-22 12:39                 ` Srivatsan
2004-12-22 14:48                   ` Wolfgang Denk
2004-11-29 15:22 [U-Boot-Users] CLI over Ethernet VanBaren, Gerald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mzx0o5xp.fsf@deepthought.outer.space.org \
    --to=dzu@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.