From: "Dedy Lansky" <dlansky@codeaurora.org>
To: "'David Dean'" <daviddean166@gmail.com>,
<linux-wireless@vger.kernel.org>
Subject: RE: wil6210: low level sector API
Date: Thu, 29 Mar 2018 15:29:12 +0300 [thread overview]
Message-ID: <001901d3c759$8cd5b970$a6812c50$@codeaurora.org> (raw)
In-Reply-To: <CAFnQ7os8AQGwJfkunZG-x9f9jdnOw=tjGCHE9wNxNwLfqka_tQ@mail.gmail.com>
From: linux-wireless-owner@vger.kernel.org =
[mailto:linux-wireless-owner@vger.kernel.org] On Behalf Of David Dean
Sent: Monday, March 26, 2018 9:38 PM
> My question is how I can disable TXSS. One way I found in the wmi.h is =
setting the number of sectors of TXSS to 0 or 1 > by using =
wmi_prio_tx_sectors_num_cmd so that the TXSS will only use 1 sector.
> However, when I called this cmd, I got this error:
> wil6210 0000:03:00.0 wlp3s0: wil6210_irq_misc: Firmware error =
detected, assert codes FW 0x00001038, UCODE 0x00000000
> wil6210 0000:03:00.0 wlp3s0: wil_fw_core_dump: fw core dumped, size =
823296 bytes
> wil6210 0000:03:00.0 wlp3s0: wil_notify_fw_error: Notify about =
firmware error
> So I am wondering whether the firmware does not support these kinds of =
wmi commands. Does anyone have any experience on this? Thank you.
Indeed this error indicates that FW doesn't support these WMI commands.
We are working on releasing new FW version with support for these =
commands.
Thanks,
Dedy.
next prev parent reply other threads:[~2018-03-29 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 18:37 wil6210: low level sector API David Dean
2018-03-29 12:29 ` Dedy Lansky [this message]
2018-04-18 18:01 ` David Dean Zhang
2018-04-22 14:29 ` Dedy Lansky
2018-04-27 21:40 ` David Dean Zhang
-- strict thread matches above, loose matches on Subject: below --
2024-08-24 17:31 Herman Zeilstra
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='001901d3c759$8cd5b970$a6812c50$@codeaurora.org' \
--to=dlansky@codeaurora.org \
--cc=daviddean166@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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.