Sergey Darakov
05/19/2009 10:48 AM
post29671
|
>Which nic/driver are you testing with?
I had started with sample driver, then developed it in a
way like speedo (or mpc85xx) driver.
There is no real hardware, I'm plaing with driver in two
stacks framework with drivers communicating via
some library at bottom layer with lib interface primitives
like read/write packets and get_connection_state etc.
This is helpfull in investigating io-pkt and drivers architecture.
Driver pass the traffic quite stable (flud ping),
and `ifconfig` controls/show interface up/down/destroy
appropriatly, but
when I take interface under `ifwatch` - it doesn't recognised the state changes.
> if_link_state_change(ifp, LINK_STATE_UP);
Yes, there is
callout_msec(&pan->mii_callout, 1000, pan_monitor_ln, pan);
with if_link_state_change() calls in pan_monitor_ln().
Is this enough for `ifwatchd`?
What about of
ifmedia_ioctl(ifp, ifr, &pan->bsd_mii.mii_media, cmd);
in <drvr>_ioctl() in devctl.c and its relation to mii.c
(especialy in context of no hardware)?
Is it mandatory or another workarounds possible for `ifwatchd` work?
Regards,
Sergey
|
|
|