BMC4310 support (03f0:171d)

BMC4310 support (03f0:171d)

[Nadav Kavalerchik]

i just got a new HP tx2520ej tablet laptop with a BCM4310 wlan
it is identified as Vendor : 03f0  , Product : 171d

any chance i can try a development version that might work ?

:-)

Re: BMC4310 support (03f0:171d)

[Michael Buesch]

On Monday 01 September 2008 22:49:20 Nadav Kavalerchik wrote:
> i just got a new HP tx2520ej tablet laptop with a BCM4310 wlan
> it is identified as Vendor : 03f0  , Product : 171d
> 
> any chance i can try a development version that might work ?

no


-- 
Greetings Michael.

Re: BMC4310 support (03f0:171d)

[Nadav Kavalerchik]

 anything i can do to help ?

 ndiswrapper can handle the vista drivers ver 6.1 so i am stuck :-(

 throw me a bone :-)


> On Tue, Sep 2, 2008 at 12:33 AM, Michael Buesch <mb@bu3sch.de> wrote:
>>
>> On Monday 01 September 2008 22:49:20 Nadav Kavalerchik wrote:
>> > i just got a new HP tx2520ej tablet laptop with a BCM4310 wlan
>> > it is identified as Vendor : 03f0  , Product : 171d
>> >
>> > any chance i can try a development version that might work ?
>>
>> no
>>
>>
>> --
>> Greetings Michael.
>

Re: BMC4310 support (03f0:171d)

[Larry Finger]

Nadav Kavalerchik wrote:
>  anything i can do to help ?
> 
>  ndiswrapper can handle the vista drivers ver 6.1 so i am stuck :-(
> 
>  throw me a bone :-)

We are almost done with the reverse engineering. AFAIK, code writing 
has not started yet.

Larry

Re: BMC4310 support (03f0:171d)

[Pavel Roskin]

On Tue, 2008-09-09 at 22:41 +0300, Nadav Kavalerchik wrote:
> anything i can do to help ?
> 
>  ndiswrapper can handle the vista drivers ver 6.1 so i am stuck :-(

I guess that you mean that it cannot.

>  throw me a bone :-)

svn co https://ndiswrapper.svn.sourceforge.net/svnroot/ndiswrapper/branches/ndisv6/ndiswrapper

That's an experimental version of ndiswrapper that supports NDIS v6
only.  As far as I know, it's not fully functional, but at least you
don't have to wait for reverse engineering.  NDIS is documented.  I
believe x86_64 has better chances to work than i386.

Just a reminder - please don't discuss issues with ndiswrapper in this
list.  It has a list of its own.

-- 
Regards,
Pavel Roskin

Re: BMC4310 support (03f0:171d)

[Mike Cui]

What's the PCI ID? I have a BCM 4315 which is misidentified as BCM4310
by lspci. In any case,  Dell releases NDIS 5.1 drivers for broadcom,
while HP doesn't. Try googling for Dell wireless 1395. It works for
me.


On Tue, Sep 9, 2008 at 12:41 PM, Nadav Kavalerchik <nadavkav@gmail.com> wrote:
>  anything i can do to help ?
>
>  ndiswrapper can handle the vista drivers ver 6.1 so i am stuck :-(
>
>  throw me a bone :-)
>
>
>> On Tue, Sep 2, 2008 at 12:33 AM, Michael Buesch <mb@bu3sch.de> wrote:
>>>
>>> On Monday 01 September 2008 22:49:20 Nadav Kavalerchik wrote:
>>> > i just got a new HP tx2520ej tablet laptop with a BCM4310 wlan
>>> > it is identified as Vendor : 03f0  , Product : 171d
>>> >
>>> > any chance i can try a development version that might work ?
>>>
>>> no
>>>
>>>
>>> --
>>> Greetings Michael.
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: BMC4310 support (03f0:171d)

[Stefanik Gábor]

On Fri, Sep 12, 2008 at 10:33 AM, Mike Cui <cuicui@gmail.com> wrote:
> What's the PCI ID? I have a BCM 4315 which is misidentified as BCM4310
> by lspci. In any case,  Dell releases NDIS 5.1 drivers for broadcom,
> while HP doesn't. Try googling for Dell wireless 1395. It works for
> me.

It is not a "BCM4315", it is a BCM4310. There is no such thing as a
BCM4315. Chip ID != PCI ID!
Most chip IDs match with their respective PCI IDs, but here are some exceptions:
0x4320 is BCM4306.
0x4315 is BCM4310.
0x4328 is BCM4321.
0x432b is BCM4322.

-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)

Re: BMC4310 support (03f0:171d)

[Mike Cui]

> It is not a "BCM4315", it is a BCM4310. There is no such thing as a
> BCM4315. Chip ID != PCI ID!
> Most chip IDs match with their respective PCI IDs, but here are some exceptions:
> 0x4320 is BCM4306.
> 0x4315 is BCM4310.
> 0x4328 is BCM4321.
> 0x432b is BCM4322.

Maybe...

But on the miniPCIe chip itself, there is a sticker that says Broadcom
4312. But it's not a BCM4312 either, because BCM4312 actually works...

Re: BMC4310 support (03f0:171d)

[Stefanik Gábor]

On Sat, Sep 13, 2008 at 5:11 AM, Mike Cui <cuicui@gmail.com> wrote:
>> It is not a "BCM4315", it is a BCM4310. There is no such thing as a
>> BCM4315. Chip ID != PCI ID!
>> Most chip IDs match with their respective PCI IDs, but here are some exceptions:
>> 0x4320 is BCM4306.
>> 0x4315 is BCM4310.
>> 0x4328 is BCM4321.
>> 0x432b is BCM4322.
>
> Maybe...
>
> But on the miniPCIe chip itself, there is a sticker that says Broadcom
> 4312. But it's not a BCM4312 either, because BCM4312 actually works...
>

Maybe we should refine the list a bit then, as follows:
0x4320 is BCM4306
0x4311 is BCM4311BG (colloquially "BCM4311")
0x4312 is BCM4311ABG (colloquially "BCM4312")
0x4315 is BCM4312 (colloquially "BCM4310")
0x4318 can be both BCM4318 and BCM4318E
0x4328 is BCM4321 (colloquially "BCM4328")
0x432b is BCM4322

In that case, is "BCM4309" actually BCM4306ABG?
-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)

Re: BMC4310 support (03f0:171d)

[Michael Buesch]

On Saturday 13 September 2008 05:11:50 Mike Cui wrote:
> > It is not a "BCM4315", it is a BCM4310. There is no such thing as a
> > BCM4315. Chip ID != PCI ID!
> > Most chip IDs match with their respective PCI IDs, but here are some exceptions:
> > 0x4320 is BCM4306.
> > 0x4315 is BCM4310.
> > 0x4328 is BCM4321.
> > 0x432b is BCM4322.
> 
> Maybe...
> 
> But on the miniPCIe chip itself, there is a sticker that says Broadcom
> 4312. But it's not a BCM4312 either, because BCM4312 actually works...

the numbers printed on the chip package are package IDs. These are
different from chip-ids sometimes. ;)

The only way to find out the chipid really is to load b43 and look
for the message saying "found Broadcom XXXX WLAN".

But still, having a chip with the same chipid and/or package ids doesn't
mean it's the same chip. :)

-- 
Greetings Michael.