lkml.org 
[lkml]   [2001]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Possible PCI subsystem bug in 2.4

On Thu, 3 May 2001, Alan Cox wrote:
>
> Obvious one is to go to the next power of two clear.

The question is mainly _which_ power of two.

I don't think we can round up infinitely, as that might just end up
causing us to not have any PCI space at all. Or we could end up deciding
that real PCI space is memory, and then getting a clash when a real device
tries to register its bios-allocated area that clashes with our extreme
rounding.

I suspect it would be safe to round up to the next megabyte, possibly up
to 64MB or so. But much more would make me nervous.

Any suggestions?

> Semi related question: To do I2O properly I need to grab PCI bus space and
> 'loan' it to the controller when I configure it. Im wondering what the
> preferred approach there is.

Do the same thing that the yenta driver does, just do a

root = pci_find_parent_resource(dev, res);
allocate_resource(root, res, size, min, max, align, NULL, NULL);

and keep it allocated (and then the i2o driver can do sub-allocations
within that resource by doing "allocate_resource(res, ...)").

Linus

-
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 12:52    [W:0.265 / U:0.108 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site