public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
	Yinghai Lu <yhlu.kernel.send@gmail.com>
Subject: Re: [git pull] PCI updates for 2.6.26
Date: Tue, 29 Apr 2008 14:32:19 -0700	[thread overview]
Message-ID: <200804291432.19653.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080429202632.GA4967@elte.hu>

On Tuesday, April 29, 2008 1:26 pm Ingo Molnar wrote:
> * Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > Nothing really major here: some bug fixes, documentation fixes and
> > some trivial stuff for 2.6.26.  Some of the more important changes are
> > actually coming in through Ingo's "big box" tree, so the excitement
> > (and risk) level here should be pretty low.
>
> i see they are now both upstream and the combination mixed well :)
>
> there are a few other PCI items in x86.git btw that you might want to
> have a look at and which you might want to pick up into your tree - they
> dont really belong into x86.git.
>
> one would be the patch below - it gives us a boot option to enable a lot
> more port IO resource space on modern (large) systems, and increases the
> maximum number of PCI cards that Linux can support.
>
> given that true ISA cards with port decode mirroring problems are
> history on new systems, shouldnt this DMI opt-in feature be a
> default-enabled thing instead somehow? DMI really sucks for sane
> features, it does not scale at all as it always lags behind reality.
>
> Can we discover it in a robust way that the system has no chance for ISA
> cards and turn the tighter non-ISA alignment of port resources on
> automatically? [for cases where Linux does the port allocation and
> sizing]

Hm, there's some ISA stuff in ACPI, but I'm not sure how reliable that would 
be...  I'll take a look through some chipset manuals.

Jesse

      parent reply	other threads:[~2008-04-29 21:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 17:12 [git pull] PCI updates for 2.6.26 Jesse Barnes
2008-04-29 20:26 ` Ingo Molnar
2008-04-29 21:09   ` Ingo Molnar
2008-05-05 16:45     ` Jesse Barnes
2008-05-06 16:58       ` Ingo Molnar
2008-04-29 21:32   ` Jesse Barnes [this message]

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=200804291432.19653.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    --cc=yhlu.kernel.send@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