Re: ACPI vs PCI: configuration space

[Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>]

On Wed, Jun 18, 2003 at 11:17:52PM +0100, Matthew Wilcox wrote:
> 
> It's kind of annoying to invent some structures and put some values into
> them only to pull them out again.  This leads to try 5 ...
> 
> struct acpi_pci_ops {
> 	int (*read)(int domain, int bus, int devfn, int where, int size, u32 *val);
> 	int (*write)(int domain, int bus, int devfn, int where, int size, u32 val);
> }
> 
> It reduces stack consumption, which is a clear win ... it's also _incredibly_
> easy to implement since all the existing pci_ops call functions which take
> exactly this form.
> 
> Go on, approve Try 5.  You know you want to ;-)

So for i386, what would domain be?

Anyway, yeah, I agree with try 5, that seems the most sane.

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php