On Fri, Jun 22, 2012 at 2:45 PM, Matt Chen <machen@xxxxxxxx> wrote: > Hi Mohammed, > > 2012/6/20 Mohammed Shafi <shafi.wireless@xxxxxxxxx>: >> Hi Matt, >> >>> Both 0x2f and 0x2d can work fine to me of enabling >>> wiphy_rfkill_start_polling() in gpio.c:ath_start_rfkill_poll(). >>> >>> 1) with 0x2f >>> 0x404c address would change when press wifi button >>> rfkill block : yes -> 0x00000455 >>> rfkill block : no -> 0x00000c55 >>> 2) with 0x2d >>> 0x404c address would change when press wifi button >>> rfkill block : yes -> 0x00000455 >>> rfkill block : no -> 0x00000c55 >>> >>> >>> But I don't see the LED is changing, it is staying OFF (Amber). >> >> not sure about that, but i think rfkill is working for both of us >> i told 0xeed changes to 0x6ed for me >> >> you got 0x455 changes to 0xc55 >> >> BIT 12(GPIO pin 11 seems to toggle 4 ->C), you can confirm by rfkill list > Would it be the patch to fix it ? or it is just a workaround to prove > the rfkill_poll can be enabled ? ideally, this should have been properly hard coded in the EEPROM stuff itself. i think you got a very brand new AR9462 just when it came to the market :) its a kind of workaround only. -- thanks, shafi -- 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
