From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: thockin@hockin.org
Cc: Greg KH <greg@kroah.com>, Tejun Heo <htejun@gmail.com>,
Jeff Garzik <jeff@garzik.org>,
Kumar Gala <galak@kernel.crashing.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: proper way to assign fixed PCI resources to a "hotplug" device
Date: Thu, 9 Mar 2006 01:11:47 +0300 [thread overview]
Message-ID: <20060309011147.C9651@jurassic.park.msu.ru> (raw)
In-Reply-To: <20060308215734.GA22826@hockin.org>; from thockin@hockin.org on Wed, Mar 08, 2006 at 01:57:34PM -0800
On Wed, Mar 08, 2006 at 01:57:34PM -0800, thockin@hockin.org wrote:
> > Otherwise we have plenty of MMIO space.
>
> Not true. Plenty of root bridges have the same base/limit style
> configuration registers, but they are non-standard. Even worse - the MMIO
> hole thatthe chipset carves out, is not guaranteed to be big enough for
> some new random allocation.
I'm intrigued. Care to give us an example of such system (where the
root bridge window is too small), please? lspci -vxxx?
> Cleaning up and re-doing are not the same thing. The plethora of x86
> chipsets makes this unpleasant at best and more likely unworkable.
Yes, re-doing is a LOT simpler. ;-)
If needed, we could introduce 'pci=totallyingnorefsckingbiossettings'
boot option - it would be 10 or less lines of code.
Ivan.
next prev parent reply other threads:[~2006-03-08 22:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 17:42 Kumar Gala
2006-03-03 22:07 ` Greg KH
2006-03-03 22:39 ` Kumar Gala
2006-03-03 23:18 ` Greg KH
2006-03-03 23:28 ` Kumar Gala
2006-03-03 23:50 ` Scott Murray
2006-03-09 16:49 ` Kumar Gala
2006-03-03 23:18 ` Jeff Garzik
2006-03-08 2:00 ` Greg KH
2006-03-08 2:31 ` Tejun Heo
2006-03-08 5:27 ` Greg KH
2006-03-08 11:39 ` Ivan Kokshaysky
2006-03-08 16:40 ` thockin
2006-03-08 21:21 ` Ivan Kokshaysky
2006-03-08 21:57 ` thockin
2006-03-08 22:11 ` Ivan Kokshaysky [this message]
2006-03-08 23:54 ` thockin
2006-03-03 23:13 ` Kumar Gala
2006-03-03 23:27 ` Greg KH
2006-03-03 23:40 ` Scott Murray
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=20060309011147.C9651@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=galak@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=thockin@hockin.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®