<div dir="ltr"><div dir="ltr"><div>Hi,<br><br></div>Thank you both for your comments.<br><div><br>@郭传鈜:<br><br>>> + ucidef_set_led_wlan "wlan2g" "WLAN2G" "mercury:green:wlan2g" "phy1tpt"<br>> I think the following line is incorrect:<span><br>>> + ucidef_set_led_wlan "wlan5g" "WLAN5G" "mercury:green:wlan5g" "phy0tpt"<br></span>> There is no LED trigger called 'phy0tpt' so I think we should use netdev trigger like this:<br>> ucidef_set_led_netdev "wlan5g" "WLAN5G" "mercury:green:wlan5g" "wlan0"<br></div><div><br>Ok!<br><br><br>>> +static struct gpio_keys_button mac1200r_gpio_keys[] __initdata = {<br>>> + {<br>>> + .desc = "WPS button",<br>>> + .type = EV_KEY,<br>>> + .code = KEY_WPS_BUTTON,<br>>> + .debounce_interval = MAC1200R_KEYS_DEBOUNCE_INTERVAL,<br><div>>> + .gpio = MAC1200R_GPIO_BTN_WPS,<br>>> + .active_low = 1,<br>>> + },<br>>> +};<br>> Although the key is called WPS/RESET , I think a reset button is more
important than a WPS button.That's just my personal opinion :)<br></div><div><br>I think you are right.<br></div><br><br>>> + ap91_pci_init(art + MAC1200R_PCIE_CALDATA_OFFSET, tmpmac);<br>> What? I think this function is only able to load CALDATA for ath9k devices.Maybe I'm wrong:)<br></div><div><br></div><div>The
router has two radios, one ath9k and one ath10k. Isn't it needed for
the ath9k calibration data? Or this radio is already covered by
"ath79_register_wmac(art + MAC1200R_WMAC_CALDATA_OFFSET, tmpmac); ...?<br><br><br><div>>> +$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,MAC1200R,mc-mac1200r,MC-MAC1200R,ttyS0,115200,0x12000001,1,8Mlzma))<br></div><div>>The
factory image is broken since TP-LINK started to use a new firmware
format with RSA signature in China.This should be introduced in the TOH
wiki I think:)<br><br></div><div>Done!<br><br><br><br></div><div>@John:<br><br></div>Sorry. Do you mean a description for the patch? I am not aware of what SoB means.<br><br><br></div><div>Thanks!<br><br>Roger</div></div></div>