From: Arend van Spriel <aspriel@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"Schmirr Wurst" <schmirrwurst@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
b43-dev <b43-dev@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: lspci not working
Date: Sun, 17 May 2015 11:27:55 +0200 [thread overview]
Message-ID: <55585F1B.5050008@gmail.com> (raw)
In-Reply-To: <CACna6rzxZJg3MHsBV3vtaEtgUbh9umE6CS=2YkgkexT51J1oiw@mail.gmail.com>
On 17-05-15 10:47, Rafa? Mi?ecki wrote:
> On 17 May 2015 at 02:21, Schmirr Wurst <schmirrwurst@gmail.com> wrote:
>> 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...
>
> Why do you guess so? You didn't provide us any details about entries there.
Indeed a wrong guess. The sdio specification allows a physical sdio
device to provide multiple sdio functions, which are instantiated as
devices in the linux driver model. So they will have the same modalias.
>> In that directory, I see a directory mmc1:0001:2
>> under device I have 0xa94d
>>
>> I completly lost, maybe you understand that information, sorry..
>
> You provided only one single device id, without even vendor id. Give
> us at least a list of devices, e.g. by their modalias, like
> cat /sys/bus/sdio/devices/*/modalias
>
Converting 0xa94d gives 43341, which does not look like a coincidence to
me. So this Asus device comes with a newer chip, but it is supported by
brcmfmac (provided vendor id is indeed 0x02d0!).
Regards,
Arend
next prev parent reply other threads:[~2015-05-17 9:27 UTC|newest]
Thread overview: 19+ 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
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 [this message]
2015-05-17 11:17 ` Rafał Miłecki
2015-05-17 10:23 ` Arend van Spriel
2015-05-17 11:18 ` Rafał Miłecki
[not found] ` <CA+0W_AuXCgFoH2fm0kr5V9nkcNB9bCp8M4KF=J2=c5QCBrbL8A@mail.gmail.com>
[not found] ` <CA+0W_Asj3f10VJ=NVu_WGRO3iLyLZY3AhHnD3pkb7-r45j-yYA@mail.gmail.com>
2015-05-17 13:00 ` Schmirr Wurst
2015-05-17 13:17 ` Hauke Mehrtens
2015-05-17 14:10 ` Schmirr Wurst
[not found] ` <CA+0W_AsY3sz9+t=guZYi9v-_X1-MMc5=11FPm=4QKkMxNd=uFQ@mail.gmail.com>
[not found] ` <CA+0W_Au9-xCi4mb1+1UTqQJ+ymHTqzbiORO6yiZD6CBAjZN1yQ@mail.gmail.com>
2015-05-17 14:34 ` Fwd: " Arend van Spriel
[not found] ` <CA+0W_Au6N1cSELTBOQG2yPkiT5Pe9-sg3s_5YtNc9zFZ6T13sw@mail.gmail.com>
[not found] ` <CA+0W_AsDSA_Pg2f2HtgLkm2Nnn8C-FdxbrXe2F9p-d+y4ACbvg@mail.gmail.com>
2015-05-17 16:49 ` Fwd: " 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
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=55585F1B.5050008@gmail.com \
--to=aspriel@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--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).