From: Larry Finger <Larry.Finger@lwfinger.net>
To: Ruben De Smet <ruben.de.smet@telenet.be>,
b43-dev@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>,
brcm80211-dev-list@broadcom.com
Subject: BCM43228
Date: Fri, 01 Nov 2013 12:07:18 -0500 [thread overview]
Message-ID: <5273DFC6.8000305@lwfinger.net> (raw)
In-Reply-To: <5273D018.7080607@telenet.be>
On 11/01/2013 11:00 AM, Ruben De Smet wrote:
> AFAIK, broadcom only offers it's drivers for intel x86 and x64_86; I
> guess by MIPS, you mean the architecture? (why wouldn't the intel
> driver work? Pretty unknown on the subject ;) )
>
> I read the WIP mail about the 227 chip, I could possibly wait for that
> one to be released and test it out on mine?
>
> For the record: the issue I'm having is as follows: when connecting
> via the bluetooth part of the chip to my phone and using DUN to
> connect to the internet, everything works fine until I shut down the
> connection. Then my kernel panics. (Another issue of course is the
> fact that wl is the only closed source thing in my kernel running atm
> on my notebook...)
>
> On brcmsmac: is linux-wireless the right mailinglist to post to then?
> I see that the range of supported devices is more close to my chip
> than b43 is ;)
> I added brcm80211-dev-list at broadcom.com to this mail too, which looks
> like the more appropriate mailinglist to post the issue to.
>
> R
>
> PS. snippet of the output of 'lspci -nn':
>
> 03:00.0 Network controller [0280]: Broadcom Corporation BCM43228
> 802.11a/b/g/n [14e4:4359]
>
> Other information on request, will try to answer asap.
The MIPS drivers are part of the codes used in various SoC implementations used
in wireless routers. Disassembling an x86 code stream is much harder than for a
machine like MIPS where all instructions are the same size.
Larry
WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Ruben De Smet <ruben.de.smet@telenet.be>,
b43-dev@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>,
brcm80211-dev-list@broadcom.com
Subject: Re: BCM43228
Date: Fri, 01 Nov 2013 12:07:18 -0500 [thread overview]
Message-ID: <5273DFC6.8000305@lwfinger.net> (raw)
In-Reply-To: <5273D018.7080607@telenet.be>
On 11/01/2013 11:00 AM, Ruben De Smet wrote:
> AFAIK, broadcom only offers it's drivers for intel x86 and x64_86; I
> guess by MIPS, you mean the architecture? (why wouldn't the intel
> driver work? Pretty unknown on the subject ;) )
>
> I read the WIP mail about the 227 chip, I could possibly wait for that
> one to be released and test it out on mine?
>
> For the record: the issue I'm having is as follows: when connecting
> via the bluetooth part of the chip to my phone and using DUN to
> connect to the internet, everything works fine until I shut down the
> connection. Then my kernel panics. (Another issue of course is the
> fact that wl is the only closed source thing in my kernel running atm
> on my notebook...)
>
> On brcmsmac: is linux-wireless the right mailinglist to post to then?
> I see that the range of supported devices is more close to my chip
> than b43 is ;)
> I added brcm80211-dev-list@broadcom.com to this mail too, which looks
> like the more appropriate mailinglist to post the issue to.
>
> R
>
> PS. snippet of the output of 'lspci -nn':
>
> 03:00.0 Network controller [0280]: Broadcom Corporation BCM43228
> 802.11a/b/g/n [14e4:4359]
>
> Other information on request, will try to answer asap.
The MIPS drivers are part of the codes used in various SoC implementations used
in wireless routers. Disassembling an x86 code stream is much harder than for a
machine like MIPS where all instructions are the same size.
Larry
next prev parent reply other threads:[~2013-11-01 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 9:55 BCM43228 Ruben De Smet
2013-11-01 15:31 ` BCM43228 Larry Finger
2013-11-01 15:31 ` BCM43228 Larry Finger
2013-11-01 16:00 ` BCM43228 Ruben De Smet
2013-11-01 16:00 ` BCM43228 Ruben De Smet
2013-11-01 17:07 ` Larry Finger [this message]
2013-11-01 17:07 ` BCM43228 Larry Finger
2013-11-01 18:09 ` BCM43228 Ruben De Smet
2013-11-01 18:09 ` BCM43228 Ruben De Smet
2013-11-01 17:53 ` BCM43228 Arend van Spriel
2013-11-01 17:53 ` BCM43228 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=5273DFC6.8000305@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=brcm80211-dev-list@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=ruben.de.smet@telenet.be \
/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.