All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: pci id 14e4:4727 (bcm4313) status?
Date: Wed, 03 Nov 2010 11:53:03 -0500	[thread overview]
Message-ID: <4CD1936F.4030100@lwfinger.net> (raw)
In-Reply-To: <4CD18DB4.60405@lakedaemon.net>

On 11/03/2010 11:28 AM, Jason wrote:
> All,
> 
> I have a pci-express card that shows itself as pci_id 14e4:4727. 
> According to [1], it says partial support since 2.6.33
> (b43/wl/brcm80211).  I was hoping that meant b43 since it has much
> better mac80211 integration than brcm80211.  I didn't think brcm80211
> was in 2.6.33.
> However, compat-wireless (built from tarball) doesn't see it.  grep the
> source code doesn't pull up '4727' in b43... I tried to update my
> wireless-testing-2.6 tree, but it looks like it's still having trouble,
> latest is 229aebb... from Oct 24th.
> 
> So, what will it take to get it up and running?  I've contributed some
> patches to staging, but they're mainly janitorial/checkpatch stuff for
> brcm80211.  Are there some beginner tasks for b43 (ie dig through
> brcm80211 and port over) that might help out?

That device is not supported by b43. As it now stands, b43 requires a device
with the SSB interconnect, which the BCM4313 does not have. If you did fix b43
to operate without the SSB, then you would still have no support for N PHY. That
one is being worked on so that N PHYs with SSB can be supported.

My interpretation of the "partially supported" statement is that bleeding-edge
compat wireless has been backported that far.

My latest pull of wireless-testing has 2.6.37-rc1 from November 1. It includes
brcm80211.

Larry

  parent reply	other threads:[~2010-11-03 16:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 16:28 pci id 14e4:4727 (bcm4313) status? Jason
2010-11-03 16:35 ` Gábor Stefanik
2010-11-03 16:53 ` Larry Finger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-11-04 12:21 Ariel Pedraza
2010-11-04 14:39 ` Gábor Stefanik
2010-11-04 20:44   ` Henry Ptasinski
2010-11-04 21:42     ` Gábor Stefanik
2010-11-04 21:42       ` Gábor Stefanik
2010-11-04 21:43       ` Gábor Stefanik
2010-11-04 21:43         ` Gábor Stefanik

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=4CD1936F.4030100@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.