Need to load broadcom kernel module before loading tg3 driver

Tim Gardner tim.gardner at canonical.com
Wed Sep 9 00:45:27 UTC 2009


2.6.31-10.30 has '[Config] Build in all phylib support modules.' which 
ought to solve your issues.

Jerone Young wrote:
> What is the plan on how this will be resolved for Karmic ? 
> 
> Seems the correct solution will require some upstream input, that may
> take to long to make the Karmic cut off.
> 
> 			Thanks,
> 				Jerone
> 
> On Wed, 2009-09-02 at 16:37 +0100, Scott James Remnant wrote:
>> On Wed, 2009-09-02 at 09:27 -0600, Tim Gardner wrote:
>>
>>> The real problem is that the MII modules, while they all have some kind 
>>> of device signature, require the PCI module to be loaded in order to 
>>> extract the MII signature.
>>>
>> This is why the kernel has subsystems ;-)
>>
>> You should have an MII host driver, loaded when MIIish PCI devices are
>> detected.  That should then create an MII subsystem with kobjects which
>> the underlying device signatures.
>>
>> And then the actual drivers would be MII subsystem drivers, matching
>> mii:someinfo not pci:someinfo
>>
>>> Alternatively, it seems like the PCI module could dynamically load it's 
>>> MII phylib module before registering with phylib. After all, its not 
>>> like it doesn't _know_ which module is providing MII support.
>>>
>> Couldn't it just "depends" it?
>>
>> Scott
> 
> 


-- 
Tim Gardner tim.gardner at canonical.com




More information about the kernel-team mailing list