public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 18:26:49 +0100	[thread overview]
Message-ID: <200801081826.49556.sr@denx.de> (raw)
In-Reply-To: <47838F20.6020905@gmail.com>

On Tuesday 08 January 2008, Ben Warren wrote:
> > Probably i got the reason why this is happening. As a convention that
> > is usually followed, the code in eth_init() function in the file eth.c
> > was reworked to handle 0 in case of Success and any non zero value in
> > case of an error.
> >
> > Most of the Ethernet driver's init routines adhere to the same
> > convention of returning a 0 on Success and a non zero value in case of
> > error. However, the driver you might be using, may be returning a non
> > zero value on Successful initialization, that is why the problem is
> > arising. The solution could be to return 0 in case of Success, from
> > the Ethernet driver's init() routine.
> >
> > Thanks!!
> >
> > --
> > Regards,
> > Upakul Barkakaty
>
> Yeah, looks like ppc_4xx_eth_init() (cpu/ppc4xx/4xx_enet.c) returns 1 on
> success and -1 on failure.  I don't have hardware to test this.  Can you
> check it out Stefan?  Let's look through the other drivers to see if
> this is an isolated case.

I'm back now and will give it a try this evening. Thanks for pointing this 
out.

Note: This patch may trigger other platform ethernet driver problems as well. 
So I strongly encourage all platform maintainers/custodians to check if a 
change in the return code of the ethernet driver is needed.

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

  reply	other threads:[~2008-01-08 17: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
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 [this message]
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=200801081826.49556.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