New device in MacBook Pro, yet unsupported?

New device in MacBook Pro, yet unsupported?

[Christian Schäfer]

Hi there,

I've got here a recent 13" MacBook Pro (8,1), running Ubuntu on it 
(natty). The wireless device seems to be currently unsupported by the 
b43 driver (as of kernel 2.6.38). It seems to be a bcm4331, lspci -vn 
gives the following:

03:00.0 0280: 14e4:4331 (rev 02)
     Subsystem: 106b:00d6
     Flags: bus master, fast devsel, latency 0, IRQ 11
     Memory at a0600000 (64-bit, non-prefetchable) [size=16K]
     Capabilities: [40] Power Management version 3
     Capabilities: [58] Vendor Specific Information: Len=78 <?>
     Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
     Capabilities: [d0] Express Endpoint, MSI 00
     Capabilities: [100] Advanced Error Reporting
     Capabilities: [13c] Virtual Channel
     Capabilities: [160] Device Serial Number 83-0e-47-ff-ff-36-e0-f8
     Capabilities: [16c] Power Budgeting <?>

To my current knowledge, the only way to get it working is by means of 
ndiswrapper. Are there any plans already to get this device supported 
natively? Please let me know if you need further information regarding 
the device.

Thanks,
Chris

-- 
Dipl.-Bioinf. Christian Schaefer
Technical University Munich
Department for Bioinformatics / Rostlab
http://www.rostlab.org/~schaefer
http://gsish.tum.edu/

New device in MacBook Pro, yet unsupported?

[Rafał Miłecki]

2011/3/27 Christian Sch?fer <schaefer@rostlab.org>:
> Hi there,
>
> I've got here a recent 13" MacBook Pro (8,1), running Ubuntu on it (natty).
> The wireless device seems to be currently unsupported by the b43 driver (as
> of kernel 2.6.38). It seems to be a bcm4331, lspci -vn gives the following:
>
> 03:00.0 0280: 14e4:4331 (rev 02)
> ? ?Subsystem: 106b:00d6
> ? ?Flags: bus master, fast devsel, latency 0, IRQ 11
> ? ?Memory at a0600000 (64-bit, non-prefetchable) [size=16K]
> ? ?Capabilities: [40] Power Management version 3
> ? ?Capabilities: [58] Vendor Specific Information: Len=78 <?>
> ? ?Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
> ? ?Capabilities: [d0] Express Endpoint, MSI 00
> ? ?Capabilities: [100] Advanced Error Reporting
> ? ?Capabilities: [13c] Virtual Channel
> ? ?Capabilities: [160] Device Serial Number 83-0e-47-ff-ff-36-e0-f8
> ? ?Capabilities: [16c] Power Budgeting <?>
>
> To my current knowledge, the only way to get it working is by means of
> ndiswrapper. Are there any plans already to get this device supported
> natively? Please let me know if you need further information regarding the
> device.

What about

modprobe b43
dmesg | grep b43
?

This is new card without real entry in pciid, someone just typed some
dumb BCM4331 in http://pci-ids.ucw.cz/read/PC/14e4/4331

-- 
Rafa?

New device in MacBook Pro, yet unsupported?

[Rafał Miłecki]

W dniu 27 marca 2011 11:42 u?ytkownik Rafa? Mi?ecki <zajec5@gmail.com> napisa?:
> 2011/3/27 Christian Sch?fer <schaefer@rostlab.org>:
>> Hi there,
>>
>> I've got here a recent 13" MacBook Pro (8,1), running Ubuntu on it (natty).
>> The wireless device seems to be currently unsupported by the b43 driver (as
>> of kernel 2.6.38). It seems to be a bcm4331, lspci -vn gives the following:
>>
>> 03:00.0 0280: 14e4:4331 (rev 02)
>> ? ?Subsystem: 106b:00d6
>> ? ?Flags: bus master, fast devsel, latency 0, IRQ 11
>> ? ?Memory at a0600000 (64-bit, non-prefetchable) [size=16K]
>> ? ?Capabilities: [40] Power Management version 3
>> ? ?Capabilities: [58] Vendor Specific Information: Len=78 <?>
>> ? ?Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
>> ? ?Capabilities: [d0] Express Endpoint, MSI 00
>> ? ?Capabilities: [100] Advanced Error Reporting
>> ? ?Capabilities: [13c] Virtual Channel
>> ? ?Capabilities: [160] Device Serial Number 83-0e-47-ff-ff-36-e0-f8
>> ? ?Capabilities: [16c] Power Budgeting <?>
>>
>> To my current knowledge, the only way to get it working is by means of
>> ndiswrapper. Are there any plans already to get this device supported
>> natively? Please let me know if you need further information regarding the
>> device.
>
> What about
>
> modprobe b43
> dmesg | grep b43
> ?

