Hello again, On Sun, Jul 21, 2019 at 3:10 PM Kristian Evensen <[email protected]> wrote: > Considering that the next byte has the value 0x1, I suspect the issue > might be related to endianess. However, I haven't found a way to > trigger an endianess-conversion when the calibration data is read for > file. Is there something I am missing or is this not supported? > > Could endianess be an explanation for the error I am seeing, or are > there other things in the calibration data the looks like it could > cause problems as well?
I took a second look at the ath9k-driver and see that 0x1 is the value of AR5416_OPFLAGS_11A, which sets the CAP_5GHz flag. My card is only 2.4 GHz, so then I guess the endianess-theory was wrong. BR, Kristian
