From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ssb/b43: add new N PHY device
Date: Wed, 24 Dec 2008 13:09:26 +0100 [thread overview]
Message-ID: <200812241309.27072.mb@bu3sch.de> (raw)
In-Reply-To: <1230119049.4566.1.camel@johannes>
On Wednesday 24 December 2008 12:44:09 Johannes Berg wrote:
> This is used on my macbook. N PHY, obviously nothing works
> yet, but we can detect the chip with this patch.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
ACK. Please queue for 2.6.29
> ---
> drivers/net/wireless/b43/main.c | 1 +
> drivers/ssb/b43_pci_bridge.c | 1 +
> 2 files changed, 2 insertions(+)
>
> --- wireless-testing.orig/drivers/ssb/b43_pci_bridge.c 2008-12-24 12:33:23.000000000 +0100
> +++ wireless-testing/drivers/ssb/b43_pci_bridge.c 2008-12-24 12:34:41.000000000 +0100
> @@ -29,6 +29,7 @@ static const struct pci_device_id b43_pc
> { PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4325) },
> { PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4328) },
> { PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4329) },
> + { PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x432b) },
> { 0, },
> };
> MODULE_DEVICE_TABLE(pci, b43_pci_bridge_tbl);
> --- wireless-testing.orig/drivers/net/wireless/b43/main.c 2008-12-24 12:43:09.000000000 +0100
> +++ wireless-testing/drivers/net/wireless/b43/main.c 2008-12-24 12:43:18.000000000 +0100
> @@ -97,6 +97,7 @@ static const struct ssb_device_id b43_ss
> SSB_DEVICE(SSB_VENDOR_BROADCOM, SSB_DEV_80211, 10),
> SSB_DEVICE(SSB_VENDOR_BROADCOM, SSB_DEV_80211, 11),
> SSB_DEVICE(SSB_VENDOR_BROADCOM, SSB_DEV_80211, 13),
> + SSB_DEVICE(SSB_VENDOR_BROADCOM, SSB_DEV_80211, 16),
> SSB_DEVTABLE_END
> };
>
>
>
>
>
--
Greetings, Michael.
prev parent reply other threads:[~2008-12-24 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 11:44 [PATCH] ssb/b43: add new N PHY device Johannes Berg
2008-12-24 12:09 ` Michael Buesch [this message]
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=200812241309.27072.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).