From: Greg KH <greg@kroah.com>
To: Tejun Heo <htejun@gmail.com>
Cc: 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: Tue, 7 Mar 2006 21:27:23 -0800 [thread overview]
Message-ID: <20060308052723.GD29867@kroah.com> (raw)
In-Reply-To: <440E4203.7040303@gmail.com>
On Wed, Mar 08, 2006 at 11:31:31AM +0900, Tejun Heo wrote:
> Greg KH wrote:
> >On Fri, Mar 03, 2006 at 06:18:32PM -0500, Jeff Garzik wrote:
> >
> >>I have a similar situation:
> >>
> >>BIOS initializes PCI device to mode A, I need to switch it to mode B.
> >>To do this, I must assign a value to an MMIO PCI BAR that was not
> >>initialized at boot.
> >>
> >>How to do this?
> >
> >
> >I really don't know, what kind of device wants to do this?
> >
>
> Jeff is probably talking about ABAR of ICH controllers. ABAR (AHCI BAR,
> memory mapped IO region covering all AHCI registers) isn't needed for
> IDE mode operation and the BAR register is disabled when the chip is in
> IDE mode. However, ABAR becomes necessary for 1. accessing SCR registers
> (for SATA phy monitor and control) or 2. switching on AHCI mode manually
> (some notebook BIOSes always initalize ICH6/7m's into IDE mode even when
> the controller does support AHCI mode.
>
> 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?
thanks,
greg k-h
next prev parent reply other threads:[~2006-03-08 5:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 17:42 proper way to assign fixed PCI resources to a "hotplug" device 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 [this message]
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
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=20060308052723.GD29867@kroah.com \
--to=greg@kroah.com \
--cc=galak@kernel.crashing.org \
--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 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.