From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Greg KH <greg@kroah.com>
Cc: 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: Wed, 8 Mar 2006 14:39:52 +0300 [thread overview]
Message-ID: <20060308143952.B4851@jurassic.park.msu.ru> (raw)
In-Reply-To: <20060308052723.GD29867@kroah.com>; from greg@kroah.com on Tue, Mar 07, 2006 at 09:27:23PM -0800
On Tue, Mar 07, 2006 at 09:27:23PM -0800, Greg KH wrote:
> On Wed, Mar 08, 2006 at 11:31:31AM +0900, Tejun Heo wrote:
> > So, the problem is that the chip actually disables the PCI BAR if
> > certain switches aren't turned on and thus BIOSes are likely not to
> > reserve mmio address for the BAR. We can turn on proper switches during
> > driver initialization but we don't know how to wiggle the BAR into mmio
> > address space.
>
> Thanks for the explaination, that makes more sense. Unfortunatly I do
> not know how to do this right now :(
>
> Anyone with any ideas?
We have 'pci_fixup_early' stuff exactly for that sort of hardware.
IOW, just add a quirk routine that turns on desired mode of the
device and use DECLARE_PCI_FIXUP_EARLY() for it.
The new BAR will be discovered an assigned automatically then.
Ivan.
next prev parent reply other threads:[~2006-03-08 11:39 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 [this message]
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
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=20060308143952.B4851@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 \
/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®