leakydata / bcmon Goto Github PK
View Code? Open in Web Editor NEWAutomatically exported from code.google.com/p/bcmon
Automatically exported from code.google.com/p/bcmon
root@nexus7-47767ab4:/usr/src/linux# make modules
SUBDIRS=drivers/net/wireless/bcmdhd CC [M]
drivers/net/wireless/bcmdhd/src/bcmsdio/sys/bcmsdh.o
In file included from drivers/net/wireless/bcmdhd/src/bcmsdio/sys/bcmsdh.c:41:0:
drivers/net/wireless/bcmdhd/src/dhd/sys/dhd_sec_feature.h:53:23: error:
operator '>=' has no left operand
drivers/net/wireless/bcmdhd/src/dhd/sys/dhd_sec_feature.h:60:23: error:
operator '>=' has no left operand
drivers/net/wireless/bcmdhd/src/dhd/sys/dhd_sec_feature.h:104:23: error:
operator '>=' has no left operand
make[1]: *** [drivers/net/wireless/bcmdhd/src/bcmsdio/sys/bcmsdh.o] Error 1
make: *** [_module_drivers/net/wireless/bcmdhd] Error 2
Original issue reported on code.google.com by sidhayn
on 29 Nov 2012 at 11:19
What steps will reproduce the problem?
1. Checked out code from bcmon project.
2. made some changes to source tree to compile correctly. The changes I made is
attached in the patch file.Also changed kernel configuration. It is also
attached
3. moved new compiled module to /system/lib and "bcm4330_sta.bcmon.bin" to
"/system/etc/wifi/bcm4330_sta.bin"
4. insmod' ed cfg80211.ko
5. turned on wifi by pressing icon in desktop
6. checked status by using 'iwconfig'
What is the expected output? What do you see instead?
I expect a normal iwconfig output. but instead iwconfig waits lot of time and not printing info about the wireless interface. in that waiting time kmsg produces some error s . Its attached as iwconfig.log
What version of the product are you using? On what operating system?
'svn info' says
Path: .
URL: http://bcmon.googlecode.com/svn/trunk/bcm4330
Repository Root: http://bcmon.googlecode.com/svn
Repository UUID: f22563d7-eeaa-7245-33f1-0b5dc2617f4f
Revision: 7
Node Kind: directory
Schedule: normal
Last Changed Author: [email protected]
Last Changed Rev: 4
Last Changed Date: 2012-09-18 16:36:50 +0530 (Tue, 18 Sep 2012)
My phones os
cat /proc/version
Linux version 2.6.35.7 (harish@ubuntu) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-68) ) #35 PREEMPT Sun Mar 18 23:49:27 IST 2012
cat /proc/cmdline
console=ttyS0,115200n8 mem=362M kmemleak=off root=/dev/ram0 rw androidboot.console=ttyS0 mtdparts=bcm_umi-nand:256K@0K(bcm_boot)ro,2048K@256K(loke)ro,2048K@2304K(loke_bk)ro,256K@4352K(systemdata)ro,12800K@4608K(modem)ro,5120K@17408K(param_lfs)rw,5120K@22528K(boot)ro,5120K@27648K(boot_backup)ro,235520K@32768K(system)rw,40960K@268288K(cache)rw,201984K@309248K(userdata)rw,256K@511232K(efs)rw,256K@511488K(sysparm_dep)ro,256K@511744K(umts_cal)ro,1024K@512000K(cal)r BOOT_MODE=0 loglevel=0 BOOT_FOTA=0 DEBUG_LEVEL=LOW
Please provide any additional information below.
So I tried the above procedure with stock firmware.
at this time, iwconfig shows that wireless at monitor mode.But its clear that its not true. because we cant get monitor mode with stock firmware.
not only that, at this situation, I couldn't change the mode of wifi interface to 'managed' by using iwconfig.
the complete source tree is available at http://sourceforge.net/p/galaxyykernel/code/ci/958afa38ecf2ef20ea5586ce24796af36f5feac8/tree/drivers/net/wireless/4330/
So with my little knowledge, i think firmware changes is necessary for this device specially.
So I here attached my stock firmware .
One more request.
People like me are very much enthusiastic to know that how you people hacked the firmware. so please consider us.
Original issue reported on code.google.com by [email protected]
on 19 Mar 2013 at 4:28
Attachments:
What steps will reproduce the problem?
1.apk wont install firmware just Fc's
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
On 4330
Please provide any additional information below.
Any help would be great,or if theres any way i can help you to help me i would
be more than happy to do it/any other files u need etc.
Original issue reported on code.google.com by [email protected]
on 20 Aug 2013 at 4:44
[deleted issue]
What steps will reproduce the problem?
1. Firmware model: Not detected
2.
3.
What is the expected output? What do you see instead?
Firmware model: Not detected
What version of the product are you using? On what operating system?
CyanogenMod 10-20121101-Nightly-p1
Please provide any additional information below.
The apps launches normaly, after having the status I have :
Firmware model: Not detected
installed Tools version: 0
installed fw version: 0
Original issue reported on code.google.com by [email protected]
on 22 Jul 2013 at 11:05
What steps will reproduce the problem?
1. download gs2_bundle
2. unzip it
3. sh setup.sh
What is the expected output? What do you see instead?
LOADING MODULE
insmod: can't insert 'dhd.ko': invalid module format
What version of the product are you using? On what operating system?
r5 on cm9.0.0 (stable)
Original issue reported on code.google.com by 01ttouch
on 18 Sep 2012 at 7:10
Monitoring mode on HTC HD2 with android 4.0.2,
is it possible?
Original issue reported on code.google.com by [email protected]
on 21 Feb 2013 at 1:55
Is anyone working on this? And i apologize for my pervious post. Also how do I
setup the drives. Is there a good tutorial around?
Original issue reported on code.google.com by [email protected]
on 4 Dec 2012 at 3:49
What steps will reproduce the problem?
1. I'm opening the bcmon app
2. I'm getting asket if I want to install the firmware and the Tools
3. I click on yes
4. I'm returning to the Android desktop (Superuser rights have been given)
What is the expected output? What do you see instead?
I'm returning back to Desktop
What version of the product are you using? On what operating system?
On Android 4.0.3
Please provide any additional information below.
Original issue reported on code.google.com by [email protected]
on 29 Aug 2013 at 7:13
What steps will reproduce the problem?
1. Compile driver for CM10 4.1.1 kernel
2. Copy driver and monitor-enabled firmware to sdcard
3. Execute setup.sh from console
What is the expected output? What do you see instead?
Driver should load when executing insmod.
Instead, insmod never ends execution.
lsmod output shows:
bcm4329 292751 1 - Loading 0x00000000
What version of the product are you using? On what operating system?
Android Cyanogen Mod 10 (4.1.1 kernel 3.0.43+)
Please provide any additional information below.
Original issue reported on code.google.com by [email protected]
on 8 Oct 2012 at 8:46
What steps will reproduce the problem?
1.apk wont install firmware just Fc's
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
Any help would be great,or if theres any way i can help you to help me i would
be more than happy to do it/any other files u need etc.
Original issue reported on code.google.com by [email protected]
on 20 Aug 2013 at 4:41
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Mostly stock gingerbread, rooted
Please provide any additional information below.
Firmware files are located in /system/etc/wifi and are:
bcm4329_aps.bin
bcm4329_mfg.bin
bcm4329_sta.bin
Original issue reported on code.google.com by [email protected]
on 17 Jul 2013 at 9:06
I'm using a HTC sensation with CyanogenMod 9 and it features the BCM4329
chipset.
I installed the bcmon.apk and it installed smoothly.
When I press "Enable Monitor Mode" it just hangs for a moment and then nothing
happens.
I noticed that my wifi get's turned off and it won't turn on again without a
reboot of the phone.
Original issue reported on code.google.com by [email protected]
on 7 Aug 2013 at 6:33
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
Original issue reported on code.google.com by [email protected]
on 16 Mar 2013 at 4:03
What steps will reproduce the problem?
1. I tried to find my Broadcom Processor but unable to find it
2. I also searched for It on Internet but not found
3.
What is the expected output? What do you see instead?
Hoping Monitor Mode For Karbonn A15 From You For me and for all Intrested Users
What version of the product are you using? On what operating system?
No Version OS: Android 4.0.4
Please provide any additional information below.
You will find about my handsets config here:
http://www.gsmarena.com/karbonn_a15-5196.php
Original issue reported on code.google.com by [email protected]
on 26 Jul 2013 at 12:38
The Galaxy Nexus uses the bcm4330 chipset. dhd.ko in bcm4330 can be built with
no issue for 3.0.31 kernel (used with Jelly Bean), however the kernel .config
has to be modified so the bcmdhd driver is built as a kernel module, not built
in to the kernel. Otherwise, you can't rmmod the driver. With that, the
dhd.ko module inserts, but has the following error. Note all DHD debug info is
turned on.
<4>[16382.549194] ## wifi_probe
<4>[16382.549285] wifi_set_power = 1
<4>[16383.280883] wifi_set_carddetect = 1
<6>[16383.422271] mmc1: new high speed SDIO card at address 0001
<4>[16383.424133] dhd_bus_register: Enter
<4>[16383.424835] dhd_module_init:
<4>[16383.424835] Dongle Host Driver, version 1.15.11
<4>[16383.424835] Compiled in drivers/net/wireless/bcmdhd-mon/src on Sep 25
2012 at 15:32:22
<4>[16383.426696] dhdsdio_probe : no mutex held. set lock
<4>[16383.426879] dhdsdio_probe: Enter
<4>[16383.426940] dhdsdio_probe: venid 0x14e4 devid 0x0000
<4>[16383.427124] dhdsdio_probe: allow device id 0, will check chip internals
<4>[16383.427368] F1 signature read @0x18000000=0x16444330
<4>[16383.427703] sdioh_cis_read: func_cis_ptr[0]=0x1070
<4>[16383.437286] Function 0 CIS:
<4>[16383.437377] 20 04 d0 02 30 43 21 02 0c 00 22 04 00 20 00 5a
<4>[16383.438842] ff
<4>[16383.439086] sdioh_cis_read: func_cis_ptr[1]=0x1000
<4>[16383.448638] Function 1 CIS:
<4>[16383.448791] 20 04 d0 02 30 43 21 02 0c 00 22 2a 01 00 00 00
<4>[16383.450256] 00 00 00 00 00 00 00 00 40 00 00 ff ff 80 00 00
<4>[16383.451690] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<4>[16383.453247] 00 00 00 00 00 00 ff
<4>[16383.454040] sdioh_cis_read: func_cis_ptr[2]=0x1038
<4>[16383.463562] Function 2 CIS:
<4>[16383.463653] 20 04 d0 02 30 43 21 02 0c 00 22 2a 01 01 00 00
<4>[16383.465118] 00 00 00 00 00 00 00 00 00 02 00 ff ff 80 00 00
<4>[16383.466522] 00 00 00 00 00 00 00 00 c8 00 00 00 00 00 00 00
<4>[16383.468078] 00 00 00 00 00 00 ff
<4>[16383.474121] DHD: dongle ram size is set to 294912(orig 294912)
<4>[16383.474639] dhd_attach: Enter
<4>[16383.474761] dhd_add_if: idx 0, handle->c68b7800
<3>[16383.476898] CFG80211-INFO2) wl_cfg80211_attach : wl_cfg80211_attach: wl =
0xc68b5320
<3>[16383.477233] CFG80211-INFO2) wl_create_event_handler : Enter
<3>[16383.477447] CFG80211-INFO2) wl_create_event_handler : wl = 0xc68b5320,
wl->event_tsk = 0xc68b5534
<4>[16383.477691] wl_create_event_handler thr:9f1 created
<3>[16383.477722] CFG80211-INFO2) wl_event_handler : tsk Enter, tsk = 0xc68b5534
<3>[16383.477752] CFG80211-INFO2) wl_event_handler : DAEMONIZE completed
<3>[16383.477752] CFG80211-INFO2) wl_event_handler : tsk completed
<4>[16383.478149] wl_create_event_handler thr:9f1 started
<4>[16383.479766] dhd_attach thr:9f2 created
<4>[16383.479858] dhd_attach thr:9f2 started
<4>[16383.479980] dhd_attach thr:9f3 created
<4>[16383.480133] dhd_attach thr:9f3 started
<4>[16383.480255] dhd_attach thr:9f4 created
<4>[16383.480346] dhd_attach thr:9f4 started
<4>[16383.480499] dhd_early_suspend: enter
<4>[16383.480621] dhd_set_suspend: enter, value = 1 in_suspend=1
<4>[16383.480773] dhdsdio_probe_malloc: Enter
<4>[16383.480865] dhdsdio_probe_init: Enter
<4>[16383.481048] dhdsdio_probe_init: Initial value for sd_divisor is 2
<4>[16383.481201] dhdsdio_probe_init: Initial value for sd_mode is 2
<4>[16383.481323] dhdsdio_probe_init: Initial value for sd_blocksize is 512
<4>[16383.481475] dhdsdio_probe_init: bus module (through bcmsdh API) does not
support chaining
<4>[16383.481628] dhdsdio_probe: disable SDIO interrupts (not interested yet)
<4>[16383.481719] dhdsdio_probe: registered SDIO interrupt function ok
<4>[16383.481872] dhdsdio_probe: completed!!
<4>[16383.481964] Enter dhd_bus_start:
<4>[16383.482055] dhdsdio_clkctl: Enter
<4>[16383.482208] dhdsdio_htclk: Enter
<4>[16383.482360] CLKCTL: turned ON
<4>[16383.482452] dhd_os_wd_timer: Enter
<4>[16383.482543] dhdsdio_clkctl: 1 -> 3
<4>[16383.483459] dhdsdio_membytes: write 4 bytes at offset 0x00007ffc in
window 0x00040000
<4>[16383.483673] dhdsdio_download_code_file: download firmware
/sdcard/bcm4330_sta.bcmon.bin
<4>[16383.484863] dhdsdio_membytes: write 2048 bytes at offset 0x00000000 in
window 0x00000000
<4>[16383.485931] dhdsdio_membytes: write 2048 bytes at offset 0x00000800 in
window 0x00000000
<4>[16383.487396] dhdsdio_membytes: write 2048 bytes at offset 0x00001000 in
window 0x00000000
<4>[16383.487823] dhdsdio_membytes: write 2048 bytes at offset 0x00001800 in
window 0x00000000
<4>[16383.488311] dhdsdio_membytes: write 2048 bytes at offset 0x00002000 in
window 0x00000000
<4>[16383.488800] dhdsdio_membytes: write 2048 bytes at offset 0x00002800 in
window 0x00000000
<4>[16383.489196] dhdsdio_membytes: write 2048 bytes at offset 0x00003000 in
window 0x00000000
<4>[16383.489685] dhdsdio_membytes: write 2048 bytes at offset 0x00003800 in
window 0x00000000
<4>[16383.491058] dhdsdio_membytes: write 2048 bytes at offset 0x00004000 in
window 0x00000000
<4>[16383.492095] dhdsdio_membytes: write 2048 bytes at offset 0x00004800 in
window 0x00000000
<4>[16383.492523] dhdsdio_membytes: write 2048 bytes at offset 0x00005000 in
window 0x00000000
<4>[16383.493011] dhdsdio_membytes: write 2048 bytes at offset 0x00005800 in
window 0x00000000
<4>[16383.493469] dhdsdio_membytes: write 2048 bytes at offset 0x00006000 in
window 0x00000000
<4>[16383.493957] dhdsdio_membytes: write 2048 bytes at offset 0x00006800 in
window 0x00000000
<4>[16383.494354] dhdsdio_membytes: write 2048 bytes at offset 0x00007000 in
window 0x00000000
<4>[16383.494842] dhdsdio_membytes: write 2048 bytes at offset 0x00007800 in
window 0x00000000
<4>[16383.495300] dhdsdio_membytes: write 2048 bytes at offset 0x00000000 in
window 0x00008000
<4>[16383.495727] dhdsdio_membytes: write 2048 bytes at offset 0x00000800 in
window 0x00008000
<4>[16383.496185] dhdsdio_membytes: write 2048 bytes at offset 0x00001000 in
window 0x00008000
<4>[16383.496673] dhdsdio_membytes: write 2048 bytes at offset 0x00001800 in
window 0x00008000
<4>[16383.497161] dhdsdio_membytes: write 2048 bytes at offset 0x00002000 in
window 0x00008000
<4>[16383.497558] dhdsdio_membytes: write 2048 bytes at offset 0x00002800 in
window 0x00008000
<4>[16383.498046] dhdsdio_membytes: write 2048 bytes at offset 0x00003000 in
window 0x00008000
<4>[16383.498504] dhdsdio_membytes: write 2048 bytes at offset 0x00003800 in
window 0x00008000
<4>[16383.499999] dhdsdio_membytes: write 2048 bytes at offset 0x00004000 in
window 0x00008000
<4>[16383.500518] dhdsdio_membytes: write 2048 bytes at offset 0x00004800 in
window 0x00008000
<4>[16383.501007] dhdsdio_membytes: write 2048 bytes at offset 0x00005000 in
window 0x00008000
<4>[16383.501495] dhdsdio_membytes: write 2048 bytes at offset 0x00005800 in
window 0x00008000
<4>[16383.501922] dhdsdio_membytes: write 2048 bytes at offset 0x00006000 in
window 0x00008000
<4>[16383.502380] dhdsdio_membytes: write 2048 bytes at offset 0x00006800 in
window 0x00008000
<4>[16383.502868] dhdsdio_membytes: write 2048 bytes at offset 0x00007000 in
window 0x00008000
<4>[16383.503295] dhdsdio_membytes: write 2048 bytes at offset 0x00007800 in
window 0x00008000
<4>[16383.503784] dhdsdio_membytes: write 2048 bytes at offset 0x00000000 in
window 0x00010000
<4>[16383.504241] dhdsdio_membytes: write 2048 bytes at offset 0x00000800 in
window 0x00010000
<4>[16383.504730] dhdsdio_membytes: write 2048 bytes at offset 0x00001000 in
window 0x00010000
<4>[16383.505126] dhdsdio_membytes: write 2048 bytes at offset 0x00001800 in
window 0x00010000
<4>[16383.505615] dhdsdio_membytes: write 2048 bytes at offset 0x00002000 in
window 0x00010000
<4>[16383.506103] dhdsdio_membytes: write 2048 bytes at offset 0x00002800 in
window 0x00010000
<4>[16383.506500] dhdsdio_membytes: write 2048 bytes at offset 0x00003000 in
window 0x00010000
<4>[16383.507019] dhdsdio_membytes: write 2048 bytes at offset 0x00003800 in
window 0x00010000
<4>[16383.507507] dhdsdio_membytes: write 2048 bytes at offset 0x00004000 in
window 0x00010000
<4>[16383.507995] dhdsdio_membytes: write 2048 bytes at offset 0x00004800 in
window 0x00010000
<4>[16383.508392] dhdsdio_membytes: write 2048 bytes at offset 0x00005000 in
window 0x00010000
<4>[16383.508850] dhdsdio_membytes: write 2048 bytes at offset 0x00005800 in
window 0x00010000
<4>[16383.509338] dhdsdio_membytes: write 2048 bytes at offset 0x00006000 in
window 0x00010000
<4>[16383.509826] dhdsdio_membytes: write 2048 bytes at offset 0x00006800 in
window 0x00010000
<4>[16383.510223] dhdsdio_membytes: write 2048 bytes at offset 0x00007000 in
window 0x00010000
<4>[16383.510711] dhdsdio_membytes: write 2048 bytes at offset 0x00007800 in
window 0x00010000
<4>[16383.511169] dhdsdio_membytes: write 2048 bytes at offset 0x00000000 in
window 0x00018000
<4>[16383.511596] dhdsdio_membytes: write 2048 bytes at offset 0x00000800 in
window 0x00018000
<4>[16383.512084] dhdsdio_membytes: write 2048 bytes at offset 0x00001000 in
window 0x00018000
<4>[16383.512542] dhdsdio_membytes: write 2048 bytes at offset 0x00001800 in
window 0x00018000
<4>[16383.513031] dhdsdio_membytes: write 2048 bytes at offset 0x00002000 in
window 0x00018000
<4>[16383.513427] dhdsdio_membytes: write 2048 bytes at offset 0x00002800 in
window 0x00018000
<4>[16383.513916] dhdsdio_membytes: write 2048 bytes at offset 0x00003000 in
window 0x00018000
<4>[16383.514434] dhdsdio_membytes: write 2048 bytes at offset 0x00003800 in
window 0x00018000
<4>[16383.514862] dhdsdio_membytes: write 2048 bytes at offset 0x00004000 in
window 0x00018000
<4>[16383.515319] dhdsdio_membytes: write 2048 bytes at offset 0x00004800 in
window 0x00018000
<4>[16383.515808] dhdsdio_membytes: write 2048 bytes at offset 0x00005000 in
window 0x00018000
<4>[16383.516265] dhdsdio_membytes: write 2048 bytes at offset 0x00005800 in
window 0x00018000
<4>[16383.516693] dhdsdio_membytes: write 2048 bytes at offset 0x00006000 in
window 0x00018000
<4>[16383.517150] dhdsdio_membytes: write 2048 bytes at offset 0x00006800 in
window 0x00018000
<4>[16383.517639] dhdsdio_membytes: write 2048 bytes at offset 0x00007000 in
window 0x00018000
<4>[16383.518066] dhdsdio_membytes: write 2048 bytes at offset 0x00007800 in
window 0x00018000
<4>[16383.518524] dhdsdio_membytes: write 2048 bytes at offset 0x00000000 in
window 0x00020000
<4>[16383.518981] dhdsdio_membytes: write 2048 bytes at offset 0x00000800 in
window 0x00020000
<4>[16383.519470] dhdsdio_membytes: write 2048 bytes at offset 0x00001000 in
window 0x00020000
<4>[16383.519897] dhdsdio_membytes: write 2048 bytes at offset 0x00001800 in
window 0x00020000
<4>[16383.520355] dhdsdio_membytes: write 2048 bytes at offset 0x00002000 in
window 0x00020000
<4>[16383.520843] dhdsdio_membytes: write 2048 bytes at offset 0x00002800 in
window 0x00020000
<4>[16383.521240] dhdsdio_membytes: write 2048 bytes at offset 0x00003000 in
window 0x00020000
<4>[16383.521728] dhdsdio_membytes: write 2048 bytes at offset 0x00003800 in
window 0x00020000
<4>[16383.522216] dhdsdio_membytes: write 2048 bytes at offset 0x00004000 in
window 0x00020000
<4>[16383.522705] dhdsdio_membytes: write 2048 bytes at offset 0x00004800 in
window 0x00020000
<4>[16383.523132] dhdsdio_membytes: write 2048 bytes at offset 0x00005000 in
window 0x00020000
<4>[16383.523590] dhdsdio_membytes: write 2048 bytes at offset 0x00005800 in
window 0x00020000
<4>[16383.524078] dhdsdio_membytes: write 2048 bytes at offset 0x00006000 in
window 0x00020000
<4>[16383.524536] dhdsdio_membytes: write 2048 bytes at offset 0x00006800 in
window 0x00020000
<4>[16383.524963] dhdsdio_membytes: write 2048 bytes at offset 0x00007000 in
window 0x00020000
<4>[16383.525421] dhdsdio_membytes: write 2048 bytes at offset 0x00007800 in
window 0x00020000
<4>[16383.525909] dhdsdio_membytes: write 2048 bytes at offset 0x00000000 in
window 0x00028000
<4>[16383.526306] dhdsdio_membytes: write 2048 bytes at offset 0x00000800 in
window 0x00028000
<4>[16383.526794] dhdsdio_membytes: write 2048 bytes at offset 0x00001000 in
window 0x00028000
<4>[16383.527282] dhdsdio_membytes: write 2048 bytes at offset 0x00001800 in
window 0x00028000
<4>[16383.527740] dhdsdio_membytes: write 2048 bytes at offset 0x00002000 in
window 0x00028000
<4>[16383.528167] dhdsdio_membytes: write 2048 bytes at offset 0x00002800 in
window 0x00028000
<4>[16383.528625] dhdsdio_membytes: write 2048 bytes at offset 0x00003000 in
window 0x00028000
<4>[16383.529113] dhdsdio_membytes: write 2048 bytes at offset 0x00003800 in
window 0x00028000
<4>[16383.529510] dhdsdio_membytes: write 2048 bytes at offset 0x00004000 in
window 0x00028000
<4>[16383.529998] dhdsdio_membytes: write 2048 bytes at offset 0x00004800 in
window 0x00028000
<4>[16383.530517] dhdsdio_membytes: write 2048 bytes at offset 0x00005000 in
window 0x00028000
<4>[16383.530975] dhdsdio_membytes: write 2048 bytes at offset 0x00005800 in
window 0x00028000
<4>[16383.531402] dhdsdio_membytes: write 2048 bytes at offset 0x00006000 in
window 0x00028000
<4>[16383.531860] dhdsdio_membytes: write 2048 bytes at offset 0x00006800 in
window 0x00028000
<4>[16383.532348] dhdsdio_membytes: write 2048 bytes at offset 0x00007000 in
window 0x00028000
<4>[16383.532745] dhdsdio_membytes: write 2048 bytes at offset 0x00007800 in
window 0x00028000
<4>[16383.533386] dhdsdio_membytes: write 425 bytes at offset 0x00000000 in
window 0x00030000
<4>[16383.533996] dhdsdio_downloadvars: Enter
<4>[16383.534301] dhdsdio_membytes: write 1208 bytes at offset 0x00007b44 in
window 0x00040000
<4>[16383.534637] Compare NVRAM dl & ul; varsize=1208
<4>[16383.534820] dhdsdio_membytes: read 1208 bytes at offset 0x00007b44 in
window 0x00040000
<4>[16383.535217] dhdsdio_write_vars: Download, Upload and compare of NVRAM
succeeded.
<4>[16383.535369] Physical memory size: 294912, usable memory size: 294912
<4>[16383.535461] Vars are at 293700, orig varsize is 1208
<4>[16383.535614] New varsize is 1208, length token=0xfed1012e
<4>[16383.535766] dhdsdio_membytes: write 4 bytes at offset 0x00007ffc in
window 0x00040000
<4>[16383.536529] dhdsdio_clkctl: Enter
<4>[16383.536621] dhdsdio_htclk: Enter
<4>[16383.536743] CLKCTL: turned OFF
<4>[16383.536895] dhd_os_wd_timer: Enter
<4>[16383.536987] dhdsdio_clkctl: 3 -> 1
<4>[16383.537078] dhd_os_wd_timer: Enter
<4>[16383.537231] dhd_bus_init: Enter
<4>[16383.537322] dhdsdio_clkctl: Enter
<4>[16383.537384] dhdsdio_htclk: Enter
<4>[16384.312164] dhdsdio_htclk: HT Avail timeout (1000000): clkctl 0x50
<4>[16384.312499] dhdsdio_clkctl: 1 -> 1
<4>[16384.312683] dhd_bus_init: clock state is wrong. state = 1
<4>[16384.313049] dhdsdio_clkctl: Enter
<4>[16384.313232] dhdsdio_htclk: Enter
<4>[16385.100494] dhdsdio_htclk: HT Avail timeout (1000000): clkctl 0x50
<4>[16385.100830] dhdsdio_clkctl: 1 -> 1
<4>[16385.101226] dhdsdio_clkctl: Enter
<4>[16385.101440] dhd_bus_start failed bus is not ready
<4>[16385.101776] dhd_watchdog_thread:
<4>[16385.101959] dhd_bus_watchdog: Enter
<4>[16385.102172] dhdsdio_probe: dhd_bus_start failed
<4>[16385.102478] dhd_net_attach: ifidx 0
<4>[16385.112548] dhd_get_stats: Enter
<4>[16385.112823] Broadcom Dongle Host Driver: register interface
[wlan0]dhdsdio_probe : the lock is released.
As can be seen from the log, there is an issue turning the SDIO "backplane"
clock (htclk) back on after the firmware loads. However, if you try to load
the original firmware instead of bcm4330_sta.bcmon.bin with the bcmon version
of dhd.ko, the driver works fine, albeit with no monitor mode. I also tried
increasing the "HT Avail" timeout to 10 seconds instead of 1 second with the
same result.
Could it be an incompatibility issue with the firmware? Would it be possible
to post the firmware soure and build instructions as well?
Original issue reported on code.google.com by [email protected]
on 27 Sep 2012 at 1:43
What steps will reproduce the problem?
1. Copy your sources to drivers/net/wireless/bcm4329/
2. Enable BCM4329 [=m] in menuconfig
3. Try to build using make
What is the expected output?
CC [M] drivers/net/wireless/bcm4329/bcmsdh_linux.o
What do you see instead?
CC [M] drivers/net/wireless/bcm4329/bcmsdh_linux.o
drivers/net/wireless/bcm4329/bcmsdh_linux.c: In function
'bcmsdh_register_oob_intr':
drivers/net/wireless/bcm4329/bcmsdh_linux.c:639:3: error: implicit declaration
of function 'set_irq_wake' [-Werror=implicit-function-declaration]
cc1: all warnings being treated as errors
What version of the product are you using? On what operating system?
Svn trunk at revision 11, kernel Linux/arm 3.0.48-ck1, toolchain
linaro-android_toolchain-4.7-2012.07
Please provide any additional information below.
Looking at original bcm4329_248/bcmsdh_linux.c file I found that we need to add
only one line to fix this warning. Patch attached.
Original issue reported on code.google.com by [email protected]
on 28 Oct 2012 at 12:31
Attachments:
1. Copy your sources to drivers/net/wireless/bcm4329/
2. Enable BCM4329 [=m] in menuconfig
3. Try to build using make
What is the expected output?
CC [M] drivers/net/wireless/bcm4329/wl_iw.o
What do you see instead?
CC [M] drivers/net/wireless/bcm4329/wl_iw.o
drivers/net/wireless/bcm4329/wl_iw.c: In function 'wl_iw_set_pmksa':
drivers/net/wireless/bcm4329/wl_iw.c:5162:5: error: array subscript is above
array bounds [-Werror=array-bounds]
drivers/net/wireless/bcm4329/wl_iw.c:5165:5: error: array subscript is above
array bounds [-Werror=array-bounds]
cc1: all warnings being treated as errors
What version of the product are you using? On what operating system?
Svn trunk at revision 11, kernel Linux/arm 3.0.48-ck1, toolchain
linaro-android_toolchain-4.7-2012.07
Original issue reported on code.google.com by [email protected]
on 28 Oct 2012 at 12:48
Radiotap support wold be great.
If Reaver could be used with bcm4329 smart phone, 80% of networks could be
cracked in meter of minutes.
In att PCAP file of Reaver with current driver.
Original issue reported on code.google.com by [email protected]
on 23 Jun 2013 at 8:51
Attachments:
What steps will reproduce the problem?
Trying to compile the module
What is the expected output? What do you see instead?
CC [M] drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.o
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:801: error:
'NUM_NL80211_IFTYPES' undeclared here (not in a function)
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:802: error: array index in
non-array initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:802: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:803: error: field name not
in record or union initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:803: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:804: error: field name not
in record or union initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:804: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:806: error: array index in
non-array initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:806: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:807: error: field name not
in record or union initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:807: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:808: error: field name not
in record or union initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:808: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:811: error: array index in
non-array initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:811: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:812: error: field name not
in record or union initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:812: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:813: error: field name not
in record or union initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:813: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:821: error: array index in
non-array initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:821: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:823: error: field name not
in record or union initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:823: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:824: error: field name not
in record or union initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:824: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:832: error:
'NL80211_IFTYPE_P2P_CLIENT' undeclared here (not in a function)
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:832: error: array index in
initializer not of integer type
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:832: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:833: error: field name not
in record or union initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:833: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:834: error: field name not
in record or union initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:834: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:837: error:
'NL80211_IFTYPE_P2P_GO' undeclared here (not in a function)
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:837: error: array index in
initializer not of integer type
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:837: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:838: error: field name not
in record or union initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:838: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:839: error: field name not
in record or union initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:839: error: (near
initialization for 'wl_cfg80211_default_mgmt_stypes')
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c: In function
'wl_cfg80211_mgmt_tx':
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:4371: error: implicit
declaration of function 'cfg80211_mgmt_tx_status'
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c: In function
'wl_cfg80211_change_bss':
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:4692: error: 'struct
bss_parameters' has no member named 'ht_opmode'
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c: At top level:
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5383: warning:
initialization from incompatible pointer type
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5393: warning:
initialization from incompatible pointer type
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5394: warning:
initialization from incompatible pointer type
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5395: warning:
initialization from incompatible pointer type
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5396: warning:
initialization from incompatible pointer type
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5408: error: unknown field
'mgmt_tx' specified in initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5408: warning:
initialization from incompatible pointer type
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5409: error: unknown field
'mgmt_frame_register' specified in initializer
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5409: warning:
initialization from incompatible pointer type
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c: In function
'wl_setup_wiphy':
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5458: error: 'struct
wiphy' has no member named 'max_remain_on_channel_duration'
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5459: error: 'struct
wiphy' has no member named 'mgmt_stypes'
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5468: error:
'WIPHY_FLAG_SUPPORTS_SEPARATE_DEFAULT_KEYS' undeclared (first use in this
function)
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5468: error: (Each
undeclared identifier is reported only once
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5468: error: for each
function it appears in.)
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c: In function
'wl_inform_single_bss':
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5597: error: too many
arguments to function 'ieee80211_channel_to_frequency'
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c: In function
'wl_notify_connect_status_ap':
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5796: error: too many
arguments to function 'ieee80211_channel_to_frequency'
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:5806: error: implicit
declaration of function 'cfg80211_rx_mgmt'
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c: In function
'wl_notify_rx_mgmt_frame':
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:6475: error: too many
arguments to function 'ieee80211_channel_to_frequency'
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c: In function
'wl_construct_reginfo':
drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.c:8104: error: too many
arguments to function 'ieee80211_channel_to_frequency'
make[4]: *** [drivers/net/wireless/bcmdhd/src/wl/sys/wl_cfg80211.o] Error 1
make[3]: *** [drivers/net/wireless/bcmdhd] Error 2
make[2]: *** [drivers/net/wireless] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
What version of the product are you using? On what operating system?
android
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 36
EXTRAVERSION = .3-I927RUXKJ5-CL652095
kernel config
CONFIG_BCM4330=m
CONFIG_BROADCOM_WIFI_RESERVED_MEM=y
CONFIG_WLAN_COUNTRY_CODE=m
CONFIG_WLAN_REGION_CODE=100
toolchain =
android-ndk-r5/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi-
Please provide any additional information below.
Contact for any extra information needed.
Original issue reported on code.google.com by [email protected]
on 20 Sep 2012 at 1:33
What steps will reproduce the problem?
1. Attempt to 'make modules' to build bcmon bcm4329.ko against current CM10
android_samsung_aries kernel
What is the expected output? What do you see instead?
CC [M] drivers/net/wireless/bcm4329/bcmon.o
CC [M] drivers/net/wireless/bcm4329/dhd_linux.o
CC [M] drivers/net/wireless/bcm4329/linux_osl.o
CC [M] drivers/net/wireless/bcm4329/bcmutils.o
CC [M] drivers/net/wireless/bcm4329/dhd_common.o
CC [M] drivers/net/wireless/bcm4329/dhd_custom_gpio.o
CC [M] drivers/net/wireless/bcm4329/wl_iw.o
CC [M] drivers/net/wireless/bcm4329/siutils.o
CC [M] drivers/net/wireless/bcm4329/sbutils.o
CC [M] drivers/net/wireless/bcm4329/aiutils.o
CC [M] drivers/net/wireless/bcm4329/hndpmu.o
CC [M] drivers/net/wireless/bcm4329/bcmwifi.o
CC [M] drivers/net/wireless/bcm4329/dhd_sdio.o
CC [M] drivers/net/wireless/bcm4329/dhd_linux_sched.o
CC [M] drivers/net/wireless/bcm4329/dhd_cdc.o
CC [M] drivers/net/wireless/bcm4329/bcmsdh_sdmmc.o
CC [M] drivers/net/wireless/bcm4329/bcmsdh.o
CC [M] drivers/net/wireless/bcm4329/bcmsdh_linux.o
drivers/net/wireless/bcm4329/bcmsdh_linux.c: In function
'bcmsdh_register_oob_intr':
drivers/net/wireless/bcm4329/bcmsdh_linux.c:639: error: implicit declaration of
function 'set_irq_wake'
make[4]: *** [drivers/net/wireless/bcm4329/bcmsdh_linux.o] Error 1
make[3]: *** [drivers/net/wireless/bcm4329] Error 2
make[2]: *** [drivers/net/wireless] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
What version of the product are you using? On what operating system?
Please provide any additional information below.
I am inexperienced at building kernel modules, not sure where I could grab the
necessary headers from
Original issue reported on code.google.com by [email protected]
on 21 Sep 2012 at 5:15
How I can know my chipset on android ?
I have CT1010 tablet
Original issue reported on code.google.com by [email protected]
on 4 Jan 2013 at 12:41
Will this work for samsung galaxy note 2? And is there a beta I can test?
Original issue reported on code.google.com by [email protected]
on 4 Dec 2012 at 1:30
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.