All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: Dan Carpenter <error27.lkml@gmail.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: Fri, 15 Sep 2006 08:02:26 -0500	[thread overview]
Message-ID: <20060915130226.GA2291@lists.us.dell.com> (raw)
In-Reply-To: <b263e5900609142053r12fbb71ep6ea3e1d63a722d4e@mail.gmail.com>

On Thu, Sep 14, 2006 at 08:53:16PM -0700, Dan Carpenter wrote:
> 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.

2.4 i386 by default resorts the list by what BIOS reports the order
should be.  No other arches do this.  So I'd expect it to be opposite
of what you say.

Care to send the output of 'lspci -tv' and the first 80 or so lines of
dmidecode?  This is curious.

 
> 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?

Unfortunately, DMI data doesn't include enough information.  It says
"there's a port called NIC1", but doesn't say where to find it in PCI
space. :-(  I'm looking at ACPI 3.0 extensions, but am not finding
what I'm needing here either yet.

-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

  reply	other threads:[~2006-09-15 13:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-08  3:14 [PATCH 2.6.18-rc5] PCI: sort device lists breadth-first 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
2006-09-15 13:02   ` Matt Domsch [this message]
2006-09-16  2:39     ` Dan Carpenter
  -- strict thread matches above, loose matches on Subject: below --
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=20060915130226.GA2291@lists.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=error27.lkml@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.