9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Intel 82544EI Gigabit Ethernet (Fiber)
Date: Wed,  4 Feb 2009 14:16:18 -0500	[thread overview]
Message-ID: <04d7a616e2e8db73a4e49c663b2c5f46@quanstro.net> (raw)
In-Reply-To: <257553.2a40b988.247P.mx@tumtum.plumbweb.net>

On Wed Feb  4 11:34:03 EST 2009, 9p-st@imu.li wrote:
> I've several Intel PRO/1000 XF cards that I would like to use. I remember
> these cards working before, but they don't now. Looking at etherigbe.c, I
> see 'intergrate fiber stuff back in' in the todo list. Has anybody looked
> at this recently and know what would be involved? I can muddle around and
> try to figure out what is happening, but any advice would be swell.
>
> % pci -v
> ...
> 1.10.0: net  02.00.00 8086/1009   5 0:e3040000 131072 1:e3060000 131072 2:000a001 32
>     Intel Corporation 82544EI Gigabit Ethernet Controller (Fiber)

if you're just looking for gbe and you're not looking for a 40km
link, you might consider getting a intel pro 1000/pt.  they're about
$35 and perform as well as (and often better than) intel's earlier
nics.  i've got three or four at home.

if you do need the fiber, i would imagine that many things about
the exsting driver will work.  things like link detection might
be broken.  and they may be some phy configuration that needs
to happen manually.  but most intel cards do a pretty good job
of picking workable defaults.  i'd be happy to answer questions
offline.  unfortunately, i don't have any such cards, so i won't
be all that useful.

- erik



      reply	other threads:[~2009-02-04 19:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 16:35 Tristan Plumb
2009-02-04 19:16 ` 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=04d7a616e2e8db73a4e49c663b2c5f46@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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).