On (06/20/07 11:21), Erik Nordmark wrote:
>
>> Brussels properties will be available when the driver attaches: early on
>> in the xxx_attach routine, each converted driver will invoke dladmd with a
>> door_upcall and persistent properties will be loaded up in the kernel
>> for the driver as part of the door_upcall. So this should work equivalent
>> to the driver.conf behavior for diskless client.
>
> For diskless boot the driver attached long before init runs, hence there is
> no daemon to talk to.
>
> Erik
This would be an issue for those {driver, property} combinations where
the driver has been inflexibly written to expect all properties to be
available at the start of attach. FoR the cases where a property is being
converted to the Brussels framework, we are also cleaning up the driver
code so that the property can accomodate changes more flexibly, e.g.,
for the case of default_mtu/jumbo-frames, re-organize the driver code
so that the property can be updated on unplumbed (but attached) driver.
I do acknowledge that it would be ideal to have something that is exactly
equivalent to driver.conf (and we are investigating this), but the
side-effect of flexible code brings its own benefits.
--Sowmini
