Abour linux driver supports BCM4325

Abour linux driver supports BCM4325

[feng tian]

Dear All,

We are working on a project which supports the BCM4325 linux wireless
driver. The interface between the BCM chip and SOC(pxa310) is SDIO.
I did some searches online and found that there is no available driver
for this chip. Do I have to implement this myself? Is there anyone can
provide us some related materials?  Thanks very much.

BR
Feng

Abour linux driver supports BCM4325

[feng tian]

Dear All,

We are working on a project which supports the BCM4325 linux wireless
driver. The interface between the BCM chip and SOC(pxa310) is SDIO.
I did some searches online and found that there is no available driver
for this chip. Do I have to implement this myself? Is there anyone can
provide us some related materials?  Thanks very much.

BR
Feng

Re: Abour linux driver supports BCM4325

[Dan Williams]

On Fri, 2009-08-21 at 14:22 +0800, feng tian wrote:
> Dear All,
> 
> We are working on a project which supports the BCM4325 linux wireless
> driver. The interface between the BCM chip and SOC(pxa310) is SDIO.
> I did some searches online and found that there is no available driver
> for this chip. Do I have to implement this myself? Is there anyone can
> provide us some related materials?  Thanks very much.

You'll probably want to ask on the linux-wireless list where the
wireless people hang out.  Partial answer: there is already a driver
(b43) for many of broadcom 802.11 devices, including some of the
"LP-PHY" devices.  This driver may or may not be suitable for the 4325
depending on the 4325's firmware interface.  The b43 driver is not yet
capable of using SDIO to communicate with the wifi chip, but that
appears to be what you are working on.  So I'd suggest posting to the
linux-wireless mailing list and seeing what the b43 driver people say.

http://linuxwireless.org/en/developers/MailingLists

Dan

Re: Abour linux driver supports BCM4325

[feng tian]

Thanks very much, I'll post this to linux-wireless mailing list.

2009/8/21 Dan Williams <dcbw@redhat.com>:
> On Fri, 2009-08-21 at 14:22 +0800, feng tian wrote:
>> Dear All,
>>
>> We are working on a project which supports the BCM4325 linux wireless
>> driver. The interface between the BCM chip and SOC(pxa310) is SDIO.
>> I did some searches online and found that there is no available driver
>> for this chip. Do I have to implement this myself? Is there anyone can
>> provide us some related materials?  Thanks very much.
>
> You'll probably want to ask on the linux-wireless list where the
> wireless people hang out.  Partial answer: there is already a driver
> (b43) for many of broadcom 802.11 devices, including some of the
> "LP-PHY" devices.  This driver may or may not be suitable for the 4325
> depending on the 4325's firmware interface.  The b43 driver is not yet
> capable of using SDIO to communicate with the wifi chip, but that
> appears to be what you are working on.  So I'd suggest posting to the
> linux-wireless mailing list and seeing what the b43 driver people say.
>
> http://linuxwireless.org/en/developers/MailingLists
>
> Dan
>
>
>

Re: Abour linux driver supports BCM4325

[Larry Finger]

feng tian wrote:
> Dear All,
> 
> We are working on a project which supports the BCM4325 linux wireless
> driver. The interface between the BCM chip and SOC(pxa310) is SDIO.
> I did some searches online and found that there is no available driver
> for this chip. Do I have to implement this myself? Is there anyone can
> provide us some related materials?  Thanks very much.

The code for the LP PHY, which I believe is present in the 4325, is
just being written. At the moment, the chip is able to receive on some
channels, and may be able to transmit. These results are reported on
this mailing list, and the code is being applied to the wireless
testing git tree.

Larry

Re: Abour linux driver supports BCM4325

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 798 bytes --]

On Fri, 2009-08-21 at 07:13 -0500, Larry Finger wrote:

> > We are working on a project which supports the BCM4325 linux wireless
> > driver. The interface between the BCM chip and SOC(pxa310) is SDIO.
> > I did some searches online and found that there is no available driver
> > for this chip. Do I have to implement this myself? Is there anyone can
> > provide us some related materials?  Thanks very much.
> 
> The code for the LP PHY, which I believe is present in the 4325, is
> just being written. At the moment, the chip is able to receive on some
> channels, and may be able to transmit. These results are reported on
> this mailing list, and the code is being applied to the wireless
> testing git tree.

