b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Sven Köhler" <sven.koehler@gmail.com>
To: b43-dev@lists.infradead.org
Subject: BCM4360 support
Date: Mon, 29 Jun 2015 19:04:47 +0300	[thread overview]
Message-ID: <55916C9F.6090704@gmail.com> (raw)
In-Reply-To: <CACna6rzUjU8WCHMN7+zWVJbsrs_iBSHceTr=C3WQ03zPbqpzNg@mail.gmail.com>

Am 17.02.2015 um 17:57 schrieb Rafa? Mi?ecki:
> On 17 February 2015 at 16:40,  <ockham-wpgQ8x317gheoWH0uzbU5w@public.gmane.org> wrote:
>> I recently got a new MacBook Pro Retina (15"), which comes with a Broadcom
>> 4360 Wifi:
>>
>> 03:00.0 Network controller [0280]: Broadcom Corporation BCM4360 802.11ac
>> Wireless Network Adapter [14e4:43a0] (rev 03)
>>
>> I installed Fedora 21 on it. Getting Wifi up and running was sort of a PITA,
>> as it required installing the kmod-wl RPM via an USB stick [1].
>>
>> Can I, as a user, contribute to having the b43 kernel module support BCM4360
>> [2], e.g. by testing stuff?
> 
> Not really. I already have some AC-PHY hardware, once I get it
> running, it may be useful to test other models as well. But today
> we're still far away from getting it running.

It would help if we get anything usable, even if it was limited to
802.11g or 802.11n. Does that make things simpler? Or are AC-PHYs simply
that different from previous ones?

Note that Broadcom's wl driver isn't that good either. I cannot get a
stable connection to my access point at 802.11n. I see dramatic
increases in ping time here and there. I had to downgrade my AP to
802.11g. I never tested 802.11ac performance.


Regards,
  Sven

  reply	other threads:[~2015-06-29 16:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 15:40 BCM4360 support ockham at raz.or.at
2015-02-17 15:57 ` Rafał Miłecki
2015-06-29 16:04   ` Sven Köhler [this message]
2015-02-17 16:08 ` Evgeniy Dushistov
  -- strict thread matches above, loose matches on Subject: below --
2015-09-09 21:49 Moro Modo
2015-09-13 16:38 ` Sven Köhler
2015-09-16  4:19   ` Kyle Sanderson

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=55916C9F.6090704@gmail.com \
    --to=sven.koehler@gmail.com \
    --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 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).