From: erik quanstrom <quanstro@labs.coraid.com>
To: lyndon@orthanc.ca, 9fans@9fans.net
Subject: Re: [9fans] ether82563.c and i82574 chips
Date: Sun, 15 May 2011 13:56:51 -0400 [thread overview]
Message-ID: <1b2db9f941df877dc7f5ad4243ff7f3a@coraid.com> (raw)
In-Reply-To: <a1116823b8a463ea2dc006a5f52085e5@gandalf.orthanc.ca>
On Sun May 15 13:25:35 EDT 2011, lyndon@orthanc.ca wrote:
> The driver says this about the '574:
>
> // case 0x10d3: /* l */ // type = i82574; /* never heard of it */ //
> break;
>
> I've heard of it: my Asus Z8NA-D6C motherboard has one. Is there any
> history I should know about before I light this up in the driver?
i have also heard of it, as i wrote the original code and am currently
typing this on a terminal with 2x 82574 lom chips.
i have no idea why that was commented out.
you may have better luck with 82563 from 9atom. it supports a
more hardware than the one in the distribution, and works around
some intel-mb bugs.
- erik
prev parent reply other threads:[~2011-05-15 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 17:23 Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-05-15 17:56 ` erik quanstrom [this message]
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=1b2db9f941df877dc7f5ad4243ff7f3a@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.net \
--cc=lyndon@orthanc.ca \
/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;
as well as URLs for NNTP newsgroup(s).