Re: RFC: bare pci configuration access functions ?

Greg KH (greg@kroah.com)
Thu, 31 Oct 2002 17:02:41 -0800


Wait, first off, are we talking about 2.4, or 2.5 here? For 2.5 I think
everything is covered, right?

On Thu, Oct 31, 2002 at 11:29:19AM -0800, Lee, Jung-Ik wrote:
> Question:
> ========
> Will it be desirable to have bare global pci config access functions as seen
> in i386/ia64 pci codes ? It's clean and needs just what it takes - seg, bus,
> dev, func, where, value, and size.

No, I do not think so. I think the way 2.5 does this is the correct
way. But as I did that patch, I might be a bit biased :)

We could just force every arch to export the same functions that i386
and ia64 does, that shouldn't be a big deal. I think this would solve
the problem on 2.4 for pci hotplug, as ACPI is already "cheating" and
doing this right now...

thanks,

greg k-h
-
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/