yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] mikereidis:
Ktoonsez has posted his FM enabled kernel here: http://www.mediafire.com/?4lho3j79ee1oy1g

If you haven't already, please read at least his 1st post here to see if you can use it, and how: http://xdaforums.com/showthread.php?t=1756776

He says:

•Must have a AT&T, Bell, Rogers and Telus Samsung ROM

•Must have recovery installed from here: http://www.epiccm.org/2012/06/team-epics-root-from-recovery.html

So I'd guess this is only for SGH-I747 and SGH-I747M.

Once the kernel is loaded, my testing instructions are here: http://xdaforums.com/showpost.php?p=28524828&postcount=123

XDA user crash822 posted this error (and I think Ktoonsez had the same):

My response:

"init_success:1 after 9 seconds" means it timed out after 9 seconds. This likely means that "insmod /lib/modules/radio-iris-transport.ko" failed.

You need to be at an SU/root prompt to do this. I presume '#'. Run "su" if you aren't. And you can try it manually:

su

insmod /lib/modules/radio-iris-transport.ko

If it gives an "exec error" something may be messed up with the symbols, but that shouldn't happen when kernel and modules are built together. Checking kernel messages with "dmesg" might show something like this:

<4>[64224.008446] radio_iris_transport: disagrees about version of symbol module_layout
[Sprint Samsung Galaxy S III] mikereidis:
Yes, the SGH-T999 (T-Mobile) and SGH-T999V (Canada Wind/Mobilicity/Videotron) seem to have MSM8260A. Apparently it's identical to the 8960, except the modem is different.

Yes, there is hardware for 2 FM radios (?). Same as Galaxy S/S2/S3/Note etc. (Silicon Labs FM plus Broadcom combo.)

I put a (?) above because I suddenly realised I may not have given that much thought. Are we sure the Broadcom chip is there ? Files don't prove chip presence. I've seen even stock ROMs with files for different combo chips. MSM8960 has Bluetooth, WiFi and FM integrated. Why the heck would that not be used, and an additional chip added ?

There have been various complaints about LTE HTC OneX WiFi and BT, and Qualcomm hasn't shipped a lot of BT/WiFi chips, so perhaps a wise manufacturer might have gone with a more proven product line ?

If either has a usable FM antenna connection, I think it's more likely to be to the Qualcomm SOC. Partly because the Qualcomm reference design likely includes that. But if Samsung added a Broadcom chip, then I'm not so sure.
[Sprint Samsung Galaxy S III] jnadke:
AnandTech has lost their edge over the years. I don't really trust them.

That said, they are correct. Until now I've been following he said/she said.

I checked my dmesg kernel log and it does seem to be detecting a BCM4334_B2. Chip version 0x3.

So the best chance that FM Radio is connected is through the BCM4334.

I'm not sure why the chip isn't in the TechRepublic breakdown.

EDIT: It seems from the i9300 breakdown, the chip is actually a Murata Wireless chip. It seems they probably use a slightly different model than the i9300.

The chip is likely this one:

http://www.techrepublic.com/photos/...?seq=46&tag=content;siu-container#photopaging

You can see the chip is similar to this one:

http://www.ifixit.com/Teardown/Samsung-Galaxy-S-III-Teardown/9391/2
[Sprint Samsung Galaxy S III] jamesbra:
Using ktoons FM kernal I get time out as in your earlier post and reboot when setting frequency. Insmod does not give exec error. I tried it a few ways to hopefully rule out user error.

Sent from my slowly but surely customizing SGS3
[Sprint Samsung Galaxy S III] mikereidis:
My snapdragon-specs.pdf file has an asterisk for S4 SOCs that says:

*-Digital integrated in SoC, Analog added via WCN3660/80

And I thought that was kind of weird. Why would you want analog if digital is available ?

I, and many FM users would like digital audio so we can listen on Bluetooth, record, change audio effects and measure the audio etc.

The only reasons I can think you might want analog audio is to drive headphones (or speakers if possible) or to use less power possibly. But for low power, fewer chips is usually better, and there are supposed to be digital audio paths that are low power, even for decoding (or even encoding) MP3s.

