From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: BCM4318KFBG not recognized by b43
Date: Wed, 17 Nov 2010 17:23:10 -0600 [thread overview]
Message-ID: <4CE463DE.60609@lwfinger.net> (raw)
In-Reply-To: <AANLkTimAk2Mf7PvhyOZ3PGEg15hgznbySADn6OpbGS4F@mail.gmail.com>
On 11/17/2010 05:10 PM, Rafa? Mi?ecki wrote:
> W dniu 17 listopada 2010 23:48 u?ytkownik Daniel Klaffenbach
> <danielklaffenbach@gmail.com> napisa?:
>> On Wednesday 17 November 2010 22:39:31 Rafa? Mi?ecki wrote:
>>> Daniel: anything new on this? Could you put that card in some "normal"
>>> machine where it's relatively easy to install deubgging symbols?
>> I'm afraid no. My wireless router is the only machine in my environment with a
>> mini-PCI slot.
>>
>> I could however compile the kernel for my OpenWRT box with debugging symbols
>> (KERNEL_DEBUG_INFO in OpenWRT config), if this helps.
>
> Would be nice. I was afraid compiling kernel for OpenWRT won't be easy/fast.
>
>
>> Could the PCI vendor id alone be the reason for this problem? As I mentioned
>> earlier I've added the ID to b43_pci_bridge.c, but I am not sure whether this
>> is sufficient or not.
>
> Really, hard to say. dmesg with debugging symbold would at least give
> some info what's going on.
As the driver never loaded until you changed the vendor id, one could say that
your change "caused" the problem, but the data error you saw is likely due to an
attempt to read or write an address that is not properly mapped. There are too
many possibilities to speculate.
Larry
next prev parent reply other threads:[~2010-11-17 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 19:28 BCM4318KFBG not recognized by b43 Daniel Klaffenbach
2010-10-20 21:21 ` Gábor Stefanik
2010-10-20 22:43 ` Daniel Klaffenbach
2010-10-22 9:15 ` Daniel Klaffenbach
2010-10-22 20:16 ` Larry Finger
2010-11-17 21:39 ` Rafał Miłecki
2010-11-17 22:48 ` Daniel Klaffenbach
2010-11-17 23:10 ` Rafał Miłecki
2010-11-17 23:23 ` Larry Finger [this message]
2010-11-19 17:26 ` Daniel Klaffenbach
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=4CE463DE.60609@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
/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.