"John W. Linville" <linville@xxxxxxxxxxxxx> writes: > On Wed, Apr 30, 2014 at 10:29:53AM +0200, Johannes Berg wrote: >> On Wed, 2014-04-30 at 10:41 +0300, Kalle Valo wrote: >> > Johannes Berg <johannes@xxxxxxxxxxxxxxxx> writes: >> > >> > > On Thu, 2014-04-24 at 20:35 -0700, Bing Zhao wrote: >> > > >> > >> Sorry about the hassle. We will find a proper way to implement this. >> > > >> > > FWIW, a pretty simple way is to trigger a uevent or so and have a >> > > debugfs file that all the info can be read out from in userspace. >> > >> > I think we need a similar feature in ath10k as well. Should we have a >> > generic interface this, would that make any sense? >> >> We have it in iwlwifi as well - we were considering a generic uevent but >> beyond that I don't think there's much that could be done? > > There is an ethtool op for that, no? Do you mean this one: * @get_dump_flag: Get dump flag indicating current dump length, version, * and flag of the device. * @get_dump_data: Get dump data. * @set_dump: Set dump specific flags to the device. 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. -- Kalle Valo -- 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
