lkml.org 
[lkml]   [2001]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Possible PCI subsystem bug in 2.4
Date
From
> 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?

I'd go for 1MByte simply because I've not seen an EBDA/NVRAM area that large
stuck at the top of RAM. 1Mb would fix the Dell. (It was only when I saw
your email it suddenely clicked and I grabbed the bootup log)

> > 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, ...)").

Thanks.

Alan

-
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:1.565 / U:0.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site