From: Amin Azez <azez@ufomechanic.net>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: linux-kernel@vger.kernel.org, Michael.ODonnell@stratus.com,
NetDEV list <netdev@vger.kernel.org>,
Auke Kok <auke-jan.h.kok@intel.com>
Subject: Re: e100 breakage located
Date: Sat, 09 Dec 2006 09:17:07 +0000 [thread overview]
Message-ID: <457A7F13.6050002@ufomechanic.net> (raw)
In-Reply-To: <4807377b0611301134q33d1cd78l5a1f2eda33da21bc@mail.gmail.com>
Jesse Brandeburg wrote:
> sorry for the delay, your mail got marked as spam. In the future
> please copy networking issues to netdev@vger.kernel.org, and be sure
> to copy the maintainers of the driver you're having problems with
> (they are in the MAINTAINERS file)
>
> On 11/22/06, Amin Azez <azez@ufomechanic.net> wrote:
>> I notice a patch in 2005 from Micahel O'Donnel to the e100.c driver has
>> stopped auto-crossover working on some e100 devices we use.
>>
>> On one system the auto-negotiation was restored by commenting out:
>> (nic->mac == mac_82551_10) in function e100_phy_init where the MDI/MDI-X
>> is disabled.
>
> are you sure that patch did that? What version of e100 are you using?
> we've since enabled MDI-X on most parts with this patch:
> http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=60ffa478759f39a2eb3be1ed179bc3764804b2c8;hp=09e590e5d5a93f2eaa748a89c623258e6bad1648
>
>
> Please try the latest kernel or the latest e100 available from
> e1000.sf.net
> if that doesn't work we'll need to know what kernel are you using?
Let me have another check and get back to you.
It will be at least a week though.
Thanks for your response.
Sam
prev parent reply other threads:[~2006-12-09 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 9:37 e100 breakage located Amin Azez
2006-11-30 19:34 ` Jesse Brandeburg
2006-12-09 9:17 ` Amin Azez [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=457A7F13.6050002@ufomechanic.net \
--to=azez@ufomechanic.net \
--cc=Michael.ODonnell@stratus.com \
--cc=auke-jan.h.kok@intel.com \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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