public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] NetConsole & TFTP
Date: Fri, 23 Mar 2012 20:46:52 +0100	[thread overview]
Message-ID: <20120323194652.8FAFF200056@gemini.denx.de> (raw)
In-Reply-To: <OF0B4B1E6C.B54B0C2D-ONC12579CA.0038E059-C12579CA.0038F311@sick.de>

Dear Thomas,

In message <OF0B4B1E6C.B54B0C2D-ONC12579CA.0038E059-C12579CA.0038F311@sick.de> you wrote:
>
> Is it possible to use NetConsole and TFTP parallel at one Ethernet 
> interface? My fist thoughts were that this could be possible, because TFTP

Yes, this is supposed to work.  We've even seen running TFTP and
Netconsole over Ethernet over USB...

> and NetConsole use different ports. But out of the box the behavior is 
> different. In my tests TFTP tries to use another Ethernet interface 
> (eTSEC1) as the NetConsole (eTSEC0), but the final Hardware has only one 

Hm... you are not running mainline code, right?  Because we always
have a single network interface active at any time.

> Therefore I need a possibility to communicate with a target (via 
> NetConsole) and transfer the flash images (via TFTP). Has anybody 
> experiences with this? Is this possible with U-Boot? Maybe I am doing 
> something wrong?

I recommend you undo any modifications made to the network stack,
and/or try plain mainline code instead.

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: wd at denx.de
Premature optimization is the root of all evil.         -- D.E. Knuth

  reply	other threads:[~2012-03-23 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23 10:22 [U-Boot] NetConsole & TFTP Thomas Pohl
2012-03-23 19:46 ` Wolfgang Denk [this message]
2012-03-26 10:24   ` [U-Boot] Antwort: " Thomas Pohl
2012-07-23 22:30     ` Joe Hershberger

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=20120323194652.8FAFF200056@gemini.denx.de \
    --to=wd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox