From: Michael John <MJohn@midmark.com>
To: James Prestwood <prestwoj@gmail.com>,
"iwd@lists.linux.dev" <iwd@lists.linux.dev>
Subject: Re: issue using virtual interface with iwd
Date: Wed, 7 Jun 2023 12:04:05 +0000 [thread overview]
Message-ID: <BY3PR08MB7220054B5EC6EB85D17B6ACDAE53A@BY3PR08MB7220.namprd08.prod.outlook.com> (raw)
In-Reply-To: <696f641a-59ac-a476-a17f-a9ad43a524fb@gmail.com>
Hi James,
> Hi Michael,
>
>>
>>
>> After looking through the commit history I see the DisableHT support was
>> added right after the 2.3 release. I've updated to 2.5 and retried and
>> was successful at getting the AP up.
>>
>> Thanks for your help James!
>
> Great! To try and get this addressed better could you provide the
> wireless hardware you are using?
>
>>
>> -Michael
The wireless chipset is a NXP 88W8997/88PG823. It's part of a 60SOM from Laird,
believe its one of Laird's Sterling radio.
~> cat /sys/class/net/wlan0/device/lrd/info
Driver name : lrdmwl
Chip type : 88W8997-SDIO
HW version : 7
FW version : 5.5.43.5
DRV version : 9.32.0.13
OTP version : 2
OTP num mac : 3
Radio Type : SU
MAC address : c0:ee:40:64:4a:1c
Region code : 0x10 (0x10)
Country code: 'US' ('US')
TX antenna : 2
RX antenna : 2
lrdmwl is the Laird wireless driver being used.
For reference: this is the SOM:
https://www.lairdconnect.com/system-on-module/microchip/60-series-som-wifi-80211ac-and-bluetooth-51
-Michael
CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
next prev parent reply other threads:[~2023-06-07 12:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 13:17 issue using virtual interface with iwd Michael John
2023-06-01 15:06 ` James Prestwood
2023-06-01 15:17 ` James Prestwood
2023-06-01 15:42 ` Michael John
2023-06-01 15:53 ` James Prestwood
2023-06-01 18:28 ` Michael John
2023-06-01 18:34 ` James Prestwood
2023-06-01 20:00 ` Michael John
2023-06-01 20:18 ` James Prestwood
2023-06-02 11:39 ` Michael John
2023-06-02 12:09 ` Michael John
2023-06-06 16:14 ` James Prestwood
2023-06-07 12:04 ` Michael John [this message]
2023-06-01 15:38 ` Denis Kenzior
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=BY3PR08MB7220054B5EC6EB85D17B6ACDAE53A@BY3PR08MB7220.namprd08.prod.outlook.com \
--to=mjohn@midmark.com \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).