Bob Copeland <me@xxxxxxxxxxxxxxx> writes: > On Wed, May 20, 2009 at 3:05 PM, Kalle Valo <kalle.valo@xxxxxx> wrote: >> Bob Copeland <me@xxxxxxxxxxxxxxx> writes: >>> So much for hubris! >> >> Don't feel down about this, this is always difficult and you are making >> good progress already. > > Heh, just a joke :) Good :) >> Current wl12xx code assumes that user space provides the NVS file. I'm >> guessing that Android has NVS file stored in chip's EEPROM. Check the >> !pWhalBus->pEEPROMBuf code path from TI's driver how to implement it. > > If you don't mind, check my work Definitely not, feel free to ask me. > -- the shmFwCtrl.c code seems to do the equivalent of: > > // initiate eeprom transfer > wl12xx_reg_write32(wl, ACX_REG_EE_START, ACX_REG_EEPROM_START_BIT); // *** > msleep(40); > msleep(40); > > // sets spad4 to 0, I guess this is some kind of address register? > wl12xx_reg_write32(wl, ACX_EEPROMLESS_IND_REG, 0); > > // everything from here on out is the same - read spad2 and 3 then boot. To me the code looks same. Only difference I found was that the TI driver had only one msleep(40), but that won't make any difference. > *** NB: I redefined ACX_REG_EEPROM_START_BIT to BIT(0) -- BIT(1) looked > wrong unless that define is meant for something else. I think BIT(1) is wrong, most probably I introduced the bug. > The state machine is kind of hard to read, but it seems like there > should be more to it. Did I miss anything as far as you can tell? My understanding is that nothing else is needed, but I can be wrong. > I get all zeros from spad2 and spad3 so it's not working with just the > above... Not good. Can you somehow check if Google stores the NVS file to the chip or somewhere else? -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
