From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>,
f.fainelli@gmail.com, jonas.gorski@gmail.com, nbd@nbd.name,
kvalo@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, chunkeey@gmail.com,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: "Álvaro Fernández Rojas" <noltari@gmail.com>
Subject: Re: [PATCH] ath9k: fix calibration data endianness
Date: Sat, 15 Apr 2023 17:25:31 +0200 [thread overview]
Message-ID: <87leitxj4k.fsf@toke.dk> (raw)
In-Reply-To: <20230415150542.2368179-1-noltari@gmail.com>
Álvaro Fernández Rojas <noltari@gmail.com> writes:
> BCM63xx (Big Endian MIPS) devices store the calibration data in MTD
> partitions but it needs to be swapped in order to work, otherwise it fails:
> ath9k 0000:00:01.0: enabling device (0000 -> 0002)
> ath: phy0: Ignoring endianness difference in EEPROM magic bytes.
> ath: phy0: Bad EEPROM VER 0x0001 or REV 0x00e0
> ath: phy0: Unable to initialize hardware; initialization status: -22
> ath9k 0000:00:01.0: Failed to initialize device
> ath9k: probe of 0000:00:01.0 failed with error -22
How does this affect other platforms? Why was the NO_EEP_SWAP flag set
in the first place? Christian, care to comment on this?
-Toke
next prev parent reply other threads:[~2023-04-15 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 15:05 [PATCH] ath9k: fix calibration data endianness Álvaro Fernández Rojas
2023-04-15 15:25 ` Toke Høiland-Jørgensen [this message]
2023-04-15 16:02 ` Christian Lamparter
2023-04-15 19:32 ` Christian Lamparter
2023-04-16 10:50 ` Toke Høiland-Jørgensen
2023-04-16 13:37 ` Christian Lamparter
2023-04-16 14:28 ` Álvaro Fernández Rojas
2023-04-16 14:44 ` Andrew Lunn
2023-04-16 21:49 ` Toke Høiland-Jørgensen
2023-04-17 5:33 ` Álvaro Fernández Rojas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87leitxj4k.fsf@toke.dk \
--to=toke@toke.dk \
--cc=chunkeey@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).