From: Andy Botting <andy@andybotting.com>
To: b43-dev@lists.infradead.org
Subject: New device in MacBook Pro, yet unsupported?
Date: Thu, 7 Apr 2011 19:45:41 +0100 [thread overview]
Message-ID: <BANLkTikEgRC4bt06Nzcdk95h8TdicSZFoQ@mail.gmail.com> (raw)
>> Any chance you can see how it's labeled? Is that possible to open
>> MacBook's slot to see this wifi card?
>> I mean something like BCM943....
>> I could not find you card on ebay.
> I fear I cannot be of any help with this. The MacBook is from my employer
> and has a warranty seal on its back, which I'm not willing to break.
> Perhaps remote access to my machine could help you? Let me know.
Hi - I just stumbled upon this thread while looking around for support
for the new bcm4331.
Maybe this is some help - it's a photo of the wireless chip from the
iFixIt teardown of the new Macbook Pro
http://guide-images.ifixit.net/igi/MIYRQcks54DunO3k.huge
I'm curious about how much work is involved with supporting a new chip
like this?
next reply other threads:[~2011-04-07 18:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 18:45 Andy Botting [this message]
2011-04-07 18:51 ` New device in MacBook Pro, yet unsupported? Rafał Miłecki
[not found] <BANLkTinooer0aFqJfn0ui+QXpLO6YkPhEg@mail.gmail.com>
2011-04-16 4:37 ` Darren
2011-04-16 13:41 ` Rafał Miłecki
-- strict thread matches above, loose matches on Subject: below --
2011-03-27 9:23 Christian Schäfer
2011-03-27 9:42 ` Rafał Miłecki
2011-03-27 9:43 ` Rafał Miłecki
2011-03-28 9:06 ` Christian Schaefer
2011-03-28 11:42 ` Rafał Miłecki
2011-03-28 12:29 ` Christian Schaefer
2011-03-27 10:12 ` Jonas Gorski
2011-03-30 18:20 ` Rafał Miłecki
2011-04-05 23:54 ` Rafał Miłecki
2011-04-07 10:09 ` Christian Schaefer
2011-04-07 10:32 ` Rafał Miłecki
2011-04-08 19:17 ` Rafał Miłecki
2011-04-10 9:16 ` Andy Botting
2011-04-10 9:20 ` Rafał Miłecki
2011-06-10 22:23 ` David Woodhouse
2011-06-10 22:35 ` Rafał Miłecki
2011-06-11 9:36 ` Rafał Miłecki
2011-06-11 10:09 ` David Woodhouse
2011-06-12 15:40 ` Darren
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=BANLkTikEgRC4bt06Nzcdk95h8TdicSZFoQ@mail.gmail.com \
--to=andy@andybotting.com \
--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 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).