Please, provide also dmesg | grep ssb.

This can be AI card, not ssb.

-- 
Rafa?

New device in MacBook Pro, yet unsupported?

[Jonas Gorski]

2011/3/27 Rafa? Mi?ecki <zajec5@gmail.com>:
> This is new card without real entry in pciid, someone just typed some
> dumb BCM4331 in http://pci-ids.ucw.cz/read/PC/14e4/4331

BCM4331 seems to be correct:

<http://lxr.linux.no/#linux+v2.6.38/drivers/staging/brcm80211/include/bcmdevs.h#L53>:

#define BCM4331_D11N_ID         0x4331  /* 4331 802.11n dualband id */

Since this is a three stream device, this is most likely an AI card.
So if any driver might support it, then it's brcm80211 from staging.

Jonas

New device in MacBook Pro, yet unsupported?

[Christian Schaefer]

>>> I've got here a recent 13" MacBook Pro (8,1), running Ubuntu on it (natty).
>>> The wireless device seems to be currently unsupported by the b43 driver (as
>>> of kernel 2.6.38). It seems to be a bcm4331, lspci -vn gives the following:
[...]
>>> To my current knowledge, the only way to get it working is by means of
>>> ndiswrapper. Are there any plans already to get this device supported
>>> natively? Please let me know if you need further information regarding the
>>> device.
>> What about
>> modprobe b43
>> dmesg | grep b43
> Please, provide also dmesg | grep ssb.
> This can be AI card, not ssb.

modprobe b43
dmesg | grep b43
dmesg | grep ssb

returns nothing. The modprobe however produces the following:

  cfg80211: Calling CRDA to update world regulatory domain
  cfg80211: World regulatory domain updated:
  cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, 
max_eirp)
  cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
  cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
  cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
  cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
  cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
  Broadcom 43xx driver loaded [ Features: PNL, Firmware-ID: FW13 ]

Chris

-- 
Dipl.-Bioinf. Christian Schaefer
Technical University Munich
Department for Bioinformatics / Rostlab
http://www.rostlab.org/~schaefer
http://gsish.tum.edu/

New device in MacBook Pro, yet unsupported?

[Rafał Miłecki]

W dniu 28 marca 2011 11:06 u?ytkownik Christian Schaefer
<schaefer@rostlab.org> napisa?:
> > modprobe b43
> > dmesg | grep b43
> > dmesg | grep ssb
>
> returns nothing. The modprobe however produces the following:

Try brcm80211

-- 
Rafa?

New device in MacBook Pro, yet unsupported?

[Christian Schaefer]

On 03/28/2011 01:42 PM, Rafa? Mi?ecki wrote:
>>> modprobe b43
>>> dmesg | grep b43
>>> dmesg | grep ssb
>> returns nothing. The modprobe however produces the following:
> Try brcm80211

This doesn't seem to be very fruitful either:

brcm80211: module is from the staging directory, the quality is unknown, 
you have been warned.

btw, uname -r gives:
2.6.38-7-generic

Perhaps support for the device is included in recent development kernels?

Thanks,
Chris

-- 
Dipl.-Bioinf. Christian Schaefer
Technical University Munich
Department for Bioinformatics / Rostlab
http://www.rostlab.org/~schaefer
http://gsish.tum.edu/

