On Mon, 2014-05-05 at 07:19 -0700, Amitkumar Karwar wrote: > In mwifiex, we are interested in providing separate firmware dump file to user for each memory segment. Ex. ITCM, DTCM, SQRAM etc. We have multiple things as well, firmware memory, last driver commands, ... > It looks simpler with ethtool ops instead of creating multiple debugfs files. What we decided to do is encode the file with an IE-like structure so we can extend the format in the future. > 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 This works, though I'd be worried about getting a consistent snapshot, no? > Common uevent through cfg80211 API to notify firmware dump is over would be useful for us. That makes some sense. The way our code works is that it stores all the desired data on an error, triggers the event & restart, and then you can request the data later. I'm not sure ethtool dump is appropriate for that - it seems to be more used for "get a dump right now during operation" type scenarios? johannes -- 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
