From: Greg KH <greg@kroah.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Linus Torvalds <torvalds@osdl.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6.13-rc2] yet another fix for setup-bus.c/x86 merge
Date: Wed, 6 Jul 2005 16:13:10 -0700 [thread overview]
Message-ID: <20050706231310.GA4505@kroah.com> (raw)
In-Reply-To: <20050707030756.B6806@den.park.msu.ru>
On Thu, Jul 07, 2005 at 03:07:56AM +0400, Ivan Kokshaysky wrote:
> There is a slight disagreement between setup-bus.c code and traditional
> x86 PCI setup wrt which recourses are invalid vs resources that are
> free for further allocations.
> Precisely, in the setup-bus.c, if we failed to allocate some resource,
> we nullify "start" and "flags" fields, but *not* the "end" one.
> But x86 pcibios_enable_resources() does the following check:
> if (!r->start && r->end) {
> printk(KERN_ERR "PCI: Device %s not available because of resource collisions\n", pci_name(dev));
> return -EINVAL;
> which means that the device owning the offending resource cannot be
> enabled.
> In particular, this breaks cardbus behind the normal decode p2p bridge -
> the cardbus code from setup-bus.c requests rather large IO and MEM windows,
> and if it fails, the socket is completely unavailable. Which is wrong, as
> the yenta code is capable to allocate smaller windows.
>
> Signed-off-by: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Thanks Ivan for finding this so quickly.
greg k-h
prev parent reply other threads:[~2005-07-06 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 23:07 [patch 2.6.13-rc2] yet another fix for setup-bus.c/x86 merge Ivan Kokshaysky
2005-07-06 23:13 ` Greg KH [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=20050706231310.GA4505@kroah.com \
--to=greg@kroah.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=torvalds@osdl.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