From: Larry Finger <Larry.Finger@lwfinger.net>
To: Schmirr Wurst <schmirrwurst@gmail.com>, b43-dev@lists.infradead.org
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: lspci not working
Date: Sat, 16 May 2015 09:34:20 -0500 [thread overview]
Message-ID: <5557556C.2080107@lwfinger.net> (raw)
In-Reply-To: <CA+0W_As0c=eAijuvWfSBLMY4vj2P1-zoMsjz1mmNm0_vfepPCA@mail.gmail.com>
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.
I am not familiar with any Broadcom devices that use SDIO, but I have Cc'd the
linux-wireless mailing list. Perhaps someone there will be able to help.
I am currently working with a Winbook TW100, which is another Bay Trail device.
It uses a Realtek RTL8723BS, which also has an SDIO interface.
Larry
WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Schmirr Wurst <schmirrwurst@gmail.com>, b43-dev@lists.infradead.org
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: lspci not working
Date: Sat, 16 May 2015 09:34:20 -0500 [thread overview]
Message-ID: <5557556C.2080107@lwfinger.net> (raw)
In-Reply-To: <CA+0W_As0c=eAijuvWfSBLMY4vj2P1-zoMsjz1mmNm0_vfepPCA@mail.gmail.com>
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.
I am not familiar with any Broadcom devices that use SDIO, but I have Cc'd the
linux-wireless mailing list. Perhaps someone there will be able to help.
I am currently working with a Winbook TW100, which is another Bay Trail device.
It uses a Realtek RTL8723BS, which also has an SDIO interface.
Larry
next prev parent reply other threads:[~2015-05-16 14:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 9:12 lspci not working Schmirr Wurst
2015-05-16 14:34 ` Larry Finger [this message]
2015-05-16 14:34 ` Larry Finger
2015-05-16 14:58 ` Rafał Miłecki
2015-05-16 14:58 ` Rafał Miłecki
2015-05-16 21:16 ` Arend van Spriel
2015-05-16 21:16 ` Arend van Spriel
2015-05-17 0:21 ` Schmirr Wurst
2015-05-17 0:21 ` Schmirr Wurst
2015-05-17 8:47 ` Rafał Miłecki
2015-05-17 8:47 ` Rafał Miłecki
2015-05-17 9:27 ` Arend van Spriel
2015-05-17 9:27 ` Arend van Spriel
2015-05-17 11:17 ` Rafał Miłecki
2015-05-17 11:17 ` Rafał Miłecki
2015-05-17 10:23 ` Arend van Spriel
2015-05-17 10:23 ` Arend van Spriel
2015-05-17 11:18 ` Rafał Miłecki
2015-05-17 11:18 ` Rafał Miłecki
2015-05-17 12:42 ` Schmirr Wurst
2015-05-17 12:57 ` Schmirr Wurst
2015-05-17 13:00 ` Schmirr Wurst
2015-05-17 13:00 ` Schmirr Wurst
2015-05-17 13:17 ` Hauke Mehrtens
2015-05-17 13:17 ` Hauke Mehrtens
[not found] ` <CA+0W_AsY3sz9+t=guZYi9v-_X1-MMc5=11FPm=4QKkMxNd=uFQ@mail.gmail.com>
2015-05-17 14:08 ` Fwd: " Schmirr Wurst
2015-05-17 14:34 ` Arend van Spriel
2015-05-17 14:34 ` Arend van Spriel
[not found] ` <CA+0W_Au6N1cSELTBOQG2yPkiT5Pe9-sg3s_5YtNc9zFZ6T13sw@mail.gmail.com>
2015-05-17 14:48 ` Fwd: " Schmirr Wurst
2015-05-17 16:49 ` Arend van Spriel
2015-05-17 16:49 ` Arend van Spriel
2015-05-17 16:56 ` Hauke Mehrtens
2015-05-17 16:56 ` Hauke Mehrtens
2015-05-17 17:37 ` Arend van Spriel
2015-05-17 17:37 ` Arend van Spriel
2015-05-17 17:56 ` Schmirr Wurst
2015-05-17 17:56 ` Schmirr Wurst
2015-05-17 18:56 ` Arend van Spriel
2015-05-17 18:56 ` Arend van Spriel
2015-05-17 14:10 ` Schmirr Wurst
2015-05-17 14:10 ` Schmirr Wurst
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=5557556C.2080107@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=schmirrwurst@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.