mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Holger Freyther <holger@freyther.de>
Cc: barebox@lists.infradead.org
Subject: Re: Activating network during start
Date: Fri, 21 Nov 2014 08:11:16 +0100	[thread overview]
Message-ID: <20141121071116.GP30369@pengutronix.de> (raw)
In-Reply-To: <loom.20141120T214035-355@post.gmane.org>

Hi Holger,

On Thu, Nov 20, 2014 at 08:50:17PM +0000, Holger Freyther wrote:
> Good Evening,
> 
> I wrote a small command to send a LLDP frame over the network. Then I
> tried to integrate this command into the start script but I noticed that
> while a message is printed on the console no actual packet is being
> sent on the wire.
> 
> I am using a Phytec AM335X SoM and I am not on the latest version of
> barebox either so this might be something that is already fixed.
> 
> My assumption is that when I use eth_get_current/eth_send the network
> is being activated. I had a quick look at the return code of eth_send
> to see if I could see that my packet has been dropped but in both
> success/failure the method returns 0. Is this to be expected? My
> interim solution is to add a sleep after the first command invocation
> and then do it again?

I don't understand what the exact problem is. So your command generally
works, only when it's called from the start script it doesn't work. Did
I get that correctly? Also a second invocation of the command then
works, right?
This sounds like the phy is not yet ready. I often get the impression
that the very first packet sent to the network is lost, even though the
phy registers tell us the phy is ready. I never found out what the
problem is here.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-11-21  7:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 20:50 Holger Freyther
2014-11-21  7:11 ` Sascha Hauer [this message]
2014-11-21  8:40   ` Holger Hans Peter Freyther
2014-11-21  9:18     ` Sascha Hauer
2014-11-21  9:20     ` Sascha Hauer

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=20141121071116.GP30369@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=holger@freyther.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