Also, somebody is working on SDIO support with Michael.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

Re: Abour linux driver supports BCM4325

[feng tian]

Instead of waiting for the codes, we decide to do someting on
supporting the BCM 4325 running in linux via SDIO.
The linux wireless dirver supports another chip (marvel 8686) with
SDIO interface, the sources codes locate in
drivers/net/wireless/libertas.
We are wondering to develop the BCM4325 driver in the reference to the
marvel 8686 SDIO driver.
Please give comments on this, thanks.

BR
Feng

2009/8/21 Johannes Berg <johannes@sipsolutions.net>:
> On Fri, 2009-08-21 at 07:13 -0500, Larry Finger wrote:
>
>> > We are working on a project which supports the BCM4325 linux wireless
>> > driver. The interface between the BCM chip and SOC(pxa310) is SDIO.
>> > I did some searches online and found that there is no available driver
>> > for this chip. Do I have to implement this myself? Is there anyone can
>> > provide us some related materials?  Thanks very much.
>>
>> The code for the LP PHY, which I believe is present in the 4325, is
>> just being written. At the moment, the chip is able to receive on some
>> channels, and may be able to transmit. These results are reported on
>> this mailing list, and the code is being applied to the wireless
>> testing git tree.
>
> Also, somebody is working on SDIO support with Michael.
>
> johannes
>

Re: Abour linux driver supports BCM4325

[Larry Finger]

feng tian wrote:
> Instead of waiting for the codes, we decide to do someting on
> supporting the BCM 4325 running in linux via SDIO.
> The linux wireless dirver supports another chip (marvel 8686) with
> SDIO interface, the sources codes locate in
> drivers/net/wireless/libertas.
> We are wondering to develop the BCM4325 driver in the reference to the
> marvel 8686 SDIO driver.
> Please give comments on this, thanks.

The SDIO routines might be transferable; however, the radio and PHY
code will be completely different.

Re: Abour linux driver supports BCM4325

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 874 bytes --]

On Sat, 2009-08-22 at 09:27 -0500, Larry Finger wrote:
> feng tian wrote:
> > Instead of waiting for the codes, we decide to do someting on
> > supporting the BCM 4325 running in linux via SDIO.
> > The linux wireless dirver supports another chip (marvel 8686) with
> > SDIO interface, the sources codes locate in
> > drivers/net/wireless/libertas.
> > We are wondering to develop the BCM4325 driver in the reference to the
> > marvel 8686 SDIO driver.
> > Please give comments on this, thanks.
> 
> The SDIO routines might be transferable; however, the radio and PHY
> code will be completely different.

Very few of them will be, afaict the SDIO bus access is vastly
different. Learning how to write an SDIO driver might be possible, but I
suspect transferring code won't make much sense.

Either way, isobel has some b43 sdio code already.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

Re: Abour linux driver supports BCM4325

[feng tian]

Thank you for the information.
I get your point. As for the radio and phy driver, I think it's  some
command based configurations for the chip via SDIO. And that I can
refer to the BCM 43xx PCI driver codes.
Wonder if it's feasible. Needs your comments.
Thanks

BR
Feng

2009/8/23 Johannes Berg <johannes@sipsolutions.net>:
> On Sat, 2009-08-22 at 09:27 -0500, Larry Finger wrote:
>> feng tian wrote:
>> > Instead of waiting for the codes, we decide to do someting on
>> > supporting the BCM 4325 running in linux via SDIO.
>> > The linux wireless dirver supports another chip (marvel 8686) with
>> > SDIO interface, the sources codes locate in
>> > drivers/net/wireless/libertas.
>> > We are wondering to develop the BCM4325 driver in the reference to the
>> > marvel 8686 SDIO driver.
>> > Please give comments on this, thanks.
>>
>> The SDIO routines might be transferable; however, the radio and PHY
>> code will be completely different.
>
> Very few of them will be, afaict the SDIO bus access is vastly
> different. Learning how to write an SDIO driver might be possible, but I
> suspect transferring code won't make much sense.
>
> Either way, isobel has some b43 sdio code already.
>
> johannes
>

Re: Abour linux driver supports BCM4325

[Larry Finger]

