Return-path: Received: from mail-ie0-f181.google.com ([209.85.223.181]:33194 "EHLO mail-ie0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751035AbbEPO6E (ORCPT ); Sat, 16 May 2015 10:58:04 -0400 Received: by iebgx4 with SMTP id gx4so142631548ieb.0 for ; Sat, 16 May 2015 07:58:04 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <5557556C.2080107@lwfinger.net> References: <5557556C.2080107@lwfinger.net> Date: Sat, 16 May 2015 16:58:04 +0200 Message-ID: (sfid-20150516_165808_216098_78C45BE8) Subject: Re: lspci not working From: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= To: Larry Finger Cc: Schmirr Wurst , b43-dev , linux-wireless Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 16 May 2015 at 16:34, Larry Finger wrote: > On 05/16/2015 04:12 AM, Schmirr Wurst wrote: >> >> I've already posted the message once, but as it was my first, I'm not >> sure, if it worked... >> >> Actually I'm trying to get read of a t100af from asus, that has a nice >> broadcom wifi chipset, but I'm wondering that I don't see anything >> with lspci, do that mean, that the chipset is broken ? >> (I though lspci is one level deeper than driver, and I should see >> something, even if I have driver problems) ? >> >> Could just somebody tell me if I'm right or wrong ? > > > On Intel Bay Trail tablets, the wifi device is frequently attached using an > SDIO bus, not a PCI connection. Accordingly, lspci will probably not show > the device. But you should be able to browse /sys/bus/sdio/devices/ I guess (assuming bus host driver is working).