From: Ben Collins <ben.collins@ubuntu.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] PCI legacy resource fix
Date: Fri, 08 Dec 2006 19:46:18 -0500 [thread overview]
Message-ID: <1165625178.7443.334.camel@gullible> (raw)
In-Reply-To: <20061206134143.GA6772@linux-mips.org>
On Wed, 2006-12-06 at 13:41 +0000, Ralf Baechle wrote:
> Since commit 368c73d4f689dae0807d0a2aa74c61fd2b9b075f the kernel will try
> to update the non-writeable BAR registers 0..3 of PIIX4 IDE adapters if
> pci_assign_unassigned_resources() is used to do full resource assignment
> of the bus. This fails because in the PIIX4 these BAR registers have
> implicitly assumed values and read back as zero; it used to work because
> the kernel used to just write zero to that register the read back value
> did match what was written.
>
> The fix is a new resource flag IORESOURCE_PCI_FIXED used to mark a
> resource as non-movable. This will also be useful to keep other import
> system resources from being moved around - for example system consoles
> on PCI busses.
I have a problem where an ich6 (SATA+PATA) is getting its port0 reserved
by the pci quirk for libata so that it gets picked up by ata_piix. In
current git, ata_piix complains:
[ 124.507570] PCI: Unable to reserve I/O region #1:8@1f0 for device 0000:00:1f.2
I bisected to the same commit, 368c73d4f689dae0807d0a2aa74c61fd2b9b075f,
however, your patch doesn't fix my problem.
next prev parent reply other threads:[~2006-12-09 0:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 13:41 [PATCH] PCI legacy resource fix Ralf Baechle
2006-12-06 13:57 ` Alan
2006-12-09 0:46 ` Ben Collins [this message]
2006-12-09 1:25 ` Ralf Baechle
2006-12-09 2:13 ` Ben Collins
2006-12-09 2:46 ` Alan
2006-12-09 8:12 ` Ben Collins
2006-12-09 13:14 ` Alan
2006-12-09 15:50 ` Ben Collins
2006-12-09 13:15 ` Alan
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=1165625178.7443.334.camel@gullible \
--to=ben.collins@ubuntu.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.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 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.