But it's always possible that the early 8960 SOCs, which are reportedly in short supply, have or have had some hardware issues that might make an external chip make sense. Manufacturers don't like to announce problems.
[Sprint Samsung Galaxy S III] mikereidis:
Then just go into the Spirit app settings and set Debug-> FM Chip to "BCM433x/207xx", then restart the app.

Even with no antenna connection it should still start and "sort of work". RSSI will likely be low and could be -128 or 0 or similar.

Be sure to have wired earphones plugged in
[Sprint Samsung Galaxy S III] mikereidis:
"No such device" is a new error, so that's progress. :)

IF the phone is using a Broadcom chip for Bluetooth then there may be a Qualcomm Bluetooth driver we need to load first.

radio-iris should be in the kernel already. No insmod needed.

radio-iris talks to radio-iris-transport.

radio-iris-transport needs to be insmod'd.

radio-iris-transport needs to talk to a low level Bluetooth driver. Like every other combo chip, a single "core" is used for both Bluetooth and FM, so there's a need to mediate access.

I'll see what I can dig up.

EDIT: dmesg will likely show an error, like "Cannot open the command channel". From:

/* Open the SMD Channel and device and register the callback function */

rc = smd_named_open_on_edge("APPS_FM", SMD_APPS_WCNSS,

&hsmd->fm_channel, hdev, radio_hci_smd_notify_cmd);

if (rc < 0) {

FMDERR("Cannot open the command channel");

return -ENODEV;

}

EDIT2: Yeah, all the LTE GS3 kernel config files have this, while the LTE OneX config does not:

CONFIG_BT_BCM4334=y

CONFIG_BCM4334=y

I think there are several kernel config options with the acronym "SMD" in them that are also needed. This is the Qualcomm "Shared Memory Device" API that deals with a lot of communications between cores inside the SOC.

It will take some study to figure out just what's needed.

In the meantime, let's see if the BCM4334 is active with the Debug-> FM Chip setting in Spirit. I doubt it but it's easy enough to try.
[Sprint Samsung Galaxy S III] Copyright5:
I believe the module for the S3 is /system/lib/modules/msm-buspm-dev.ko. MSM = multismart modem, the chip on the s3 should be MSM8960.
[Sprint Samsung Galaxy S III] mikereidis:
Not sure what you're saying. I think it's well established most LTE S3s have 8960, and the T999(V) is 8260A.

What is msm-buspm-dev ? Just looks like it reads and writes memory to me.
[Sprint Samsung Galaxy S III] brfield:
If you need any help, I am on T-mo and can build kernels. I have the stock source ready to go and the source modules released by Sammy.

Also, I have Spirit. So just tell me what's needed!
[Sprint Samsung Galaxy S III] mikereidis:
radio-tavarua is for an older external Qualcomm FM chip in devices like Huawei X5/X6. radio-iris is the new Qualcomm FM stuff; they both present almost identical V4L APIs but the hardware is different enough that a new driver was written.

For whatever reason Samsung service manuals always end up available sooner or later, and we'll see then. Don't know if different manuals for different carriers though.
[Sprint Samsung Galaxy S III] mikereidis:
Great !

The first thing I'd like at least 1-2 people with every carrier version to try is see if the Broadcom chip works.

July 10 test release of Spirit is here: http://d-h.st/hRR

Disable Bluetooth, set Debug-> FM Chip to "BCM43xx/207xx", ensure wired earphones are plugged in for an antenna and restart the app.

If it starts without error, see if you can get the RSSI at top left over 10 when tuned to a known good station.

Turn Spirit/FM off, turn Bluetooth on, and see if there is any difference when you restart Spirit.

If no carrier variant shows an RSSI over 10, then most likely the Broadcom chip antenna pins aren't connected.

So then we need to get the iris-radio-transport driver loaded, then if we can run fmconfig and successfully use the "enable" command, we are good to look at RSSI from the Qualcomm chip.

I've written lots in the last few pages about this. Basically we need these lines in the kernel config:

CONFIG_RADIO_ADAPTERS=y

CONFIG_RADIO_IRIS=y

CONFIG_RADIO_IRIS_TRANSPORT=m

But radio-iris-transport seems to have some dependencies on "SMD" and there are a lot of SMD kernel config options I don't understand at this time.