New device in MacBook Pro, yet unsupported?

[Rafał Miłecki]

2011/3/27 Christian Sch?fer <schaefer@rostlab.org>:
> I've got here a recent 13" MacBook Pro (8,1), running Ubuntu on it (natty).
> The wireless device seems to be currently unsupported by the b43 driver (as
> of kernel 2.6.38). It seems to be a bcm4331, lspci -vn gives the following:
>
> 03:00.0 0280: 14e4:4331 (rev 02)

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.

-- 
Rafa?

New device in MacBook Pro, yet unsupported?

[Rafał Miłecki]

W dniu 30 marca 2011 20:20 u?ytkownik Rafa? Mi?ecki <zajec5@gmail.com> napisa?:
> 2011/3/27 Christian Sch?fer <schaefer@rostlab.org>:
>> I've got here a recent 13" MacBook Pro (8,1), running Ubuntu on it (natty).
>> The wireless device seems to be currently unsupported by the b43 driver (as
>> of kernel 2.6.38). It seems to be a bcm4331, lspci -vn gives the following:
>>
>> 03:00.0 0280: 14e4:4331 (rev 02)
>
> 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.

Ping?

-- 
Rafa?

New device in MacBook Pro, yet unsupported?

[Christian Schaefer]

On 04/06/2011 01:54 AM, Rafa? Mi?ecki wrote:
>>> I've got here a recent 13" MacBook Pro (8,1), running Ubuntu on it (natty).
>>> The wireless device seems to be currently unsupported by the b43 driver (as
>>> of kernel 2.6.38). It seems to be a bcm4331, lspci -vn gives the following:
>>> 03:00.0 0280: 14e4:4331 (rev 02)
>> 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.
> Ping?

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.

Chris

-- 
Dipl.-Bioinf. Christian Schaefer
Technical University Munich
Department for Bioinformatics / Rostlab
http://www.rostlab.org/~schaefer
http://gsish.tum.edu/

New device in MacBook Pro, yet unsupported?

[Rafał Miłecki]

W dniu 7 kwietnia 2011 12:09 u?ytkownik Christian Schaefer
<schaefer@rostlab.org> napisa?:
> On 04/06/2011 01:54 AM, Rafa? Mi?ecki wrote:
>>>>
>>>> I've got here a recent 13" MacBook Pro (8,1), running Ubuntu on it
>>>> (natty).
>>>> The wireless device seems to be currently unsupported by the b43 driver
>>>> (as
>>>> of kernel 2.6.38). It seems to be a bcm4331, lspci -vn gives the
>>>> following:
>>>> 03:00.0 0280: 14e4:4331 (rev 02)
>>>
>>> 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.
>>
>> Ping?
>
> 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.

Not right now, but in future, I think I could support it this way. We
need to introduce support for AI first. Maybe before that 4331 cards
will appear on ebays? I'll ping you when support for AI is done :)

-- 
Rafa?

New device in MacBook Pro, yet unsupported?

[Rafał Miłecki]

Could you apply my axi patch, compile axi module, load it and provide
dmesg | grep axi output?

http://marc.info/?l=linux-wireless&m=130228970402623&w=2

-- 
Rafa?

New device in MacBook Pro, yet unsupported?

[Andy Botting]

Hi Rafa?,

I compiled it into my 2.6.38.2 kernel and booted it. When I modprobe'd
it, I get nothing in dmesg.

Anything else I can try?

cheers,

Andy

2011/4/8 Rafa? Mi?ecki <zajec5@gmail.com>:
> Could you apply my axi patch, compile axi module, load it and provide
> dmesg | grep axi output?
>
> http://marc.info/?l=linux-wireless&m=130228970402623&w=2
>
> --
> Rafa?
>

New device in MacBook Pro, yet unsupported?

[Rafał Miłecki]

W dniu 10 kwietnia 2011 11:16 u?ytkownik Andy Botting
<andy@andybotting.com> napisa?:
> Hi Rafa?,
>
> I compiled it into my 2.6.38.2 kernel and booted it. When I modprobe'd
> it, I get nothing in dmesg.
>
> Anything else I can try?

