mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "Matthew Garrett" <mjg59@srcf.ucam.org>,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	gregkh@suse.de
Subject: Re: [RFC] Runtime allocation of PCI resources
Date: Mon, 11 Jun 2007 11:11:05 -0700	[thread overview]
Message-ID: <86802c440706111111s3f52e572uc90efaf18652538e@mail.gmail.com> (raw)
In-Reply-To: <p73d502uzsj.fsf@bingen.suse.de>

On 11 Jun 2007 20:11:24 +0200, Andi Kleen <andi@firstfloor.org> wrote:
> Matthew Garrett <mjg59@srcf.ucam.org> writes:
>
> > BIOS authors don't always program all the features of hardware. This is
> > often the case for Intel IDE controllers, which are usually able to run
> > in AHCI mode but are rarely configured to do so. Reprogramming them is
> > easy enough other than the requirement for some MMIO space. If the BIOS
> > hasn't allocated this, it's necessary for us to do so manually.
>
> Traditionally we've had bad experiences forcing hardware to do something
> the BIOS didn't consider. e.g. occasionally the BIOS has good reasons
> to not allow it; maybe it knows about some errata or other problem
> the kernel doesn't.
>
> If you do this then don't make it default at least, but only allow
> to force it use an option.

Esp for AMD system with several Hypertranport chain. try to allocate
pci resource in kernel  also need some region adjust in NB
configuration space.

So leave some work to ACPI DSDT AML code at least

YH

      parent reply	other threads:[~2007-06-11 18:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 16:51 Matthew Garrett
2007-06-11 18:11 ` Andi Kleen
2007-06-11 17:41   ` Matthew Garrett
2007-06-11 18:11   ` Yinghai Lu [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=86802c440706111111s3f52e572uc90efaf18652538e@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=mjg59@srcf.ucam.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®