From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 49517C5CFFE for ; Tue, 11 Dec 2018 18:38:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 169D220989 for ; Tue, 11 Dec 2018 18:38:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1544553488; bh=yCgCdyK1fBGSGXfuw9k6xiuVD+sR2FU2KbOb7mxa/RM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=SiZf0lUPI9oPJ2YiXOVXbixyYCTqZgCZbKf4uKItOgV7RHgBtOuIyq9FpERilWscA wFl3GC6Hh4+oldePpklux1BpBYtm65ALNxH28EQk8hmMUMJ2WR4muquHBTvLGuxEm4 YrPAX0qsd/uA+G2Z0IiPGGMPqJE+4ju+tsWfJlBU= DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 169D220989 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-pci-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726398AbeLKSiH (ORCPT ); Tue, 11 Dec 2018 13:38:07 -0500 Received: from mail.kernel.org ([198.145.29.99]:34576 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726254AbeLKSiH (ORCPT ); Tue, 11 Dec 2018 13:38:07 -0500 Received: from localhost (unknown [64.22.249.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 4C7AC20855; Tue, 11 Dec 2018 18:38:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1544553486; bh=yCgCdyK1fBGSGXfuw9k6xiuVD+sR2FU2KbOb7mxa/RM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=wH1kFZgZ7Qo8GZnz6QpgciHdnj48jmV5VN600zDocOjWu5jo4l/YmuO3LXQKsXJ32 sBCL+SgwGku9yUu2hueU30H3xPhgi7zELB2halDgKlGNk7wCpLwYQ013lM19cKBT0A Fb/9T9MNxI2ZqppLJwI4B/3xgCMGXbGgNLs0bBWU= Date: Tue, 11 Dec 2018 12:38:05 -0600 From: Bjorn Helgaas To: "Grumbach, Emmanuel" Cc: "bjorn@helgaas.com" , "linux-pci@vger.kernel.org" , "Mertarg10@gmail.com" , "linux-kernel@vger.kernel.org" , Fran RR Subject: Re: Fwd: [Bug 201647] New: Intel Wireless card 3165 does not get detected but bluetooth works Message-ID: <20181211183805.GG99796@google.com> References: <20181128211959.GB178809@google.com> <0BA3FCBA62E2DC44AF3030971E174FB3013373E4A3@HASMSX112.ger.corp.intel.com> <20181210222452.GC85090@google.com> <0BA3FCBA62E2DC44AF3030971E174FB30133754C00@HASMSX112.ger.corp.intel.com> <20181211135121.GB99796@google.com> <0BA3FCBA62E2DC44AF3030971E174FB30133756A29@HASMSX112.ger.corp.intel.com> <20181211182630.GF99796@google.com> <0BA3FCBA62E2DC44AF3030971E174FB30133756B5D@HASMSX112.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB30133756B5D@HASMSX112.ger.corp.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org 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