From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "bjorn@helgaas.com" <bjorn@helgaas.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Mertarg10@gmail.com" <Mertarg10@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Fran RR <fjrr87@outlook.com>
Subject: RE: Fwd: [Bug 201647] New: Intel Wireless card 3165 does not get detected but bluetooth works
Date: Tue, 11 Dec 2018 16:32:25 +0000 [thread overview]
Message-ID: <0BA3FCBA62E2DC44AF3030971E174FB30133756A29@HASMSX112.ger.corp.intel.com> (raw)
In-Reply-To: <20181211135121.GB99796@google.com>
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
+ the person who reported the problem with 9560
>
> On Tue, Dec 11, 2018 at 06:35:20AM +0000, Grumbach, Emmanuel wrote:
> > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=201647
>
> > > The Windows device manager info (requested above) would be
> interesting.
>
> I *thought* I had requested it, but I can't find that. Mert, thanks for the
> screenshot you attached. Would you mind also capturing the other tabs
> from device manager? I'm really looking for a hex dump of the config space,
> which should be at least 256 bytes. I *think* that's available somewhere in
> device manager. If not, AIDA64
> (https://www.aida64.com/downloads) should be able to get it.
>
> > FWIW: I saw another problem like this with a 9650 device.
>
> Do you have a pointer to any info about this 9650 issue? Maybe that would
> have a clue.
I added him here so that you can ask whatever you like :)
The story is the same. I am attaching a picture I got from the reporter.
I can confirm that this device ID / subdevice ID is supported by the linux driver.
>
> > PS: PCI folks don't use bugzilla's anymore? It's all over the mailing list?
>
> Personally, I use bugzilla as a convenient place to archive artifacts like logs,
> screenshots, etc. But it doesn't seem as convenient for conversations as the
> mailing list, and it doesn't have the visibility that the list does.
>
[-- Attachment #2: win10.jpg --]
[-- Type: image/jpeg, Size: 130054 bytes --]
next prev parent reply other threads:[~2018-12-11 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-201647-193951@https.bugzilla.kernel.org/>
[not found] ` <CABhMZUXc4FS-f52ZDsErEhbkm_jjEz+kn75YO5Tuvp42Qm+1xw@mail.gmail.com>
2018-11-28 21:19 ` Bjorn Helgaas
2018-12-02 6:57 ` Grumbach, Emmanuel
2018-12-10 22:24 ` Bjorn Helgaas
2018-12-11 6:35 ` Grumbach, Emmanuel
2018-12-11 13:51 ` Bjorn Helgaas
2018-12-11 16:32 ` Grumbach, Emmanuel [this message]
2018-12-11 18:26 ` Bjorn Helgaas
2018-12-11 18:31 ` Grumbach, Emmanuel
2018-12-11 18:38 ` Bjorn Helgaas
2018-12-11 18:51 ` Grumbach, Emmanuel
2018-12-11 22:21 ` Bjorn Helgaas
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=0BA3FCBA62E2DC44AF3030971E174FB30133756A29@HASMSX112.ger.corp.intel.com \
--to=emmanuel.grumbach@intel.com \
--cc=Mertarg10@gmail.com \
--cc=bjorn@helgaas.com \
--cc=fjrr87@outlook.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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
all inboxes | Powered by JetHome®