All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Eloy Anguiano <eloy.anguiano@uam.es>
Cc: b43-dev@lists.infradead.org, wireless <linux-wireless@vger.kernel.org>
Subject: b43 does not work on broadcom 43227
Date: Sun, 08 Jul 2012 17:31:24 -0500	[thread overview]
Message-ID: <4FFA0A3C.3040204@lwfinger.net> (raw)
In-Reply-To: <1341782825.4900.11.camel@zeus>

On 07/08/2012 04:27 PM, Eloy Anguiano wrote:
> Dear developers,
>
> Perhaps this is not a bug because my card is not probed. I have a
> Broadcom 43227 and the wireless does not work at all. I need your driver
> to activate it as a AP, but as far as I know, is imposible at this
> moment. Then I will use Broadcom driver waiting to your next
> developments. I say you because I think that developers need some
> feedback, for free software development.

As you guessed, it is not a bug as support for that device has never been 
enabled. I think your device will use bcma just as my BCM43228 does. I have 
started developing the patches needed to implement it with b43; however, I have 
not gotten very far. Could you please confirm that the the PCI ID is 14e4:4358? 
If that is correct, could you also try the attached patch and report the info 
that is logged in the dmesg output?

I think that Broadcom will be changing brcmsmac to support these devices, but my 
understanding is that they are concentrating on fullmac devices at the moment.

Larry
-------------- next part --------------
Index: wireless-testing-new/drivers/bcma/host_pci.c
===================================================================
--- wireless-testing-new.orig/drivers/bcma/host_pci.c
+++ wireless-testing-new/drivers/bcma/host_pci.c
@@ -272,6 +272,7 @@ static DEFINE_PCI_DEVICE_TABLE(bcma_pci_
 	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4331) },
 	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4353) },
 	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4357) },
+	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4738) },
 	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4727) },
 	{ 0, },
 };

WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Eloy Anguiano <eloy.anguiano@uam.es>
Cc: b43-dev@lists.infradead.org, wireless <linux-wireless@vger.kernel.org>
Subject: Re: b43 does not work on broadcom 43227
Date: Sun, 08 Jul 2012 17:31:24 -0500	[thread overview]
Message-ID: <4FFA0A3C.3040204@lwfinger.net> (raw)
In-Reply-To: <1341782825.4900.11.camel@zeus>

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

On 07/08/2012 04:27 PM, Eloy Anguiano wrote:
> Dear developers,
>
> Perhaps this is not a bug because my card is not probed. I have a
> Broadcom 43227 and the wireless does not work at all. I need your driver
> to activate it as a AP, but as far as I know, is imposible at this
> moment. Then I will use Broadcom driver waiting to your next
> developments. I say you because I think that developers need some
> feedback, for free software development.

As you guessed, it is not a bug as support for that device has never been 
enabled. I think your device will use bcma just as my BCM43228 does. I have 
started developing the patches needed to implement it with b43; however, I have 
not gotten very far. Could you please confirm that the the PCI ID is 14e4:4358? 
If that is correct, could you also try the attached patch and report the info 
that is logged in the dmesg output?

I think that Broadcom will be changing brcmsmac to support these devices, but my 
understanding is that they are concentrating on fullmac devices at the moment.

Larry

[-- Attachment #2: bcma_enable_43227 --]
[-- Type: text/plain, Size: 548 bytes --]

Index: wireless-testing-new/drivers/bcma/host_pci.c
===================================================================
--- wireless-testing-new.orig/drivers/bcma/host_pci.c
+++ wireless-testing-new/drivers/bcma/host_pci.c
@@ -272,6 +272,7 @@ static DEFINE_PCI_DEVICE_TABLE(bcma_pci_
 	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4331) },
 	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4353) },
 	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4357) },
+	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4738) },
 	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4727) },
 	{ 0, },
 };

  reply	other threads:[~2012-07-08 22:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-08 21:27 b43 does not work on broadcom 43227 Eloy Anguiano
2012-07-08 22:31 ` Larry Finger [this message]
2012-07-08 22:31   ` Larry Finger
2012-07-09  8:53   ` Arend van Spriel
2012-07-09  8:53     ` 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=4FFA0A3C.3040204@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=eloy.anguiano@uam.es \
    --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.