public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] What if eth_init() fails?
Date: Wed, 14 Nov 2007 09:24:17 -0600	[thread overview]
Message-ID: <473B1321.2090305@freescale.com> (raw)
In-Reply-To: <13740586.post@talk.nabble.com>

Upakul Barkakaty wrote:
> Hi all, I observed that when the Ethernet initialization fails, it is 
> not properly halting the operation and exiting. On walking through the 
> Networking files, I saw that the eth_init() in eth.c either returns a 0 
> or 1. Now, in the NetLoop() in net.c file, from where the eth_init() 
> gets called, checks the condition if (eth_init(bd) < 0) { eth_halt(); 
> return(-1); } which is thus never true. Thus the network operation, 
> never exits gracefully, if Ethernet init fails. Any of you, have any 
> clues about this??

This is a known bug.  The problem is that it's been around for so long, people 
don't realize what's happening.  If you fix it, you might break something else.

I still think it should be fixed.  In fact, I was planning on submitting a patch 
next month for it.

-- 
Timur Tabi
Linux kernel developer at Freescale

  parent reply	other threads:[~2007-11-14 15:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14  6:21 [U-Boot-Users] What if eth_init() fails? Upakul Barkakaty
2007-11-14 11:07 ` Detlev Zundel
2007-11-16  6:13   ` Upakul Barkakaty
2007-11-16 12:29     ` Detlev Zundel
2007-11-16 16:27       ` Detlev Zundel
2007-11-16 16:35     ` Wolfgang Denk
2007-11-14 15:08 ` Ben Warren
2007-11-14 15:24 ` Timur Tabi [this message]
2007-11-14 16:49   ` Mike Frysinger
2007-11-14 16:53     ` Timur Tabi
2007-11-14 17:00       ` Mike Frysinger
  -- strict thread matches above, loose matches on Subject: below --
2007-11-19  4:37 Upakul Barkakaty
2007-11-19 13:26 ` Wolfgang Denk

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=473B1321.2090305@freescale.com \
    --to=timur@freescale.com \
    --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