[HTC Amaze 4G] oryan_dunn:
The playbook uses it's own kernel, so any drivers used there probably wouldn't be all that useful.

A couple interesting links:

http://bobcopeland.com/android_wifi.html

http://linuxwireless.org/en/users/Drivers/wl12xx

Not sure if it's relevent, but here is some info on WL1271 on Droid X

http://www.droidforums.net/forum/pr...drivers-droid-x-wifi-driver-info-success.html

I wonder if it's true that there were tweaks to for this driver as this chip is connected to a Qualcomm CPU. If so, HTC would be oblicated to release those tweaks as the source for the WL12xx drivers are also GPL. In kernels prior to 2.6.38, the WL12xx driver had source for WL1251 and WL1271. The only thing WL128x added was GPS, so I'd assume the WL127x driver would work for WiFI on a WL128x (Some info here http://e2e.ti.com/support/low_power_rf/f/307/t/181995.aspx )

Driver source in kernel used in GB:

http://lxr.linux.no/#linux+v2.6.35/drivers/net/wireless/wl12xx/

Driver source in kernel used in ICS:

http://lxr.linux.no/#linux+v3.0.16/drivers/net/wireless/wl12xx/

Really, this is just me brainstorming and sharing links. I'm not sure how useful any of this is.

---------- Post added at 05:50 PM ---------- Previous post was at 05:36 PM ----------

Doh, helps if I completely read the thread before posting.

So, what I'm wondering now, if the only module we're missing is the sdio, and if it truly just configures the io lines (which makes sense as a modification HTC would have to make to get it to work on a Snapdragon vs an OMAP), I wonder how hard it'd be to reverse engineer that? Also, I wonder if we could just use the built .ko module and include it on any other 3.0.16 kernels and just use it as is for the time being. Unless we'd need to modify anything in the WiFi/Bluetooth stack, as long as we build a 3.0.16 kernel, why would we need the WiFi source? Granted, lots of people have WiFi/Bluetooth issues, so perhaps it'd be nice to be able to make modifications, but I know I'm not familiar enough with it to help in that area.

Edit: kineto_gan.ko (Kineto Wireless Generic Access Network) is most likely the original WiFi Calling module from the 1.35.531.5 software. What's odd, the WL12xx chips support UMA as well as IMS (the type of WiFi calling we now have).

Edit 2: If the sdio module is what is modified, wouldn't HTC still have to release that as part of the GPL? And if it's just the hardware setup definition, why the hell would HTC care? It almost seems like it was an oversight on the last kernel release, and they just didn't devote any engineer time to fixing it. I wonder what the ICS kernel release will look like. I also wonder if there are any other HTC products that use an S3 proc and a TI WL127x or WL128x proc and what their sdio would look like.

Edit 2.5: sdio module probably doesn't need any code changes, perhaps it uses a config to change some things, but the code in wl127x_sdio.c didn't look too complex.

Edit 3: Trolling through the source of the released kernel for GB, it seems like wl12xx_sdio.ko would be built if CONFIG_WL1271_SDIO is set to y in the kernel config (I assume this was used to build what kernel you did build arch/arm/configs/ruby_defconfig).

Edit 4:

FWIW, just did an lsmod on my stock ICS phone, only lists wl12xx, no wl12xx_sdio listed.

Edit 4.5: another doh moment. wl12xx_sdio wasn't listed because I had WiFi disabled.

Edit 4.6: Here's my lsmod, just for the record:

shell@android:/ $ lsmod
lsmod
wl12xx_sdio 3062 0 - Live 0xbf003000
wl12xx 152391 1 wl12xx_sdio, Live 0xbf0f7000
mac80211 287554 1 wl12xx, Live 0xbf099000
bnep 10309 0 - Live 0xbf092000
btwilink 2928 0 - Live 0xbf08e000
hid_magicmouse 4923 0 - Live 0xbf089000
hidp 12103 0 - Live 0xbf082000
cfg80211 176680 2 wl12xx,mac80211, Live 0xbf048000
rfcomm 32621 0 - Live 0xbf03a000
bluetooth 151035 6 bnep,btwilink,hidp,rfcomm, Live 0xbf009000
compat 1658 0 - Live 0xbf005000
fm_drv 5983 0 - Live 0xbf000000 (C)

And once again Edit 5: I'm not rooted currenly, but I do have busybox installed. I'm trying to figure out how to determine the exact model number of the TI chip.