linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
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 12:38:05 -0600	[thread overview]
Message-ID: <20181211183805.GG99796@google.com> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB30133756B5D@HASMSX112.ger.corp.intel.com>

On Tue, Dec 11, 2018 at 06:31:47PM +0000, Grumbach, Emmanuel wrote:
> > On Tue, Dec 11, 2018 at 04:32:25PM +0000, Grumbach, Emmanuel wrote:
> > > > On Tue, Dec 11, 2018 at 06:35:20AM +0000, Grumbach, Emmanuel wrote:
> > > > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=201647
> > > >
> > > > > 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.
> > 
> > Was there a resolution, i.e., if somebody figured out how to make the
> > 9650 wifi work, maybe a similar solution would work for the 3165?
> 
> Unfortunately not, I am stuck there at the exact same point.
> No Wifi device shows up in lspci...

Is there a public spec?  My patience for reverse engineering things
that are documented somewhere that I'm not allowed to see is pretty
limited.  Presumably *you* should be able to see the spec, since this
is an Intel device and you have an @intel.com address?

From what we can tell so far, I don't *think* this is a PCI issue.  If
the device doesn't respond to a PCI config access, the PCI core can't
really be expected to do anything about it.

Bjorn

  reply	other threads:[~2018-12-11 18:38 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   ` Fwd: [Bug 201647] New: Intel Wireless card 3165 does not get detected but bluetooth works 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
2018-12-11 18:26               ` Bjorn Helgaas
2018-12-11 18:31                 ` Grumbach, Emmanuel
2018-12-11 18:38                   ` Bjorn Helgaas [this message]
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=20181211183805.GG99796@google.com \
    --to=helgaas@kernel.org \
    --cc=Mertarg10@gmail.com \
    --cc=bjorn@helgaas.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=fjrr87@outlook.com \
    --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;
as well as URLs for NNTP newsgroup(s).