From: Jamal Hadi Salim <hadi@cyberus.ca>
To: a1 <a1k@mail.ru>
Cc: netdev@vger.kernel.org, Jeff Kirsher <tarbal@gmail.com>
Subject: Re: Re[2]: e1000 speed/duplex error
Date: Tue, 01 Aug 2006 08:22:00 -0400 [thread overview]
Message-ID: <1154434920.5170.100.camel@jzny2> (raw)
In-Reply-To: <595776532.20060801160328@mail.ru>
On Tue, 2006-01-08 at 16:03 +0400, a1 wrote:
> I thought the common behavior is that if one side force any particular
> parameter, other side should "sense" that and go to that mode too.
>
You _cannot_ depend on that behavior at all. IOW, if one side is not
forced the other side's setting is undefined and falls back to whatever
that side defines as "default"
> In current case there is misunderstanding - one side (linux box)
> reports 100/FD and other (switch) reports 100/HD.
>
> Maybe I don't understand something...
You must force both sides for predictable behavior. I would say that
doing HD as default is more common. So Linux may need to change just
that one bit.
cheers,
jamal
next prev parent reply other threads:[~2006-08-01 12:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 10:18 e1000 speed/duplex error a1
2006-08-01 11:20 ` Jeff Kirsher
2006-08-01 12:03 ` Re[2]: " a1
2006-08-01 12:21 ` Andy Gospodarek
2006-08-01 12:22 ` Jamal Hadi Salim [this message]
2006-08-01 17:03 ` Rick Jones
[not found] ` <793732866.20060801153230@mail.ru>
[not found] ` <9929d2390608010445w4fd81b64g310ae90a423e1a7d@mail.gmail.com>
2006-08-01 12:20 ` Re[4]: " a1
2006-08-01 12:34 ` Jeff Kirsher
2006-08-01 14:35 ` Auke Kok
2006-08-01 17:15 ` Jeff Kirsher
2006-08-02 7:34 ` a1
2006-08-02 7:43 ` Jeff Kirsher
2006-08-02 8:39 ` a1
2006-08-02 15:02 ` Auke Kok
2006-08-03 7:51 ` a1
2006-08-02 16:19 ` Auke Kok
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=1154434920.5170.100.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=a1k@mail.ru \
--cc=netdev@vger.kernel.org \
--cc=tarbal@gmail.com \
/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).