@Martin - this is a generic problem with a number of the drm/agp hardware pairs as long as the AGP hardware code is built as a module. Its also worth noting that this load race issue affects network drivers that are consumers of libphy, e.g., if the associated MII driver has not already registered with libphy, then the NIC driver can't do much. I solved that issue awhile ago by building into the kernel all of the phylib HW modules, not the most elegant solution. I'm going to talk to upstream to see if there is a better solution.
@Martin - this is a generic problem with a number of the drm/agp hardware pairs as long as the AGP hardware code is built as a module. Its also worth noting that this load race issue affects network drivers that are consumers of libphy, e.g., if the associated MII driver has not already registered with libphy, then the NIC driver can't do much. I solved that issue awhile ago by building into the kernel all of the phylib HW modules, not the most elegant solution. I'm going to talk to upstream to see if there is a better solution.