Ah, sorry.

Can you modify axi_pci_bridge_tbl in host_pci.c on you own, adding
entry for your PCI ID?

If lspci -nn gives you 14e4:4331, try adding:
{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4331) },
(which exuals to:
{ PCI_DEVICE(0x14e4, 0x4331) },
).

-- 
Rafa?

New device in MacBook Pro, yet unsupported?

[David Woodhouse]

On Thu, 2011-04-07 at 12:32 +0200, Rafa? Mi?ecki wrote:
> Not right now, but in future, I think I could support it this way. We
> need to introduce support for AI first. Maybe before that 4331 cards
> will appear on ebays? I'll ping you when support for AI is done :)

The brcm80211 driver seems to have lots of references to 4331, although
it doesn't include 0x4331 in its PCI device table. Might be interesting
just to load it and make it bind to the device.

I just bought a new MBP, and am stuck with one of these. Who wants it,
if it isn't currently working?

And what can I use in its place? I don't recognise the form factor at
http://guide-images.ifixit.net/igi/MIYRQcks54DunO3k.huge

-- 
dwmw2

New device in MacBook Pro, yet unsupported?

[Rafał Miłecki]

W dniu 11 czerwca 2011 00:23 u?ytkownik David Woodhouse
<dwmw2@infradead.org> napisa?:
> On Thu, 2011-04-07 at 12:32 +0200, Rafa? Mi?ecki wrote:
>> Not right now, but in future, I think I could support it this way. We
>> need to introduce support for AI first. Maybe before that 4331 cards
>> will appear on ebays? I'll ping you when support for AI is done :)
>
> The brcm80211 driver seems to have lots of references to 4331, although
> it doesn't include 0x4331 in its PCI device table. Might be interesting
> just to load it and make it bind to the device.

It does not include the most important one: support for the HT PHY.


> I just bought a new MBP, and am stuck with one of these. Who wants it,
> if it isn't currently working?
>
> And what can I use in its place? I don't recognise the form factor at
> http://guide-images.ifixit.net/igi/MIYRQcks54DunO3k.huge

Were you able to find Windows driver for this card? The one you could
use with ndiswrapper?

I'm interested in playing with such a card, if Windows driver exists.

-- 
Rafa?

New device in MacBook Pro, yet unsupported?

[Rafał Miłecki]

W dniu 11 czerwca 2011 00:35 u?ytkownik Rafa? Mi?ecki
<zajec5@gmail.com> napisa?:
> W dniu 11 czerwca 2011 00:23 u?ytkownik David Woodhouse
> <dwmw2@infradead.org> napisa?:
>> On Thu, 2011-04-07 at 12:32 +0200, Rafa? Mi?ecki wrote:
>>> Not right now, but in future, I think I could support it this way. We
>>> need to introduce support for AI first. Maybe before that 4331 cards
>>> will appear on ebays? I'll ping you when support for AI is done :)
>>
>> The brcm80211 driver seems to have lots of references to 4331, although
>> it doesn't include 0x4331 in its PCI device table. Might be interesting
>> just to load it and make it bind to the device.
>
> It does not include the most important one: support for the HT PHY.
>
>
>> I just bought a new MBP, and am stuck with one of these. Who wants it,
>> if it isn't currently working?
>>
>> And what can I use in its place? I don't recognise the form factor at
>> http://guide-images.ifixit.net/igi/MIYRQcks54DunO3k.huge
>
> Were you able to find Windows driver for this card? The one you could
> use with ndiswrapper?
>
> I'm interested in playing with such a card, if Windows driver exists.

I've read a little about this card on Ubuntu forum. It seems to be
problematic to be used with ndiswrapper:
1) Standard Windows driver uses NDIS 6 API, which is not supported by
ndiswrapper
2) 64-bit Windows driver [0] can be used with ndiswrapper but causes
instabilities after some time of using

