Ido Yariv <ido@xxxxxxxxxx> writes: > A recently added feature to the firmware enables the driver to retrieve > firmware logs via the host bus (SDIO or SPI). > > There are two modes of operation: > 1. On-demand: The FW collects its log in an internal ring buffer. This > buffer can later be read, for example, upon recovery. > 2. Continuous: The FW pushes the FW logs as special packets in the RX > path. > > Reading the internal ring buffer does not involve the FW. Thus, as long > as the HW is not in ELP, it should be possible to read the logs, even if > the FW crashes. I have been thinking something similar and hence my interest. > A sysfs binary file named "fwlog" was added to support this feature, > letting a monitor process read the FW messages. The log is transferred > from the FW only when available, so the reading process might block. Using a sysfs file sounds ugly, isn't there a better way to do this? For example, does ftrace&co provide anything which wireless drivers could use? -- 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
