Re: Abour linux driver supports BCM4325

[Michael Buesch <mb@bu3sch.de>]

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.