I've asked for tests of mmiotracer and ndiswrapper on Ubuntu forum [1] [2].

We can at least see what does Windows driver does for this card. How
much does it differ from N-PHY, etc.

[0] http://ubuntuforums.org/showpost.php?p=10504930&postcount=11
[1] http://ubuntuforums.org/showpost.php?p=10927272&postcount=478
[2] http://ubuntuforums.org/showpost.php?p=10927276&postcount=479

-- 
Rafa?

New device in MacBook Pro, yet unsupported?

[David Woodhouse]

On Sat, 2011-06-11 at 11:36 +0200, Rafa? Mi?ecki wrote:
> I've asked for tests of mmiotracer and ndiswrapper on Ubuntu forum [1] [2].

I can do that but it will probably take a while; I may just use the box
with wired and Bluetooth networking for now, or not use it at all until
I'm not quite so snowed under with other things.

If you send me a SSH public key I can give you root access on the box
over the wired connection and you can play with it yourself, which might
be a lot faster all round?

-- 
dwmw2

New device in MacBook Pro, yet unsupported?

[Darren]

On 06/11/2011 06:09 AM, David Woodhouse wrote:
> On Sat, 2011-06-11 at 11:36 +0200, Rafa? Mi?ecki wrote:
>> I've asked for tests of mmiotracer and ndiswrapper on Ubuntu forum [1] [2].
> I can do that but it will probably take a while; I may just use the box
> with wired and Bluetooth networking for now, or not use it at all until
> I'm not quite so snowed under with other things.
>
> If you send me a SSH public key I can give you root access on the box
> over the wired connection and you can play with it yourself, which might
> be a lot faster all round?
>
If you are using Ubuntu David, you can get the mmio trace without
recompiling the kernel.
Just do

echo mmiotrace > /sys/kernel/debug/tracing/current_tracer
cat /sys/kernel/debug/tracing/trace_pipe > /tmp/dump.txt &

echo "Modprobe start" > /sys/kernel/debug/tracing/trace_marker
modprobe ndiswrapper
echo "Modprobe end" > /sys/kernel/debug/tracing/trace_marker

echo "ifconfig wlan1 up start" > /sys/kernel/debug/tracing/trace_marker
ifconfig wlan1 up
echo "ifconfig wlan1 up end" > /sys/kernel/debug/tracing/trace_marker

killall cat

New device in MacBook Pro, yet unsupported?

[Rafał Miłecki]

W dniu 16 kwietnia 2011 06:37 u?ytkownik Darren <dmbtech@gmail.com> napisa?:
> I also just got a macbook pro 2011,
> I ran the patch on 2.6.38.3, had a couple compiler errors related to
> axi_debug (I just commented them out) added the pciid, and got some results:
> Apr 16 00:01:36 dmb-MacBookPro kernel: [? 144.218759] axi-pci-bridge
> 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> Apr 16 00:01:36 dmb-MacBookPro kernel: [? 144.218786] axi-pci-bridge
> 0000:03:00.0: setting latency timer to 64
> Apr 16 00:01:36 dmb-MacBookPro kernel: [? 144.218884] Core 0 found:
> ChipCommon (manuf 0x4BF, id 0x800, rev 0x25, class 0x0)
> Apr 16 00:01:36 dmb-MacBookPro kernel: [? 144.218919] Core 1 found: IEEE
> 802.11 (manuf 0x4BF, id 0x812, rev 0x1D, class 0x0)
> Apr 16 00:01:36 dmb-MacBookPro kernel: [? 144.218988] Core 2 found: PCIe
> (manuf 0x4BF, id 0x820, rev 0x13, class 0x0)
> Apr 16 00:01:36 dmb-MacBookPro kernel: [? 144.219142] PMU resource config
> unknown for device 0x4331
> Apr 16 00:01:36 dmb-MacBookPro kernel: [? 144.219150] Enabling Ext PA lines
> not implemented
> Apr 16 00:04:10 dmb-MacBookPro kernel: [? 144.248126] AXI registered
> Anything else you want me to try? Looks encouraging.

