mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: Greg KH <gregkh@suse.de>, akpm@osdl.org
Cc: Pierre Peiffer <pierre.peiffer@bull.net>,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [Bug ??] 2.6.18-rc6-mm2 - PCI ethernet board does not seem to work
Date: Fri, 15 Sep 2006 16:43:54 -0500	[thread overview]
Message-ID: <20060915214354.GB24399@lists.us.dell.com> (raw)
In-Reply-To: <20060915102954.GA7014@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]

On Fri, Sep 15, 2006 at 03:29:54AM -0700, Greg KH wrote:
> That being said, I think we need to reverse the order of this patch,
> keeping the current scheme as default, and allowing it to be overridden
> on the command line for those few machines where it matters to be
> compatible with the old, 2.4 ordering scheme.
> 
> Matt, care to rework the patch in this manner?

Greg, Andrew,

I'd really like to rework this patch in a different direction.  As
such, please drop the patch:

gregkh-pci-pci-sort-device-lists-breadth-first.patch

from your trees, and I'll provide a new one next week.

Breadth-first vs depth-first is really only part of the problem.  More
fundamental is the expectation that embedded devices get discovered
before add-in devices in physical slots.  From there, breadth-first vs
depth-first is interesting again.  I'd like to sort the list to put
the embedded devices first, subsort those breadth-first, then list the
add-in devices in ascending slot number order, subsort breadth-first.
I'll default this sorting routine off, enabled/disabled via a command
line option, and enabled by default for some systems based on DMI
strings.

arch/i386/pci/irq.c already has the PCI IRQ Routing Table available,
from which we can get embedded vs slotN information.  It's not
currently being used in this manner, so I'm massaging that.

How does this sound?

Thanks,
Matt

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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-09-15 21:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15 10:21 Pierre Peiffer
2006-09-15 10:29 ` Greg KH
2006-09-15 21:43   ` Matt Domsch [this message]
2006-09-15 12:59 ` Matt Domsch
2006-09-15 13:28   ` Pierre Peiffer

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=20060915214354.GB24399@lists.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=pierre.peiffer@bull.net \
    /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