On Fri, 2007-09-14 at 14:17 -0400, Jeff Garzik wrote:
> Dan Williams wrote:
> > WTF? why would the default be to _not_ propagate carrier state? Are
> > there some mitigating circumstances that require this driver to not
> > notify the stack of carrier on/off? Userspace stuff really should know
> > about the carrier state, and this disables it by default.
>
>
> The commit explains that...
I admit that I probably don't understand the system architecture of
where ehea would be used, but would this
cause /sys/class/net/ethX/carrier to be TRUE even if the device has no
carrier? That seems quite wrong IMHO. When does ehea not have a
carrier? And in that case, does sysfs say 1 or 0 for the carrier?
Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
