From: "Arend van Spriel" <arend@broadcom.com>
To: "John Talbut" <jt@dpets.co.uk>
Cc: "Hauke Mehrtens" <hauke@hauke-m.de>,
"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 23:00:42 +0100 [thread overview]
Message-ID: <51521A8A.6060900@broadcom.com> (raw)
In-Reply-To: <5151FB85.5080007@dpets.co.uk>
On 03/26/2013 08:48 PM, John Talbut wrote:
> On 26/03/13 19:01, Hauke Mehrtens wrote:
>> Hi,
>>
>> Could you provide the output of "modinfo bcma | grep alias" as Rafał asked.
>>
>> The Debian kernel 3.2 contains some patch removing all PCI IDs expect
>> 14e4:4331 from bcma, if this is still in your kernel that's the problem.
>>
>> If this is the case please try this:
>>
>> echo "14e4 4357" > /sys/bus/pci/drivers/bcma-pci-bridge/new_id
>>
>> Hauke
>>
> Hi
>
> modinfo bcma | grep alias
> ERROR: Module bcma not found.
That is because you have it compiled into the kernel.
> echo "14e4 4357" > /sys/bus/pci/drivers/bcma-pci-bridge/new_id
> bash: /sys/bus/pci/drivers/bcma-pci-bridge/new_id: No such file or directory
This could mean you do not have CONFIG_BCMA_HOST_PCI=y in your .config
> Because I am not using modules?
>
> I found a reference to this patch:
> http://git.grml.org/?p=grml-kernel.git;a=blobdiff;f=linux-3/debian/patches/debian/bcma-Do-not-claim-PCI-device-IDs-also-claimed-by-brc.patch;fp=linux-3/debian/patches/debian/bcma-Do-not-claim-PCI-device-IDs-also-claimed-by-brc.patch;h=0000000000000000000000000000000000000000;hp=f8fd94163e10ff9fa3803d6f7aaae7adb3b2c0f5;hb=dfd70ee5283216f7635b367327a9389b10030d87;hpb=76b7ce681bb74b69aea9b155747c47ec86d4e6c5
>
> This appears to refer to /drivers/bcma/host_pci.c, but the patch does
> not appear to be applied to that file in the Debian 3.8 kernel source,
> there are lines including:
> { PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4357) },
> in the 3.8 version of the file.
That patch was from the days that brcmsmac did not use bcma. In 3.8 you
do not need that patch.
Gr. AvS
next prev parent reply other threads:[~2013-03-26 22:00 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 ` brcmsmac in kernel driver on a Samsung NC110 Arend van Spriel
2013-03-26 14:30 ` 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 [this message]
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=51521A8A.6060900@broadcom.com \
--to=arend@broadcom.com \
--cc=hauke@hauke-m.de \
--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).