feng tian wrote:
> Thank you for the information.
> I get your point. As for the radio and phy driver, I think it's  some
> command based configurations for the chip via SDIO. And that I can
> refer to the BCM 43xx PCI driver codes.
> Wonder if it's feasible. Needs your comments.
> Thanks

The first step is to be able to read/write the various registers via
SDIO. That will be similar to the PCI operations. The next step is
knowing what to read/write and when. We are still working that out for
PCI. It is not trivial. See the recent postings of patches for the LP
pHY in the linux-wireless mailing list. These are _NOT_ complete.

Re: Abour linux driver supports BCM4325

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]

On Sat, 2009-08-22 at 21:59 -0500, Larry Finger wrote:
> feng tian wrote:
> > Thank you for the information.
> > I get your point. As for the radio and phy driver, I think it's  some
> > command based configurations for the chip via SDIO. And that I can
> > refer to the BCM 43xx PCI driver codes.
> > Wonder if it's feasible. Needs your comments.
> > Thanks
> 
> The first step is to be able to read/write the various registers via
> SDIO. That will be similar to the PCI operations. The next step is
> knowing what to read/write and when. We are still working that out for
> PCI. It is not trivial. See the recent postings of patches for the LP
> pHY in the linux-wireless mailing list. These are _NOT_ complete.

Right.

You have two completely orthogonal problems:

 1) changing b43 so it knows how to talk not just to SSB/PCI/PCMCIA
    chips but also SDIO chips
 2) changing b43 so it knows how to talk to your specific radio/PHY
    chip, and LP PHY

However, 1) is being solved for you by somebody on the IRC channel with
whom Michael is in contact, and 2) is (hopefully) being solved for you
by Larry and Gabor.

Thus, the best thing you can do is familiarise yourself with the
existing efforts and eventually try to put them together and test with
your chip.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

Re: Abour linux driver supports BCM4325

[Michael Buesch]

On Sunday 23 August 2009 11:13:50 Johannes Berg wrote:
> On Sat, 2009-08-22 at 21:59 -0500, Larry Finger wrote:
> > feng tian wrote:
> > > Thank you for the information.
> > > I get your point. As for the radio and phy driver, I think it's  some
> > > command based configurations for the chip via SDIO. And that I can
> > > refer to the BCM 43xx PCI driver codes.
> > > Wonder if it's feasible. Needs your comments.
> > > Thanks
> > 
> > The first step is to be able to read/write the various registers via
> > SDIO. That will be similar to the PCI operations. The next step is
> > knowing what to read/write and when. We are still working that out for
> > PCI. It is not trivial. See the recent postings of patches for the LP
> > pHY in the linux-wireless mailing list. These are _NOT_ complete.
> 
> Right.
> 
> You have two completely orthogonal problems:
> 
>  1) changing b43 so it knows how to talk not just to SSB/PCI/PCMCIA
>     chips but also SDIO chips

We already have working support for that and we're currently merging it mainline.
If you want to help, please test the spinlock removal patchset I just posted.

>  2) changing b43 so it knows how to talk to your specific radio/PHY
>     chip, and LP PHY

Also almost working and in the progress of merging mainline.

-- 
Greetings, Michael.

Re: Abour linux driver supports BCM4325

[Gábor Stefanik]

On Sun, Aug 23, 2009 at 2:55 PM, Michael Buesch<mb@bu3sch.de> wrote:
> On Sunday 23 August 2009 11:13:50 Johannes Berg wrote:
>> On Sat, 2009-08-22 at 21:59 -0500, Larry Finger wrote:
>> > feng tian wrote:
>> > > Thank you for the information.
>> > > I get your point. As for the radio and phy driver, I think it's  some
>> > > command based configurations for the chip via SDIO. And that I can
>> > > refer to the BCM 43xx PCI driver codes.
>> > > Wonder if it's feasible. Needs your comments.
>> > > Thanks
>> >
>> > The first step is to be able to read/write the various registers via
>> > SDIO. That will be similar to the PCI operations. The next step is
>> > knowing what to read/write and when. We are still working that out for
>> > PCI. It is not trivial. See the recent postings of patches for the LP
>> > pHY in the linux-wireless mailing list. These are _NOT_ complete.
>>
>> Right.
>>
>> You have two completely orthogonal problems:
>>
>>  1) changing b43 so it knows how to talk not just to SSB/PCI/PCMCIA
>>     chips but also SDIO chips
>
> We already have working support for that and we're currently merging it mainline.
> If you want to help, please test the spinlock removal patchset I just posted.
>
>>  2) changing b43 so it knows how to talk to your specific radio/PHY
>>     chip, and LP PHY
>
> Also almost working and in the progress of merging mainline.

