From: "Arend van Spriel" <arend@broadcom.com>
To: "John Talbut" <jt@dpets.co.uk>
Cc: "Rafał Miłecki" <zajec5@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: brcmsmac in kernel driver on a Samsung NC110
Date: Tue, 26 Mar 2013 13:01:24 +0100 [thread overview]
Message-ID: <51518E14.3050500@broadcom.com> (raw)
In-Reply-To: <515189C6.7070003@dpets.co.uk>
On 03/26/2013 12:43 PM, John Talbut wrote:
> On 26/03/13 11:29, Arend van Spriel wrote:
>> On 03/26/2013 12:13 PM, John Talbut wrote:
>>>
>>> On 26/03/13 10:53, Arend van Spriel wrote:
>>>> On 03/26/2013 11:34 AM, John Talbut wrote:
>>>>> Kernel log attached.
>>>>>
>>>>
>>>> Now this is weird. I do not see any BCMA log messages. Can you give
>>>> output of following command:
>>>>
>>>> $ lspci -n -s 1:0.0
>>>
>>> 01:00.0 0280: 14e4:4357 (rev 01)
>>
>> Ok, no problem there.
>>
>> digging further in sysfs. Can you execute the following commands:
>>
>> if it exists:
>> $ ls /sys/bus/bcma
>> $ ls /sys/bus/bcma/devices
>> $ ls /sys/bus/bcma/drivers
>>
>> if it exists also following:
>> $ ls -l /sys/bus/bcma/drivers/brcmsmac
>
> root@johnwtnc110:/usr/src/linux-source-3.8# ls /sys/bus/bcma
> devices drivers drivers_autoprobe drivers_probe uevent
> root@johnwtnc110:/usr/src/linux-source-3.8# ls /sys/bus/bcma/devices
The fact that there are no devices detected under bcma is suspicious.
Adding bcma developer to the list. Maybe he knows about issues when
having bcma compiled in kernel image.
Regards,
Arend
next parent reply other threads:[~2013-03-26 12:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51514F1B.1080207@dpets.co.uk>
[not found] ` <5151639F.4010700@broadcom.com>
[not found] ` <51516BC2.5010004@dpets.co.uk>
[not found] ` <515173A4.7030607@broadcom.com>
[not found] ` <515179C5.50406@dpets.co.uk>
[not found] ` <51517E28.5000303@broadcom.com>
[not found] ` <515182C6.5030305@dpets.co.uk>
[not found] ` <51518682.7060503@broadcom.com>
[not found] ` <515189C6.7070003@dpets.co.uk>
2013-03-26 12:01 ` Arend van Spriel [this message]
2013-03-26 14:30 ` brcmsmac in kernel driver on a Samsung NC110 John Talbut
2013-03-26 17:01 ` Rafał Miłecki
2013-03-26 16:59 ` Rafał Miłecki
2013-03-26 18:43 ` John Talbut
2013-03-26 19:01 ` Hauke Mehrtens
2013-03-26 19:48 ` John Talbut
2013-03-26 22:00 ` Arend van Spriel
2013-03-27 7:46 ` Rafał Miłecki
2013-03-27 10:24 ` John Talbut
2013-03-27 10:33 ` Rafał Miłecki
2013-03-27 10:45 ` John Talbut
2013-03-27 11:22 ` Arend van Spriel
2013-03-27 12:00 ` John Talbut
2013-03-27 12:06 ` Arend van Spriel
2013-03-27 12:21 ` John Talbut
2013-03-27 16:15 ` Arend van Spriel
2013-03-28 10:03 ` John Talbut
2013-03-28 11:23 ` 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=51518E14.3050500@broadcom.com \
--to=arend@broadcom.com \
--cc=jt@dpets.co.uk \
--cc=linux-wireless@vger.kernel.org \
--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).