From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] NET: Proper return code handling in eth_init() function in file eth.c
Date: Tue, 8 Jan 2008 15:26:41 +0100 [thread overview]
Message-ID: <200801081526.42284.sr@denx.de> (raw)
In-Reply-To: <bb58ac4d0711282246p3b8245bbhe112124a380eb462@mail.gmail.com>
On Thursday 29 November 2007, Upakul Barkakaty wrote:
> NET: Proper return code handling in eth_init() function in file eth.c
>
> This patch modifies the return code handling in the eth_init()
> function, to be compatible with the handling of the return codes in
> the other network stack files. It now returns a 0 on Success and -1 on
> error.
I just noticed that this patch breaks TFTP on 4xx platforms:
commit 505be87a65e4f87ad7d8da1d57ea4dcd487d7e32
Author: Upakul Barkakaty <upakul@gmail.com>
Date: Thu Nov 29 12:16:13 2007 +0530
NET: Proper return code handling in eth_init() function in file eth.c
This patch modifies the return code handling in the eth_init()
function, to be compatible with the handling of the return codes in
the other network stack files. It now returns a 0 on Success and -1 on
error.
Signed-off-by: Upakul Barkakaty <upakul.barkakaty@conexant.com>
Signed-off-by: Ben Warren <biggerbadderben@gmail.com>
I just see link auto-negotiation going on, and after that no real transaction
is happening! :-(
=> tftp 100000 u-image.bin
Waiting for PHY auto negotiation to complete.... done
ENET Speed is 1000 Mbps - FULL duplex connection (EMAC0)
Would be great if someone could look into this ASAP. Unfortunately I have no
time left today.
Thanks.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2008-01-08 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 6:04 [U-Boot-Users] [PATCH] NET: Proper return code handling in eth_init() function in file eth.c Upakul Barkakaty
2007-11-29 6:24 ` Stefan Roese
2007-11-29 6:46 ` Upakul Barkakaty
2008-01-08 14:26 ` Stefan Roese [this message]
2008-01-08 14:35 ` Upakul Barkakaty
2008-01-08 14:50 ` Upakul Barkakaty
2008-01-08 14:56 ` Ben Warren
2008-01-08 17:26 ` Stefan Roese
2008-01-08 21:10 ` Ben Warren
-- strict thread matches above, loose matches on Subject: below --
2007-11-28 5:18 Upakul Barkakaty
2007-11-28 15:39 ` Ben Warren
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=200801081526.42284.sr@denx.de \
--to=sr@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