From: "Leech, Christopher" <christopher.leech@intel.com>
To: "'Jeff Garzik'" <jgarzik@pobox.com>, "H. J. Lu" <hjl@lucon.org>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: RE: PCI device order problem
Date: Thu, 24 Oct 2002 17:21:10 -0700 [thread overview]
Message-ID: <BD9B60A108C4D511AAA10002A50708F2073175F7@orsmsx118.jf.intel.com> (raw)
I've heard some grumbling about this with specific motherboards and 82546
LOMs. While I understand what's happening, and that using nameif to manage
this is the correct answer, I am a bit surprised that function 1 would be
placed on the global PCI device list before function 0 for a multi-function
device.
-- Chris Leech
> >>Without answering your specific question, but addressing $subject,
> >>what
> >>problem is caused by the PCI device order you see?
> >>
> >>
> >
> >It is different from the hardware documentation. The hardware manual
> >says it has 2 NICs, NIC 1 (03:07.0) and NIC2 (03:07.1), which makes
> >senses to me. NIC 1 is a special one which supports IPMI over LAN.
> >Since we only use one NIC now, we'd like to use NIC 1 and
> call it eth0.
> >
> >
>
> Well, overall, depending on ordering is error-prone (as you see). I
> would suggest migrating to a less-fragile scheme. nameif and ethtool
> together should get you exactly the device you need...
> (though I wonder
> why simply using eth1 is so awful, if this situation is constant...)
>
> Jeff
next reply other threads:[~2002-10-25 0:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 0:21 Leech, Christopher [this message]
2002-10-25 0:31 ` Jeff Garzik
2002-10-25 0:40 ` H. J. Lu
-- strict thread matches above, loose matches on Subject: below --
2002-10-25 0:25 Leech, Christopher
2002-10-25 0:39 ` H. J. Lu
2002-10-24 23:39 H. J. Lu
2002-10-24 23:49 ` Jeff Garzik
2002-10-24 23:56 ` H. J. Lu
2002-10-25 0:14 ` Jeff Garzik
2002-10-25 0:18 ` H. J. Lu
2002-10-25 10:00 ` Alan Cox
2002-10-25 16:11 ` H. J. Lu
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=BD9B60A108C4D511AAA10002A50708F2073175F7@orsmsx118.jf.intel.com \
--to=christopher.leech@intel.com \
--cc=hjl@lucon.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®