All of lore.kernel.org
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] e1000: add i210 support
Date: Sat, 4 Oct 2014 02:15:06 +0000	[thread overview]
Message-ID: <bcv6cre55mx6oconjftekd6c.1412388901757@email.android.com> (raw)
In-Reply-To: <201410032323.45305.marex@denx.de>

Marek,

I can try piece by piece but I don't know much about this driver. Some guidance will be appreciated.

York

-------- Original Message --------
From: Marek Vasut
Sent: Fri, 03/10/2014 19:12
To: Sun York-R58495
CC: Tim Harvey ; u-boot at lists.denx.de
Subject: Re: [U-Boot] [PATCH 0/2] e1000: add i210 support


On Friday, October 03, 2014 at 06:33:28 PM, York Sun wrote:
> On 08/08/2014 07:57 AM, Marek Vasut wrote:
> > On Friday, August 08, 2014 at 04:41:37 PM, Tim Harvey wrote:
> >> Two patches to add Intel i210 support to the e1000 driver.
> >>
> >> Marek Vasut (2):
> >>   e1000: Implement dcache support
> >>   e1000: add i210 support
> >>
> >>  drivers/net/e1000.c | 266
> >>
> >> ++++++++++++++++++++++++++++++++++++++++++---------- drivers/net/e1000.h
> >> |
> >>
> >>  12 +++
> >>  include/pci_ids.h   |   7 ++
> >>  3 files changed, 236 insertions(+), 49 deletions(-)
> >
> > Thanks for taking care of those!
>
> Tim,
>
> I am having problem with this patch/commit. We use e1000 cards on many of
> our boards for debugging. Recently I found it is not working on some.
> Using "git bisect" I narrowed down to this commit
> 951860634fdb557bbb58e0f99215391bc0c29779. What information I can provide
> to help you investigate? The vendor id is 0x8086. The device id is 0x107d.

Hey,

can you dive into the patch and see which chunk broke your card please ? Right
now, I really cannot tell, I suspect it might have to do with the EEPROM
handling changes though.

Best regards,
Marek Vasut

  reply	other threads:[~2014-10-04  2:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08 14:41 [U-Boot] [PATCH 0/2] e1000: add i210 support Tim Harvey
2014-08-08 14:41 ` [U-Boot] [PATCH 1/2] e1000: Implement dcache support Tim Harvey
2014-08-23 12:42   ` [U-Boot] [U-Boot,1/2] " Tom Rini
2014-08-26 10:38   ` Vasili Galka
2014-08-26 10:44     ` Marek Vasut
2014-08-26 10:46       ` Marek Vasut
2014-08-08 14:41 ` [U-Boot] [PATCH 2/2] e1000: add i210 support Tim Harvey
2014-08-23 12:42   ` [U-Boot] [U-Boot,2/2] " Tom Rini
2014-08-08 14:57 ` [U-Boot] [PATCH 0/2] " Marek Vasut
2014-10-03 16:33   ` York Sun
2014-10-03 21:23     ` Marek Vasut
2014-10-04  2:15       ` York Sun [this message]
2014-08-21  6:40 ` Tim Harvey
2014-08-21  6:58   ` Marek Vasut

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=bcv6cre55mx6oconjftekd6c.1412388901757@email.android.com \
    --to=yorksun@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 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.