On Wed, 2014-04-30 at 19:14 +0300, Kalle Valo wrote: > >> 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. What was the intended use case for this though? Neither the header file nor the ethtool documentation seem particularly clear, other than saying "firmware dump" - we'll want to include driver data as well though? 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
