Artem, Ted and I were discussing the changes to convert e1000g to Brussels, and he raise the following question:
> I asked this because e1000g link > configuration method is different from other drivers, and with the > Brussels porting, e1000g will use the same way as other drivers when > using dladm and ndd. But the e1000g.conf file still uses the old method, > which will conflict with the permanent property settings. So I'm > considering to make some changes to the conf file. I believe (Ted?) that Ted is referring to the fact that the syntax that e1000g reads from e1000g.conf is linux-style configuration, not the traditional "default_mtu" config. Artem: can you confirm that this is the model being proposed by the Persistence component: In that case, e1000g_attach should make a door_call (the prototype uses a mac_prop_init() function) to the dlmgmtd that will result in the driver properties being loaded into the kernel in a mac_prop_list that is managed by the mac layer. Then, instead of doing ddi_prop_get* interfaces to read the property from driver.conf, e1000g should call something like mac_prop_get_int to get the value of mtu. The latter function will first search the mac_prop_list, and second do the ddi_prop_get to get the requested value. (I'm assigning precedence for the dladm configuration arbitrarily- not sure what choices Artem is making). --Sowmini
