From: Luciano Coelho <luciano.coelho@intel.com>
To: Izzy Kulbe <kernel@unikorn.me>, Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: add device ID for Rivet Networks Killer Wireless-AC 1550
Date: Tue, 27 Mar 2018 16:10:52 +0300 [thread overview]
Message-ID: <1522156252.3786.272.camel@intel.com> (raw)
In-Reply-To: <a7f17e2bd232252004f71cbbc719781d68e735a4.camel@unikorn.me>
On Tue, 2018-03-27 at 14:48 +0200, Izzy Kulbe wrote:
> On Tue, 2018-03-27 at 15:38 +0300, Luciano Coelho wrote:
> > On Tue, 2018-03-27 at 15:37 +0300, Luciano Coelho wrote:
> > > On Tue, 2018-03-27 at 14:03 +0200, Izzy Kulbe wrote:
> > > Wait a bit. This ID looks strange, someone else reported this
> > > already
> > > and it looked strange, with an incorrect subsystem vendor ID.
> > >
> > > Can you run lspci like this and let us know the results?
> > > weird
> > > lspci -nv -s 3b:00.0
> >
> > Sorry, please substitute the 3b:00.0 with the correct PCI slot in
> > your
> > system. If you're not sure, remove the '-s 3b:00.0' entirely so
> > we'll
> > get the results for all devices.
> >
> > --
> > Luca.
>
> The subsystem device in lspci itself reports "Bigfoot Networks,
> Inc. Wireless-AC 9260" instead of when lookup is enabled. AFAIR this
> was a company that was bought by Qualcomm? So not Rivet/Killer.
>
> Here's the lspci output:
>
> root@dokidoki $> # lspci-nv -s 04:00.0
> 04:00.0 0280: 8086:2526 (rev 29)
> Subsystem: 1a56:1550
> Flags: bus master, fast devsel, latency 0, IRQ 17
> Memory at d3d00000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: [c8] Power Management version 3
> Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [40] Express Endpoint, MSI 00
> Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [14c] Latency Tolerance Reporting
> Capabilities: [154] L1 PM Substates
> Kernel driver in use: iwlwifi
> Kernel modules: iwlwifi
Thanks!
Yeah, this looks wrong and the same as someone else reported. :(
This value is coming from the OTP in the NIC and seems to be wrong. I
have to contact our engineer who is responsible for the OTP data. I'll
let you know once I get back some more information.
--
Cheers,
Luca.
next prev parent reply other threads:[~2018-03-27 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 10:54 [PATCH] iwlwifi: add device ID for Rivet Networks Killer Wireless-AC 1550 Izzy Kulbe
2018-03-27 11:48 ` Kalle Valo
2018-03-27 12:03 ` Izzy Kulbe
2018-03-27 12:37 ` Luciano Coelho
2018-03-27 12:38 ` Luciano Coelho
2018-03-27 12:48 ` Izzy Kulbe
2018-03-27 13:10 ` Luciano Coelho [this message]
2018-03-27 14:09 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2018-03-27 10:43 Izzy Kulbe
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=1522156252.3786.272.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=kernel@unikorn.me \
--cc=kvalo@codeaurora.org \
--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 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).