My AT&T HTX OneX LTE has the same MSM8960 (/ 8260A for your T-Mobile) as the LTE GS3s, and the Qualcomm FM radio works fine, despite AT&T not supporting it.

There is no kernel source released yet to see the config file, but the config.gz from my device is here: http://d-h.st/WAW

AT&T kernel source is conspicuously absent. But perhaps the Rogers version, or a One S will be pretty similar.

EDIT: Even the Rogers OneX kernel code is missing. But One S code is available here for Telus, Bell and Rogers, and as a "bonus" the One S has the same MSM8260A that the T999s do: http://www.htcdev.com/devcenter/downloads
[Sprint Samsung Galaxy S III] LLStarks:
Are the chances in our favor that at least one of the radios are wired up in a useful manner?
[Sprint Samsung Galaxy S III] rakeshchn:
I have an unrooted T999 (Tmobile US version) and I tested the Spirit FM app you posted after changing the FM chip to BCM. Plugged in headphones and tuned to a known station and the number at the top left stayed 0. Below are the screens. See the one error message I got when opening the app as well as closing the app. Also bluetooth will automatically turn on when the app is open, so I was not able to test with bluetooth off.
[Sprint Samsung Galaxy S III] jnadke:
The app requires root, IIRC.

I've worked with Broadcom before. They make you sign your life away through NDA, and provide watermarked PDFs with highly unique passwords. They're paranoid of anything about their chips getting out.

I hear Qualcomm is 10 times worse.
[Sprint Samsung Galaxy S III] macdroid01:
lol, watermarked PDF? Wouldn't converting to an image that is plain 1 bit B&W then scanning with OCR to convert to text defeat this? Or perhaps they have a clever way of rewording a key sentence slightly for each version of a document they give to each entity they distribute to. My that would be clever.
[Sprint Samsung Galaxy S III] jrbaker624:
My play button keeps going back and forth on its own from play to pause BUT its says zero instead of -128 now
[Sprint Samsung Galaxy S III] jrbaker624:
Also in terminal when I do fmconfig then enable I still get Enablereciver failed to open = -1
[Sprint Samsung Galaxy S III] mikereidis:
"Insufficient data". :)
[Sprint Samsung Galaxy S III] mikereidis:
Not always, but in this case yes.

While all help is appreciated, there is no useful information we can get from un-rooted devices at this time.

That helps explain why datasheets are so hard to find, even on those dodgy Chinese file sites.

At least Qualcomm has the Code Aurora forum, and there's quite a bit of useful source code there. Without the Code Aurora FM app, none of us might have had FM on any custom ROMs.
[Sprint Samsung Galaxy S III] mikereidis:
For the dancing mute/unmute button, set Debug-> Audio Focus to "Disable" and restart the app.

The Unlocked app can also do this sometimes if the wrong wired headset is used, or is only partly inserted. The media buttons keep getting triggered in this case.

I think I had an email from someone who set FM chip to Broadcom. He said that RSSI was always 17 with Bluetooth off, and 0 with it on.

Unchanging numbers, low numbers and negative are all bad signs. Older Broadcom chips would show a strange repeating pattern.

So, early indications are that using the Broadcom chip is unlikely.
[Sprint Samsung Galaxy S III] mikereidis:
For the Qualcomm chip/SOC we need someone to be able to successfully do an "insmod" on iris-radio-transport.ko .

We don't have that yet. We have to figure out exactly which "SMD" kernel config options are needed, in addition to the 3 V4L radio and iris-radio options we've tried.

Unfortunately, "We" usually means "I", and I've got TONS of other (working) phones and issues to deal with too, for my existing customers.

But if somebody else with some know how can figure it out, I'd be very happy to hear.
[Sprint Samsung Galaxy S III] slickdaddy96:
I am using a rooted Sprint S3 (SPH-L710). I tested with bluetooth off and I get nothing but "0" on any frequency including known good channels.
[Sprint Samsung Galaxy S III] jeffro23:
well this sucks..

I appreciate all the continued work but Im on the verge of settling for the One X
[Sprint Samsung Galaxy S III] jarnow94:
Why are you giving up already?
[Sprint Samsung Galaxy S III] mikereidis:
PM:

Precisely what I expected: http://xdaforums.com/showpost.php?p=28583879&postcount=139

We need the SMD stuff I spoke of in the last 2 pages.
[Sprint Samsung Galaxy S III] Canoe Head:
Is it possible that cmd channel errors/problems are due to power management on the phone?

If radio not powered on you cannot init etc

A suggestion would be to compile radio-iris as module, then increase the logging prior to insmod. May give further hints...
[Sprint Samsung Galaxy S III] mikereidis:
Anything is possible. I'm not familiar with the internals of these SOCs or their software stacks.

We have to get radio-iris-transport loading before we worry about radio-iris. The former serves the latter.

And again, for radio-iris-transport I think we need the SMD stuff it talks to.
[Sprint Samsung Galaxy S III] brfield:
I'm not familiar with the smd devices, so does anybody have any tips or experience with these. I'm trying to look into it, but I don't even know where to start or search.
[Sprint Samsung Galaxy S III] mikereidis:
Googling this is a start:

qualcomm "shared memory"

Unfortunately documents are kept secret.
[Sprint Samsung Galaxy S III] brfield:
I do see that the kernel source files have some SMD references, and even some source files with it in the names.

---------- Post added at 05:27 PM ---------- Previous post was at 04:42 PM ----------

I have no idea about any C/C++/C# or any programming languages, so have a look here and see if you can find anything.

https://dl.dropbox.com/u/13047317/smd.zip
[Sprint Samsung Galaxy S III] mikereidis:
Knowing C is pretty much essential for building kernels, unless you're just doing mild config mods and nothing in the build gets broken.

AFAIK, kernel C source code is pretty much the only public "documentation" for SMD.

So why don't we all just put this to rest for a while, unless and until someone steps up to the plate with knowledge of SMD and/or anything else we need to get these drivers loading.

I can try to get to this myself eventually, but I'm over extended and badly need some time off and time for personal/household matters.
[Sprint Samsung Galaxy S III] jnadke:
I can pick it up next week. Right now I've got a few important things on my plate for my for-money job that I have to do during my spare time.
[Sprint Samsung Galaxy S III] brfield:
I can see what it does, kinda. But I am not able to write it, or truly understand it.

For me, it mainly comes down to the internet to find these things :)
[Sprint Samsung Galaxy S III] mikereidis:
PM:

Hypothetically, that could be so. If it was rfkill2 for example, you could do this from adb shell to enable it, and see some info:

su

