From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] e1000: add i211 and unprogrammed i210/i211 support
Date: Thu, 11 Sep 2014 01:46:05 +0200 [thread overview]
Message-ID: <201409110146.05991.marex@denx.de> (raw)
In-Reply-To: <1410383900.16012.24.camel@localhost.localdomain>
On Wednesday, September 10, 2014 at 11:18:20 PM, Marcel Ziswiler wrote:
> On Mon, 2014-09-08 at 04:07 +0200, Marek Vasut wrote:
> > Does the network really work with an i21x with unprogrammed iNVM ?
>
> Yes, it actually does work quite nicely.
That's interesting. I never got it working with unprogrammed iNVM, I always had
to program it first.
> However I currently still have to patch it additionally as follows:
>
> diff --git a/drivers/net/e1000.c b/drivers/net/e1000.c
> index ce19173..5f9c606 100644
> --- a/drivers/net/e1000.c
> +++ b/drivers/net/e1000.c
> @@ -1128,7 +1128,7 @@ e1000_swfw_sync_acquire(struct e1000_hw *hw,
> uint16_t mask)
>
> if (!timeout) {
> DEBUGOUT("Driver can't access resource, SW_FW_SYNC
> timeout.\n");
> - return -E1000_ERR_SWFW_SYNC;
> +// return -E1000_ERR_SWFW_SYNC;
> }
>
> swfw_sync |= swmask;
> @@ -4378,7 +4378,7 @@ e1000_get_phy_cfg_done(struct e1000_hw *hw)
> if (!timeout) {
> DEBUGOUT("MNG configuration cycle has not "
> "completed.\n");
> - return -E1000_ERR_RESET;
> +// return -E1000_ERR_RESET;
> }
> break;
> }
>
> Without doing the above it fails as follows (enabled E1000_DEBUG):
[...]
> This is both with programmed (iNVM only, haven't tried external serial
> PROM possible on i210) as well as unprogrammed i210 as well as i211
> chips on our Apalis T30 modules.
>
> Have you ever seen any such issue?
No, but this looks like the card cannot acquire a semaphore. You might want to
check if there are maybe some pecularities in semaphore handling on this i210
hardware. I remember intel did change the semaphore handling between various
intel ethernet cards.
> Wondering whether this is a Tegra PCIe related issue.
I doubt so.
> May I ask about your specific platform you tried this on?
The MX6 SabreLite and the MX6 SabreSDP . Both MX6Quad.
> Could you send some output of a working session with
> E1000_DEBUG enabled? I plan to try it on a Boundary Devices Nitrogen6X
> as well as our Apalis iMX6 module as well.
I don't have the setup assembled now and the i210 is not available to me now,
but you should be getting the same result with the N6X. Right now, I only have
the MX6 SabreLite and an another intel NIC available, sorry.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-09-10 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <03c9982d8450bcbf073530edd6446ef3ec4dfddb.1410127137.git.marcel@ziswiler.com>
2014-09-07 22:02 ` [U-Boot] [PATCH] e1000: fix no nvm build Marcel Ziswiler
2014-09-08 2:07 ` Marek Vasut
2014-09-25 14:44 ` [U-Boot] " Tom Rini
2014-09-07 22:03 ` [U-Boot] [PATCH] e1000: add i211 and unprogrammed i210/i211 support Marcel Ziswiler
2014-09-08 2:07 ` Marek Vasut
2014-09-10 21:18 ` Marcel Ziswiler
2014-09-10 23:46 ` Marek Vasut [this message]
2014-10-27 22:19 ` [U-Boot] " Tom Rini
2014-10-28 1:07 ` Marcel Ziswiler
2014-10-28 11:15 ` 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=201409110146.05991.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox