From: Arend van Spriel <arend@broadcom.com>
To: Schmirr Wurst <schmirrwurst@gmail.com>
Cc: "Arend van Spriel" <aspriel@gmail.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Larry Finger" <Larry.Finger@lwfinger.net>,
b43-dev <b43-dev@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: lspci not working
Date: Sun, 17 May 2015 12:23:02 +0200 [thread overview]
Message-ID: <55586C06.8050803@broadcom.com> (raw)
In-Reply-To: <CA+0W_At43pB=FeBR4jJzKxO3ruaATAidU8rimBOE3bLM1wKGsA@mail.gmail.com>
On 05/17/15 02:21, Schmirr Wurst wrote:
> Thank you all, for your answers...
>
> In fact I'm trying to help a friend with that, and I must say I never
> hard such a complicated device...
Well, it depends what aspect you find complicated. It is pretty
straightforward device that just needs a driver to work.
> I tried as suggested to had a look at
> /sys/bus/sdio/devices, but the only devices around there a 3
> mmc1:0001:1 to :3, I guess it is something else...
>
> I already try to install brcmfmac_sdio , with some tutorial from the
> internet, but it didn't work...
> actually, I see under /sys/bus/sdio/drivers brcmfmac_sdio ...
>
> In that directory, I see a directory mmc1:0001:2
> under device I have 0xa94d
>
> I completly lost, maybe you understand that information, sorry..
I do. The fact that you see a subdirectory mmc1:0001:2 in
/sys/bus/sdio/drivers/brcmfmac_sdio means that the driver was probed for
this device. Now would be a good time to share your (friends') kernel
log, but my guess is you are either missing firmware or nvram data or
both for this device.
And could you try to answer inline instead of top-posting.
Regards,
Arend
> 2015-05-16 23:16 GMT+02:00 Arend van Spriel<aspriel@gmail.com>:
>>
>>
>> On 16-05-15 16:58, Rafał Miłecki wrote:
>>>
>>> On 16 May 2015 at 16:34, Larry Finger<Larry.Finger@lwfinger.net> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-17 10:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+0W_As0c=eAijuvWfSBLMY4vj2P1-zoMsjz1mmNm0_vfepPCA@mail.gmail.com>
2015-05-16 14:34 ` lspci not working Larry Finger
2015-05-16 14:58 ` Rafał Miłecki
2015-05-16 21:16 ` Arend van Spriel
2015-05-17 0:21 ` Schmirr Wurst
2015-05-17 8:47 ` Rafał Miłecki
2015-05-17 9:27 ` Arend van Spriel
2015-05-17 11:17 ` Rafał Miłecki
2015-05-17 10:23 ` Arend van Spriel [this message]
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: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
[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:56 ` Hauke Mehrtens
2015-05-17 17:37 ` Arend van Spriel
2015-05-17 17:56 ` Schmirr Wurst
2015-05-17 18:56 ` Arend van Spriel
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=55586C06.8050803@broadcom.com \
--to=arend@broadcom.com \
--cc=Larry.Finger@lwfinger.net \
--cc=aspriel@gmail.com \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=schmirrwurst@gmail.com \
--cc=zajec5@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 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).