b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Michael Büsch" <m@bues.ch>,
	linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	b43-dev@lists.infradead.org
Subject: [PATCH 0/3] ssb/b43(legacy): clean dangling cores workarounds
Date: Sun, 8 May 2011 20:36:27 +0200	[thread overview]
Message-ID: <BANLkTinwsb7zbjNBa1PTjojTR_XWaaD03Q@mail.gmail.com> (raw)
In-Reply-To: <4DC6E229.7060501@lwfinger.net>

W dniu 8 maja 2011 20:34 u?ytkownik Larry Finger
<Larry.Finger@lwfinger.net> napisa?:
> On 05/08/2011 12:16 PM, Michael B?sch wrote:
>>
>> On Sun, 2011-05-08 at 19:11 +0200, Rafa? Mi?ecki wrote:
>>>
>>> Oh, do you have some device with 2 active cores? Nice :)
>>
>> I don't think there are any supported multicore devices anyway. Those
>> are the very early A-PHY, only. AFAIK.
>
> Yes, I have a Linksys WPC54G Cardbus device that uses b43legacy.
>
> The 'dmesg | egrep "ssb|b43"' output for it is
>
> b43-pci-bridge 0000:06:00.0: PCI INT A -> Link[LNK1] -> GSI 11 (level, low)
> -> IRQ 11
> ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x02, vendor 0x4243)
> ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x04, vendor 0x4243)
> ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x01, vendor 0x4243)
> ssb: Core 3 found: V90 (cc 0x807, rev 0x01, vendor 0x4243)
> ssb: Core 4 found: PCI (cc 0x804, rev 0x07, vendor 0x4243)
> ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x04, vendor 0x4243)
> ssb: Ignoring additional 802.11 core
> ssb: chipcommon status is 0x0
> ssb: SPROM offset is 0x1000
> ssb: SPROM revision 1 detected.
> ssb: Sonics Silicon Backplane found on PCI device 0000:06:00.0
> b43legacy-phy0: Broadcom 4306 WLAN found
> b43legacy-phy0 debug: Found PHY: Analog 1, Type 2, Revision 1
> b43legacy-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
> b43legacy-phy0 debug: Radio initialized
> b43legacy-phy0: Loading firmware version 0x127, patch level 14 (2005-04-18
> 02:36:27)
> b43legacy-phy0 debug: Chip initialized
> b43legacy-phy0 debug: 30-bit DMA initialized
> b43legacy-phy0 debug: Wireless interface started
> b43legacy-phy0 debug: Adding Interface type 2
>
> You can add a Tested-by: and an ACK to the patches.

John, is this something you can do easily? Or do you want me to
resubmit patches with Larry's Tested?

-- 
Rafa?

  reply	other threads:[~2011-05-08 18:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-08 17:09 [PATCH 0/3] ssb/b43(legacy): clean dangling cores workarounds Rafał Miłecki
2011-05-08 17:06 ` Larry Finger
2011-05-08 17:11   ` Rafał Miłecki
2011-05-08 17:16     ` Michael Büsch
2011-05-08 18:34       ` Larry Finger
2011-05-08 18:36         ` Rafał Miłecki [this message]
2011-05-08 17:09 ` [PATCH 1/3] ssb: update list of devices supporting multiple 80211 cores Rafał Miłecki
2011-05-08 17:09 ` [PATCH 2/3] b43: drop ssb-duplicated workaround for dangling cores Rafał Miłecki
2011-05-08 17:09 ` [PATCH 3/3] b43legacy: " 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=BANLkTinwsb7zbjNBa1PTjojTR_XWaaD03Q@mail.gmail.com \
    --to=zajec5@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=m@bues.ch \
    /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).