lkml.org 
[lkml]   [2003]   [Jan]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Forcing PCI-PCI bridge to have memory resources
On Wed, 15 Jan 2003, Bret Indrelee wrote:

> I'm working with Linux version 2.4.18-xfs with hotswap support.
>
> I'm trying to make a PCI-PCI bridge always have a minimum of 1MB of
> memory address space allocated to it. I know that the BIOS we are
> using always (correctly, by spec) sets a bridge with no devices behind
> it to disable the memory window. It does this by setting the
> MEM_LIMIT < MEM_BASE.
>
> I've been going through the sources in drivers/pci, trying to figure
> out how things are set up. At the time of the pci scan, the resources
> are usually initialized (in bci_read_breidge_bases) by doing a read of
> the bridge registers and setting the resource values appropropriately.
>
> For the disabled bridges, the resources are copied from the parent
> which in this case results in 0 being set in flags, start and end.
>
> It looks like I will want to call pci_assign_resource(dev, 1); in
> order to give it a memory window, but I'm not sure how to initialize
> the resources so they are assigned correctly.
>
> Our situation is similiar to what a hotswap CPCI system should encounter
> when a hotswap device is inserted behind a previously empty PCI-PCI bridge.
>
> Any help people can give would be greatly appreciated.

I've some functionality in my 2.4 cPCI code that allows manually
specifying resource reservations for PCI bridges. I'm about to start
porting it forward to 2.5, but I'll dig out the bits and send you a
2.4.18 patch tomorrow. If you're impatient, there should be a version
of it in the mailing archives of this list (search for PCI resource
reservation), since I posted it for comment at the end of last summer
sometime.

Scott


--
Scott Murray
SOMA Networks, Inc.
Toronto, Ontario
e-mail: scottm@somanetworks.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:32    [W:0.029 / U:5.860 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site