From: Heiner Kallweit <hkallweit1@gmail.com>
To: Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Luca Coelho <luciano.coelho@intel.com>,
Intel Linux Wireless <linuxwifi@intel.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: AX210 version 0024 not detected by iwlwifi
Date: Sun, 22 Nov 2020 22:35:18 +0100 [thread overview]
Message-ID: <03e8284e-4ea8-fe3e-8da7-62a778b1a059@gmail.com> (raw)
I have an AX210 card that isn't detected by iwlwifi.
01:00.0 Network controller: Intel Corporation Device 2725 (rev 1a)
Subsystem: Intel Corporation Device 0024
Adding following entry seems to be sufficient.
{IWL_PCI_DEVICE(0x2725, 0x0020, iwlax210_2ax_cfg_ty_gf_a0)},
+ {IWL_PCI_DEVICE(0x2725, 0x0024, iwlax210_2ax_cfg_ty_gf_a0)},
{IWL_PCI_DEVICE(0x2725, 0x0310, iwlax210_2ax_cfg_ty_gf_a0)},
[ 419.473140] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[ 419.486984] iwlwifi 0000:01:00.0: api flags index 2 larger than supported by driver
[ 419.487190] iwlwifi 0000:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28
[ 419.488828] iwlwifi 0000:01:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm
[ 419.533136] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
Maybe there are more AX210 subversion id's to be added ..
How about the api flags index warning? I saw it in several posts,
is there something to be fixed in the driver?
next reply other threads:[~2020-11-22 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 21:35 Heiner Kallweit [this message]
2020-11-23 8:17 ` AX210 version 0024 not detected by iwlwifi Coelho, Luciano
2020-11-27 11:55 ` Heiner Kallweit
2020-11-28 21:12 ` Heiner Kallweit
2020-12-15 11:32 ` Heiner Kallweit
2020-11-27 8:31 ` Jan Fuchs
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=03e8284e-4ea8-fe3e-8da7-62a778b1a059@gmail.com \
--to=hkallweit1@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luciano.coelho@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.