Not necessarily true in this case - an important 4325-specific routine
(SSB PMU recalibration) is still missing. (And I don't tink I'm
familiar enough with ssb to do that, unfortunately.)

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



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

Re: Abour linux driver supports BCM4325

[Michael Buesch]

On Sunday 23 August 2009 15:24:29 Gábor Stefanik wrote:
> On Sun, Aug 23, 2009 at 2:55 PM, Michael Buesch<mb@bu3sch.de> wrote:
> > On Sunday 23 August 2009 11:13:50 Johannes Berg wrote:
> >> On Sat, 2009-08-22 at 21:59 -0500, Larry Finger wrote:
> >> > feng tian wrote:
> >> > > Thank you for the information.
> >> > > I get your point. As for the radio and phy driver, I think it's  some
> >> > > command based configurations for the chip via SDIO. And that I can
> >> > > refer to the BCM 43xx PCI driver codes.
> >> > > Wonder if it's feasible. Needs your comments.
> >> > > Thanks
> >> >
> >> > The first step is to be able to read/write the various registers via
> >> > SDIO. That will be similar to the PCI operations. The next step is
> >> > knowing what to read/write and when. We are still working that out for
> >> > PCI. It is not trivial. See the recent postings of patches for the LP
> >> > pHY in the linux-wireless mailing list. These are _NOT_ complete.
> >>
> >> Right.
> >>
> >> You have two completely orthogonal problems:
> >>
> >>  1) changing b43 so it knows how to talk not just to SSB/PCI/PCMCIA
> >>     chips but also SDIO chips
> >
> > We already have working support for that and we're currently merging it mainline.
> > If you want to help, please test the spinlock removal patchset I just posted.
> >
> >>  2) changing b43 so it knows how to talk to your specific radio/PHY
> >>     chip, and LP PHY
> >
> > Also almost working and in the progress of merging mainline.
> 
> Not necessarily true in this case - an important 4325-specific routine
> (SSB PMU recalibration) is still missing. (And I don't tink I'm
> familiar enough with ssb to do that, unfortunately.)

I can do that later. It's a fairly simple routine (to me knowing the code :).

-- 
Greetings, Michael.

Re: Abour linux driver supports BCM4325

[Gábor Stefanik]

2009/8/23 Michael Buesch <mb@bu3sch.de>:
> On Sunday 23 August 2009 15:24:29 Gábor Stefanik wrote:
>> Not necessarily true in this case - an important 4325-specific routine
>> (SSB PMU recalibration) is still missing. (And I don't tink I'm
>> familiar enough with ssb to do that, unfortunately.)
>
> I can do that later. It's a fairly simple routine (to me knowing the code :).
>
> --
> Greetings, Michael.
>

Thanks!

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

Re: Abour linux driver supports BCM4325

[feng tian]

>> You have two completely orthogonal problems:
>>
>>  1) changing b43 so it knows how to talk not just to SSB/PCI/PCMCIA
>>     chips but also SDIO chips
>
> We already have working support for that and we're currently merging it mainline.
> If you want to help, please test the spinlock removal patchset I just posted.
>>  2) changing b43 so it knows how to talk to your specific radio/PHY
>>     chip, and LP PHY
>
> Also almost working and in the progress of merging mainline.
>
> --
> Greetings, Michael.
>

Okay, I'll first look into it, and then do some tests.
Thanks.

BR, Feng

Re: Abour linux driver supports BCM4325

[feng tian]

>>>  1) changing b43 so it knows how to talk not just to SSB/PCI/PCMCIA
>>>     chips but also SDIO chips
>>
>> We already have working support for that and we're currently merging it mainline.
>> If you want to help, please test the spinlock removal patchset I just posted.

>>>  2) changing b43 so it knows how to talk to your specific radio/PHY
>>>     chip, and LP PHY

Where can I get theses codes which supports b43 talking to SDIO chips?
Thanks very much.

