All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] net/e1000: Fix EEPROM access error
Date: Sat, 18 Oct 2014 01:40:22 +0200	[thread overview]
Message-ID: <201410180140.22496.marex@denx.de> (raw)
In-Reply-To: <1413578646-18119-1-git-send-email-yorksun@freescale.com>

On Friday, October 17, 2014 at 10:44:06 PM, York Sun wrote:
> Commit 951860634fdb557bbb58e0f99215391bc0c29779 may have changed
> the logic unintentially from "if (!(swfw_sync & (fwmask | swmask)))"
> to "if ((swfw_sync & swmask) && !(swfw_sync & fwmask))". This change
> breaks some e1000 NIC with a message "ERROR: Unable to read EEPROM!".
> 
> Signed-off-by: York Sun <yorksun@freescale.com>
> CC: Marek Vasut <marex@denx.de>
> CC: Tim Harvey <tharvey@gateworks.com>
> ---
> Marek, please take a look at this change. I have no knowledge about
> e1000 driver. So I don't know if the original change was intended.
> Reverting this change fixes the problem I have on my board.
> 
>  drivers/net/e1000.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/e1000.c b/drivers/net/e1000.c
> index 6e8765c..b092867 100644
> --- a/drivers/net/e1000.c
> +++ b/drivers/net/e1000.c
> @@ -1113,7 +1113,7 @@ e1000_swfw_sync_acquire(struct e1000_hw *hw, uint16_t
> mask) return -E1000_ERR_SWFW_SYNC;
> 
>  		swfw_sync = E1000_READ_REG(hw, SW_FW_SYNC);
> -		if ((swfw_sync & swmask) && !(swfw_sync & fwmask))
> +		if (!(swfw_sync & (fwmask | swmask)))
>  			break;
> 
>  		/* firmware currently using resource (fwmask) */

+CC Marcel. Marcel, can you please take a look at this and test this with i210 
card ?

Thanks!

Best regards,
Marek Vasut

  reply	other threads:[~2014-10-17 23:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 20:44 [U-Boot] [RFC] net/e1000: Fix EEPROM access error York Sun
2014-10-17 23:40 ` Marek Vasut [this message]
2014-10-20 23:28   ` Marcel Ziswiler
2014-10-27 22:21 ` [U-Boot] [U-Boot,RFC] " Tom Rini

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=201410180140.22496.marex@denx.de \
    --to=marex@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.