On Thursday 30 October 2008, Steve Sakoman wrote:
> > Overo has its SDIO WLAN chip (libertas) hard wired to the second controller,
> > as I understand things ... or maybe it's the third one. :)
>
> Correct! The wi2wi chip is connected to mmc2 with a 4 bit data path.
With the appended patch on top of Tony's four, I get:
mmc1: new SDIO card at address 0001
firmware: requesting sd8686_helper.bin
...
libertas: can't load helper firmware
libertas: failed to load helper firmware
libertas_sdio: probe of mmc1:0001:1 failed with error -2
So, progress. What's the best place to get that stuff?
Do we know that this driver behaves with SDIO yet?
- dave
---
arch/arm/mach-omap2/board-overo.c | 2 +-
arch/arm/mach-omap2/hsmmc.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
--- a/arch/arm/mach-omap2/board-overo.c
+++ b/arch/arm/mach-omap2/board-overo.c
@@ -214,7 +214,7 @@ static void __init overo_init(void)
omap_board_config = overo_config;
omap_board_config_size = ARRAY_SIZE(overo_config);
omap_serial_init();
- hsmmc_init(HSMMC1);
+ hsmmc_init(HSMMC1 | HSMMC2);
usb_musb_init();
usb_ehci_init();
overo_flash_init();
--- a/arch/arm/mach-omap2/hsmmc.c
+++ b/arch/arm/mach-omap2/hsmmc.c
@@ -340,6 +340,7 @@ static struct omap_mmc_platform_data mmc
static struct omap_mmc_platform_data mmc2_data = {
.nr_slots = 1,
.slots[0] = {
+ .wire4 = 1,
.set_power = hsmmc2_set_power,
.ocr_mask = MMC_VDD_27_28 | MMC_VDD_28_29 |
MMC_VDD_29_30 | MMC_VDD_30_31 |
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
