LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Yinghai Lu" <yinghai.lu@amd.com>
To: "Jeff Garzik" <jgarzik@pobox.com>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
	"Bill Davidsen" <davidsen@tmr.com>,
	"Adrian Bunk" <bunk@stusta.de>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	saw@saw.sw.com.sg,
	"Jesse Brandeburg" <jesse.brandeburg@intel.com>
Subject: Re: [2.6 patch] the scheduled eepro100 removal
Date: Wed, 28 Mar 2007 22:08:23 -0700	[thread overview]
Message-ID: <86802c440703282208m1f79c682q876e4d08d9216cd2@mail.gmail.com> (raw)
In-Reply-To: <460AEF65.8070908@pobox.com>

On 3/28/07, Jeff Garzik <jgarzik@pobox.com> wrote:
> Kok, Auke wrote:
> Sounds sane to me.  My overall opinion on eepro100 removal is that we're
> not there yet.  Rare problem cases remain where e100 fails but eepro100
> works, and it's older drivers so its low priority for everybody.
>
> Needs to happen, though...
>

It seems that several Tyan Opteron base system that were using IPMI
add on card.  the IPMI card share intel 100Mhz nic onboard. you need
to use eepro100 instead of e100 otherwise the e100 will shutdown OOB
(out of Band) connection for IPMI when shut down the OS.

YH

  reply	other threads:[~2007-03-29  5:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25 14:58 Adrian Bunk
2007-03-28 22:17 ` Bill Davidsen
2007-03-28 22:26   ` Kok, Auke
2007-03-28 22:42     ` Jeff Garzik
2007-03-29  5:08       ` Yinghai Lu [this message]
2007-03-29  8:19         ` Roberto Nibali
2007-03-29 16:22           ` Brandeburg, Jesse
2007-03-30 16:40             ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2007-02-20  0:06 Adrian Bunk
2007-01-02 21:57 Adrian Bunk
2007-01-03  0:07 ` Eric Piel
2007-01-03 22:14   ` Jesse Brandeburg
2007-01-03  9:10 ` Jan Kiszka

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=86802c440703282208m1f79c682q876e4d08d9216cd2@mail.gmail.com \
    --to=yinghai.lu@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=auke-jan.h.kok@intel.com \
    --cc=bunk@stusta.de \
    --cc=davidsen@tmr.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    --subject='Re: [2.6 patch] the scheduled eepro100 removal' \
    /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

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).