On Thu, Oct 18, 2012 at 4:29 PM, Bjørn Mork [off-list ref] wrote:
Ming Lei [off-list ref] writes:
quoted
In ioctl path on net_device, the physical deivce is often
touched, but the physical device may have been put into runtime
suspend state already, so cause some utilitis(ifconfig, ethtool,
...) to return failure in this situation.
I have to as the stupid questions again, sorry...
Just wondering, isn't that really a driver problem? The driver will
It is or not, :-)
know whether or not hardware access is required, and should wake up the
The netcore knows that first, doesn't it?
device if necessary. Unless I misunderstand something here, this seems
like papering over driver bugs?
Suppose it is driver bug, and basically most network drivers don't consider
that, and we can fix that in netcore generally, so why bother all drivers to do
that?
Thanks,
--
Ming Lei