From: "Dan Carpenter" <error27.lkml@gmail.com>
To: "Matt Domsch" <Matt_Domsch@dell.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, "Greg KH" <greg@kroah.com>,
linux-kernel@vger.kernel.org, error27@gmail.com,
ppokorny@penguincomputing.com
Subject: Re: [PATCH 2.6.18-rc5] PCI: sort device lists breadth-first
Date: Thu, 14 Sep 2006 20:53:16 -0700 [thread overview]
Message-ID: <b263e5900609142053r12fbb71ep6ea3e1d63a722d4e@mail.gmail.com> (raw)
In-Reply-To: <20060908031422.GA4549@lists.us.dell.com>
On 9/7/06, Matt Domsch <Matt_Domsch@dell.com> wrote:
> Problem:
> Many people have come to expect this naming. Linux 2.6
> kernels name these eth1 and eth0 respectively (backwards from
> expectations). I also have reports that various Sun and HP servers
> have similar behavior.
>
On RHEL3 the 32bit and 64bit versions order the NICs differently.
64bit RHEL3 orders it the same as 2.6.
I've got a lot of systems where the NIC LEDs are labelled. The labels
are correct for 2.6 but not for 2.4 32 bit. I'm suspect the labels
were designed for Windows originally.
My boss pointed out that this patch. It was supposed to make PCI bus
ordering match 2.4.
http://kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commitdiff;h=ffdd6e8f870ca6dd0d9b9169b8c2e0fdbae99549
It's still there, why did it stop working?
Couldn't we just use the labelling from the DMI data to order the NICs?
regards,
dan carpenter
next prev parent reply other threads:[~2006-09-15 3:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 3:14 Matt Domsch
2006-09-08 15:56 ` Dave Jones
2006-09-08 16:18 ` Matt Domsch
2006-09-08 16:55 ` Arjan van de Ven
2006-09-11 19:36 ` Bill Davidsen
2006-09-12 3:08 ` Matt Domsch
2006-09-12 21:06 ` Bill Davidsen
2006-09-08 16:45 ` Greg KH
2006-09-08 18:20 ` Andrew Morton
2006-09-08 18:52 ` Matt Domsch
2006-09-08 18:59 ` Alexey Dobriyan
2006-09-09 9:05 ` Jeff Garzik
2006-09-09 12:11 ` Pavel Machek
2006-09-10 11:26 ` Stefan Richter
2006-09-10 13:02 ` Greg KH
2006-09-15 3:53 ` Dan Carpenter [this message]
2006-09-15 13:02 ` Matt Domsch
2006-09-16 2:39 ` Dan Carpenter
2006-09-08 3:18 Matt Domsch
2006-09-08 19:34 Matt Domsch
2006-09-09 14:37 Ragnar Kjørstad
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=b263e5900609142053r12fbb71ep6ea3e1d63a722d4e@mail.gmail.com \
--to=error27.lkml@gmail.com \
--cc=Matt_Domsch@dell.com \
--cc=error27@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=ppokorny@penguincomputing.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
Powered by JetHome