All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Dag Wieers <dag@wieers.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: BCM4321 (b43) on AppleTV (1st gen)
Date: Fri, 08 Feb 2013 10:24:08 -0600	[thread overview]
Message-ID: <511526A8.4010604@lwfinger.net> (raw)
In-Reply-To: <alpine.LRH.2.02.1302072238200.2736@pikachu.3ti.be>

On 02/07/2013 05:01 PM, Dag Wieers wrote:
> And that the kernel has been compiled using:
> ----
> CONFIG_B43=m
> CONFIG_B43_SSB=y
> CONFIG_B43_PCI_AUTOSELECT=y
> CONFIG_B43_PCICORE_AUTOSELECT=y
> CONFIG_B43_PIO=y
> CONFIG_B43_PHY_N=y
> CONFIG_B43_PHY_LP=y
> CONFIG_B43_PHY_HT=y
> CONFIG_B43_LEDS=y
> CONFIG_B43_DEBUG=y
> ----
>
> If the above can be trimmed down for this type of device I'd like to hear that
> as well (e.g. I am not sure if we need PIO or LEDS in this case).
>
> PS I am also interested in any power management capabilities the device has and
> that we could enable when the device is idle, since the system lacks proper
> power management capabilities by itself (suspend/hibernate) and seems to have a
> limited ACPI implementation.

As no one else seems to be responding, I'll try.

In the configuration, you certainly do not need PIO or LEDS. For that particular 
device, you also do not need PHY_LP, as that is strictly an 802.11g PHY. As to 
power-management capabilities, there are no configurable parameters.

What throughput do you get with Broadcom-wl with your setup? That will give you 
an idea of the potential performance of the device. As the equivalent of wl was 
used for the reverse engineering, that will certainly be the upper limit of what 
b43 can do. Only if the RE was perfect could we match that result.

Larry



  parent reply	other threads:[~2013-02-08 16:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 23:01 BCM4321 (b43) on AppleTV (1st gen) Dag Wieers
2013-02-08  1:06 ` Dag Wieers
2013-02-08 16:24 ` Larry Finger [this message]
2013-02-08 16:46 ` Jonas Gorski
     [not found] ` <CACna6rwrq1qF4Rmf81OhO7jrXouUdjcAvnMtJcnCb4s=zm7a2w@mail.gmail.com>
2013-04-03  9:16   ` Dag Wieers
2013-04-03  9:16     ` Dag Wieers
2013-04-03 10:35     ` Rafał Miłecki
2013-04-03 10:35       ` Rafał Miłecki

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=511526A8.4010604@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=dag@wieers.com \
    --cc=linux-wireless@vger.kernel.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.