[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
Daniel-TAz00

I know my post are too long, but you guys talk to little and some time do not respond what are ask. So I got confuse by not understanding the objectives of Jacker31. The I have a feeling you edit the Title.

In any case It may be good Idea to express our self in a Kernel development thread. Then once we are set and have the drivers ready we can come and post them here. Any way Jacker31 started his post!

[DIS][DEV]Android Kernel Modding for GT-P52xx => http://xdaforums.com/galaxy-tab-3/development-10/dis-android-kernel-modding-gt-p52xx-t3052321

I look at that post before and at at the blog that talk about that. Are those drivers modified for promiscuous com already?

Any way here is what I has found. If I serach in Android OS

# ls /system/etc/wifi
bcmdhd_apsta.bin_b2
bcmdhd_mfg.bin_b2
bcmdhd_p2p.bin_b2
bcmdhd_sta.bin_b2
cred.conf
hostapd.conf
nvram_mfg.txt
nvram_net.txt
p2p_supplicant.conf
wpa_supplicant.conf

This gives me de idea that our wifi driver is called bcmdhd.

The driver in the kernel is at

Kernel-GT-P5210_SEA_JB_Opensource/drivers/net/wireless/bcmdhd

And the modules provided in boot.img are

# ls /lib/modules
atomisp.ko
db8131m.ko
dhd.ko
exfat_core.ko
exfat_fs.ko
hid-logitech-dj.ko
s5k5ccgx.ko
scsi_wait_scan.ko
sgx.ko
videobuf-core.ko
videobuf-vmalloc.ko

So the closes thing I see is

dhd.ko

But when I search kernel source to see what modules are install during init.rc I found

ramdisk$ grep -rn "insmod /lib/modules/" *
init.avc.rc:23: insmod /lib/modules/videobuf-core.ko
init.avc.rc:24: insmod /lib/modules/videobuf-dma-contig.ko
init.avc.rc:25: insmod /lib/modules/videobuf-vmalloc.ko
init.avc.rc:26: insmod /lib/modules/videobuf2-core.ko
init.avc.rc:27: insmod /lib/modules/videobuf2-memops.ko
init.avc.rc:32: #insmod /lib/modules/ov8830.ko
init.avc.rc:33: #insmod /lib/modules/mt9m114.ko
init.avc.rc:34: #insmod /lib/modules/lm3554.ko
init.avc.rc:36: insmod /lib/modules/s5k5ccgx.ko
init.avc.rc:37: insmod /lib/modules/db8131m.ko
init.avc.rc:38: insmod /lib/modules/atomisp.ko
init.common.rc:138: insmod /lib/modules/atomisp.ko
init.rc:137:insmod /lib/modules/exfat_core.ko
init.rc:138:insmod /lib/modules/exfat_fs.ko
init.redhookbay.rc:45: insmod /lib/modules/sgx.ko
init.redhookbay.rc:48: insmod /lib/modules/matrix.ko
init.redhookbay.rc:126: insmod /lib/modules/rmi4.ko
init.redhookbay.rc:198: insmod /lib/modules/rmi4.ko boot_mode=1
init.santos10wifi.rc:63: insmod /lib/modules/sgx.ko
init.santos10wifi.rc:66: insmod /lib/modules/matrix.ko
init.santos10wifi.rc:176: insmod /lib/modules/rmi4.ko
init.santos10wifi.rc:353: insmod /lib/modules/rmi4.ko boot_mode=1
init.wifi.vendor.rc:3:# insmod /lib/modules/cfg80211.ko
init.wireless.rc:4: insmod /lib/modules/fmdrv_chr.ko
init.wireless.rc:6: insmod /lib/modules/ipv6.ko

So it is not clear why there is a dhd.ko but it never loads!. This may means only that dhd is in fact build inside the kernel!!! I am not sure.

As a note "dhd.ko" have references inside about "bcmdhd". So I am prety sure this is the driver.

ramdisk$ grep -rn "bcmdhd" *
Binary file lib/modules/dhd.ko matches

Again to start you guys should start testing with JB 4.2.2, then try in KK 4.4.2. You will see what I mean if you don't.

Another funny thing you are saying you are P5200 but show me a P5210 for selection!!

for KK you have ( Look in the Source Code column)

GT-P5200_SEA_KK_Opensource.zip
GT-P5200_EUR_KK_Opensource.zip

Now I am not sure but I think for kernel development any one is OK, I think that bzimage will work for all TAB3 10.1. I imagine, the importance could be only to match KK or JB version. But I am not Totally sure about that. Now going back to KK 4.4.2 issue. It is possible that does not apply to KK since Selinux and related security may prevent mixing!! But I am not sure on that it is just a feeling!.