Hello Martin,
Thank you (and Dmitry Tunin and Chuanhong Guo) for explaining this topic
to me. Now it is perfectly clear. So the idea of reading mtd isn't
completely abandoned, Martin's approach just seems to be more flexible
and universal. On the other hand, I've never assumed sparing this 4k
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi Michal,
On Wed, Aug 14, 2019
Hi!
On Wed, Aug 14, 2019 at 4:59 PM Michal Cieslakiewicz
wrote:
> /etc/hotplug.d/firmware/10-ath9k-eeprom for these routers just extracts
> 4k of calibration data from ART to bin file in /lib/firmware. I
> compared bin file to mtd area and they are identical. Why ath9k cannot
> use this data
> /etc/hotplug.d/firmware/10-ath9k-eeprom for these routers just extracts
> 4k of calibration data from ART to bin file in /lib/firmware. I
> compared bin file to mtd area and they are identical. Why ath9k cannot
> use this data directly accessing /dev/mtd6? Is that 'mtd-cal-data' dts
> option