cat /sys/class/rfkill/rfkill2/*

echo 1 > /sys/class/rfkill/rfkill2/state

cat /sys/class/rfkill/rfkill2/*

But I don't see this on my HTC OneX LTE with the same 8960 SOC:

ls -l /sys/class/rfkill

lrwxrwxrwx root root 2012-07-14 16:17 rfkill0 -> ../../devices/virtual/bluetooth/hci0/rfkill0

lrwxrwxrwx root root 2012-07-14 16:17 rfkill1 -> ../../devices/platform/wcnss_wlan.0/ieee80211/phy0/rfkill1

That said, the Samsung ROMs might be using an rfkill for the FM radio.

Normally, I think you only need an rfkill for transmitting. I've never seen a GPS rfkill for example; GPS only does receive.

The Qualcomm FM (like almost every FM) technically supports transmit, so it makes sense there might be an rfkill for it.
[Sprint Samsung Galaxy S III] jrbaker624:
It was in the rfkill0 folder
[Sprint Samsung Galaxy S III] jrbaker624:
Mean anything? I really don't know what I'm doing just trying to help
[Sprint Samsung Galaxy S III] mikereidis:
That's the Bluetooth rfkill, and 0 means it's off.

The PM'er likely saw something like this:

ls -l /sys/class/rfkill

...

lrwxrwxrwx root root 2012-07-14 16:17 rfkill2 -> ../../devices/virtual/iris-fm/fm0/rfkill2

...

If the letters "FM" aren't in the pseudo-file names or their content, it's probably not directly related to FM.
[Sprint Samsung Galaxy S III] sblees:
Has anyone tried to get stuff related to fm radio from the I9300 forum?

Sent from my SAMSUNG-SGH-I747
[Sprint Samsung Galaxy S III] mikereidis:
Please don't take any offense, this is meant "all in good fun", but...

If you go to a dentists' conference and point out that tooth brushing might be a good idea, you might get some funny looks.

:)

The answer is yes, BTW.

If you have any knowledge of Qualcomm SMD or the specifics of the iris-fm driver, that is what we need now.

Everything else is pretty much us blabbing at each other and agreeing that FM would be nice.
[Sprint Samsung Galaxy S III] jrbaker624:
This help with anything?

Sorry I don't know "code stuff" just trying to find anything FM and hope that it may help or get somewhere
[Sprint Samsung Galaxy S III] mikereidis:
What is that ? Kernel messages or logcat ?

Pretty much FM audio related stuff in the green circle but there's some possible core FM stuff above it: NB & WB are narrowband and wideband settings on the Qualcomm FM I think.

Can you send or post a full text file ?
[Sprint Samsung Galaxy S III] brfield:
On CM10, the radio still outputs the same things. The numbers are either -17 or 0 in Spirit.
[Sprint Samsung Galaxy S III] bbelos:
I don't have too much to add here yet, except working with a custom sprint kernel, I threw in some debugging to try and figure out where the command channel failure is. If you trace the "smd_named_open_on_edge" call from drivers/media/radio/radio-iris-transport.c it will lead you to the failure point inside arch/arm/mach-msm/smd.c:smd_get_channel. It appears to loop through some devices looking for the APPS_FM channel, which from my debugging, doesn't appear to exist (no surprise there). Although I haven't figured out yet where that channel comes from.

<6>[ 117.385411] [0: insmod: 3003] Entering smd_named_open_on_edge

<6>[ 117.391210] [0: insmod: 3003] smd_named_open_on_edge: smd_open('APPS_FM', da072400, bf0150c4)

<6>[ 117.400610] [0: insmod: 3003] Entering smd_get_channel

<6>[ 117.596062] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = DATA40_CNTL, type = 6, ch->type = 0

<6>[ 117.607691] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = DATA16_CNTL, type = 6, ch->type = 0

<6>[ 117.619227] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = DATA15_CNTL, type = 6, ch->type = 0

<6>[ 117.631374] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = DATA40, type = 6, ch->type = 0

<6>[ 117.642240] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = DATA11, type = 6, ch->type = 0

<6>[ 117.653349] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = DATA4, type = 6, ch->type = 0

<6>[ 117.664367] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = DATA3, type = 6, ch->type = 0

<6>[ 117.675385] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = DATA2, type = 6, ch->type = 0

<6>[ 117.687013] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = DATA1, type = 6, ch->type = 0

<6>[ 117.697787] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = apr_voice_svc, type = 6, ch->type = 0

<6>[ 117.709507] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = DIAG_2, type = 6, ch->type = 0

<6>[ 117.720585] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = SSM_RTR, type = 6, ch->type = 0

<6>[ 117.732397] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = IPCROUTER, type = 6, ch->type = 0

<6>[ 117.743506] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = apr_apps2, type = 6, ch->type = 1

<6>[ 117.754890] [0: insmod: 3003] smd_get_channel: Before if, name = APPS_FM, ch->name = local_loopback, type = 6, ch->type = 100

<6>[ 117.767099] [0: insmod: 3003] smd_get_channel: Returning NULL

<6>[ 117.773019] [0: insmod: 3003] smd_named_open_on_edge: Failing CCC

<3>[ 117.779978] [0: insmod: 3003] iris_radio: Cannot open the command channel[/CODE]
[Sprint Samsung Galaxy S III] kinwolf:
Edit, wrong thread
[Sprint Samsung Galaxy S III] mikereidis:
Googling "APPS_FM" leads me to this file:

https://www.codeaurora.org/gitweb/q...3;hb=bea97f312a22f62387ad58959921a2f40592d85b

So I'd guess smd_tty_init(), smd_tty_dummy_probe() or smd_tty_open() might register it. (?)

From this: http://pastebin.com/UMtJK88h

I learn to look for /sys/devices/platform/APPS_FM.6/* . One my LTE OneX I see:

ls -l /sys/devices/platform/APPS_FM.6

lrwxrwxrwx root root 2012-07-19 07:27 driver -> ../../../bus/platform/drivers/APPS_FM

-r--r--r-- root root 4096 2012-07-19 07:27 modalias

drwxr-xr-x root root 2012-07-19 07:27 power

lrwxrwxrwx root root 2012-07-19 07:27 subsystem -> ../../../bus/platform

-rw-r--r-- root root 4096 2012-07-19 07:27 uevent

cat /sys/devices/platform/APPS_FM.6/*

/sys/devices/platform/APPS_FM.6/driver: invalid length

platform:APPS_FM

/sys/devices/platform/APPS_FM.6/power: invalid length

/sys/devices/platform/APPS_FM.6/subsystem: invalid length

DRIVER=APPS_FM

MODALIAS=platform:APPS_FM

My OneX kernel log shows this for SMD, including APPS_FM:

<6>[ 3.288386] msm_smd_probe(): get msm_smd_debug_mask=0xc

<6>[ 3.288448] [SMD] smd probe

<6>[ 3.288692] [SMD] smd_core_init()

<6>[ 3.288875] [SMD] smd_core_init() done

<6>[ 3.288966] [SMD] smd_alloc_loopback_channel: 'local_loopback' cid=100

<3>[ 3.289272] [SMD] smd_channel_probe_worker: allocation table not initialized

...

<6>[ 8.956569] [SMD] smd_alloc_channel() 'sys_mon' cid=4 size=01024, [Package mode]

<6>[ 8.956966] [SMD] SMD: ch 4 0 -> 1, state: 0

<6>[ 8.957057] [SMD] SMD: ch 4 1 -> 2, state: 1

<6>[ 8.965237] [SMD] smd_alloc_channel() 'APPS_RIVA_CTRL' cid=5 size=08192, [Package mode]

<6>[ 8.965542] [SMD] SMD: ch 5 0 -> 1, state: 0

<6>[ 8.965695] [SMD] smd_alloc_channel() 'APPS_RIVA_DATA' cid=6 size=08192, [Package mode]

<6>[ 8.965786] [SMD] SMD: ch 5 1 -> 2, state: 1

<6>[ 8.966000] diag: incomplete pkt on WCNSS CNTL ch

<6>[ 8.966122] [SMD] SMD: ch 6 0 -> 1, state: 0

<6>[ 8.968441] [SMD] SMD: ch 6 1 -> 2, state: 1

...

<6>[ 9.165359] [SMD] smd_alloc_channel() 'WLAN_CTRL' cid=7 size=08192, [Package mode]

<6>[ 9.165817] [WCNSS]wcnss_wlan_ctrl_probe: SMD ctrl channel up

<6>[ 9.171616] [SMD] smd_alloc_channel() 'APPS_RIVA_BT_CMD' cid=8 size=08192, [Package mode]

<6>[ 9.171951] [SMD] smd_alloc_channel() 'APPS_RIVA_BT_ACL' cid=9 size=08192, [Package mode]

<6>[ 9.178116] [SMD] smd_alloc_channel() 'APPS_FM' cid=10 size=08192, [Package mode]
[Sprint Samsung Galaxy S III] bbelos:
I see what you have there, mine is missing APPS_FM.6, APPS_RIVA_BT_ACL.6, APPS_RIVA_BT_CMD.6, APPS_RIVA_CTRL.6 & APPS_RIVA_DATA.6:

shell@android:/ # ls /sys/devices/platform/

BAM_RMNT

DATA1.0

DATA11.0

DATA12_CNTL.0

DATA13_CNTL.0

DATA14_CNTL.0

DATA15_CNTL.0

...

It's curious that those make reference to WCNSS which seems to be related to a different wireless driver? Does the OneX kernel use CONFIG_WCNSS_CORE?
[Sprint Samsung Galaxy S III] mikereidis:
Yes. The LTE OneX uses the Bluetooth, Wifi and FM built into the MSM8960 SOC.

The LTE GS3s use an external Broadcom chip for Bluetooth and Wifi.

I think the iris transport might require at least some of the Qualcomm integrated Bluetooth be loaded. Like most combo chips the FM controls ride on top of the Bluetooth HCI channel.