On Wed, Aug 17, 2005 at 11:10:34AM -0700, Stephen Hemminger wrote: > Jeff observed a problem with sky2 driver where if pci_request_regions > failed, the probe code would disable the device. Since if request_regions > fails, this means another device is conflicting, disabling the device > seems to be the wrong. > > This problem seems to occur in almost all PCI drivers I look at: > 8139cp, amd8111e, b44, bnx2, dl2k, e100, epic100 > forcedeth, r8169, rrunner, s2io, saa9730, skge, tg3, > typhoon, via-velocity, sk98lin, olympic, tulip(s) > dscc4, farsync, pci200syn, wanxl, orinoco > > Is it worth fixing all those? How about a kernel janitor task?
I don't think that's a "fix" at all. If it's colliding it must be some other device because ->probe isn't called if there's a pci driver registered for that device yet. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
