Hi Johannes, > > > > int (*get_dump_flag)(struct net_device *, struct ethtool_dump *); > > int (*get_dump_data)(struct net_device *, > > struct ethtool_dump *, void *); > > int (*set_dump)(struct net_device *, struct ethtool_dump *); > > > > Yeah, maybe we could use that in wireless as well. > > What was the intended use case for this though? In mwifiex, we are interested in providing separate firmware dump file to user for each memory segment. Ex. ITCM, DTCM, SQRAM etc. It looks simpler with ethtool ops instead of creating multiple debugfs files. 1) User can set index for required memory segment. #ethtool --set-dump wlan0 3 2) Get the details #ethtool --get-dump wlan0 flag: 3, version:xyz, length:13450 3) Dump the info in ITCM.log file #ethtool --get-dump wlan0 data ITCM.log Common uevent through cfg80211 API to notify firmware dump is over would be useful for us. Thanks, Amitkumar Karwar -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