This seems to be the same situation as in case of Andy's machine. We
don't have any reference driver so I'll be hard to implement support
for this card.

Possible solutions I can see:
1) Wait for wl to support BCM4331
2) Try to use ndiswrapper and MMIO trace it's operations. Didn't try
it ever, not sure how much is this possible.

-- 
Rafa?

New device in MacBook Pro, yet unsupported?

[Darren]

I also just got a macbook pro 2011,
I ran the patch on 2.6.38.3, had a couple compiler errors related to
axi_debug (I just commented them out) added the pciid, and got some results:
Apr 16 00:01:36 dmb-MacBookPro kernel: [  144.218759] axi-pci-bridge
0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Apr 16 00:01:36 dmb-MacBookPro kernel: [  144.218786] axi-pci-bridge
0000:03:00.0: setting latency timer to 64
Apr 16 00:01:36 dmb-MacBookPro kernel: [  144.218884] Core 0 found:
ChipCommon (manuf 0x4BF, id 0x800, rev 0x25, class 0x0)
Apr 16 00:01:36 dmb-MacBookPro kernel: [  144.218919] Core 1 found: IEEE
802.11 (manuf 0x4BF, id 0x812, rev 0x1D, class 0x0)
Apr 16 00:01:36 dmb-MacBookPro kernel: [  144.218988] Core 2 found: PCIe
(manuf 0x4BF, id 0x820, rev 0x13, class 0x0)
Apr 16 00:01:36 dmb-MacBookPro kernel: [  144.219142] PMU resource config
unknown for device 0x4331
Apr 16 00:01:36 dmb-MacBookPro kernel: [  144.219150] Enabling Ext PA lines
not implemented
Apr 16 00:04:10 dmb-MacBookPro kernel: [  144.248126] AXI registered
Anything else you want me to try? Looks encouraging.

2011/4/16 *Rafa? Mi?ecki* zajec5 at gmail.com
<b43-dev%40lists.infradead.org?Subject=Re:%20Re%3A%20New%20device%20in%20MacBook%20Pro%2C%20yet%20unsupported%3F&In-Reply-To=%3CBANLkTi%3DNj67rVqwdH06A9tKq8%3DZUn2xx5Q%40mail.gmail.com%3E>
>
> W dniu 10 kwietnia 2011 11:16 u?ytkownik Andy Botting
> <andy@andybotting.com <http://lists.infradead.org/mailman/listinfo/b43-dev>> napisa?:
> >* Hi Rafa?,*>**>* I compiled it into my 2.6.38.2 kernel and booted it. When I modprobe'd*>* it, I get nothing in dmesg.*>**>* Anything else I can try?*
> Ah, sorry.
>
> Can you modify axi_pci_bridge_tbl in host_pci.c on you own, adding
> entry for your PCI ID?
>
> If lspci -nn gives you 14e4:4331, try adding:
> { PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4331) },
> (which exuals to:
> { PCI_DEVICE(0x14e4, 0x4331) },
> ).
>
> --
> Rafa?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20110416/da368c67/attachment.html>

New device in MacBook Pro, yet unsupported?

[Rafał Miłecki]

2011/4/7 Andy Botting <andy@andybotting.com>:
>>> 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?
>
> From the photo, this particular device it looks like is has a
> non-standard connector, as opposed to the usual mini-pcie type card,
> which would obviously make it harder for you guys to get your hands on
> it.
>
> Is there anything we can do to help with this, like supply you with
> some sort of debugging on the card?

Interesting, this is card like noone other seen earlier. If there
won't be any other BCM4331 cards available for mini PCIe, it may be
harder to support them. The only solution (except buying MacBook)
seems to be SSH-ing to someone's machine. Or finding a proper adapter
for this kind of slot.

The amount of work mostly depends on used PHY and radio on this card.
This should be possible soon, when bcmai/whatever-name will be ready.

-- 
Rafa?

New device in MacBook Pro, yet unsupported?

[Andy Botting]

>> 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?