linux-kernel - Re: kernel BUG at drivers/mmc/core/sdio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <60722BDE-68CB-47B7-856E-6986D760FE42@mac.com>
Date:	Wed, 27 Oct 2010 18:16:45 +0400
From:	Elvis Dowson <elvis.dowson@....com>
To:	Ohad Ben-Cohen <ohad@...ery.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: kernel BUG at drivers/mmc/core/sdio_io.c:28!

Hi Ohad,

On Oct 27, 2010, at 6:05 PM, Ohad Ben-Cohen wrote:

> You actually seem to have two problems here:
> 1. Your SDIO driver's probe function isn't called
> 2. Your WLAN driver is using the SDIO API without having a valid SDIO function
> 
> Ignoring the 2nd issue for now, you most probably have an integration
> problem.  Is the chip powered up correctly ?

Yes, I checked the VBAT, and VIO and WLAN Power Enable signals.

> is it mmc rescanned after it is powered up ?

I'm not sure about this. How can I check this? Could you point me to a code fragment?

> are you using the correct mmc controller ?

Yes, MMC2, as per the schematics.

> have you configured your mmc lines correctly (board muxing) ? etc..

Yes, I've setup the mux settings correctly.

> Maybe you want to checkout the mainline wl1271 driver using Luca's
> Beagle board patches :)

Ok, will try it once again. 

Best regards,

Elvis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/