BR, Feng

Re: Abour linux driver supports BCM4325

[Michael Buesch]

On Monday 24 August 2009 08:03:12 feng tian wrote:
> >>>  1) changing b43 so it knows how to talk not just to SSB/PCI/PCMCIA
> >>>     chips but also SDIO chips
> >>
> >> We already have working support for that and we're currently merging it mainline.
> >> If you want to help, please test the spinlock removal patchset I just posted.
> 
> >>>  2) changing b43 so it knows how to talk to your specific radio/PHY
> >>>     chip, and LP PHY
> 
> Where can I get theses codes which supports b43 talking to SDIO chips?
> Thanks very much.

They are not ready for public review, yet. We're working on merging them mainline.
But it does basically work and we (Albert Herranz) got the SDIO chip on the Nintendo Wii running.


-- 
Greetings, Michael.

Re: Abour linux driver supports BCM4325

[feng tian]

Wow, that's really cool.
We wonder if you can send these codes to us a little earlier, then we
can start to integrate and test them on our platform.
That'll save us some time.

Thanks very much.
BR, Feng.

>> Where can I get theses codes which supports b43 talking to SDIO chips?
>> Thanks very much.
>
> They are not ready for public review, yet. We're working on merging them mainline.
> But it does basically work and we (Albert Herranz) got the SDIO chip on the Nintendo Wii running.
>
>
> --
> Greetings, Michael.
>

Re: Abour linux driver supports BCM4325

[feng tian]

Dear Michael,

Another question:
We can't get the actual "datasheet" of BCM 4325. The pdf from broadcom
is so rough, and we also sent email to ask more detailed spec, but no
feedback.
What kind of datasheet of BCM4325 are you using now?
Could you please share this with us?

Thank you very much.

BR, Feng

Re: Abour linux driver supports BCM4325

[Michael Buesch]

On Tuesday 25 August 2009 09:16:36 feng tian wrote:
> Dear Michael,
> 
> Another question:
> We can't get the actual "datasheet" of BCM 4325. The pdf from broadcom
> is so rough, and we also sent email to ask more detailed spec, but no
> feedback.
> What kind of datasheet of BCM4325 are you using now?
> Could you please share this with us?
> 
> Thank you very much.
> 
> BR, Feng
> 
> 

http://bcm-v4.sipsolutions.net/

-- 
Greetings, Michael.

Re: Abour linux driver supports BCM4325

[feng tian]

Hi Michael,
We found that broadcom drops some BCM codes which support SDIO
interface on following url:
"http://android.git.kernel.org/?p=platform/system/wlan/broadcom.git;a=summary"
Just FYI.
Hope this can help.

BR, Feng.

2009/8/25 Michael Buesch <mb@bu3sch.de>:
> On Tuesday 25 August 2009 09:16:36 feng tian wrote:
>> Dear Michael,
>>
>> Another question:
>> We can't get the actual "datasheet" of BCM 4325. The pdf from broadcom
>> is so rough, and we also sent email to ask more detailed spec, but no
>> feedback.
>> What kind of datasheet of BCM4325 are you using now?
>> Could you please share this with us?
>>
>> Thank you very much.
>>
>> BR, Feng
>>
>>
>
> http://bcm-v4.sipsolutions.net/
>
> --
> Greetings, Michael.
>

Re: Abour linux driver supports BCM4325

[Michael Buesch]

On Thursday 27 August 2009 11:33:12 feng tian wrote:
> Hi Michael,
> We found that broadcom drops some BCM codes which support SDIO
> interface on following url:
> "http://android.git.kernel.org/?p=platform/system/wlan/broadcom.git;a=summary"
> Just FYI.
> Hope this can help.

No, it's fullmac.


-- 
Greetings, Michael.

Re: Abour linux driver supports BCM4325

[Holger Schurig]

>  1) changing b43 so it knows how to talk not just to
> SSB/PCI/PCMCIA chips but also SDIO chips

Feng, for this you could use another b43 card with SDIO, which 
doesn't use the LP-PHY, but the older phy. If you find such a 
device, you'll be start to code this now. As the SDIO-via-SSB 
code is identical to b43-with-LP-PHY and b43-without-LP-PHY, can 
you transfer all of this.

-- 
http://www.holgerschurig.de