Problem with Marvell SD8686 with Linux-2.6.29

[Dan Williams]

On Wed, 2010-10-20 at 20:54 +0800, Ivan Li wrote:
> ----- Original Message ----- 
> From: "Alberto Panizzo" <maramaopercheseimorto at gmail.com>
> To: "Ivan Li" <lijinlei1 at 163.com>
> Cc: "Marek Vasut" <marek.vasut at gmail.com>; <libertas-dev at lists.infradead.org>
> Sent: Wednesday, October 13, 2010 1:47 AM
> Subject: Re: Problem with Marvell SD8686 with Linux-2.6.29
> 
> 
> > Hi Ivan,
> > Please, do not top-post..
> > 2010/10/12 Ivan Li <lijinlei1 at 163.com>:
> >> Hi Alberto,
> >>
> >> Thanks for your reply.
> >>
> >> Interface: SDIO
> >> FW: 9.70.15p0
> >>
> >> Below is the log when I insert the module:
> >> root at onyx ~$ modprobe libertas_sdio
> >> lib80211: common routines for IEEE802.11 drivers
> >> libertas_sdio: Libertas SDIO driver
> >> libertas_sdio: Copyright Pierre Ossman
> >> libertas_sdio mmc1:0001:1: firmware: requesting sd8686_helper.bin
> >> libertas_sdio mmc1:0001:1: firmware: requesting sd8686.bin
> >> libertas: 00:27:13:e2:bd:30, fw 9.70.15p0, cap 0x00000303
> >> libertas: PREP_CMD: command 0x00a3 failed: 2
> >> libertas: PREP_CMD: command 0x00a3 failed: 2
> >> libertas: eth0: Marvell WLAN 802.11 adapter
> >>
> > It seems that you are stucked with the Mesh initialization..
> > Do you need this feature?
> > While the advice is still upgrade the kernel, you can disable the mesh
> > support in:
> > -> Device Drivers
> > -> Network device support (NETDEVICES)
> >  -> Wireless LAN (WLAN)
> >   -> Marvell 8xxx Libertas WLAN driver support (LIBERTAS)
> >    -> LIBERTAS_MESH [=n]
> Thanks for your reply.
> I don't need Mesh feature, but for some reason I can't upgrade my kernel to 2.6.34 (Most of my driver will be re-written).
> But I managed to upgrade to 2.6.32, but the problem is still there.
> 
> I am wondering if there is some defects(bugs) in my SDIO driver?
> My problem is: I can use 'iwlist eth0 scan' to get AP list, but association failed. If SDIO issue then why just 'iwlist eth0 scan' can work?

Can you turn on MMC debugging, and also modprobe libertas.ko with:

debug=0x5043a7

so we can get more info about what's going on in the driver?  I'd like
to see why the driver thinks the original association command failed.

Dan