Return-path: Received: from mail-wg0-f53.google.com ([74.125.82.53]:33337 "EHLO mail-wg0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751117AbbEPVQI (ORCPT ); Sat, 16 May 2015 17:16:08 -0400 Received: by wgin8 with SMTP id n8so149728051wgi.0 for ; Sat, 16 May 2015 14:16:07 -0700 (PDT) Message-ID: <5557B396.9080300@gmail.com> (sfid-20150516_231614_027088_80CFB231) Date: Sat, 16 May 2015 23:16:06 +0200 From: Arend van Spriel MIME-Version: 1.0 To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , Larry Finger CC: Schmirr Wurst , b43-dev , linux-wireless Subject: Re: lspci not working References: <5557556C.2080107@lwfinger.net> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 16-05-15 16:58, Rafał Miłecki wrote: > 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). Indeed. The broadcom device would have a modalias starting 'sdio:c00v02D0d'. The Asus T100 series use 43241 if I am not mistaken. It should be supported by the brcmfmac driver. Regards, Arend