Hi Jes, I'm posting this patch set to show in what direction the work is going. Hopefully any changes (e.g. renames) which you wouldn't see fit for this driver can be identified early this way. The work is nowhere near the end. These changes only get me past the parse_efuse() step in the probe() routine. I've structured the patch set in such a way that changes that are not RTL8188EU-specific (preparatory work) come first. All but the last two patches (tagged "rtl8188eu:") fall into this category. If you were considering to apply any of them, note that they were not tested with any device that is known to work with rtl8xxxu, only a TP-Link TL-WN725N (RTL8188EU) dongle. The corresponding git branch for this patch set is at: git https://github.com/jsitnicki/linux.git branch rtl8xxxu-rtl8188eu Cheers, Jakub Jakub Sitnicki (16): rtl8xxxu: Treat REG_9346CR as an 8-bit wide register rtl8xxxu: Use REG_EFUSE_TEST register only on multifunctional devices rtl8xxxu: Don't check for illegal offset when reading from efuse rtl8xxxu: Skip disabled efuse words early rtl8xxxu: Unbreak a user-visible string rtl8xxxu: rtl8723au: Introduce a pointer to efuse rtl8xxxu: rtl8192cu: Introduce a pointer to efuse rtl8xxxu: Extract TX power fields from struct rtl8xxu_priv rtl8xxxu: Rename struct struct rtl8723au_tx_power fields rtl8xxxu: Rename struct rtl8723au_idx rtl8xxxu: Make efuse content length a parameter rtl8xxxu: Prepare to have more than one kind of struct *_tx_power rtl8xxxu: Make set_tx_power a chip-type-dependent operation rtl8xxxu: Introduce a device agnostic constant for efuse map length rtl8xxxu: rtl8188eu: Add stubbed fileops and chip-specific constants rtl8xxxu: rtl8188eu: Implement parse_efuse() drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c | 318 ++++++++++++++--------- drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h | 96 +++++-- 2 files changed, 262 insertions(+), 152 deletions(-) -- 2.1.0 -- 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
