So it is so stable that it isn't even merged into the mainline 2.4.x
sources? :-)
We're talking about a port which doesn't even exist in the mainline
sources yet.
> > Which means it is
> > 2.5.x material, and 2.5.x has been quoted as being a week or two away.
>
> I sure hope that ppc64 is NOT considered 2.5.x material.
No, I'm saying that ppc64 with >=256 physical PCI busses, is 2.5.x
material.
> A real solution would be nice. And if the real solution can ONLY be in 2.5, then
> is it such a bad idea moving the bus number type to unsigned int for 2.4.x?
Yes, no kludges for 2.4.x
Look, I do not even feel for you.
I waited patiently for a sane PCI dma architecture so I could support
>4GB ram on 64-bit PCI systems (sparc64, alpha, etc.). And it was
worth the wait, most of the important PCI drivers fully use this
interface, and it was all done properly.
Similarly you can wait for 2.5.x for >=256 physical PCI bus support.
Ok?
Later,
David S. Miller
davem@redhat.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/